summary refs log tree commit diff stats
path: root/results/scraper/launchpad-without-comments/1793275
diff options
context:
space:
mode:
authorChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:24:58 +0000
committerChristian Krinitsin <mail@krinitsin.com>2025-06-30 12:27:06 +0000
commit33606b41d35115f887ea688b1a16f2ff85bf2fe4 (patch)
tree406b2c7b19a087ba437c68f3dbf0b589fa1d6150 /results/scraper/launchpad-without-comments/1793275
parentadedf8771bc4de3113041ca21bd4d0d1c0014b6a (diff)
downloadqemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.tar.gz
qemu-analysis-33606b41d35115f887ea688b1a16f2ff85bf2fe4.zip
add launchpad bug reports without comments
Diffstat (limited to 'results/scraper/launchpad-without-comments/1793275')
-rw-r--r--results/scraper/launchpad-without-comments/179327526
1 files changed, 26 insertions, 0 deletions
diff --git a/results/scraper/launchpad-without-comments/1793275 b/results/scraper/launchpad-without-comments/1793275
new file mode 100644
index 000000000..eae74bfd0
--- /dev/null
+++ b/results/scraper/launchpad-without-comments/1793275
@@ -0,0 +1,26 @@
+Hosts fail to start after update to QEMU 3.0
+
+Host OS: Archlinux
+Host Architecture: AMD64
+Guest OS: FreeBSD-11.2 (x2) and Archlinux (x1)
+Guest Architecture: AMD64
+
+I have been using QEMU 2.x without issue for a number of years but since updating to QEMU 3.0 my guests do not complete startup.
+
+FreeBSD 11.2 guest failure symptom:
+The two FreeBSD-11.2 guests output repeated messages of "unexpected cache type 4". This appears to be an internal error message and I've not found any instances of it through Google search.
+
+Archlinux guest failure symptom:
+The single Archlinux guest gets no further than the message "uncompressing initial ramdisk".
+
+The guests are started by a qemu-kvm invokation. No virtual machine managers are used. The command lines used (from ps awx) to launch the VMs are:
+
+[neil@optimus ~]$ ps awx |grep qemu
+ 1492 ?        Sl     3:19 /usr/bin/qemu-system-x86_64 -daemonize -pidfile /run/qemu_vps1.pid -enable-kvm -cpu host -smp 2 -k en-gb -boot order=c -drive file=/dev/system/vps1,cache=none,format=raw,if=virtio,index=0,media=disk -m 1024 -name FreeBSD_1 -net nic,macaddr=52:54:AD:86:64:00,model=virtio -net vde,sock=/run/vde_switch-tap0.sock -monitor telnet:127.0.0.2:23,server,nowait -vnc 192.168.0.1:0
+ 1510 ?        Sl     0:54 /usr/bin/qemu-system-x86_64 -daemonize -pidfile /run/qemu_vps2.pid -enable-kvm -cpu host -smp 2 -k en-gb -boot order=c -drive file=/dev/system/vps2,cache=none,format=raw,if=virtio,index=0,media=disk -m 1024 -name Archlinux -net nic,macaddr=52:54:AD:86:64:01,model=virtio -net vde,sock=/run/vde_switch-tap0.sock -monitor telnet:127.0.0.3:23,server,nowait -vnc 192.168.0.1:1
+ 1529 ?        Sl     3:07 /usr/bin/qemu-system-x86_64 -daemonize -pidfile /run/qemu_vps3.pid -enable-kvm -cpu host -smp 2 -k en-gb -boot order=c -drive file=/dev/system/vps3,cache=none,format=raw,if=virtio,index=0,media=disk -m 1024 -name FreeBSD_2 -net nic,macaddr=52:54:AD:86:64:02,model=virtio -net vde,sock=/run/vde_switch-tap0.sock -monitor telnet:127.0.0.4:23,server,nowait -vnc 192.168.0.1:2
+
+The VMs were installed to LVM volumes on the host machine (hence the /dev/system/vpsN device names). Networking is over a Linux tap interface connected to a VDE2 virtual network switch.
+
+Currently working version of QEMU: qemu-headless 2.12.1-1
+Failing version of QEMU: qemu-headless-3.0.0-1
\ No newline at end of file