[Qemu-devel] [Bug 1714331] Re: Virtual machines not working anymore on 2.10

[Chris Unsworth]

I was using a version of OVMF from about a year ago which works fine
with QEMU 2.8 and 2.9 but doesn't work with 2.10.  I just updated to the
latest OVMF from master and everything's working now with QEMU 2.10 and
WIndows 10 64 bit, so the old OVMF was the issue.

Thanks for your help,
Chris

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1714331

Title:
  Virtual machines not working anymore on 2.10

Status in QEMU:
  New

Bug description:
  Using 2.10, my virtual machine(s) don't work anymore. This happens
  100% of the times.

  -----

  I use QEMU compiling it from source, on Ubuntu 16.04 amd64. This is
  the configure command:

      configure --target-list=x86_64-softmmu --enable-debug --enable-gtk
  --enable-spice --audio-drv-list=pa

  I have one virtual disk, with a Windows 10 64-bit, which I launch in
  two different ways; both work perfectly on 2.9 (and used to do on 2.8,
  but I haven't used it for a long time).

  This is the first way:

      qemu-system-x86_64
        -drive if=pflash,format=raw,readonly,file=/path/to/OVMF_CODE.fd
        -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd.tmp
        -enable-kvm
        -machine q35,accel=kvm,mem-merge=off
        -cpu 
host,kvm=off,hv_vendor_id=vgaptrocks,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time
        -smp 4,cores=4,sockets=1,threads=1
        -m 4096
        -display gtk
        -vga qxl
        -rtc base=localtime
        -serial none
        -parallel none
        -usb
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device virtio-scsi-pci,id=scsi
        -drive 
file=/path/to/image-diff.img,id=hdd1,format=qcow2,if=none,cache=writeback
        -device scsi-hd,drive=hdd1
        -net nic,model=virtio
        -net user

  On QEMU 2.10, I get the `Recovery - Your PC/Device needs to be
  repaired` windows screen; on 2.9, it boots regularly.

  This is the second way:

      qemu-system-x86_64
        -drive if=pflash,format=raw,readonly,file=/path/to/OVMF_CODE.fd
        -drive if=pflash,format=raw,file=/tmp/OVMF_VARS.fd.tmp
        -enable-kvm
        -machine q35,accel=kvm,mem-merge=off
        -cpu 
host,kvm=off,hv_vendor_id=vgaptrocks,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time
        -smp 4,cores=4,sockets=1,threads=1
        -m 10240
        -vga none
        -rtc base=localtime
        -serial none
        -parallel none
        -usb
        -device vfio-pci,host=01:00.0,multifunction=on
        -device vfio-pci,host=01:00.1
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device usb-host,vendorid=0xNNNN,productid=0xNNNN
        -device virtio-scsi-pci,id=scsi
        -drive 
file=/path/to/image-diff.img,id=hdd1,format=qcow2,if=none,cache=writeback
        -device scsi-hd,drive=hdd1
        -net nic,model=virtio
        -net user

  On QEMU 2.10, I get the debug window on the linux monitor, and blank screen 
on VFIO one (no BIOS screen at all); after 10/20 seconds, QEMU crashes without 
any message.
  On 2.9, this works perfectly.

  -----

  I am able to perform a git bisect, if that helps, but if this is the
  case, I'd need this issue to be reviewed, since bisecting is going to
  take me a lot of time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1714331/+subscriptions