Description of problem: Since having upgraded Fedora 24 to 25 I'm not able to run (and configure) any new virtual machine. In all logs I get the error in the Summary Version-Release number of selected component (if applicable): kernel-4.8.15-300.fc25.x86_64 qemu-kvm-2.7.0-8.fc25.x86_64 How reproducible: I have one machine running based on RHEL6 but I'm not able to install any VM (tried with virt-manager and virt-install) Steps to Reproduce: 1. Upgrade to F25 2. Try to run or install a VM Actual results: The VM gets paused and the logs show the error in Summary Expected results: The VM should run normally Additional info: I have another F25 notebook where I can run any VM without problems.
Some additional info: - full logs: 2016-12-26 17:19:33.816+0000: starting up libvirt version: 2.2.0, package: 2.fc25 (Fedora Project, 2016-11-14-21:04:29, buildvm-25.phx2.fedoraproject.org), qemu version: 2.7.0(qemu-2.7.0-8.fc25), hostname: plambri-fedora.usersys.redhat.com LC_ALL=C PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name guest=rhel7-test1,debug-threads=on -S -object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-3-rhel7-test1/master-key.aes -machine pc-i440fx-2.7,accel=kvm,usb=off,vmport=off -cpu Nehalem -m 1024 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 8e782cd1-e6dc-4595-8378-bdd51d320b27 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-3-rhel7-test1/monitor.sock,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-reboot -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot strict=on -device ich9-usb-ehci1,id=usb,bus=pci.0,addr=0x6.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x6 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x6.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x6.0x2 -device lsi,id=scsi0,bus=pci.0,addr=0x5 -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x7 -drive file=/dev/mapper/bigdata-rhel7--test1,format=raw,if=none,id=drive-scsi0-0-0,cache=none,aio=native -device scsi-hd,bus=scsi0.0,scsi-id=0,drive=drive-scsi0-0-0,id=scsi0-0-0,bootindex=2 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=30 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5e:4f:7a,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-3-rhel7-test1/org.qemu.guest_agent.0,server,nowait -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -chardev spicevmc,id=charchannel1,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel1,id=channel1,name=com.redhat.spice.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -spice port=5901,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device intel-hda,id=sound0,bus=pci.0,addr=0x4 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -chardev spicevmc,id=charredir0,name=usbredir -device usb-redir,chardev=charredir0,id=redir0,bus=usb.0,port=2 -chardev spicevmc,id=charredir1,name=usbredir -device usb-redir,chardev=charredir1,id=redir1,bus=usb.0,port=3 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on char device redirected to /dev/pts/2 (label charserial0) KVM internal error. Suberror: 1 emulation failure EAX=c01a8cc0 EBX=000000a0 ECX=00002e50 EDX=0009eed8 ESI=3ffa4890 EDI=3fef4000 EBP=ffffffff ESP=00007b92 EIP=000006ab EFL=00000087 [--S--PC] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES =0000 00000000 ffffffff 00c09300 CS =9c48 0009c480 ffffffff 00809b00 SS =0000 00000000 ffffffff 00809300 DS =9ccc 0009ccc0 ffffffff 00c09300 FS =0000 00000000 ffffffff 00c09300 GS =0000 00000000 ffffffff 00c09300 LDT=0000 00000000 0000ffff 00008200 TR =0000 00000000 0000ffff 00008b00 GDT= 00000000 00000000 IDT= 00000000 000003ff CR0=00000010 CR2=00000000 CR3=00000000 CR4=00000000 DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 DR6=00000000ffff0ff0 DR7=0000000000000400 EFER=0000000000000000 Code=00 16 66 9c 66 60 0f a8 0f a0 06 1e 16 0e fa 2e 8e 1e 90 06 <0f> ae 06 00 1d 0f 01 0e f6 1c 0f 01 06 f0 1c fc 66 b9 38 00 00 00 66 ba 10 02 00 00 66 68 - on this hypervisor (HP Z400) I use almost exclusively Logical Volumes for the VMs disks
There's a RHEL bug tracking this issue, it's due to ipxe. A comment from that bug: (In reply to Laszlo Ersek from comment #14) > Some more reports on ipxe-devel: > > http://lists.ipxe.org/pipermail/ipxe-devel/2016-October/005203.html > http://lists.ipxe.org/pipermail/ipxe-devel/2016-October/005210.html > > Radim just posted the KVM feature patches: > > [PATCH 0/2] KVM: x86: emulate fxsave and fxrstor > https://www.spinics.net/lists/kernel/msg2370327.html > > I thought suppressing the regression within iPXE proper could be helpful in > the interim: > > [ipxe-devel] > [PATCH 0/2] mask lack of KVM's FXSAVE/FXRSTOR emulation in the QEMU build > http://lists.ipxe.org/pipermail/ipxe-devel/2016-October/005221.html Seems rawhide ipxe version ipxe-roms-qemu-20161108-1.gitb991c67.fc26.noarch fixes this issue, so we can use this bug to track pulling that version into f25
ipxe-20161108-1.gitb991c67.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-01d88d3c06
ipxe-20161108-1.gitb991c67.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-01d88d3c06
ipxe-20161108-1.gitb991c67.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.