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
File "/usr/share/virt-manager/virtinst/guest.py", line 465, in start_install
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:
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
I just upgraded to F29 from F28 yesterday.
The current kernel that I am running according to uname -r is:
However when I run "dnf upgrade" today I get the following dependencies
to be installed:
kernel-core x86_64 4.19.13-
300.fc29 updates 25 M
kernel-devel x86_64 4.19.13-
300.fc29 updates 13 M
kernel-modules x86_64 4.19.13-
300.fc29 updates 28 M
kernel-modules-extra x86_64 4.19.13-
300.fc29 updates 2.2 M
kernel 4.19.13-300.fc29 appears to be a downgrade from the kernel that
I am currently booting into. Is this right? And If not any
I just installed Fedora29 on my brand new HP laptop. The installation
went fine, and Fedora comes up fine. However, I was trying to install
it as a dual boot machine, and the Windows option does not come up
either with a "normal" grub bootup or when I choose boot options in
THe box has hybrid drive -- 256G SSD and 1 TB regular. I'm installing
everything on the SSD right now, and then will link out stuff or
repartition just a bit to move things to the 1 TB drive. But I thought
I'd just stick to the SSD for installation to minimize hassles.
I didn't delete or overwrite the EFI partition, and /boot/efi has what
appears to be old HP, Microsoft, and Boot directories in addition to
the new fedora directory.
The only thing that was unusual in this installation was that I got the
warning that because I was using GPT, I had to create a 1 MB
bootsomethingsomething partition -- which I did.
So, now my drive looks like:
partition name fs mount sz flags
/dev/nvme0n1p1 EFI fat32 /boot/efi 260 MB boot,esp
/dev/nvme0n1p2 MS reserved unknown 16 MB msftres
/dev/nvme0n1p3 basic data ntfs 60 GB msftdata
/dev/nvme0n1p5 grub2.core.img 2 MB bios_grub
/dev/nvme0n1p6 lvm2 pv fedora 55.89 GB lvm
/dev/nvme0n1p4 basic data ntfs 980 MB hidden,diag
There's about 121 unallocated GB on the SSD, and the 1 TB drive isn't
Eventually, this will be a triple boot system, with the other OS being
qubesOS. However, I need a vanilla Fedora boot option because qubesOS
won't support some graphics I need for some apps. But, I usually
install the Qubes stuff last, since it's such a joy.
So, I have two questions:
1) WHat is this 1 M bootsomethingsomething I had to make? It looks
like it turned into something called bios_grub. I've never had to do
2) Can someone point me to resources to learn how to troubleshoot
making grub see my Windows stuff? Or give me any ideas?
I just bought a brand new little HP laptop and decided to try to
install Fedora 29. I created the bootable flash drive in Windows using
Rufus. When I try to boot from the flash drive, I get the following
[ 8.520307] dracut: FATAL: Failed to mount block device of live image:
Missing NTFS support
[ 8.530427] dracut: Reufusing to continue
[ 9.112611] reboot: System halted
Any help would be appreciated!