qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] [Bug 1714331] [NEW] Virtual machines not working anymore on 2.10
@ 2017-08-31 19:14 Mary Sherman
  2017-09-01 11:03 ` [Qemu-devel] [Bug 1714331] " Stefan Hajnoczi
                   ` (11 more replies)
  0 siblings, 12 replies; 15+ messages in thread
From: Mary Sherman @ 2017-08-31 19:14 UTC (permalink / raw)
  To: qemu-devel

Public bug reported:

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.

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
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

^ permalink raw reply	[flat|nested] 15+ messages in thread
end of thread, other threads:[~2019-10-01 21:46 UTC | newest]

Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-31 19:14 [Qemu-devel] [Bug 1714331] [NEW] Virtual machines not working anymore on 2.10 Mary Sherman
2017-09-01 11:03 ` [Qemu-devel] [Bug 1714331] " Stefan Hajnoczi
2017-09-01 11:26 ` Mary Sherman
2017-09-03 18:49 ` Chris Unsworth
2017-09-05 10:14 ` Stefan Hajnoczi
2017-09-05 10:31 ` Mary Sherman
2017-09-05 18:42 ` Chris Unsworth
2017-09-06 14:34   ` Stefan Hajnoczi
2017-09-07  9:23     ` Phil Dennis-Jordan
2017-09-07  9:37 ` Mary Sherman
2017-09-07 11:42 ` Chris Unsworth
2017-09-07 12:38 ` Mary Sherman
2017-10-23 18:57 ` Laszlo Ersek (Red Hat)
2017-10-23 21:02 ` Mary Sherman
2019-10-01 21:25 ` Saverio Miroddi

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).