qemu 4.1.0 - Corrupt guest filesystem after new vm install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QEMU |
Expired
|
Undecided
|
Unassigned |
Bug Description
When I install a new vm with qemu 4.1.0 all the guest filesystems are corrupt. The first boot from the install dvd iso is ok and the installer work fine. But the guest system hangs after the installer finishes and I reboot the guest. I can see the grub boot menue but the system cannot load the initramfs.
Testet with:
- RedHat Enterprise Linux 7.5, 7.6 and 7.7 (RedHat uses xfs for the /boot and / partition)
Guided install with the graphical installer, no lvm selected.
- Debian Stable/Buster (Debian uses ext4 for / and /home partition)
Guidet install with the graphical installer and default options.
Used commandline to create the vm disk image:
qemu-img create -f qcow2 /volumes/
Used qemu commandline for vm installation:
#!/bin/sh
# vmtest10 Installation
#
/usr/bin/
-soundhw hda \
-M q35 \
-k de \
-vga qxl \
-machine accel=kvm \
-m 4096 \
-display gtk \
-drive file=/volumes/
-drive file=/volumes/
-boot once=d,menu=off \
-device virtio-
-netdev bridge,
-rtc base=localtime \
-name "vmtest10" \
-usb -device usb-tablet \
-spice disable-ticketing \
-device virtio-serial-pci \
-device virtserialport,
-chardev spicevmc,
Host OS:
Archlinux (last updated at 10.10.2019)
Linux testing 5.3.5-arch1-1-ARCH #1 SMP PREEMPT Mon Oct 7 19:03:08 UTC 2019 x86_64 GNU/Linux
No libvirt in use.
With qemu 4.0.0 it works fine without any errors.
Hi Claus,
Some things to try:
a) after you quit qemu can you try qemu-img check on the qcow2 file to see if it's happy?
b) If you repeat your test using a raw image file rather than a qcow2 is it any happier?
c) How repeatable is it? If it's very repeatable it would be great if you could perform a git bisect to find which commit breaks it; we can walk you through it if you've not done it before.