I currently run a couple of VMs (one Windows 10 and one Fedora Server)
under QEMU/KVM. I wanted to create a new one and got this:
Unable to complete install: 'internal error: process exited while connecting to
monitor: 2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global
IvyBridge-IBRS-x86_64-cpu.osxsave=on: Property '.osxsave' not found'
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 75, in
cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/create.py", line 2559, in
_do_async_install
guest.start_install(meter=meter)
File "/usr/share/virt-manager/virtinst/guest.py", line 465, in
start_install
doboot, transient)
File "/usr/share/virt-manager/virtinst/guest.py", line 401, in
_create_guest
domain = self.conn.createXML(install_xml or final_xml, 0)
File "/usr/lib64/python3.7/site-packages/libvirt.py", line 3718, in
createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed',
conn=self)
libvirt.libvirtError: internal error: process exited while connecting to monitor:
2018-12-31T14:23:14.816147Z qemu-system-x86_64: can't apply global
IvyBridge-IBRS-x86_64-cpu.osxsave=on: Property '.osxsave' not found
The last line is the key. This is similar to a bug I had a while back and reported at the
time:
https://bugzilla.redhat.com/show_bug.cgi?id=1644848
When it happened before I edited the XML file to remove the .osxsave
flag and that solved the problem. However now it's happening with a
fresh VM so there's no XML file to edit. Note that the new VM is a
small Windows test install with no special configuration, i.e.
everything just uses the default settings.
I've posted about this on the VFIO list but haven't received a solution
so far. See
https://www.redhat.com/archives/vfio-users/2018-December/msg00026.html
poc