[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm ins
From: |
psyhomb |
Subject: |
[Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install |
Date: |
Wed, 16 Oct 2019 15:41:40 -0000 |
I can confirm exactly the same issue on Arch linux with ext4 filesystem
(qemu-4.1.0).
After downgrading from 4.1.0 => 4.0.0 everything is running normal
again, no corruption detected and all qcow2 images stays healthy.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1847793
Title:
qemu 4.1.0 - Corrupt guest filesystem after new vm install
Status in QEMU:
New
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/disk2-part2/vmdisks/vmtest10-1.qcow2 20G
Used qemu commandline for vm installation:
#!/bin/sh
# vmtest10 Installation
#
/usr/bin/qemu-system-x86_64 -cpu SandyBridge-IBRS \
-soundhw hda \
-M q35 \
-k de \
-vga qxl \
-machine accel=kvm \
-m 4096 \
-display gtk \
-drive
file=/volumes/disk2-part2/images/debian-10.0.0-amd64-DVD-1.iso,if=ide,media=cdrom
\
-drive
file=/volumes/disk2-part2/images/vmtest10-1.qcow2,if=virtio,media=disk,cache=writeback
\
-boot once=d,menu=off \
-device virtio-net-pci,mac=52:54:00:2c:02:6c,netdev=vlan0 \
-netdev bridge,br=br0,id=vlan0 \
-rtc base=localtime \
-name "vmtest10" \
-usb -device usb-tablet \
-spice disable-ticketing \
-device virtio-serial-pci \
-device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 \
-chardev spicevmc,id=spicechannel0,name=vdagent $*
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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1847793/+subscriptions
- [Bug 1847793] [NEW] qemu 4.1.0 - Corrupt guest filesystem after new vm install, Claus Paetow, 2019/10/11
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Dr. David Alan Gilbert, 2019/10/14
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Claus Paetow, 2019/10/16
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Dr. David Alan Gilbert, 2019/10/16
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Max Reitz, 2019/10/16
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install,
psyhomb <=
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Laszlo Ersek (Red Hat), 2019/10/17
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Max Reitz, 2019/10/21
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Simon John, 2019/10/21
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Max Reitz, 2019/10/24
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Matti Hameister, 2019/10/30
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Max Reitz, 2019/10/30
- [Bug 1847793] Re: qemu 4.1.0 - Corrupt guest filesystem after new vm install, Claus Paetow, 2019/10/31