Virtual machines not working anymore on 2.10
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Invalid
|
Undecided
|
Unassigned |
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-
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-
-drive if=pflash,
-drive if=pflash,
-enable-kvm
-machine q35,accel=
-cpu host,kvm=
-smp 4,cores=
-m 4096
-display gtk
-vga qxl
-rtc base=localtime
-serial none
-parallel none
-usb
-device usb-host,
-device usb-host,
-device usb-host,
-device usb-host,
-device virtio-
-drive file=/path/
-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-
-drive if=pflash,
-drive if=pflash,
-enable-kvm
-machine q35,accel=
-cpu host,kvm=
-smp 4,cores=
-m 10240
-vga none
-rtc base=localtime
-serial none
-parallel none
-usb
-device vfio-pci,
-device vfio-pci,
-device usb-host,
-device usb-host,
-device usb-host,
-device usb-host,
-device usb-host,
-device usb-host,
-device virtio-
-drive file=/path/
-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.
Changed in qemu: | |
status: | New → Invalid |
Please try: -machine pc-q35- 2.9,accel= kvm,mem- merge=off
I'm not sure if it will make a difference in this case but it presents exactly the same onboard hardware as QEMU 2.9. The onboard hardware configuration may change unless you specify a precise version in the machine type, so I suggest using it instead of "q35".
Did you build QEMU 2.9 from source with the same ./configure options?