diff options
Diffstat (limited to 'results/classifier/deepseek-r1:14b/output/KVM')
146 files changed, 3885 insertions, 0 deletions
diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1004408 b/results/classifier/deepseek-r1:14b/output/KVM/1004408 new file mode 100644 index 00000000..43f97fd7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1004408 @@ -0,0 +1,35 @@ + +BUG: Soft Lockup - CPU#0 stuck for 22s! [qemu-system-x86: 31867] + +Environment: +------------------- + * Upstream git version: qemu-kvm-1.1-rc2-4-g3fd9fed + * Host Kernel: Mainline Kernel - 3.4.0 x86_64 GNU/Linux (Arch: x86_64) + * CPU model: Intel(R) Xeon(R) CPU X5570 @ 2.93GHz + * Guest OS: Red Hat Enterprise Linux Server release 6.2 + * Guest Kernel: 2.6.32-220.el6.x86_64 + * Qemu-command line: +/usr/local/bin/qemu-system-x86_64 -name 'vm1' -nodefaults -monitor unix:'/tmp/monitor-humanmonitor1-20120525-214210-Zua6',server,nowait -serial unix:'/tmp/serial-20120525-214210-Zua6',server,nowait -device ich9-usb-uhci1,id=usb1 -drive file='/tmp/kvm_autotest_root/images/rhel62-64.qcow2',index=0,if=ide,cache=none -device rtl8139,netdev=idvVySvg,mac='9a:6d:16:b9:b5:06',id='idiX1NmG' -netdev tap,id=idvVySvg,fd=21 -m 7198 -smp 2 -device usb-tablet,id=usb-tablet1,bus=usb1.0 -vnc :0 -vga std + +The qemu is started through autotest. + +Description: +----------------- + +While running the cgroup test through autotest, the host was hung and was not responding. When viewed through serial console, found the error "BUG: Soft lockup" error as attached in the screenshot 1. + +There are no errors displayed in /var/log/messages (no call trace) and in dmesg.* +There is a call trace seen in serial console, which is show in screenshot 2. + +Steps to reproduce: +---------------------------- +Currently am not able to consistently reproduce this error. However when I tried to reproduce it again by running the cgroup test, found another error from syslogd as shown below + +"Message from syslogd@phx3 at May 25 21:56:04 ... + kernel:Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 3" + +So this time I got a hard Lockup error. Attached is the screenshot of the same. (screenshot-3, see the message at the bottom of the screen). This time the cgroup test had completed. + +Please let me know if you require more info on this. + +-prem \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1009 b/results/classifier/deepseek-r1:14b/output/KVM/1009 new file mode 100644 index 00000000..f247b24f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1009 @@ -0,0 +1,24 @@ + +Nested KVM Networking Issue (OpenStack) +Description of problem: +Hi, + +Inside openstack i have an instance of Ubuntu 20.04 and i have installed KVM ( using virt-manager ) to setup a Virtual Machine ... i have done that and i created a VM of ubuntu 20.04 inside the Openstack Instance but there are networking issue while i set the default parameter as setting up the VM ( i mean the networking is as default to NAT ) , So when the VM is up and running the PING to 8.8.8.8 is available and also ping to google.com is also valid which shows that the DNS is correctly working ... but there is not connectivity with packages while i do sudo apt update, it will not get any package update and also the wget to google.com is shows that its connected to it but it wont able to download!!! the same happen with curl to any other websites... + + +I'm confirming that the openstack instance has full access to the internet including ping and wget , .... but the VM is not working correctly! + +P.S. I have set the ip forwarding, Iptables , ... also disabled firewals but notting changed!! + + +Would you please fix this ? +Steps to reproduce: +1. creating an openstack instance from ubuntu 20.04 server image +2. updating and upgrading packages setting ip forwarding to 1 ( Enabled), firewall +3. and kernel to 5.13.0.40 and installing virt-manager then reboot +3. creating a VM with default KVM networking ( NAT ) using ubuntu 20.04 server image +4. trying ping, wget, curl , ... + + +Thanks +Best regards diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1021 b/results/classifier/deepseek-r1:14b/output/KVM/1021 new file mode 100644 index 00000000..81b37e13 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1021 @@ -0,0 +1,10 @@ + +nVMX: QEMU does not clear nVMX state through KVM(L0) when guest(L2) trigger a reboot event through I/O-Port(0xCF9) +Description of problem: +# +Steps to reproduce: +Guest(L2) write 0xCF9 to trigger a platform reboot. + +# +Additional information: + diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1037675 b/results/classifier/deepseek-r1:14b/output/KVM/1037675 new file mode 100644 index 00000000..01de15e8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1037675 @@ -0,0 +1,10 @@ + +Guest Kernel Panic if using "-cpu host" in qemu-kvm 1.1.1 + +After Upgrading to qemu-kvm-1.1.1-r1 from version 1.0.1-r1 my virtual machines (running gentoo linux) panic at intel_pmu_init. (detailed information including stacktrace are in the uploaded screenshot). When i remove the "-cpu host" option, the system starts normally. + +the command line from whicht the system is bootet: + +qemu-kvm -vnc :7 -usbdevice tablet -daemonize -m 256 -drive file=/data/virtual_machines/wgs-l08.img,if=virtio -boot c -k de -net nic,model=virtio,macaddr=12:12:00:12:34:63,vlan=0 -net tap,ifname=qtap6,script=no,downscript=no,vlan=0 -smp 2 -enable-kvm -cpu host -monitor unix:/var/run/qemu-kvm/wgs-l08.monitor,server,nowait + +also reported on gentoo bug tracker (with some more details of the host): https://bugs.gentoo.org/show_bug.cgi?id=431640 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1045 b/results/classifier/deepseek-r1:14b/output/KVM/1045 new file mode 100644 index 00000000..385c8357 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1045 @@ -0,0 +1,27 @@ + +When a break point is set, nested virtualization sees "kvm_queue_exception: Assertion `!env->exception_has_payload' failed." +Description of problem: +I am debugging XMHF and LHV using QEMU + KVM. I found that if I set a break point using GDB, QEMU will crash when LHV is booting. The message is +``` +qemu-system-i386: ../../../target/i386/kvm/kvm.c:678: kvm_queue_exception: Assertion `!env->exception_has_payload' failed. +``` + +The address of the break point is arbitrary. The break point does not need to hit. So I chose 0 as the address in this bug report. +Steps to reproduce: +1. Start QEMU using `qemu-system-i386 -m 512M -gdb tcp::1234 -smp 2 -cpu Haswell,vmx=yes -enable-kvm -serial stdio -drive media=disk,file=1.img,index=1 -drive media=disk,file=2.img,index=2 -S` +2. In another shell, start GDB using `gdb --ex 'target remote :::1234' --ex 'hb *0' --ex c` +3. See many serial output lines. The tail of the output is + ``` + CPU #0: vcpu_vaddr_ptr=0x01e06080, esp=0x01e11000 + CPU #1: vcpu_vaddr_ptr=0x01e06540, esp=0x01e15000 + BSP(0x00): Rallying APs... + BSP(0x00): APs ready, doing DRTM... + LAPIC base and status=0xfee00900 + Sending INIT IPI to all APs... + ``` +4. See assertion error in QEMU + ``` + qemu-system-i386: ../target/i386/kvm/kvm.c:645: kvm_queue_exception: Assertion `!env->exception_has_payload' failed. + ``` +Additional information: +This bug was first incorrectly filed in KVM's bug tracker at <https://bugzilla.kernel.org/show_bug.cgi?id=216002>. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1062201 b/results/classifier/deepseek-r1:14b/output/KVM/1062201 new file mode 100644 index 00000000..7d7b59f4 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1062201 @@ -0,0 +1,28 @@ + +qemu core dumped by kvm-spice + +Hi there, + +I am trying to use kvm-spice to start the qemu virtual machines. They start fine with the /usr/ bin/kvm command, but when I use the kvm-spice command the VM will not start and the core is dumped. + +Command I used: +kvm-spice -cpu host -enable-kvm -name win-7 -m 3000 -drive file=/var/vmmachines/win-7.img -net nic,model=rtl8139 -net user -localtime -usb -vga qxl -global qxl-vga.vram_size=67108864 -spice port=5901,disable-ticketing -boot d + + +Response: +do_spice_init: starting 0.10.1 +spice_server_add_interface: SPICE_INTERFACE_MIGRATION +spice_server_add_interface: SPICE_INTERFACE_KEYBOARD +spice_server_add_interface: SPICE_INTERFACE_MOUSE +spice_server_add_interface: SPICE_INTERFACE_QXL +red_worker_main: begin +display_channel_create: create display channel +cursor_channel_create: create cursor channel +kvm-spice: /build/buildd/qemu-linaro-1.0.50-2012.03/exec.c:2641: register_subpage: Assertion `existing.mr->subpage || existing.mr == &io_mem_unassigned' failed. +Aborted (core dumped) + + +I am running Ubuntu 12.04 sserver for this. Any information about this issue would be appreciated, i'm stuck on this one. + +Kind regards, +Tom \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1062589 b/results/classifier/deepseek-r1:14b/output/KVM/1062589 new file mode 100644 index 00000000..b944eb68 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1062589 @@ -0,0 +1,89 @@ + +Xp guest disk is corrupted when the data size exceeds 4 GB + +Host : +- 2.6.30.10 i686 pentium3 i386 GNU/Linux + +Guest : +- XPsp3 + +QEMU : +- QEMU emulator version 1.2.0 and 1.2.50 +- sudo /sources/qemu/i386-softmmu/qemu-system-i386 \ + -runas user -enable-kvm -rtc base=localtime -no-shutdown \ + -m 384 -usb -usbdevice tablet -vga std \ + -net nic,model=ne2k_pci -net tap,script=no,downscript=no \ + -drive file=/qemu/XP.img,index=0,media=disk,cache=writeback \ + -hdb /qemu/data.img \ + -drive index=2,media=cdrom,file=/jukebox/iso/xpProSP2.iso + +- image: /qemu/XP.img (before problem) +file format: qcow2 +virtual size: 10G (10737418240 bytes) +disk size: 3.9G +cluster_size: 65536 + +- chkdsk on Guest (before problem) +10474348 KB total disk space. +3519880 KB in 16982 files. +4440 KB in 898 indexes. +0 KB in bad sectors. +75980 KB in use by the system. +54432 KB occupied by the log file. +6874048 KB available on disk. + +4096 bytes in each allocation unit. +2618587 total allocation units on disk. +1718512 allocation units available on disk. + +- qemu-img check +Warning: cluster offset=0x42330b55100000 is after the end of the image file, can't properly check refcounts. +Warning: cluster offset=0x42330b55120000 is after the end of the image file, can't properly check refcounts. +ERROR l2_offset=42330b55110000: Table is not cluster aligned; L1 entry corrupted +Warning: cluster offset=0xa4d26d66440000 is after the end of the image file, can't properly check refcounts. +Warning: cluster offset=0xa4d26d66460000 is after the end of the image file, can't properly check refcounts. +ERROR l2_offset=a4d26d66453300: Table is not cluster aligned; L1 entry corrupted +ERROR: invalid cluster offset=0xad1f0047300000 +ERROR: invalid cluster offset=0xad1f0047320000 +ERROR l2_offset=ad1f0047309700: Table is not cluster aligned; L1 entry corrupted +ERROR OFLAG_COPIED: l2_offset=c452330b15090000 refcount=0 +Warning: cluster offset=0x52330b15080000 is after the end of the image file, can't properly check refcounts. +Warning: cluster offset=0x52330b150a0000 is after the end of the image file, can't properly check refcounts. +ERROR l2_offset=52330b15090000: Table is not cluster aligned; L1 entry corrupted +ERROR OFLAG_COPIED: l2_offset=cc5234077956330b refcount=0 +Warning: cluster offset=0x52340779560000 is after the end of the image file, can't properly check refcounts. +Warning: cluster offset=0x52340779580000 is after the end of the image file, can't properly check refcounts. +ERROR l2_offset=52340779563300: Table is not cluster aligned; L1 entry corrupted +ERROR refcount block 0 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 1 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 2 is outside image +ERROR refcount block 3 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 4 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 5 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 6 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 7 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 8 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 9 is not cluster aligned; refcount table entry corrupted +. +. +. +. +. +ERROR refcount block 16381 is not cluster aligned; refcount table entry corrupted +ERROR refcount block 16382 is outside image +ERROR refcount block 16383 is not cluster aligned; refcount table entry corrupted +ERROR cluster 0 refcount=0 reference=1 +ERROR cluster 1 refcount=0 reference=1 +ERROR cluster 3 refcount=0 reference=1 + +16396 errors were found on the image. +Data may be corrupted, or further writes to the image may corrupt it. + +8 internal errors have occurred during the check. + + +Hi, + +Everything is running pretty good until data size on disk C exceeds 4 GB. I Tried many options before figuring out that the problem occurs when data size exceeds 4 GB. I tried with QEMU 1.2.50, same problem. + +Best Regards. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1063807 b/results/classifier/deepseek-r1:14b/output/KVM/1063807 new file mode 100644 index 00000000..71c4054a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1063807 @@ -0,0 +1,71 @@ + +KVM crashes when booting a PointSec encrypted Windows 7 + +Hi all, + +KVM crashes each time the VM boots after installing PointSec. + +Steps to reproduce are: +1) install win7 64bits +2) install PointSec FDE (Full Disk Encryption => http://www.checkpoint.com/products/full-disk-encryption/index.html) +3) regardless any other qemu parameters, one gets a "KVM internal error. Suberror: 1 / emulation failure" error message and a qemu dump like this one: + +KVM internal error. Suberror: 1 +emulation failure +EAX=00000130 EBX=00000000 ECX=00014000 EDX=00050000 +ESI=00000000 EDI=00000000 EBP=00008e3f ESP=0001802d +EIP=000006d3 EFL=00017087 [--S--PC] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0048 00000000 ffffffff 00c09300 DPL=0 DS [-WA] +CS =25a1 00025a10 0000ffff 00009b00 DPL=0 CS16 [-RA] +SS =0040 00028050 ffffffff 00c09300 DPL=0 DS [-WA] +DS =0040 00028050 ffffffff 00c09300 DPL=0 DS [-WA] +FS =0130 00300000 ffffffff 00c09300 DPL=0 DS [-WA] +GS =0040 00028050 ffffffff 00c09300 DPL=0 DS [-WA] +LDT=0000 00000000 0000ffff 00008200 DPL=0 LDT +TR =0000 00000000 0000ffff 00008b00 DPL=0 TSS32-busy +GDT= 00028050 00001dd8 +IDT= 00029e40 00000188 +CR0=00000011 CR2=00000000 CR3=00000000 CR4=00000000 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000000 +Code=00 8e c0 b8 30 01 8e e0 66 b9 00 00 00 00 66 ba 00 00 00 00 <66> 26 67 8b 9a 00 00 05 00 66 64 67 89 1a 66 83 c2 04 66 41 66 81 f9 00 80 01 00 75 e3 0f + + +My system info: +root@RJZ-LNX:/home/rjz# cat /proc/cpuinfo | tail -24 +cpu family : 6 +model : 37 +model name : Intel(R) Core(TM) i5 CPU M 480 @ 2.67GHz +stepping : 5 +microcode : 0x2 +cpu MHz : 1199.000 +cache size : 3072 KB +physical id : 0 +siblings : 4 +core id : 2 +cpu cores : 2 +apicid : 5 +initial apicid : 5 +fpu : yes +fpu_exception : yes +cpuid level : 11 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid +bogomips : 5319.72 +clflush size : 64 +cache_alignment : 64 +address sizes : 36 bits physical, 48 bits virtual +power management: + + + +and qemu (Ubuntu distribution) info is: + +root@RJZ-LNX:/home/rjz# qemu-system-x86_64 --version +QEMU emulator version 1.0 (qemu-kvm-1.0), Copyright (c) 2003-2008 Fabrice Bellard + + + +Best regards, +Rolando. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/110 b/results/classifier/deepseek-r1:14b/output/KVM/110 new file mode 100644 index 00000000..f316227b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/110 @@ -0,0 +1,2 @@ + +KVM guest VM does not reattach a throughpassed USB printer from Host after switching printer off and on diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1136 b/results/classifier/deepseek-r1:14b/output/KVM/1136 new file mode 100644 index 00000000..0199dabd --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1136 @@ -0,0 +1,2 @@ + +qemu-system-ppc64: KVM HPT guest sometimes fails to migrate diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1138 b/results/classifier/deepseek-r1:14b/output/KVM/1138 new file mode 100644 index 00000000..7fafcfe9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1138 @@ -0,0 +1,2 @@ + +Not able to get KVM in qemu-system-s390x built from 6.2.0 source on Fedora 31 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1162 b/results/classifier/deepseek-r1:14b/output/KVM/1162 new file mode 100644 index 00000000..be534292 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1162 @@ -0,0 +1,13 @@ + +`./configure` gives `big/little test failed` error when attempting to statically link on Fedora 36 +Description of problem: +I'm having trouble attempting to build the QEMU System emulator statically linked. The error `./configure` gives `big/little test failed` with nothing else. I couldn't find any information relating to this. I'm not sure where to start fixing this. If anyone can help me with this, thanks! +Steps to reproduce: +1. `git clone https://gitlab.com/qemu-project/qemu.git` +2. `cd qemu` +3. `git submodule init` +4. `git submodule update` +5. `./configure --enable-kvm --enable-vnc --enable-vhost-net --enable-avx2 --enable-avx512f --target-list=x86_64-softmmu --static` +6. Observe build error +Additional information: + diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1169049 b/results/classifier/deepseek-r1:14b/output/KVM/1169049 new file mode 100644 index 00000000..7e20603c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1169049 @@ -0,0 +1,19 @@ + +do not stop on first gdb breakpoint with -enable-kvm + +I run qemu like this: + qemu-system-x86-64 -enable-kvm -hda <path to file> -s -S, + +and start gdb with commands like this: + gdb>tartget remote localhost:1234 + gdb>break *0x7c00 + gdb>c + +but gdb don't stop on it. I then could break execution manually and then breakpoints work. + +QEMU version: 1.4.0 (from Debian repos) +GDB version: 7.5.1 (copiled from sources, but previous was 7.4.1 from Debian repo) + +PS Same problem occure on Ubuntu 13.04 with same Qemu and Gdb 7.5.0 from repo. + +Thank you \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1198 b/results/classifier/deepseek-r1:14b/output/KVM/1198 new file mode 100644 index 00000000..b067dac7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1198 @@ -0,0 +1,54 @@ + +Windows 11 Guest keeps crashing with abort in cpu_asidx_from_attrs +Steps to reproduce: +1. Create Windows 11 guest, SWTPM, SECBOOT (haven't tested without since this is not an option for installing Windows 11) +2. Use OS +3. Will eventually crash. Have tried across multiple kernels 5.17, 5.18, 5.19 +Additional information: +``` + + Stack trace of thread 76223: + #0 0x00007f24072d44dc n/a (libc.so.6 + 0x884dc) + #1 0x00007f2407284998 raise (libc.so.6 + 0x38998) + #2 0x00007f240726e53d abort (libc.so.6 + 0x2253d) + #3 0x00007f240726e45c n/a (libc.so.6 + 0x2245c) + #4 0x00007f240727d4c6 __assert_fail (libc.so.6 + 0x314c6) + #5 0x0000555681a35101 cpu_asidx_from_attrs (qemu-system-x86_64 + 0x572101) + #6 0x0000555681c6531e cpu_memory_rw_debug (qemu-system-x86_64 + 0x7a231e) + #7 0x0000555681bfb54a x86_cpu_dump_state (qemu-system-x86_64 + 0x73854a) + #8 0x0000555681d84a65 kvm_cpu_exec (qemu-system-x86_64 + 0x8c1a65) + #9 0x0000555681d85e48 kvm_vcpu_thread_fn (qemu-system-x86_64 + 0x8c2e48) + #10 0x0000555681fed0a8 qemu_thread_start (qemu-system-x86_64 + 0xb2a0a8) + #11 0x00007f24072d278d n/a (libc.so.6 + 0x8678d) + #12 0x00007f24073538e4 __clone (libc.so.6 + 0x1078e4) +``` + + +``` +KVM: entry failed, hardware error 0x80000021 + +If you're running a guest on an Intel machine without unrestricted mode +support, the failure can be most likely due to the guest entering an invalid +state for Intel VT. For example, the guest maybe running in big real mode +which is not supported on less recent Intel processors. + +EAX=00000000 EBX=00000000 ECX=00000000 EDX=04c6d3e0 +ESI=12af7eb0 EDI=9e55d420 EBP=821b5aa0 ESP=10db0fb0 +EIP=00008000 EFL=00000002 [-------] CPL=0 II=0 A20=1 SMM=1 HLT=0 +ES =0000 00000000 ffffffff 00809300 +CS =b500 7ffb5000 ffffffff 00809300 +SS =0000 00000000 ffffffff 00809300 +DS =0000 00000000 ffffffff 00809300 +FS =0000 00000000 ffffffff 00809300 +GS =0000 00000000 ffffffff 00809300 +LDT=0000 00000000 000fffff 00000000 +TR =0040 10d97000 00000067 00008b00 +GDT= 10d98fb0 00000057 +IDT= 00000000 00000000 +CR0=00050032 CR2=f80ff80c CR3=e47e7000 CR4=00000000 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000000 +Code=qemu-system-x86_64: ../qemu-7.0.0/hw/core/cpu-sysemu.c:77: cpu_asidx_from_attrs: Assertion `ret < cpu->num_ases && ret >= 0' failed. +2022-09-06 14:48:15.392+0000: shutting down, reason=crashed +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1219 b/results/classifier/deepseek-r1:14b/output/KVM/1219 new file mode 100644 index 00000000..a2d0c700 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1219 @@ -0,0 +1,14 @@ + +--enable-kvm not work for riscv64-softmmu +Description of problem: +I want to enable kvm for qemu-system-riscv64, so I compile it with `--enable-kvm` as above. But the log shows + +```sh + Targets and accelerators + KVM support : NO +``` + +And also compiled qemu-system-riscv64 does not support kvm. +Steps to reproduce: +1. clone the repo +2. `./configure --target-list=riscv64-softmmu --enable-kvm` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1248959 b/results/classifier/deepseek-r1:14b/output/KVM/1248959 new file mode 100644 index 00000000..bc97c50a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1248959 @@ -0,0 +1,82 @@ + +pdpe1gb flag is missing in guest running on Intel h/w + +I need to utilize 1G hugepages on my guest system. But this is not possible as long as there is no pdpe1gb support in guest system. The latest source code contains pdpe1gb support for AMD but not for Intel. + +Are there any obstacles that does not allow to implement it for modern Intel chips? + +My configuration: +Host: +------- +uname -a +Linux tripel.salab.cic.nsn-rdnet.net 2.6.32-358.14.1.el6.x86_64 #1 SMP Tue Jul 16 23:51:20 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux + +cat /etc/*-release +CentOS release 6.4 (Final) + +yum list installed | grep qemu +gpxe-roms-qemu.noarch 0.9.7-6.9.el6 @base +qemu-img.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.5 +qemu-kvm.x86_64 2:0.12.1.2-2.355.0.1.el6.centos.5 + +cat /proc/cpuinfo +processor : 0 +vendor_id : GenuineIntel +cpu family : 6 +model : 45 +model name : Intel(R) Xeon(R) CPU E5-2680 0 @ 2.70GHz +stepping : 7 +cpu MHz : 2700.000 +cache size : 20480 KB +physical id : 0 +siblings : 16 +core id : 0 +cpu cores : 8 +apicid : 0 +initial apicid : 0 +fpu : yes +fpu_exception : yes +cpuid level : 13 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid +bogomips : 5387.09 +clflush size : 64 +cache_alignment : 64 +address sizes : 46 bits physical, 48 bits virtual + +/usr/libexec/qemu-kvm -cpu ? +Recognized CPUID flags: + f_edx: pbe ia64 tm ht ss sse2 sse fxsr mmx acpi ds clflush pn pse36 pat cmov mca pge mtrr sep apic cx8 mce pae msr tsc pse de vme fpu + f_ecx: hypervisor rdrand f16c avx osxsave xsave aes tsc-deadline popcnt movbe x2apic sse4.2|sse4_2 sse4.1|sse4_1 dca pcid pdcm xtpr cx16 fma cid ssse3 tm2 est smx vmx ds_cpl monitor dtes64 pclmulqdq|pclmuldq pni|sse3 + extf_edx: 3dnow 3dnowext lm|i64 rdtscp pdpe1gb fxsr_opt|ffxsr fxsr mmx mmxext nx|xd pse36 pat cmov mca pge mtrr syscall apic cx8 mce pae msr tsc pse de vme fpu + extf_ecx: perfctr_nb perfctr_core topoext tbm nodeid_msr tce fma4 lwp wdt skinit xop ibs osvw 3dnowprefetch misalignsse sse4a abm cr8legacy extapic svm cmp_legacy lahf_lm + +ps ax | grep qemu + 7197 ? Sl 0:15 /usr/libexec/qemu-kvm -name vladimir.AS-0 -S -M rhel6.4.0 -cpu SandyBridge,+pdpe1gb,+osxsave,+dca,+pcid,+pdcm,+xtpr,+tm2,+est,+smx,+vmx,+ds_cpl,+monitor,+dtes64,+pbe,+tm,+ht,+ss,+acpi,+ds,+vme -enable-kvm -m 8192 -mem-prealloc -mem-path /var/lib/hugetlbfs/pagesize-1GB/libvirt/qemu -smp 4,sockets=4,cores=1,threads=1 -uuid ec2d3c58-a7f0-fdbd-9de5-b547a5b3130f -nographic -nodefconfig -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/vladimir.AS-0.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -netdev tap,fd=28,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=52:54:00:81:5b:df,bus=pci.0,addr=0x3,bootindex=1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -device pci-assign,host=02:00.0,id=hostdev0,configfd=29,bus=pci.0,addr=0x4 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 + +Guest: +--------- +# uname -a +Linux AS-0 2.6.34.13-WR4.3.fp_x86_64_standard-00019-g052bb3e #1 SMP Wed May 8 12:21:02 EEST 2013 x86_64 x86_64 x86_64 GNU/Linux + +# cat /etc/*-release +Wind River Linux 4.3 glibc_cgl + +# cat /proc/cpuinfo +processor : 0 +vendor_id : GenuineIntel +cpu family : 6 +model : 42 +model name : Intel Xeon E312xx (Sandy Bridge) +stepping : 1 +cpu MHz : 2693.893 +cache size : 4096 KB +fpu : yes +fpu_exception : yes +cpuid level : 13 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx lm constant_tsc rep_good pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt aes xsave avx hypervisor lahf_lm xsaveopt +bogomips : 5387.78 +clflush size : 64 +cache_alignment : 64 +address sizes : 46 bits physical, 48 bits virtual \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1254443 b/results/classifier/deepseek-r1:14b/output/KVM/1254443 new file mode 100644 index 00000000..4d21dc27 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1254443 @@ -0,0 +1,6 @@ + +Periodic mode of LAPIC doesn't fire interrupts when using kvm + +It works fine when not using kvm and it does also work fine when using oneshot mode. + +Tested with qemu 1.6.1 (commit 62ecc3a0e3c77a4944c92a02dd7fae2ab1f2290d). \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1254940 b/results/classifier/deepseek-r1:14b/output/KVM/1254940 new file mode 100644 index 00000000..2684b139 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1254940 @@ -0,0 +1,49 @@ + +qemu-KVM guest OS occurs many ext3-fs errors after multiple forced shutdown + +Hi: +I met some filesysterm errors in a sles guest on KVM. My system environment is: +HOST: + suse 10, the kernel version is 2.6.32.43 + Qemu-KVM 1.2 + Libvirt 1.0 +guest OS: + suse 10, the kernel version is 2.6.32.43 +VMs use a qcow2 disk. + +Description of problem: +I have 20+ VMs with qcow2 disk, these VMs have been forced to shut down by +"virsh destroy" many times during and after VM installation. +When these vm reboot,dmesg show a ext3-fs mount error occurred on /usr/local +partion /dev/vda3: + EXT3-fs warning: mounting fs with errors, running e2fsck is recommendedand +when I wrote into partion /dev/vda3,some errors occurred in dmesg: +1.error (device vda3): ext3_free_blocks: Freeing blocks not in datazone - block += 1869619311, count = 1error (device vda3): ext3_free_blocks_sb: bit already +cleared for block 2178152error (device vda3): ext3_readdir: bad entry in +directory #1083501: +2.[347470.661893] attempt to access beyond end of device[347470.661896] vda3: +rw=0, want=6870892952, limit=41945715[347470.661897] EXT3-fs error (device +vda3): ext3_free_branches: Read failure, inode=1083508, block=858861618 +3.EXT3-fs error (device vda3): ext3_new_block: block(4295028581) >= blocks +count(-1) - block_group = 1, es == ffff88021b6c7400 + +I suspect this fs-error is caused by multiple forced shutdown, but I can't +reproduce this bug now. + +Could anyone has an idea or suggestion to help me? + +Thanks in Advance +Regards +Ben + +Reproducible: Always + +Steps to Reproduce: +I can't reproduce this bug now. + + +additional: +1.multiple forced shutdown during and after the vm installing +2.vm with qcow2 disk +3.different vm dmesg different errors in above error list(1/2/3) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1257352 b/results/classifier/deepseek-r1:14b/output/KVM/1257352 new file mode 100644 index 00000000..8127ab2c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1257352 @@ -0,0 +1,32 @@ + +kvm hangs occasionally when switching out of the qemu console + +To recreate (although this does *NOT* fail most of the time alas): + +1) press "ctrl-alt-2" to switch to the qemu console. +2) type say "sendkey ctrl-alt-f1" +3) press "ctrl-alt-1". + +Expected outcome: Switch to tty1 in the VM. + +Actual outcome: No switch to tty1 in the VM. and qemu console unresponsive to any keyboard input. + + +Rather a vague problem description I'm afraid but this has happened to me 3 times recently. No crash and no excessive CPU is observed. + +I'll grab an strace when it happens again and attach... + +ProblemType: Bug +DistroRelease: Ubuntu 14.04 +Package: qemu-system-x86 1.6.0+dfsg-2ubuntu4 +ProcVersionSignature: Ubuntu 3.12.0-4.12-generic 3.12.1 +Uname: Linux 3.12.0-4-generic i686 +NonfreeKernelModules: nvidia +ApportVersion: 2.12.7-0ubuntu1 +Architecture: i386 +CurrentDesktop: Unity +Date: Tue Dec 3 15:41:40 2013 +InstallationDate: Installed on 2010-10-21 (1139 days ago) +InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) +SourcePackage: qemu +UpgradeStatus: Upgraded to trusty on 2013-11-01 (31 days ago) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1270397 b/results/classifier/deepseek-r1:14b/output/KVM/1270397 new file mode 100644 index 00000000..822ee2c6 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1270397 @@ -0,0 +1,66 @@ + +Systemd segfaults after live migration + +After live migrating my virtual machine it panics because of segmentation fault in systemd (see attachment). + +Software used (on archlinux): +qemu 1.7.0-1 +libvirt 1.2.0-1 +linux 3.12.7-1 + +This is configuration of this VM: +<domain type='kvm'> + <name>vbroker</name> + <uuid>455c9c62-10a6-11e3-a7f2-441ea153aac8</uuid> + <description>455c9c62-10a6-11e3-a7f2-441ea153aac8</description> + <memory unit='KiB'>6291456</memory> + <currentMemory unit='KiB'>6291456</currentMemory> + <vcpu placement='static'>4</vcpu> + <os> + <type arch='x86_64' machine='pc-i440fx-1.7'>hvm</type> + <boot dev='cdrom'/> + <bootmenu enable='no'/> + </os> + <features> + <acpi/> + <apic/> + </features> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>restart</on_crash> + <devices> + <emulator>/usr/bin/qemu-kvm</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' cache='none'/> + <source file='/var/lib/libvirt/images/archipel/drives/455c9c62-10a6-11e3-a7f2-441ea153aac8/vbroker.qcow2'/> + <target dev='vda' bus='virtio'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> + </disk> + <controller type='usb' index='0'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/> + </controller> + <controller type='pci' index='0' model='pci-root'/> + <interface type='bridge'> + <mac address='de:ad:fb:8e:17:c2'/> + <source bridge='br0'/> + <model type='virtio'/> + <filterref filter='clean-traffic'> + <parameter name='IP' value='10.0.0.2'/> + </filterref> + <bandwidth> + </bandwidth> + <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> + </interface> + <input type='tablet' bus='usb'/> + <input type='mouse' bus='ps2'/> + <graphics type='vnc' port='-1' autoport='yes' keymap='en-us'/> + <video> + <model type='cirrus' vram='9216' heads='1'/> + <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> + </video> + <memballoon model='virtio'> + <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> + </memballoon> + </devices> +</domain> \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1288259 b/results/classifier/deepseek-r1:14b/output/KVM/1288259 new file mode 100644 index 00000000..d0bb181b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1288259 @@ -0,0 +1,40 @@ + +KVM vms are paused and cannot be deleted due to hardware error 0x0 + +Upon creation of instances via OpenStack nova api instances got stuck in spawning state. Then, after trying to delete instances they got stuck in deleting state. After investigation the following error was found: + +KVM: entry failed, hardware error 0x0 +EAX=00000000 EBX=00000000 ECX=00000000 EDX=00000623 +ESI=00000000 EDI=00000000 EBP=00000000 ESP=00000000 +EIP=0000fff0 EFL=00000002 [-------] CPL=3 II=0 A20=1 SMM=0 HLT=0 +ES =0000 00000000 0000ffff 00009300 +CS =f000 000f0000 0000ffff 0000f300 +SS =0000 00000000 0000ffff 0000f300 +DS =0000 00000000 0000ffff 00009300 +FS =0000 00000000 0000ffff 00009300 +GS =0000 00000000 0000ffff 00009300 +LDT=0000 00000000 0000ffff 00008200 +TR =0000 00000000 0000ffff 00008b00 +GDT= 00000000 0000ffff +IDT= 00000000 0000ffff +CR0=60000010 CR2=00000000 CR3=00000000 CR4=00000000 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000000 +Code=28 95 66 ba 01 4a 03 00 66 89 d8 66 5b 66 5e e9 15 79 66 c3 <ea> 5b e0 00 f0 30 36 2f 32 33 2f 39 39 00 fc 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 + +All instances were in paused state: +root@node-7:~# virsh list +setlocale: No such file or directory + Id Name State +---------------------------------------------------- + 4 instance-00000004 paused + 5 instance-00000005 paused + 6 instance-00000006 paused + 7 instance-00000007 paused + 8 instance-00000008 paused + 9 instance-00000009 paused + +The only way to delete VM is to reset it and then resume it. After this, VM is deleted properly. +OpenStack version: Havana on Ubuntu 12.04 +KVM version: QEMU emulator version 1.2.0 (qemu-kvm-1.2.0+noroms-0ubuntu7.12.10, Debian), Copyright (c) 2003-2008 Fabrice Bellard \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1294227 b/results/classifier/deepseek-r1:14b/output/KVM/1294227 new file mode 100644 index 00000000..cdab1ebf --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1294227 @@ -0,0 +1,15 @@ + +migration wrong handling of KVM_GET_DIRTY_LOG ioctl + +In the code below kvm_vm_ioctl(...) can return --errno != -1 from ioctl call, but return only checks for -1. +Found during KVM-ARM migration which apperead to go through but was actually failing getting +memslot dirty bitmap. + +static int kvm_physical_sync_dirty_bitmap(....) +{ + .... + if(kvm_vm_ioctl(s, KVM_GET_DIRTY_LOG, &d) == -1) { + - err out + } + ... continue +} \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1297218 b/results/classifier/deepseek-r1:14b/output/KVM/1297218 new file mode 100644 index 00000000..41b7599c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1297218 @@ -0,0 +1,21 @@ + +guest hangs after live migration due to tsc jump + +We have two identical Ubuntu servers running libvirt/kvm/qemu, sharing a Gluster filesystem. Guests can be live migrated between them. However, live migration often leads to the guest being stuck at 100% for a while. In that case, the dmesg output for such a guest will show (once it recovers): Clocksource tsc unstable (delta = 662463064082 ns). In this particular example, a guest was migrated and only after 11 minutes (662 seconds) did it become responsive again. + +It seems that newly booted guests doe not suffer from this problem, these can be migrated back and forth at will. After a day or so, the problem becomes apparent. It also seems that migrating from server A to server B causes much more problems than going from B back to A. If necessary, I can do more measurements to qualify these observations. + +The VM servers run Ubuntu 13.04 with these packages: +Kernel: 3.8.0-35-generic x86_64 +Libvirt: 1.0.2 +Qemu: 1.4.0 +Gluster-fs: 3.4.2 (libvirt access the images via the filesystem, not using libgfapi yet as the Ubuntu libvirt is not linked against libgfapi). +The interconnect between both machines (both for migration and gluster) is 10GbE. +Both servers are synced to NTP and well within 1ms form one another. + +Guests are either Ubuntu 13.04 or 13.10. + +On the guests, the current_clocksource is kvm-clock. +The XML definition of the guests only contains: <clock offset='utc'/> + +Now as far as I've read in the documentation of kvm-clock, it specifically supports live migrations, so I'm a bit surprised at these problems. There isn't all that much information to find on these issue, although I have found postings by others that seem to have run into the same issues, but without a solution. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1312668 b/results/classifier/deepseek-r1:14b/output/KVM/1312668 new file mode 100644 index 00000000..858cb9ef --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1312668 @@ -0,0 +1,54 @@ + +x86 cpu nx feature: guest reboots after migrate exec + +Using instruction on +http://www.linux-kvm.org/page/Migration +I save VM state to external file and try load it, but VM starts, shows saved screen and reboots immediatly. + +Cmdline for vm state saving: + +$ sudo ./i386-softmmu/qemu-system-i386 -machine accel=kvm,kernel_irqchip=on -enable-kvm -m 512 -hda image.raw -vga std -net none -M pc -monitor stdio -cpu SandyBridge +(or -cpu "n270" , or "kvm32,+sse2,+pae,+nx") + +Monitor cmd: +(qemu) stop +(qemu) migrate_set_speed 4095m +(qemu) migrate "exec:gzip -c > STATEFILE.gz" +(qemu) q + +Cmdline for vm state loading: + +$ sudo ./i386-softmmu/qemu-system-i386 -machine accel=kvm,kernel_irqchip=on -enable-kvm -m 512 -hda image.raw -vga std -net none -M pc -monitor stdio -cpu SandyBridge -incoming "exec: gzip -c -d STATEFILE.gz" +(or -cpu "n270" , or "kvm32,+sse2,+pae,+nx") + +If I do the same without NX cpu feature (-cpu option "n270,-nx" / "SandyBridge,-nx" / "kvm32,+pae,+sse2") or on qemu-system-x86_64, VM save/load works correctly. + +Log kvm-all.c, DEBUG_KVM=y: + +QEMU 2.0.0 monitor - type 'help' for more information +(qemu) kvm_init_vcpu +...handle_io.../...handle_mmio... +kvm_cpu_exec() +shutdown +kvm_cpu_exec() +interrupt exit requested +io window exit +kvm_cpu_exec() + +Host: + + $ lsb_release -rd + Description: Ubuntu 12.04.4 LTS + Release: 12.04 + + $ uname -a + Linux <username> 3.8.0-38-generic #56~precise1 SMP Tue Apr 22 12:46:44 MSK 2014 x86_64 x86_64 x86_64 GNU/Linux + +Guest: + 1. Ubuntu 12.04 32bit + 2. WIndows 8 32bit + +Qemu: v2.0.0 +commit a9e8aeb3755bccb7b51174adcf4a3fc427e0d147 +Author: Peter Maydell <email address hidden> +Date: Thu Apr 17 13:41:45 2014 +0100 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1366836 b/results/classifier/deepseek-r1:14b/output/KVM/1366836 new file mode 100644 index 00000000..25c000f8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1366836 @@ -0,0 +1,17 @@ + +Core2Duo and KVM may not boot Win8 properly on 3.x kernels + +When I start up QEMU w/ KVM 1.7.0 on a Core2Duo machine running a vanilla kernel +3.4.67 or 3.10.12 to run a Windows 8.0 guest, the guest freezes at Windows 8 boot without any error. +When I dump the CPU registers via "info registers", nothing changes, that means +the system really stalled. Same happens with QEMU 2.0.0 and QEMU 2.1.0. + +But - when I run the very same guest using Kernel 2.6.32.12 and QEMU 1.7.0 or 2.0.0 on +the host side it works on the Core2Duo. Also the system above but just with an +i3 or i5 CPU it works fine. + +I already disabled networking and USB for the guest and changed the graphics +card - no effect. I assume that some mean bits and bytes have to be set up +properly to get the thing running. + +Seems to be related to a kvm/progressor incompatibility. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1378 b/results/classifier/deepseek-r1:14b/output/KVM/1378 new file mode 100644 index 00000000..6e33f40c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1378 @@ -0,0 +1,21 @@ + +iSCSI causes memory corruption +Description of problem: +This is a compound problem, which most likely involves a combination of how TrueNAS SCALE handles iSCSI triggering a problem **and** some memory-handling issue in QEMU leading to a crash. In short any Linux machine started with iSCSI handled by QEMU directly leads to a hard crash within 30s-1h. I was able to find a pattern in logs: + +1. First, a message like `QEMU[53139]: kvm: iSCSI Busy/TaskSetFull/TimeOut (retry #1 in 0 ms): TASK_SET_FULL` is logged + - it is always `TASK_SET_FULL` + - it is always `retry #1 in ... ms`, where only number of miliseconds varies + - the line is repeated multiple times, sometimes 5x and sometimes >200x +2. It is followed by a single line with one of the following: + - `double free or corruption (out)` + - `double free or corruption (!prev)` + - `kvm: ../block/block-backend.c:1567: blk_aio_write_entry: Assertion `!qiov || qiov->size == acb->bytes' failed.` + - `kvm: malloc.c:2379: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.` + - `kvm: iSCSI CheckCondition: SENSE KEY:UNIT_ATTENTION(6) ASCQ:BUS_RESET(0x2900)` + - `malloc(): invalid size (unsorted)` +3. The virtual machine crashes +Steps to reproduce: +I don't have a specific concrete steps, only clues really. This problem started happening after TrueNAS SCALE updated their iSCSI code in Bluefin release to a new upstream version. That iSCSI server still works when iSCSI is mounted by the kernel and QEMU uses a normal `/dev` entry. While there's probably some problem with it, QEMU shouldn't probably crash with memory errors. +Additional information: +While I'm a software developer, I don't code in C on a daily basis. However, looking at the errors, I have a suspicion the problem may be somewhere in the `iscsi_co_generic_cb()`, as it seems the struct is getting damaged (out of bound write?) and causes explosion somewhere down the line. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1438572 b/results/classifier/deepseek-r1:14b/output/KVM/1438572 new file mode 100644 index 00000000..81b9347e --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1438572 @@ -0,0 +1,17 @@ + +kvm does not support KVM_CAP_USER_MEMORY Please upgrade to at least kernel 2.6.29 or recent kvm-kmod (see http://sourceforge.net/projects/kvm) + +We have a machine which is having QEMU+KVM on below configuration of linux +uname -a +Linux cairotrior 2.6.18-308.13.1.el5 #1 SMP Thu Jul 26 05:45:09 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux +cat /etc/issue +Red Hat Enterprise Linux Server release 5.8 (Tikanga) +Kernel \r on an \m + + +But in another setup, we are trying on a different machine having RHEL 5.9 having higher kernel version but it still gives below error +kvm does not support KVM_CAP_USER_MEMORY Please upgrade to at least kernel 2.6.29 or recent kvm-kmod (see http://sourceforge.net/projects/kvm). +failed to initialize KVM: Invalid argument No accelerator found! + + +I don’t know if the qemu version have compatibility issues with redhat 5.9 version – need someone to check if the qemu can run on redhat 5.9 64 bit or not ? \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1439 b/results/classifier/deepseek-r1:14b/output/KVM/1439 new file mode 100644 index 00000000..47474b29 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1439 @@ -0,0 +1,12 @@ + +QEMU crashes when there is an "[accel]" section in the config file +Description of problem: +QEMU crashes with a segmentation fault if there is a "[accel]" section in the config file with a type="kvm" entry. It would be maybe still be OK if there was an error message instead, but it should certainly not crash. +Steps to reproduce: +``` +$ cat > /tmp/config <<EOF +[accel] +type = "kvm" +EOF +$ qemu-system-x86_64 -readconfig /tmp/config +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1487264 b/results/classifier/deepseek-r1:14b/output/KVM/1487264 new file mode 100644 index 00000000..7e24385f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1487264 @@ -0,0 +1,19 @@ + +Windows 8.1/10 Crashes during upgrade - SYSTEM_THREAD_EXCEPTION_NOT_HANDLED + +Ever since Windows 8.x, 10 I cannot upgrade or upgrade to tech builds within Windows 10 without hard shutting off the VM. + +Physical hardware: Intel(R) Core(TM) i7-4910MQ CPU @ 2.90GHz [Haswell] + +QEMU 2.1-2.3.x seem all broken, I am using Q35 chipset w/ BIOS mode. + +Launch command via virt-manager/libvirt launch: + +QEMU_AUDIO_DRV=spice /usr/bin/qemu-kvm -name Windows_10 -S -machine pc-q35-2.3,accel=kvm,usb=off -cpu Haswell-noTSX,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid ed7e372b-ebf9-4feb-a305-869f82e6aaee -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/Windows_10.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1 -boot menu=off,strict=on -device i82801b11-bridge,id=pci.1,bus=pcie.0,addr=0x1e -device pci-bridge,chassis_nr=2,id=pci.2,bus=pci.1,addr=0x1 -device ich9-usb-ehci1,id=usb,bus=pci.2,addr=0x3.0x7 -device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.2,multifunction=on,addr=0x3 -device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.2,addr=0x3.0x1 -device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.2,addr=0x3.0x2 -device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x4 -drive file=/var/lib/libvirt/images/Windows_10.qcow2,if=none,id=drive-sata0-0-0,format=qcow2 -device ide-hd,bus=ide.0,drive=drive-sata0-0-0,id=sata0-0-0,bootindex=1 -drive file=/usr/share/virtio-win/virtio-win-0.1.109.iso,if=none,media=cdrom,id=drive-sata0-0-1,readonly=on,format=raw -device ide-cd,bus=ide.1,drive=drive-sata0-0-1,id=sata0-0-1 -netdev tap,fd=22,id=hostnet0,vhost=on,vhostfd=23 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:54:14:20,bus=pci.2,addr=0x1 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev spicevmc,id=charchannel0,name=vdagent -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=com.redhat.spice.0 -device usb-tablet,id=input0 -spice port=5900,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on -device qxl-vga,id=video0,ram_size=268435456,vram_size=268435456,vgamem_mb=256,bus=pcie.0,addr=0x1 -device ich9-intel-hda,id=sound0,bus=pci.2,addr=0x2 -device hda-duplex,id=sound0-codec0,bus=sound0.0,cad=0 -device usb-host,hostbus=1,hostaddr=2,id=hostdev0 -device virtio-balloon-pci,id=balloon0,bus=pci.2,addr=0x5 -msg timestamp=on + +The workaround I've been able to come up with is to set boot menu in virt-manager, then put in a bootable CD so I have enough time to hard power off the QEMU/KVM instance, when I power it back on, it continues upgrade/install without issue, each time it needs to restart however I go though same exercise. + +Anything known about this issue? The workaround is a kludge, but it does get it to upgrade/install Windows 8.1, and upgrade between Windows 10 X builds. + +Thanks, +Shawn \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/150 b/results/classifier/deepseek-r1:14b/output/KVM/150 new file mode 100644 index 00000000..3d89d275 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/150 @@ -0,0 +1,2 @@ + +Illegal Instruction with HVF when encountering SSE instructions in the emulator diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1502934 b/results/classifier/deepseek-r1:14b/output/KVM/1502934 new file mode 100644 index 00000000..38554be3 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1502934 @@ -0,0 +1,25 @@ + +QEMU does not start when kvm enabled (SMM issue?) + +Hi! + +QEMU stopped working after "[355023f2010c4df619d88a0dd7012b4b9c74c12c] pc: add SMM property" on my server. It says "Guest has not initialized the display (yet)." and nothing happens. But only if I use -enable-kvm. + +However, the problem gone after I hardcoded pc_machine_is_smm_enabled() to always return false (but I have little to no understanding of what SMM really is). + +CMD line that reproduces the issue: qemu-system-x86_64 -enable-kvm -display curses . It doesn't work the server, but works perfectly on my laptop :(. + +I'm using Arch Linux with all updates. +Some info: +Linux machine 4.2.2-1-ARCH #1 SMP PREEMPT Tue Sep 29 22:21:33 CEST 2015 x86_64 GNU/Linux +Qemu-2.4.0 (tried HEAD as well) +CPU: Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz +Some messages from dmesg, just in case: +[ 6.996297] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround +[ 6381.722990] kvm: zapping shadow pages for mmio generation wraparound + + +I'm more than happy to provide additional information if needed. + +Cheers, +Alex \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1524 b/results/classifier/deepseek-r1:14b/output/KVM/1524 new file mode 100644 index 00000000..c97ac3bc --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1524 @@ -0,0 +1,38 @@ + +error while loading state for instance 0x0 of device 'kvm-tpr-opt',load of migration failed: Operation not permitted +Description of problem: +when i save and restore a guest,it report the error: "error while loading state for instance 0x0 of device 'kvm-tpr-opt',load of migration failed: Operation not permitted" +Steps to reproduce: +1.virsh save test ccc.img + +2.virsh restore ccc.im + + +it report error: + +[root@TOS-9772 ~]# virsh save test ccc.img + +[root@TOS-9772 ~]# virsh restore ccc.img + +error: Failed to restore domain from ccc.img + +error: internal error: qemu unexpectedly closed the monitor: qmp_cmd_name: query-hotpluggable-cpus, arguments: {} + +qmp_cmd_name: query-cpus-fast, arguments: {} + +qmp_cmd_name: query-iothreads, arguments: {} + +qmp_cmd_name: expire_password, arguments: {"protocol": "spice", "time": "never"} + +qmp_cmd_name: balloon, arguments: {"value": 1073741824} + +qmp_cmd_name: migrate-incoming, arguments: {"uri": "fd:29"} + +{"timestamp": {"seconds": 1677661413, "microseconds": 275227}, "event": "MIGRATION", "data": {"status": "setup"}} + +{"timestamp": {"seconds": 1677661413, "microseconds": 275600}, "event": "MIGRATION", "data": {"status": "active"}} + +2023-03-01T09:03:33.316549Z qemu-system-x86_64: error while loading state for instance 0x0 of device 'kvm-tpr-opt' + +2023-03-01T09:03:33.317076Z qemu-system-x86_64: load of migration failed: Operation not permitted +{"timestamp": {"seconds": 1677661413, "microseconds": 317297}, "event": "MIGRATION", "data": {"status": "failed"}} diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1530246 b/results/classifier/deepseek-r1:14b/output/KVM/1530246 new file mode 100644 index 00000000..1f62992a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1530246 @@ -0,0 +1,25 @@ + +Suppressing kvm rdmsr errors to console + +I am seeing numerous kvm rdmsr messages logged to /dev/tty1 (console), and would like to know how to suppress these messages. I've attempted "echo 1 > /sys/module/kvm/parameters/ignore_msrs" and the messages still appear on tty1. + +I'm seeing the following rdmsr messages: +kvm [22212]: vcpu0 ignored rdmsr: 0x606 +kvm [22212]: vcpu0 ignored rdmsr: 0x611 +kvm [22212]: vcpu0 ignored rdmsr: 0x639 +kvm [22212]: vcpu0 ignored rdmsr: 0x641 +kvm [22212]: vcpu0 ignored rdmsr: 0x619 +kvm [22212]: vcpu0 ignored rdmsr: 0x1ad + + +The following QEMU/KVM RPMs are installed: +ipxe-roms-qemu-20130517-7.gitc4bce43.el7.noarch +libvirt-daemon-driver-qemu-1.2.17-13.el7_2.2.x86_64 +libvirt-daemon-kvm-1.2.17-13.el7_2.2.x86_64 +qemu-img-ev-2.3.0-31.el7_2.4.1.x86_64 +qemu-kvm-common-ev-2.3.0-31.el7_2.4.1.x86_64 +qemu-kvm-ev-2.3.0-31.el7_2.4.1.x86_64 +qemu-kvm-tools-ev-2.3.0-31.el7_2.4.1.x86_64 + +uname -a +Linux server 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1534 b/results/classifier/deepseek-r1:14b/output/KVM/1534 new file mode 100644 index 00000000..7bd9c68a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1534 @@ -0,0 +1,2 @@ + +usermode emulation warns about features that are system-only (x2apic, tsc-deadline, pcid, invpcid) diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1534382 b/results/classifier/deepseek-r1:14b/output/KVM/1534382 new file mode 100644 index 00000000..c532bdb7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1534382 @@ -0,0 +1,21 @@ + +loadvm makes Windows 7 x86 guest crash with some CPUs + +Running qemu with kvm enabled and -cpu set to some of the more "modern" CPUs, +and having Windows 7 x86 as the guest. + +After guest OS loads, start some app (I started "cmd"), then do "savevm". +After that, do some more activity (I closed cmd window and opened IE), +then do "loadvm" of the previously saved snapshot. + +loadvm shows briefly the state that the system was in at the snapshot time, +then guest OS crashes (blue screen). + +Originally I saw this problem on qemu 1.4.0, +then I also tried qemu 2.5.0 and found the same problem. + +The CPUs that I tried were mostly those that support NX bit (core2duo, +qemu64, kvm64, Nehalem, etc.) + +If I use the default CPU, or some other like qemu32/kvm32, +the problem does not occur. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1536487 b/results/classifier/deepseek-r1:14b/output/KVM/1536487 new file mode 100644 index 00000000..b225eee1 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1536487 @@ -0,0 +1,24 @@ + +Unable to migrate pc-i440fx-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1 + +When migrating a pc-i440fc-2.4 KVM guest from QEMU 2.5.0 to QEMU 2.4.1, the target QEMU errors out: + + qemu-system-x86_64: error while loading state for instance 0x0 of device 'fw_cfg' + +This appears to be related to the addition of a DMA interface to fw_cfg last October: + + http://lists.nongnu.org/archive/html/qemu-devel/2015-10/msg04568.html + +"info qtree" on the source QEMU shows that the DMA interface for fw_cfg had been enabled: + + bus: main-system-bus + type System + ... + dev: fw_cfg_io, id "" + iobase = 1296 (0x510) + dma_iobase = 1300 (0x514) + dma_enabled = true + +Incidentally, this guest had just undergone a migration from QEMU 2.4.0 to QEMU 2.5.0, so it looks like DMA was enabled simply through the migration. + +It seems to me that the DMA interface for fw_cfg should only be enabled on pc-i440fx-2.5 machines or higher. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1541643 b/results/classifier/deepseek-r1:14b/output/KVM/1541643 new file mode 100644 index 00000000..5ebd1bda --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1541643 @@ -0,0 +1,8 @@ + +IA32_FEATURE_CONTROL MSR unset for nested virtualization + +I enabled nested virtualization for the kvm_intel module, and passed -enable-kvm and -cpu host to qemu. However, the qemu BIOS did not set IA32_FEATURE_CONTROL MSR (index 0x3a) to a non-zero value allow VMXON. According to the Intel manual Section 23.7 ENABLING AND ENTERING VMX OPERATION: "To enable VMX support in a platform, BIOS must set bit 1, bit 2, or both (see below), as well as the lock bit." + +I noticed an old mailing list thread on this (https://lists.nongnu.org/archive/html/qemu-devel/2015-01/msg01372.html), but I wanted to point out that the Intel manual (and all the physical hardware I've tested) specifically contradicts this response. + +Tested on kernel 4.3.3 and qemu 2.4.1. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1559 b/results/classifier/deepseek-r1:14b/output/KVM/1559 new file mode 100644 index 00000000..14599f74 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1559 @@ -0,0 +1,8 @@ + +7.2 (regression?): ppc64 KVM-HV hangs during boot +Description of problem: +qemu 7.2.0 hangs at " * Mounting ZFS filesystem(s) ..." whereas 7.1.0 would fully boot. + +Without -smp, sometimes gets further and hangs later on at " * Seeding random number generator ..." +Additional information: +7.1.0 used to work before upgrading to 7.2.0, but would hang randomly after booting (usually during my benchmark). Not sure if related. Unfortunately, after downgrading back to 7.1.0, it also now hangs the same way as 7.2.0 does. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1596579 b/results/classifier/deepseek-r1:14b/output/KVM/1596579 new file mode 100644 index 00000000..a13eeb3d --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1596579 @@ -0,0 +1,27 @@ + +segfault upon reboot + +[ 31.167946] VFIO - User Level meta-driver version: 0.3 +[ 34.969182] kvm: zapping shadow pages for mmio generation wraparound +[ 43.095077] vfio-pci 0000:1a:00.0: irq 50 for MSI/MSI-X +[166493.891331] perf interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 50000 +[315765.858431] qemu-kvm[1385]: segfault at 0 ip (null) sp 00007ffe5430db18 error 14 +[315782.002077] vfio-pci 0000:1a:00.0: transaction is not cleared; proceeding with reset anyway +[315782.910854] mptsas 0000:1a:00.0: Refused to change power state, currently in D3 +[315782.911236] mptbase: ioc1: Initiating bringup +[315782.911238] mptbase: ioc1: WARNING - Unexpected doorbell active! +[315842.957613] mptbase: ioc1: ERROR - Failed to come READY after reset! IocState=f0000000 +[315842.957670] mptbase: ioc1: WARNING - ResetHistory bit failed to clear! +[315842.957675] mptbase: ioc1: ERROR - Diagnostic reset FAILED! (ffffffffh) +[315842.957717] mptbase: ioc1: WARNING - NOT READY WARNING! +[315842.957720] mptbase: ioc1: ERROR - didn't initialize properly! (-1) +[315842.957890] mptsas: probe of 0000:1a:00.0 failed with error -1 + +The qemu-kvm segfault happens when I issue a reboot on the Windows VM. The card I have is: +1a:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev ff) + +I have two of these cards (bought with many years difference), exact same model, and they fail the same way. I'm using PCI passthrough on this card for access to the tape drive. +This is very easy to reproduce, so feel free to let me know what to try. +Kernel 3.10.0-327.18.2.el7.x86_64 (Centos 7.2.1511). +qemu-kvm-1.5.3-105.el7_2.4.x86_64 +Reporting it here because of the segfault, but I guess I might have to open a bug report with mptbase as well? \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1641 b/results/classifier/deepseek-r1:14b/output/KVM/1641 new file mode 100644 index 00000000..0c6e5514 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1641 @@ -0,0 +1,25 @@ + +[abrt] qemu-system-x86-core: do_patch_instruction(): qemu-system-x86_64 killed by SIGABRT +Description of problem: +Copied from downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=2195952 + +Description of problem: +Virtualizing a Windows XP system which tried to reboot. + +Version-Release number of selected component: +qemu-system-x86-core-2:7.2.1-1.fc38 + +Additional info: +reason: qemu-system-x86_64 killed by SIGABRT +backtrace_rating: 4 +crash_function: do_patch_instruction +comment: Virtualizing a Windows XP system which tried to reboot. + +Truncated backtrace: +Thread no. 1 (6 frames) + #4 do_patch_instruction at ../hw/i386/kvmvapic.c:439 + #5 process_queued_cpu_work at ../cpus-common.c:347 + #6 qemu_wait_io_event at ../softmmu/cpus.c:435 + #7 kvm_vcpu_thread_fn at ../accel/kvm/kvm-accel-ops.c:56 + #8 qemu_thread_start at ../util/qemu-thread-posix.c:505 + #10 clone3 at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1658141 b/results/classifier/deepseek-r1:14b/output/KVM/1658141 new file mode 100644 index 00000000..116f3449 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1658141 @@ -0,0 +1,45 @@ + +QEMU's default msrs handling causes Windows 10 64 bit to crash + +Wine uses QEMU to run its conformance test suite on Windows virtual machines. Wine's conformance tests check the behavior of various Windows APIs and verify that they behave as expected. + +One such test checks handling of exceptions down. When run on Windows 10 64 bit in QEMU it triggers a "KMOD_EXCEPTION_NOT_HANDLED" BSOD in the VM. See: +https://bugs.winehq.org/show_bug.cgi?id=40240 + + +To reproduce this bug: +* Pick a Windows 10 64 bit VM on an Intel host. + +* Start the VM. I'm pretty sure any qemu command will do but here's what I used: + qemu-system-x86_64 -machine pc-i440fx-2.1,accel=kvm -cpu core2duo,+nx -m 2048 -hda /var/lib/libvirt/images/wtbw1064.qcow2 + +* Grab the attached source code. The tar file is a bit big at 85KB because I had to include some Wine headers. However the source file proper, exception.c, is only 85 lines, including the LGPL header. + +* Compile the source code with MinGW by typing 'make'. This produces a 32 bit exception.exe executable. I'll attach it for good measure. + +* Put exception.exe on the VM and run it. + + +After investigation it turns out this happens: + * Only for Windows 10 64 bit guests. Windows 10 32 bit and older Windows versions are unaffected. + + * Only on Intel hosts. At least both my Xeon E3-1226 v3 and i7-4790K hosts are impacted but not my Opteron 6128 one. + + * It does not seem to depend on the emulated CPU type: on the Intel hosts this happened with both +core2duo,nx and 'copy the host configuration' and did not depend on the number of emulated cpus/cores. + + * This happened with both QEMU 2.1 and 2.7, and both the 3.16.0 and 4.8.11 Linux kernels, both on Debian 8.6 and Debian Testing. + + +After searching for quite some time I discovered that the kvm kernel module was sneaking the following messages into /var/log/syslog precisely when the BSOD happens: + +Dec 16 13:43:48 vm3 kernel: [ 191.624802] kvm [2064]: vcpu0, guest rIP: 0xfffff803cb3c0bf3 kvm_set_msr_common: MSR_IA32_DEBUGCTLMSR 0x1, nop +Dec 16 13:43:48 vm3 kernel: [ 191.624835] kvm [2064]: vcpu0, guest rIP: 0xfffff803cb3c0c5c unhandled rdmsr: 0x1c9 + +A search on the Internet turned up a post suggesting to change kvm's ignore_msrs setting: + + echo 1 >/sys/module/kvm/parameters/ignore_msrs + +https://www.reddit.com/r/VFIO/comments/42dj7n/some_games_crash_to_biosboot_on_launch/ + +This does actually work and provides a workaround at least. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1661386 b/results/classifier/deepseek-r1:14b/output/KVM/1661386 new file mode 100644 index 00000000..cd2eec7c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1661386 @@ -0,0 +1,58 @@ + +Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed + +Hello, + + +I see the following when try to run qemu from master as the following: + +# ./x86_64-softmmu/qemu-system-x86_64 --version +QEMU emulator version 2.8.50 (v2.8.0-1006-g4e9f524) +Copyright (c) 2003-2016 Fabrice Bellard and the QEMU Project developers +# ./x86_64-softmmu/qemu-system-x86_64 -machine accel=kvm -nodefaults +-no-reboot -nographic -cpu host -vga none -kernel .build.kernel.kvm +-initrd .build.initrd.kvm -append 'panic=1 no-kvmclock console=ttyS0 +loglevel=7' -m 1024 -serial stdio +qemu-system-x86_64: /home/matwey/lab/qemu/target/i386/kvm.c:1849: +kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed. + +First broken commit has been bisected: + +commit 48e1a45c3166d659f781171a47dabf4a187ed7a5 +Author: Paolo Bonzini <email address hidden> +Date: Wed Mar 30 22:55:29 2016 +0200 + + target-i386: assert that KVM_GET/SET_MSRS can set all requested MSRs + + This would have caught the bug in the previous patch. + + Signed-off-by: Paolo Bonzini <email address hidden> + +My cpuinfo is the following: + +processor : 0 +vendor_id : GenuineIntel +cpu family : 6 +model : 44 +model name : Intel(R) Xeon(R) CPU X5675 @ 3.07GHz +stepping : 2 +microcode : 0x14 +cpu MHz : 3066.775 +cache size : 12288 KB +physical id : 0 +siblings : 2 +core id : 0 +cpu cores : 2 +apicid : 0 +initial apicid : 0 +fpu : yes +fpu_exception : yes +cpuid level : 11 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable nonstop_tsc aperfmperf pni pclmulqdq vmx ssse3 cx16 sse4_1 sse4_2 popcnt aes hypervisor lahf_lm ida arat epb dtherm tpr_shadow vnmi ept vpid +bugs : +bogomips : 6133.55 +clflush size : 64 +cache_alignment : 64 +address sizes : 40 bits physical, 48 bits virtual +power management: \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1665 b/results/classifier/deepseek-r1:14b/output/KVM/1665 new file mode 100644 index 00000000..6564400f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1665 @@ -0,0 +1,2 @@ + +When using the"yum install qemu-kvm" command in in rhel 9 , it is not possible to proceed past the "Windows Installer Select Disk" page by iso install diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1682128 b/results/classifier/deepseek-r1:14b/output/KVM/1682128 new file mode 100644 index 00000000..16736185 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1682128 @@ -0,0 +1,6 @@ + +solaris can't power off + +I have created solaris 10 VM on KVM. Everything in VM is running OK, but finally I use shell command ‘poweroff’ or ‘init 5’, the solaris VM system could’t be poweroff but with promoting me the message: perss any key to reboot ….. + +but on Xen, solaris can be powerofff \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1686 b/results/classifier/deepseek-r1:14b/output/KVM/1686 new file mode 100644 index 00000000..1367b293 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1686 @@ -0,0 +1,44 @@ + +VPS does not boots with CPU Model QEMU64 or KVM64 +Description of problem: + +Steps to reproduce: +1. Boot the VPS using AlmaLinux 9 ISO / image and it boots to kernel panic +Additional information: +VNC shows this message : + +[ 1.749935] do_exit.cold+0x14/0x9f + +[1.7502581 do_group_exit+0x33/0xa0 + +1.7506001 _x64_sys_exit_group+0x14/0x20 + +1.7510081 do_syscall 64+0x5c/0x90 + +[1.751361] ? syscall_exit_to_user_mode+0x12/0x30 + +[1.7517911 ? do_syscall_64+0x69/0x90 + +[1.752131] ? do_user_addr_fault+0x1d8/0x698 + +[1.7525091 ? exc_page_fault+0x62/0x150 1.752896] entry_SYSCALL_64_after_hwframe+ +0x63/0xcd + +[1.753612] RIP: 0033:0x7fb0e95b62d1 + +[ 1.7539561 Code: c3 of 1f 84 00 00 00 00 00 f3 Of le fa be e7 00 00 00 ba 3c 00 00 00 eb Od 89 de Of 05 48 3d 00 fe ff ff 77 1c f4 89 fe of 05 <48> 3d 00 fe ff ff 76 e7 f7 d8 89 05 ff fe 00 00 eb dd of 1f 44 00 + +[ 1.755047] RSP: 002b:00007ffe484df 288 EFLAGS: 00000246 ORIG_RAX: 00000000000 + +000e7 + +[ 1.755590] RAX: fffff ffffda RBX: 00007fb0e95b0f30 RCX: 00007fb0e95b62d1 1.756100] RDX: 000000000000003c RSI: 00000000000000e7 RDI: 000000000000007f + +[1.756565] RBP: 00007ffe484df410 R08: 00007ffe484dedf9 R09: 0000000000000000 + +[ 1.757034] R10: 00000000ffffffff R11: 0000000000000246 R12: 00007fb0e958f000 + +[ 1.7574981 R13: 0000002300000007 R14: 0000000000000007 R15: 00007ffe484df420 + +[ 1.7579921 Kernel Offset: 0x3aa00000 from Oxffffffff81000000 (relocation ran ge: 0xffffffff80000000-0xffffffffbfffffff) + +[ 1.7589051---[ end Kernel panic code=0x00007f00 --- not syncing: Attempted to kill init! exit diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1686350 b/results/classifier/deepseek-r1:14b/output/KVM/1686350 new file mode 100644 index 00000000..f5ad31d1 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1686350 @@ -0,0 +1,48 @@ + +[KVM] The qemu ‘-cpu’ option not have skylake server cpu model + +Environment: +------------------- +KVM commit/branch: bd17117b/next +Qemu commit/branch: cd1ea508/master +Host OS: RHEL7.3 ia32e +Host Kernel:4.11.0-rc3 +Bug detailed description: +---------------------------------- +In latest qemu commit the qemu still not have skylake server cpu model +Reproduce steps: +------------------------- +[root@skl-2s2 ~]# qemu-system-x86_64 -cpu help +Available CPUs: +x86 486 +x86 Broadwell-noTSX Intel Core Processor (Broadwell, no TSX) +x86 Broadwell Intel Core Processor (Broadwell) +x86 Conroe Intel Celeron_4x0 (Conroe/Merom Class Core 2) +x86 Haswell-noTSX Intel Core Processor (Haswell, no TSX) +x86 Haswell Intel Core Processor (Haswell) +x86 IvyBridge Intel Xeon E3-12xx v2 (Ivy Bridge) +x86 Nehalem Intel Core i7 9xx (Nehalem Class Core i7) +x86 Opteron_G1 AMD Opteron 240 (Gen 1 Class Opteron) +x86 Opteron_G2 AMD Opteron 22xx (Gen 2 Class Opteron) +x86 Opteron_G3 AMD Opteron 23xx (Gen 3 Class Opteron) +x86 Opteron_G4 AMD Opteron 62xx class CPU +x86 Opteron_G5 AMD Opteron 63xx class CPU +x86 Penryn Intel Core 2 Duo P9xxx (Penryn Class Core 2) +x86 SandyBridge Intel Xeon E312xx (Sandy Bridge) +x86 Skylake-Client Intel Core Processor (Skylake) +x86 Westmere Westmere E56xx/L56xx/X56xx (Nehalem-C) +x86 athlon QEMU Virtual CPU version 2.5+ +x86 core2duo Intel(R) Core(TM)2 Duo CPU T7700 @ 2.40GHz +x86 coreduo Genuine Intel(R) CPU T2600 @ 2.16GHz +x86 kvm32 Common 32-bit KVM processor +x86 kvm64 Common KVM processor +x86 n270 Intel(R) Atom(TM) CPU N270 @ 1.60GHz +x86 pentium +x86 pentium2 +x86 pentium3 +x86 phenom AMD Phenom(tm) 9550 Quad-Core Processor +x86 qemu32 QEMU Virtual CPU version 2.5+ +x86 qemu64 QEMU Virtual CPU version 2.5+ +x86 base base CPU model type with no features enabled +x86 host KVM processor with all supported host features (only available in KVM mode) +x86 max Enables all features supported by the accelerator in the current host \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1687653 b/results/classifier/deepseek-r1:14b/output/KVM/1687653 new file mode 100644 index 00000000..5e295586 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1687653 @@ -0,0 +1,66 @@ + +QEMU-KVM / detect_zeroes causes KVM to start unlimited number of threads on Guest-Sided High-IO with big Blocksize + +QEMU-KVM in combination with "detect_zeroes=on" makes a Guest able to DoS the Host. This is possible if the Host itself has "detect_zeroes" enabled and the Guest writes a large Chunk of data with a huge blocksize onto the drive. + +E.g.: dd if=/dev/zero of=/tmp/DoS bs=1G count=1 oflag=direct + +All QEMU-Versions after implementation of detect_zeroes are affected. Prior are unaffected. This is absolutely critical, please fix this ASAP! + +##### + +Provided by Dominik Csapak: + +source , bs , count , O_DIRECT, behaviour + +urandom , bs 1M, count 1024, O_DIRECT: OK +file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1M, count 1024, O_DIRECT: OK +zero file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1G, count 1, O_DIRECT: NOT OK +zero file , bs 1G, count 1, O_DIRECT: NOT OK +zero file , bs 1G, count 1, no O_DIRECT: NOT OK +rand file , bs 1G, count 1, O_DIRECT: OK +rand file , bs 1G, count 1, no O_DIRECT: OK + +discard on: + +urandom , bs 1M, count 1024, O_DIRECT: OK +rand file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1M, count 1024, O_DIRECT: OK +zero file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1G, count 1, O_DIRECT: NOT OK +zero file , bs 1G, count 1, O_DIRECT: NOT OK +zero file , bs 1G, count 1, no O_DIRECT: NOT OK +rand file , bs 1G, count 1, O_DIRECT: OK +rand file , bs 1G, count 1, no O_DIRECT: OK + +detect_zeros off: + +urandom , bs 1M, count 1024, O_DIRECT: OK +rand file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1M, count 1024, O_DIRECT: OK +zero file , bs 1M, count 1024, O_DIRECT: OK +/dev/zero , bs 1G, count 1, O_DIRECT: OK +zero file , bs 1G, count 1, O_DIRECT: OK +zero file , bs 1G, count 1, no O_DIRECT: OK +rand file , bs 1G, count 1, O_DIRECT: OK +rand file , bs 1G, count 1, no O_DIRECT: OK + +##### + +Provided by Florian Strankowski + +bs - count - io-threads + +512K - 2048 - 2 +1M - 1024 - 2 +2M - 512 - 4 +4M - 256 - 6 +8M - 128 - 10 +16M - 64 - 18 +32M - 32 - uncountable + +Please refer to further information here: + +https://bugzilla.proxmox.com/show_bug.cgi?id=1368 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1688 b/results/classifier/deepseek-r1:14b/output/KVM/1688 new file mode 100644 index 00000000..33fffa33 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1688 @@ -0,0 +1,34 @@ + +target/riscv KVM_RISCV_SET_TIMER macro is not configured correctly +Description of problem: +When riscv kvm vm state changed, guest virtual time would stop/continue. But KVM_RISCV_SET_TIMER is wrong, qemu-kvm can only set 'time'. +Steps to reproduce: +1.start host kernel +2.start qemu-kvm +Additional information: +Below code has some probelm: +``` +=================================================================== +#define KVM_RISCV_SET_TIMER(cs, env, name, reg) \ + do { \ + int ret = kvm_set_one_reg(cs, RISCV_TIMER_REG(env, time), ®); \ + +=================================================================== +``` +I think it should be like this: + +``` +diff --git a/target/riscv/kvm.c b/target/riscv/kvm.c +index 30f21453d6..0c567f668c 100644 +--- a/target/riscv/kvm.c ++++ b/target/riscv/kvm.c +@@ -99,7 +99,7 @@ static uint64_t kvm_riscv_reg_id(CPURISCVState *env, uint64_t type, + + #define KVM_RISCV_SET_TIMER(cs, env, name, reg) \ + do { \ +- int ret = kvm_set_one_reg(cs, RISCV_TIMER_REG(env, time), ®); \ ++ int ret = kvm_set_one_reg(cs, RISCV_TIMER_REG(env, name), ®); \ + if (ret) { \ + abort(); \ + } \ +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1699567 b/results/classifier/deepseek-r1:14b/output/KVM/1699567 new file mode 100644 index 00000000..1cdbb028 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1699567 @@ -0,0 +1,16 @@ + +Qemu does not force SSE data alignment + +I have an OS that tries to use SSE operations. It works fine in qemu. But it crashes when I try to run the OS at the host cpu using KVM. + +The instruction that crahes with #GP(0) is + movaps ADDR,%xmm0 + +The documentation says ADDR has to be 16-bytes alignment otherwise #GP is generated. And indeed the problem was with the data alignment. After adjusting it at my side the OS works fine both with Qemu and KVM. + +It would be great if QEMU followed specification more closely and forced SSE data alignment requirements. It will help to catch alignment issues early and debug it easier. + + +$ qemu-system-x86_64 -version +QEMU emulator version 2.9.50 (v2.9.0-1363-g95eef1c68b) +Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1705717 b/results/classifier/deepseek-r1:14b/output/KVM/1705717 new file mode 100644 index 00000000..5ad36193 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1705717 @@ -0,0 +1,50 @@ + +Live migration fails with 'host' cpu when KVM is inserted with nested=1 + +Qemu v2.9.0 +Linux kernel 4.9.34 + +Live migration(pre-copy) being done from one physical host to another: + +Source Qemu: +sudo qemu-system-x86_64 -drive file=${IMAGE_DIR}/${IMAGE_NAME},if=virtio -m 2048 -smp 1 -net nic,model=virtio,macaddr=${MAC} -net tap,ifname=qtap0,script=no,downscript=no -vnc :1 --enable-kvm -cpu kvm64 -qmp tcp:*:4242,server,nowait + +And KVM is inserted with nested=1 on both source and destination machine. + +Migration fails with a nested specific assertion failure on destination at target/i386/kvm.c +1629 + +Migration is successful in the following cases- + +A) cpu model is 'host' and kvm is inserted without nested=1 parameter +B) If instead of 'host' cpu model, 'kvm64' is used (KVM nested=1) +C) If instead of 'host' cpu model, 'kvm64' is used (KVM nested=0) +D) Between an L0 and a guest Hypervisor L1, with 'kvm64' as CPU type (and nested=1 for L0 KVM) + +Physical host(s)- +$ lscpu +Architecture: x86_64 +CPU op-mode(s): 32-bit, 64-bit +Byte Order: Little Endian +CPU(s): 12 +On-line CPU(s) list: 0-11 +Thread(s) per core: 1 +Core(s) per socket: 6 +Socket(s): 2 +NUMA node(s): 2 +Vendor ID: GenuineIntel +CPU family: 6 +Model: 62 +Model name: Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz +Stepping: 4 +CPU MHz: 1200.091 +CPU max MHz: 2600.0000 +CPU min MHz: 1200.0000 +BogoMIPS: 4203.28 +Virtualization: VT-x +L1d cache: 32K +L1i cache: 32K +L2 cache: 256K +L3 cache: 15360K +NUMA node0 CPU(s): 0-5 +NUMA node1 CPU(s): 6-11 +Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm epb tpr_shadow vnmi flexpriority ept vpid fsgsbase smep erms xsaveopt dtherm ida arat pln pts \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1707274 b/results/classifier/deepseek-r1:14b/output/KVM/1707274 new file mode 100644 index 00000000..53b759c5 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1707274 @@ -0,0 +1,7 @@ + +Segfaults inside QEMU + +I'm running a server with QEMU emulator version 2.9.0. Although i gave the machine plenty RAM it begins segfaulting some processes after some hours which ends in a complete crash. +This is the commandline from libvirt: + +/usr/bin/qemu-system-x86_64-nameguest=server,debug-threads=on-S-objectsecret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-2-server/master-key.aes-machinepc-i440fx-2.9,accel=kvm,usb=off,dump-guest-core=off-cpuhost-m8192-realtimemlock=off-smp4,sockets=4,cores=1,threads=1-uuid5329bfd3-b947-473b-9880-d95b4ca78f28-no-user-config-nodefaults-chardevsocket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-2-server/monitor.sock,server,nowait-monchardev=charmonitor,id=monitor,mode=control-rtcbase=utc,driftfix=slew-globalkvm-pit.lost_tick_policy=delay-no-hpet-no-shutdown-globalPIIX4_PM.disable_s3=1-globalPIIX4_PM.disable_s4=1-bootstrict=on-deviceich9-usb-ehci1,id=usb,bus=pci.0,addr=0x9.0x7-deviceich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pci.0,multifunction=on,addr=0x9-deviceich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pci.0,addr=0x9.0x1-deviceich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pci.0,addr=0x9.0x2-deviceahci,id=sata0,bus=pci.0,addr=0x6-devicevirtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x5-drivefile=/mnt/htpc/windows/VM/disks/qcow2/server-boot.qcow2,format=qcow2,if=none,id=drive-virtio-disk0-devicevirtio-blk-pci,scsi=off,bus=pci.0,addr=0xa,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1-drivefile=/dev/sda,format=raw,if=none,id=drive-virtio-disk1-devicevirtio-blk-pci,scsi=off,bus=pci.0,addr=0xb,drive=drive-virtio-disk1,id=virtio-disk1-netdevtap,fd=24,id=hostnet0,vhost=on,vhostfd=26-devicevirtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:12:34:56,bus=pci.0,addr=0x3-spiceport=5902,addr=127.0.0.1,disable-ticketing,image-compression=off,seamless-migration=on-deviceqxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2-devicevirtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8-msgtimestamp=on \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1721221 b/results/classifier/deepseek-r1:14b/output/KVM/1721221 new file mode 100644 index 00000000..67d81d5f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1721221 @@ -0,0 +1,56 @@ + +PCI-E passthrough of Nvidia GTX GFX card to Win 10 guest fails with "kvm_set_phys_mem: error registering slot: Invalid argument" + +Problem: +Passthrough of a PCI-E Nvidia GTX 970 GFX card to a Windows 10 guest from a Debian Stretch host fails after recent changes to kvm in QEMU master/trunk. Before this recent commit, everything worked as expected. + +QEMU Version: +Master/trunk pulled from github 4/10/17 ( git reflog: d147f7e815 HEAD@{0} ) + +Host: +Debian Stretch kernel SMP Debian 4.9.30-2+deb9u5 (2017-09-19) x86_64 GNU/Linux + +Guest: +Windows 10 Professional + +Issue is with this commit: +https://github.com/qemu/qemu/commit/f357f564be0bd45245b3ccfbbe20ace08fe83ca8 + +Subsequent commit does not help: +https://github.com/qemu/qemu/commit/3110cdbd8a4845c5b5fb861b0a664c56d993dd3c#diff-7b7a17f6e8ba4195198dd685073f43cb + +Error output from qemu: +(qemu) kvm_set_phys_mem: error registering slot: Invalid argument + +QEMU commandline used: + +./sources/qemu/x86_64-softmmu/qemu-system-x86_64 -machine q35,accel=kvm -serial none -parallel none -name Windows \ +-enable-kvm -cpu host,kvm=off,hv_vendor_id=sugoidesu,-hypervisor -smp 6,sockets=1,cores=3,threads=2 \ +-m 8G -mem-path /dev/hugepages -mem-prealloc -balloon none \ +-drive if=pflash,format=raw,readonly,file=vms/ovmf-x64/ovmf-x64/OVMF_CODE-pure-efi.fd \ +-drive if=pflash,format=raw,file=vms/ovmf-x64/ovmf-x64/OVMF_VARS-pure-efi.fd \ +-rtc clock=host,base=localtime \ +-readconfig ./vms/q35-virtio-graphical.cfg \ +-object iothread,id=iothread0 -object iothread,id=iothread1 -object iothread,id=iothread2 -object iothread,id=iothread3 \ +-device virtio-scsi-pci,iothread=iothread0,id=scsi0 -device virtio-scsi-pci,iothread=iothread1,id=scsi1 -device virtio-scsi-pci,iothread=iothread2,id=scsi2 -device virtio-scsi-pci,iothread=iothread3,id=scsi3 \ +-device scsi-hd,bus=scsi0.0,drive=drive0,bootindex=1 -device scsi-hd,bus=scsi1.0,drive=drive1 -device scsi-hd,bus=scsi2.0,drive=drive2 -device scsi-hd,bus=scsi3.0,drive=drive3 -device scsi-hd,bus=scsi1.0,drive=drive4 -device scsi-hd,bus=scsi2.0,drive=drive5 -device scsi-hd,bus=scsi3.0,drive=drive6 -device scsi-hd,bus=scsi1.0,drive=drive7 -device scsi-hd,bus=scsi2.0,drive=drive8 -device scsi-hd,bus=scsi3.0,drive=drive9 \ +-drive if=none,id=drive0,file=vms/w10p64.qcow2,format=qcow2,cache=none,discard=unmap \ +-drive if=none,id=drive1,file=vms/w10p64-2.qcow2,format=qcow2,cache=none,discard=unmap \ +-drive if=none,id=drive2,file=/dev/mapper/w10p64-3,format=raw,cache=none \ +-drive if=none,id=drive3,file=vms/w10p64-4.qcow2,format=qcow2,cache=none \ +-drive if=none,id=drive4,file=vms/w10p64-5.qcow2,format=qcow2,cache=none \ +-drive if=none,id=drive5,file=vms/w10p64-6.qcow2,format=qcow2,cache=none,discard=unmap \ +-drive if=none,id=drive6,file=/dev/mapper/w10p64-7,format=raw,cache=none \ +-drive if=none,id=drive7,file=vms/w10p64-8.qcow2,format=qcow2,cache=none,discard=unmap \ +-device vfio-pci,host=01:00.0,multifunction=on,x-vga=on \ +-device vfio-pci,host=01:00.1,multifunction=on \ +-netdev type=tap,id=net1,ifname=tap1,script=no,downscript=no,vhost=on \ +-device virtio-net-pci,netdev=net1,mac=52:54:00:18:32:c9,bus=pcie.2,addr=00.0,ioeventfd=on \ +-device usb-host,bus=usb.0,hostbus=3,hostport=2.1 \ +-device usb-host,hostbus=3,hostport=2.2 \ +-device usb-host,bus=ich9-ehci-1.0,hostbus=3,hostport=2.4 \ +-object input-linux,id=kbd1,evdev=/dev/input/event0,grab_all=yes,repeat=on \ +-drive if=none,id=drive8,file=vms/w10p64.qcow2-9,format=qcow2,discard=unmap \ +-drive if=none,id=drive9,file=vms/w10p64-10.qcow2,format=qcow2,cache=none,discard=unmap \ +-device usb-host,bus=usb.0,hostbus=3,hostport=9 \ +-monitor stdio \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1722074 b/results/classifier/deepseek-r1:14b/output/KVM/1722074 new file mode 100644 index 00000000..f35932b8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1722074 @@ -0,0 +1,70 @@ + +warning: host doesn't support requested feature: CPUID.01H:ECX.vmx + +I encountered the bug today: + +warning: host doesn't support requested feature: CPUID.01H:ECX.vmx + +My Ubuntu have this version of QEMU installed: + +qemu-system-x86_64 --version + +QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.16), Copyright (c) 2003-2008 Fabrice Bellard + +And PC is a AMD Ryzen7 CPU built, and since it is not Intel CPU: + + +cat /proc/cpuinfo |more + +processor : 0 +vendor_id : AuthenticAMD +cpu family : 23 +model : 1 +model name : AMD Ryzen 7 1700X Eight-Core Processor +stepping : 1 +microcode : 0x800110e +cpu MHz : 2200.000 +cache size : 512 KB +physical id : 0 +siblings : 16 +core id : 0 +cpu cores : 8 +apicid : 0 +initial apicid : 0 +fpu : yes +fpu_exception : yes +cpuid level : 13 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov +pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp + lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf pni pclmulqdq +monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf +_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw s +kinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate +vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt +xsavec xgetbv1 xsaves clzero irperf arat npt lbrv svm_lock nrip_save tsc_scale v +mcb_clean flushbyasid decodeassists pausefilter pfthreshold avic overflow_recov +succor smca +bugs : fxsave_leak sysret_ss_attrs null_seg +bogomips : 6787.24 +TLB size : 2560 4K pages +clflush size : 64 +cache_alignment : 64 +address sizes : 48 bits physical, 48 bits virtual +power management: ts ttp tm hwpstate eff_freq_ro [13] [14] + +processor : 1 +vendor_id : AuthenticAMD +cpu family : 23 +model : 1 +model name : AMD Ryzen 7 1700X Eight-Core Processor +stepping : 1 +microcode : 0x800110e +cpu MHz : 2200.000 +cache size : 512 KB + +From other places, it can be seen that this is an AMD CPU issue: + +https://www.virtualmin.com/node/52227 + +not sure? \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1732959 b/results/classifier/deepseek-r1:14b/output/KVM/1732959 new file mode 100644 index 00000000..d1347e74 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1732959 @@ -0,0 +1,60 @@ + +[regression] stop/cont triggers clock jump proportional to host clock drift + +We (ab)use migration + block mirroring to perform transparent zero downtime VM backups. Basically: + +1) do a block mirror of the source VM's disk +2) migrate the source VM to a destination VM using the disk copy +3) cancel the block mirroring +4) resume the source VM +5) shut down the destination VM gracefully and move the disk to backup + +Relatively recently, the source VM's clock started jumping after step #4. More specifically, the clock jumps an amount of time proportional to the time since it was last migrated. With a week between migrations, clock jumps between ~2.5s and ~12s have been observed. For a particular host, the amount of clock jump is fairly consistent, but there is a large variation from one host to the next (this is likely down to hardware variations and the amount of NTP adjusted clock drift on the host). + +This is caused by a kernel regression which I was able to bisect. The result of the bisect was: + +108b249c453dd7132599ab6dc7e435a7036c193f is the first bad commit +commit 108b249c453dd7132599ab6dc7e435a7036c193f +Author: Paolo Bonzini <email address hidden> +Date: Thu Sep 1 14:21:03 2016 +0200 + + KVM: x86: introduce get_kvmclock_ns + + Introduce a function that reads the exact nanoseconds value that is + provided to the guest in kvmclock. This crystallizes the notion of + kvmclock as a thin veneer over a stable TSC, that the guest will + (hopefully) convert with NTP. In other words, kvmclock is *not* a + paravirtualized host-to-guest NTP. + + Drop the get_kernel_ns() function, that was used both to get the base + value of the master clock and to get the current value of kvmclock. + The former use is replaced by ktime_get_boot_ns(), the latter is + the purpose of get_kernel_ns(). + + This also allows KVM to provide a Hyper-V time reference counter that + is synchronized with the time that is computed from the TSC page. + + Reviewed-by: Roman Kagan <email address hidden> + Signed-off-by: Paolo Bonzini <email address hidden> + +I am able to reproduce the issue with much newer kernels as well, including 4.12.5 and 4.9.6. + +Reliably reproducing the problem in isolation is difficult, as one must run a VM for many hours before the clock jump from this bug is noticeable over the clock jump inherent with a pause and resume of the VM. The reproducer I am including is set to run the VM for 18 hours before migration and looks for >= 150 ms of clock jump. On different hardware, you may need to let the VM run for more than 18 hours to reliably reproduce the issue. + +To reproduce the issue, please see the attached reproducer. The host needs to have perl, screen and socat installed for the backup script to work. Both the host and guest need to be running NTP (and NTP must autostart at boot in the guest). The host needs to be able to SSH into the guest using SSH keys (to measure the clock jump), so you will need to configure the network and SSH keys appropriately, then change the hardcoded IP address in checktime.sh and test.sh. I have only tested with CentOS 7 guests. + +The qemu command that gets run is in .kvmscreen (the destination VM's command line is programmatically constructed from this command as well), you may need to tweak the bridge configuration. Also, although the reproducer is relatively self contained, it has several built in assumptions that will break if the image file is not in the /var/lib/kvm directory or if the monitor file is not in the /var/lib/kvm/monitor directory, or if the /backup directory does not exist. Finally, if you change the process name or socket name in .kvmscreen, you'll need to adjust the cleanup section in test.sh. + +With all of the above in place, run test.sh and check back in a little over 18 hours, part of the output should include something along these lines: + +Target not found (wanted 150, at 10) + +- or - + +Target found (wanted 150, found 340) + +If the target is reported as found, that means that we have probably reproduced the described issue. + +The version of QEMU in use does not appear to matter. At one point I tested every major version from 2.4 to 2.9 (inclusive) and reproduced the issue in all of them. + +This was initially observed on two different Gentoo hosts. I have also started to see this issue happening with four different RHEL 7 hosts as of the upgrade to RHEL 7.4. This is not too surprising as it appears that the above commit has been backported into RHEL 7. All hosts and guests are 64-bit. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1769053 b/results/classifier/deepseek-r1:14b/output/KVM/1769053 new file mode 100644 index 00000000..cef670d2 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1769053 @@ -0,0 +1,34 @@ + +Ability to control phys-bits through libvirt + +Attempting to start a KVM guest with more than 1TB of RAM fails. + +It looks like we might need some extra patches: https://lists.gnu.org/archive/html/qemu-discuss/2017-12/msg00005.html + +ProblemType: Bug +DistroRelease: Ubuntu 18.04 +Package: qemu-system-x86 1:2.11+dfsg-1ubuntu7 +ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 +Uname: Linux 4.15.0-20-generic x86_64 +ApportVersion: 2.20.9-0ubuntu7 +Architecture: amd64 +CurrentDesktop: Unity:Unity7:ubuntu +Date: Fri May 4 16:21:14 2018 +InstallationDate: Installed on 2017-04-05 (393 days ago) +InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) +MachineType: Dell Inc. XPS 13 9360 +ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash transparent_hugepage=madvise vt.handoff=1 +SourcePackage: qemu +UpgradeStatus: Upgraded to bionic on 2018-04-30 (3 days ago) +dmi.bios.date: 02/26/2018 +dmi.bios.vendor: Dell Inc. +dmi.bios.version: 2.6.2 +dmi.board.name: 0PF86Y +dmi.board.vendor: Dell Inc. +dmi.board.version: A00 +dmi.chassis.type: 9 +dmi.chassis.vendor: Dell Inc. +dmi.modalias: dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr: +dmi.product.family: XPS +dmi.product.name: XPS 13 9360 +dmi.sys.vendor: Dell Inc. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1779162 b/results/classifier/deepseek-r1:14b/output/KVM/1779162 new file mode 100644 index 00000000..19579f83 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1779162 @@ -0,0 +1,45 @@ + +qemu versions 2.10 and 2.11 have error during migration of larger guests + +== Comment: #0 - Christian Borntraeger - 2018-06-28 06:39:27 == +Migration fails with larger guests (e.g. 10GB) on a z system prints an error message in the log + +see /var/log/libvirt/qemu/... +[...] +qemu-system-s390x: KVM_S390_SET_CMMA_BITS failed: Bad address + +This messes up guest state for the CMMA values (guest data corruption) + +This is fixed with + +commit 46fa893355e0bd88f3c59b886f0d75cbd5f0bbbe +Author: Claudio Imbrenda <email address hidden> +AuthorDate: Thu Jan 18 18:51:44 2018 +0100 +Commit: Cornelia Huck <email address hidden> +CommitDate: Mon Jan 22 11:04:52 2018 +0100 + + s390x: fix storage attributes migration for non-small guests + + Fix storage attribute migration so that it does not fail for guests + with more than a few GB of RAM. + With such guests, the index in the buffer would go out of bounds, + usually by large amounts, thus receiving -EFAULT from the kernel. + Migration itself would be successful, but storage attributes would then + not be migrated completely. + + This patch fixes the out of bounds access, and thus migration of all + storage attributes when the guest have large amounts of memory. + + Cc: <email address hidden> + Signed-off-by: Claudio Imbrenda <email address hidden> + Fixes: 903fd80b03243476 ("s390x/migration: Storage attributes device") + Message-Id: <email address hidden> + Reviewed-by: Christian Borntraeger <email address hidden> + Signed-off-by: Cornelia Huck <email address hidden> + +This fix is part of 2.11.1 so the qemu in bionic is fine. +The qemu in artful, as well as the qemu in the cloud archives for 16.04 need this fix, so we have +affected qemus in 17.10 and 16.04. + +Regarding 16.04: +The bug only triggers for host kernels >= 4.13 - in other words when you combine HWE kernel with the qemu from the cloud archive. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1785734 b/results/classifier/deepseek-r1:14b/output/KVM/1785734 new file mode 100644 index 00000000..fe040888 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1785734 @@ -0,0 +1,76 @@ + +movdqu partial write at page boundary + +In TCG mode, when a 16-byte write instruction (such as movdqu) is executed at a page boundary and causes a page fault, a partial write is executed in the first page. See the attached code for an example. + +Tested on the qemu-3.0.0-rc1 release. + + +% gcc -m32 qemu-bug2.c && ./a.out && echo && qemu-i386 ./a.out +*(0x70000ff8+ 0) = aa +*(0x70000ff8+ 1) = aa +*(0x70000ff8+ 2) = aa +*(0x70000ff8+ 3) = aa +*(0x70000ff8+ 4) = aa +*(0x70000ff8+ 5) = aa +*(0x70000ff8+ 6) = aa +*(0x70000ff8+ 7) = aa +*(0x70000ff8+ 8) = 55 +*(0x70000ff8+ 9) = 55 +*(0x70000ff8+10) = 55 +*(0x70000ff8+11) = 55 +*(0x70000ff8+12) = 55 +*(0x70000ff8+13) = 55 +*(0x70000ff8+14) = 55 +*(0x70000ff8+15) = 55 +page fault: addr=0x70001000 err=0x7 +*(0x70000ff8+ 0) = aa +*(0x70000ff8+ 1) = aa +*(0x70000ff8+ 2) = aa +*(0x70000ff8+ 3) = aa +*(0x70000ff8+ 4) = aa +*(0x70000ff8+ 5) = aa +*(0x70000ff8+ 6) = aa +*(0x70000ff8+ 7) = aa +*(0x70000ff8+ 8) = 55 +*(0x70000ff8+ 9) = 55 +*(0x70000ff8+10) = 55 +*(0x70000ff8+11) = 55 +*(0x70000ff8+12) = 55 +*(0x70000ff8+13) = 55 +*(0x70000ff8+14) = 55 +*(0x70000ff8+15) = 55 + +*(0x70000ff8+ 0) = aa +*(0x70000ff8+ 1) = aa +*(0x70000ff8+ 2) = aa +*(0x70000ff8+ 3) = aa +*(0x70000ff8+ 4) = aa +*(0x70000ff8+ 5) = aa +*(0x70000ff8+ 6) = aa +*(0x70000ff8+ 7) = aa +*(0x70000ff8+ 8) = 55 +*(0x70000ff8+ 9) = 55 +*(0x70000ff8+10) = 55 +*(0x70000ff8+11) = 55 +*(0x70000ff8+12) = 55 +*(0x70000ff8+13) = 55 +*(0x70000ff8+14) = 55 +*(0x70000ff8+15) = 55 +page fault: addr=0x70001000 err=0x6 +*(0x70000ff8+ 0) = 77 +*(0x70000ff8+ 1) = 66 +*(0x70000ff8+ 2) = 55 +*(0x70000ff8+ 3) = 44 +*(0x70000ff8+ 4) = 33 +*(0x70000ff8+ 5) = 22 +*(0x70000ff8+ 6) = 11 +*(0x70000ff8+ 7) = 0 +*(0x70000ff8+ 8) = 55 +*(0x70000ff8+ 9) = 55 +*(0x70000ff8+10) = 55 +*(0x70000ff8+11) = 55 +*(0x70000ff8+12) = 55 +*(0x70000ff8+13) = 55 +*(0x70000ff8+14) = 55 +*(0x70000ff8+15) = 55 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1788098 b/results/classifier/deepseek-r1:14b/output/KVM/1788098 new file mode 100644 index 00000000..5ec03e2f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1788098 @@ -0,0 +1,12 @@ + +Avoid migration issues with aligned 2MB THB + +------- Comment From <email address hidden> 2018-08-20 17:12 EDT------- +Hi, in some environments it was observed that this qemu patch to enable THP made it more likely to hit guest migration issues, however the following kernel patch resolves those migration issues: + +https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next&id=c066fafc595eef5ae3c83ae3a8305956b8c3ef15 +KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix() + +Once merged upstream, it would be good to include that change as well to avoid potential migration problems. Should I open a new bug for that or is it better to track here? + +Note Paelzer: I have not seen related migration issues myself, but it seems reasonable and confirmed by IBM. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1792193 b/results/classifier/deepseek-r1:14b/output/KVM/1792193 new file mode 100644 index 00000000..3b78eae4 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1792193 @@ -0,0 +1,17 @@ + +AMD Athlon(tm) X2 Dual-Core QL-64 bug + +I upgrade my qemu 2.12.0-2 => 3.0.0-1. After that I can't load virtual machine with "-cpu host" option. Full command line is +qemu-system-x86_64 \ + -monitor stdio \ + -enable-kvm \ + -cpu host \ + -smp cpus=2 \ + -m 1G \ + -vga virtio \ + -display gtk,gl=on \ + -soundhw ac97 \ + -drive file=/ehdd/qemu/arch_hw_12_08_2018/arch_shrinked.raw,format=raw,if=virtio +I have Arch Linux on virtual machine. When I start QEMU, GRUB tries to load initial ramdisk and stops. System doesn't load. If I try to start virtual machine with "-cpu athlon" option then get the same bug. +I downgrade back to qemu 2.12.0-2 and virtual machine works fine, system loads. +My processor is AMD Athlon(tm) X2 Dual-Core QL-64. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1797262 b/results/classifier/deepseek-r1:14b/output/KVM/1797262 new file mode 100644 index 00000000..a73f5523 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1797262 @@ -0,0 +1,21 @@ + +qemu arm no longer able to boot RPI Kernels + +Since RPi Kernel 1.20170427, qemu is no longer able to emulate the Rasberry Pi, as the linux kernel is complaining about timing issues. + +Old kernel output - https://pastebin.com/wvkneNNF +New kernel output - https://pastebin.com/QTwgCkV2 + +Note that the actual error is caused by the kernel being unable to get the timing source for the mmc (Line 160), which causes an unable-to-mount-root panic. There are other issues with the serial port returning an invalid speed, which displays a divide-by-zero error, which is PROBABLY a symptom of the same root cause. + +This is simple to replicate - The last working kernel is available here: + +https://github.com/raspberrypi/firmware/tree/1.20170405/boot + +Download kernel7 and the dtb, and try to boot with (for example) + +qemu-system-aarch64 -M raspi2 -kernel kernel7.img -dtb bcm2709-rpi-2-b.dtb -serial stdio -sd noobs.img -append "root=/dev/mmcblk0p2 init=/bin/bash" + +This works, and boots successfully. + +However, if you replace the kernel7.img and dtb with ones taken from https://github.com/raspberrypi/firmware/tree/1.20170427/boot it will NOT boot because of various clock timing issues (as in the second paste) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1806040 b/results/classifier/deepseek-r1:14b/output/KVM/1806040 new file mode 100644 index 00000000..531c2bcc --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1806040 @@ -0,0 +1,16 @@ + +Nested VMX virtualization error on last Qemu versions + +Recently updated Qemu on a Sony VAIO sve14ag18m with Ubuntu Bionic 4.15.0-38 from Git + +After launching a few VMs, noticed that i could not create Snapshot due to this error: +"Nested VMX virtualization does not support live migration yet" + +I've created a new Windows 7 X64 machine with this compilation of Qemu and the problem persisted, so it's not because of the old machines. + +I launch Qemu with this params (I use them for malware analisys adn re...): +qemu-system-x86_64 -monitor stdio -display none -m 4096 -smp cpus=4 -usbdevice tablet -drive file=VM.img,index=0,media=disk,format=qcow2,cache=unsafe -net nic,macaddr="...." -net bridge,br=br0 -cpu host,-hypervisor,kvm=off -vnc 127.0.0.1:0 -enable-kvm + + +Deleting the changes made on this commit solved the problem, but I dont have idea what is this for, so... xDD +https://github.com/qemu/qemu/commit/d98f26073bebddcd3da0ba1b86c3a34e840c0fb8 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1814 b/results/classifier/deepseek-r1:14b/output/KVM/1814 new file mode 100644 index 00000000..d052049c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1814 @@ -0,0 +1,17 @@ + +`-M none` breaks on ARM64 platforms with max IPA size < 40 +Description of problem: +QEMU fails to initialize the KVM type properly when `-M none` is used. On ARM64, the KVM type sets the IPA size. Without that setting, the kernel defaults to 40 bits. This fails on machines which cannot support that IPA size, such as Apple M1 machines. + +This presumably happens because `virt_machine_class_init()` in `hw/arm/virt.c` never gets called in that case, which means it doesn't initialize `mc->kvm_type` to the correct callback to do the IPA check. + +Since the max IPA size is a property of the host CPU and must be queried properly for things to work at all, this logic should be invoked unconditionally for all machines, even `none`. + +This is breaking libvirt on Apple M1/M2 systems, since it uses `-M none,accel=kvm` for its KVM test, and when it fails it considers KVM support unavailable. See: https://gitlab.com/libvirt/libvirt/-/issues/365 +Steps to reproduce: +On any ARM64 machine: + +1. strace -e ioctl qemu-system-aarch64 -M none,accel=kvm 2>&1 | grep -C1 CREATE_VM +2. strace -e ioctl qemu-system-aarch64 -M virt,accel=kvm 2>&1 | grep -C1 CREATE_VM + +Observe that the first command line does not issue a `KVM_CAP_ARM_VM_IPA_SIZE` and does not set the machine type argument to `KVM_CREATE_VM`, while the second one does. On machines with <40 bit max IPA, the first invocation would fail to initialize KVM. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1836501 b/results/classifier/deepseek-r1:14b/output/KVM/1836501 new file mode 100644 index 00000000..5007dc84 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1836501 @@ -0,0 +1,34 @@ + +cpu_address_space_init fails with assertion + +qemu-system-arm does not start with version >= 2.6 and KVM enabled. + + cpu_address_space_init: Assertion `asidx == 0 || !kvm_enabled()' failed. + +Hardware is Odroid XU4 with Exynos with 4.9.61+ Tested with Debian Stretch (9) or Buster (10). + +Without KVM it is running fine but slow. I'm operating Debian Jessie with qemu 2.1 for a long time with KVM virtualization working flawlessly. When I upgraded to Stretch I ran into the trouble described before. I tried Debian Stretch and Buster with all Kernels provided by the Board manufacturer (Hardkernel). + +It seems to be related to the feature introduced in Version 2.6: +https://wiki.qemu.org/ChangeLog/2.6 +- Support for a separate EL3 address space + +KVM is enabled, so I assume the adress space index asidx to be causing the assert to fail. + +dmesg | grep -i KVM +[ 0.741714] kvm [1]: 8-bit VMID +[ 0.741721] kvm [1]: IDMAP page: 40201000 +[ 0.741729] kvm [1]: HYP VA range: c0000000:ffffffff +[ 0.742543] kvm [1]: Hyp mode initialized successfully +[ 0.742600] kvm [1]: vgic-v2@10484000 +[ 0.742924] kvm [1]: vgic interrupt IRQ16 +[ 0.742943] kvm [1]: virtual timer IRQ60 + +Full command line is: +qemu-system-arm -M vexpress-a15 -smp 2 -m 512 -cpu host -enable-kvm -kernel vmlinuz -initrd initrd.gz -dtb vexpress-v2p-ca15-tc1.dtb -device virtio-blk-device,drive=inst-blk -drive file=PATHTOFILE,id=inst-blk,if=none,format=raw -append "vga=normal rw console=ttyAMA0" -nographic + +Is there anything to do to understand, if this is a hardware related failure or probably just a missing parameter? + +Regards + +Lutz \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1837851 b/results/classifier/deepseek-r1:14b/output/KVM/1837851 new file mode 100644 index 00000000..376f55a3 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1837851 @@ -0,0 +1,12 @@ + +hv-tlbflush malfunctions on Intel host CPUs with neither EPT nor VPID (qemu-kvm) + +Enabling hv-tlbflush on older hosts using Intel CPUs supporting VT-x but neither EPT nor VPID will lead to bluescreens on the guest. + +It seems KVM only checks if EPT is available, and if it isn't it forcibly uses VPID. If that's *also* not available, it defaults to basically a no-op hypercall, though windows is expecting the TLB to be flushed. + +hv-tlbflush is pretty useless on machines not supporting these extensions anyway (only reasonably fix I can see would be to flush the *entire* TLB on tlbflush hypercall in KVM (i.e. a kernel fix), but that would remove any performance benefits), so I would suggest some kind of preliminary check and warning/error if hv-tlbflush is specified on such a host. + +All CPUs mentioned in this thread[0] are confirmed to be affected by the bug, and I have successfully reproduced it on an Intel Core2Duo E8500. + +[0] https://forum.proxmox.com/threads/windows-guest-bluescreen-with-proxmox-6.56053/ \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1848244 b/results/classifier/deepseek-r1:14b/output/KVM/1848244 new file mode 100644 index 00000000..db69739c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1848244 @@ -0,0 +1,12 @@ + +QEMU KVM IGD SandyBridge Passthrough crash + +I try to passthrough my Intel GPU with this command: + +qemu-system-x86_64 -nodefaults -parallel none -k de -rtc base=localtime -serial unix:/run/qemu/win7-serial.sock,server,nowait -monitor unix:/run/qemu/win7-monitor.sock,server,nowait -netdev user,id=net0 -device virtio-net-pci,netdev=net0,mac=52:54:00:00:00:07 -device vfio-pci,host=0000:00:02.0,addr=0x2 -device vfio-pci,host=0000:00:1b.0 -device virtio-keyboard-pci -device virtio-mouse-pci -object input-linux,id=kbd1,evdev=/dev/input/by-path/pci-0000:00:1a.0-usb-0:1.2.2:1.2-event-kbd,grab_all=on,repeat=on -object input-linux,id=mouse1,evdev=/dev/input/by-path/pci-0000:00:1a.0-usb-0:1.2.2:1.2-event-mouse -enable-kvm -cpu host -smp 4,sockets=1,cores=4,threads=1 -vga none -display none -m 2g -device virtio-blk-pci,drive=boot,bootindex=1 -drive file=/opt/vm/qcow2/win7.qcow2,format=qcow2,if=none,id=boot + +This ONLY works if i remove "-enable-kvm" else the windows (7 and 10) boot crashes in bluescreen "stop 0x0000003b" (probably while loading the intel gpu driver (intel graphics 3000). + +The system is an older ThinkPad T420 with Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz. + +CMDLINE: BOOT_IMAGE=/vmlinuz-linux root=LABEL=root rw ipv6.disable=0 net.ifnames=0 intel_iommu=on iommu=pt video=LVDS-1:d \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1848901 b/results/classifier/deepseek-r1:14b/output/KVM/1848901 new file mode 100644 index 00000000..0b887160 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1848901 @@ -0,0 +1,36 @@ + +kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28) + +=> QEMU process has stopped, return code: -6 + +Start QEMU with /usr/bin/qemu-system-x86_64 -name CiscoASAv9.8.1-1 -m 2048M -smp cpus=1 -enable-kvm -machine smm=off -boot order=c -drive 'file=/home/deemon/GNS3/projects/ASAv my ass/project-files/qemu/7725cdea-5e66-4777-b4dd-c3905f258394/hda_disk.qcow2,if=virtio,index=0,media=disk,id=drive0' -uuid 7725cdea-5e66-4777-b4dd-c3905f258394 -serial telnet:127.0.0.1:5000,server,nowait -monitor tcp:127.0.0.1:44629,server,nowait -net none -device e1000,mac=0c:7a:1d:83:94:00,netdev=gns3-0 -netdev socket,id=gns3-0,udp=127.0.0.1:10001,localaddr=127.0.0.1:10000 -device e1000,mac=0c:7a:1d:83:94:01,netdev=gns3-1 -netdev socket,id=gns3-1,udp=127.0.0.1:10003,localaddr=127.0.0.1:10002 -device e1000,mac=0c:7a:1d:83:94:02,netdev=gns3-2 -netdev socket,id=gns3-2,udp=127.0.0.1:10005,localaddr=127.0.0.1:10004 -device e1000,mac=0c:7a:1d:83:94:03,netdev=gns3-3 -netdev socket,id=gns3-3,udp=127.0.0.1:10007,localaddr=127.0.0.1:10006 -device e1000,mac=0c:7a:1d:83:94:04,netdev=gns3-4 -netdev socket,id=gns3-4,udp=127.0.0.1:10009,localaddr=127.0.0.1:10008 -device e1000,mac=0c:7a:1d:83:94:05,netdev=gns3-5 -netdev socket,id=gns3-5,udp=127.0.0.1:10011,localaddr=127.0.0.1:10010 -device e1000,mac=0c:7a:1d:83:94:06,netdev=gns3-6 -netdev socket,id=gns3-6,udp=127.0.0.1:10013,localaddr=127.0.0.1:10012 -device e1000,mac=0c:7a:1d:83:94:07,netdev=gns3-7 -netdev socket,id=gns3-7,udp=127.0.0.1:10015,localaddr=127.0.0.1:10014 -nographic + + +Execution log: +kvm_mem_ioeventfd_add: error adding ioeventfd: No space left on device (28) + +and then it just closes... + + + +[deemon@Zen ~]$ coredumpctl info 8638 + PID: 8638 (qemu-system-x86) + UID: 1000 (deemon) + GID: 1000 (deemon) + Signal: 6 (ABRT) + Timestamp: Sun 2019-10-20 04:27:29 EEST (5min ago) + Command Line: /usr/bin/qemu-system-x86_64 -name CiscoASAv9.8.1-1 -m 2048M -smp cpus=1 -enable-kvm -machine smm=off -boot order=c -drive file=/home/deemon/GNS3/projects/ASAv my ass/project-files/qemu> + Executable: /usr/bin/qemu-system-x86_64 + Control Group: /user.slice/user-1000.slice/session-2.scope + Unit: session-2.scope + Slice: user-1000.slice + Session: 2 + Owner UID: 1000 (deemon) + Boot ID: cd30f69a8d194359a31889dc7b6b026c + Machine ID: d0a2d74a5cd9430797d902f5237c448d + Hostname: Zen + Storage: /var/lib/systemd/coredump/core.qemu-system-x86.1000.cd30f69a8d194359a31889dc7b6b026c.8638.1571534849000000.lz4 (truncated) + Message: Process 8638 (qemu-system-x86) of user 1000 dumped core. + + Stack trace of thread 8642: + #0 0x00007f1a33609f25 n/a (n/a) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1850751 b/results/classifier/deepseek-r1:14b/output/KVM/1850751 new file mode 100644 index 00000000..2aef9e6a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1850751 @@ -0,0 +1,9 @@ + +kvm flag is not exposed by default + +Hi I found that the kvm flags is not exposed by default, but according to the source code, it should be exposed by default when the CPU Model is a X86CPU. + +we have to specifically add "kvm=on" in QEMU custom cpu args like this: +<qemu:arg value='host,kvm=on,+invtsc,+hypervisor'/> + +Also the libvirt can't expose kvm because this (libvirt assumes the kvm flag is exposed by default, only "kvm hidden = 'true'" can be used. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1859310 b/results/classifier/deepseek-r1:14b/output/KVM/1859310 new file mode 100644 index 00000000..4e6e1e0f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1859310 @@ -0,0 +1,21 @@ + +libvirt probing fails due to assertion failure with KVM and 'none' machine type + +Using libvirt on Ubuntu 19.10, I get the following error when I try to set <emulator> to the latest qemu from git (commit dc65a5bdc9): + + error: internal error: Failed to start QEMU binary /usr/local/bin/qemu-system-x86_64 for probing: /home/joey/git/qemu/target/i386/kvm.c:2176:kvm_arch_init: Object 0x564bfd5c3200 is not an instance of type x86-machine + +Qemu command line to reproduce: + + sudo x86_64-softmmu/qemu-system-x86_64 -machine 'none,accel=kvm' + +Commit ed9e923c3c (Dec 12, 2019) introduced the issue by removing an object_dynamic_cast call. In this scenario, kvm_arch_init is passed an instance of "none-machine" instead of "x86-machine". + +The following one-line change to target/i386/kvm.c reintroduces the cast: + + if (kvm_check_extension(s, KVM_CAP_X86_SMM) && ++ object_dynamic_cast(OBJECT(ms), TYPE_X86_MACHINE) && + x86_machine_is_smm_enabled(X86_MACHINE(ms))) { + smram_machine_done.notify = register_smram_listener; + qemu_add_machine_init_done_notifier(&smram_machine_done); + } \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1862874 b/results/classifier/deepseek-r1:14b/output/KVM/1862874 new file mode 100644 index 00000000..1eee5c74 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1862874 @@ -0,0 +1,67 @@ + +java may stuck for a long time in system mode with "-cpu max" + +Bug Description: +Run "java -version" in guest VM, java may stuck for a long time (several hours) and then recover. + +Steps to reproduce: +1. Launch VM by attached simple script: launch.sh +2. Execute "java -version" and then print "date" in a loop + while : + do + /home/bot/jdk/bin/java -version + date + done +3. A long time gap will be observed: may > 24 hours. + +Technical details: +* host: x86_64 Linux 4.15.0-70-generic +* qemu v4.2.0 +* java: tried two versions: openjdk-11-jre-headless or compiled java-13 +* command-line: (See details in launch.sh) +/home/bot/qemu/qemu-build/qemu-4.2.0/binaries/bin/qemu-system-x86_64 \ + -drive "file=${img},format=qcow2" \ + -drive "file=${user_data},format=raw" \ + -cpu max \ + -m 24G \ + -serial mon:stdio \ + -smp 8 \ + -nographic \ +; + +* Observed by java core dump generated by "kill -SIGSEGV" when java stucked: +Different pthreads are blocked on their own condition variables: + + Id Target Id Frame + 1 Thread 0x7f48a041a080 (LWP 22470) __GI_raise (sig=sig@entry=6) + at ../sysdeps/unix/sysv/linux/raise.c:51 + 2 Thread 0x7f487197d700 (LWP 22473) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f48980197c0) + at ../sysdeps/unix/sysv/linux/futex-internal.h:88 + 3 Thread 0x7f4861b89700 (LWP 22483) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861b88960, expected=0, + futex_word=0x7f489801b084) + at ../sysdeps/unix/sysv/linux/futex-internal.h:142 + 4 Thread 0x7f4861e8c700 (LWP 22480) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f48980107c0) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 + 5 Thread 0x7f4861c8a700 (LWP 22482) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861c89800, expected=0, + futex_word=0x7f489801ed44) + at ../sysdeps/unix/sysv/linux/futex-internal.h:142 + 6 Thread 0x7f48a0418700 (LWP 22471) 0x00007f4880b13200 in ?? () + 7 Thread 0x7f48703ea700 (LWP 22478) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489801dfc0) + at ../sysdeps/unix/sysv/linux/futex-internal.h:88 + 8 Thread 0x7f48702e9700 (LWP 22479) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489838cd84) + at ../sysdeps/unix/sysv/linux/futex-internal.h:88 + 9 Thread 0x7f4870f71700 (LWP 22475) 0x00007f489f5c49f3 in futex_wait_cancelable (private=<optimized out>, expected=0, futex_word=0x7f489801a300) + at ../sysdeps/unix/sysv/linux/futex-internal.h:88 + 10 Thread 0x7f487187b700 (LWP 22474) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f48980cf770) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 + 11 Thread 0x7f4871a7f700 (LWP 22472) 0x00007f489f5c76d6 in futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0, futex_word=0x7f489809ba30) + at ../sysdeps/unix/sysv/linux/futex-internal.h:205 + 12 Thread 0x7f4861d8b700 (LWP 22481) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4861d8a680, expected=0, + futex_word=0x7f489801ed44) + at ../sysdeps/unix/sysv/linux/futex-internal.h:142 + 13 Thread 0x7f48704ec700 (LWP 22477) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f48704eb910, expected=0, + futex_word=0x7f489801d120) + at ../sysdeps/unix/sysv/linux/futex-internal.h:142 + 14 Thread 0x7f4870e6f700 (LWP 22476) 0x00007f489f5c4ed9 in futex_reltimed_wait_cancelable (private=<optimized out>, reltime=0x7f4870e6eb20, expected=0, + futex_word=0x7f489828abd0) + at ../sysdeps/unix/sysv/linux/futex-internal.h:142 \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1863819 b/results/classifier/deepseek-r1:14b/output/KVM/1863819 new file mode 100644 index 00000000..b58ef71e --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1863819 @@ -0,0 +1,42 @@ + +repeated KVM single step crashes leaks into SMP guest and crashes guest application + +Guest: Windows 7 x64 +Host: Ubuntu 18.04.4 (kernel 5.3.0-40-generic) +QEMU: master 6c599282f8ab382fe59f03a6cae755b89561a7b3 + +If I try to use GDB to repeatedly single-step a userspace process while running a KVM guest, the userspace process will eventually crash with a 0x80000004 exception (single step). This is easily reproducible on a Windows guest, I've not tried another guest type but I've been told it's the same there also. + +On a Ubuntu 16 host with an older kernel, this will hang the entire machine. However, it seems it may have been fixed by https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5cc244a20b86090c087073c124284381cdf47234 ? + +It's not clear to me whether this is a KVM or a QEMU bug. A TCG guest does not crash the userspace process in the same way, but it does hang the VM. + +I've tried a variety of QEMU versions (3.0, 4.2, master) and they all exhibit the same behavior. I'm happy to dig into this more if someone can point me in the right direction. + +Here's the outline for reproducing the bug: + +* Compile iloop.cpp (attached) as a 32-bit application using MSVC +* Start Windows 7 x64 guest under GDB + * Pass '-enable-kvm -smp 4,cores=2 -gdb tcp::4567' to QEMU along with other typical options + +(need to get CR3 to ensure we're in the right application context -- if there's an easier way to do this I'd love to hear it!) +* Install WinDBG on guest +* Copy SysInternals LiveKD to guest +* Start iloop.exe in guest, note loop address +* Run LiveKD from administrative prompt + * livekd64.exe -w +* In WinDBG: + * !process 0 0 + * Search for iloop.exe, note DirBase (this is CR3) + +In GDB: +* Execute 'target remote tcp::4567' +* Execute 'c' +* Hit CTRL-C to pause the VM +* Execute 'p/x $cr3' + .. continue if not equal to DirBase in WinDBG, keep stopping until it is equal +* Once $cr3 is correct value, if you 'stepi' a few times you'll note the process going in a loop, it should keep hitting the address echoed to the console by iloop.exe + +Crash the process from GDB: +* Execute 'stepi 100000000' +* Watch the process, eventually it'll die with an 0x80000004 error \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1866870 b/results/classifier/deepseek-r1:14b/output/KVM/1866870 new file mode 100644 index 00000000..f45a0704 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1866870 @@ -0,0 +1,10 @@ + +KVM Guest pauses after upgrade to Ubuntu 20.04 + +As outlined here: https://bugs.launchpad.net/qemu/+bug/1813165/comments/15 + +After upgrade, all KVM guests are in a default pause state. Even after forcing them off via virsh, and restarting them the guests are paused. + +These Guests are not nested. + +A lot of diganostic information are outlined in the previous bug report link provided. The solution mentioned in previous report had been allegedly integrated into the downstream updates. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1877052 b/results/classifier/deepseek-r1:14b/output/KVM/1877052 new file mode 100644 index 00000000..93e409ae --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1877052 @@ -0,0 +1,13 @@ + +KVM Win 10 guest pauses after kernel upgrade + + + +Hello! +Unfortunately the bug has apparently reappeared. I have a Windows 10 running in a VM, which after my today's "apt upgrade" goes into pause mode after a few seconds of running time. + +Until yesterday it used to work and I was able to boot the VM. During the kernel update (from 5.4.0-28.33 to 5.4.0-29.34) the VM was active and then went into pause mode. Even after a reboot of my host system the problem still persists: the VM boots for a few seconds and then switches to pause mode. + + +Kind regards, + Andreas \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1877526 b/results/classifier/deepseek-r1:14b/output/KVM/1877526 new file mode 100644 index 00000000..9297310b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1877526 @@ -0,0 +1,54 @@ + +KVM internal crash + +Hi, +I am new to this. (apologies if I miss something) + +I see the following error when I run an application on my QEMU based VM running ubuntu linux: + +Code=4d 39 c8 7f 64 0f 1f 40 00 4d 8d 40 80 49 81 f8 80 00 00 00 <66> 0f 7f 07 66 0f 7f 47 10 66 0f 7f 47 20 66 0f 7f 47 30 +66 0f 7f 47 40 66 0f 7f 47 50 66 +KVM internal error. Suberror: 1 +emulation failure +RAX=00007fffeb85a000 RBX=00000000069ee400 RCX=0000000000000000 RDX=0000000000000000 +RSI=0000000000000000 RDI=00007fffeb85a000 RBP=00007fffffff9570 RSP=00007fffffff9548 +R8 =0000000000000f80 R9 =0000000001000000 R10=0000000000000000 R11=0000003694e83f3a +R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000006b75350 +RIP=0000003694e8443b RFL=00010206 [-----P-] CPL=3 II=0 A20=1 SMM=0 HLT=0 +ES =0000 0000000000000000 ffffffff 00000000 +CS =0033 0000000000000000 ffffffff 00a0fb00 DPL=3 CS64 [-RA] +SS =002b 0000000000000000 ffffffff 00c0f300 DPL=3 DS [-WA] +DS =0000 0000000000000000 ffffffff 00000000 +FS =0000 00007ffff45b5720 ffffffff 00000000 +GS =0000 0000000000000000 ffffffff 00000000 +LDT=0000 0000000000000000 ffffffff 00000000 +TR =0040 ffff88047fd13140 00002087 00008b00 DPL=0 TSS64-busy +GDT= ffff88047fd04000 0000007f +IDT= ffffffffff57c000 00000fff +CR0=80050033 CR2=00007ffff7ff4000 CR3=000000046cb38000 CR4=000006e0 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000d01 + +This occurs with qemu-kvm version(host m/c has RHEL 6.6) : +Name : qemu-kvm +Arch : x86_64 +Epoch : 2 +Version : 0.12.1.2 +Release : 2.506.el6_10.7 + +I have another m/c with RHEL 7.5, and the same test case passes with the 1.5.3 version. +yum info qemu-kvm +Name : qemu-kvm +Arch : x86_64 +Epoch : 10 +Version : 1.5.3 + + +How do I investigate this? +I would need to patch up the qemu-kvm on the host to get this fixed, I think. + +Please let me know if I need to provide more info, (and what?) + +Regards, +Prashant \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1890069 b/results/classifier/deepseek-r1:14b/output/KVM/1890069 new file mode 100644 index 00000000..bd22b5e0 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1890069 @@ -0,0 +1,24 @@ + +QEMU is not allowing multiple cores with mips architecture + +I may have found a bug as when trying to boot up an QEMU VM with the following command: "qemu-system-mips -M malta -m 512 -hda hda.img -kernel vmlinux-4.19.0-10-4kc-malta -initrd initrd.img-4.19.0-10-4kc-malta -append "root=/dev/sda1 console=ttyS0" -nographic -device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::5555-:22 -smp cores=12,threads=1,sockets=1", it will use up all of the CPU cores on the host, but not bootup? + +Kernel log also shows: +[ 100.303136] perf: interrupt took too long (2506 > 2500), lowering kernel.perf_event_max_sample_rate to 79750 +[ 107.656869] perf: interrupt took too long (3195 > 3132), lowering kernel.perf_event_max_sample_rate to 62500 +[ 117.668390] perf: interrupt took too long (4033 > 3993), lowering kernel.perf_event_max_sample_rate to 49500 +[ 217.166763] perf: interrupt took too long (5126 > 5041), lowering kernel.perf_event_max_sample_rate to 39000 +[ 231.910132] perf: interrupt took too long (6445 > 6407), lowering kernel.perf_event_max_sample_rate to 31000 +[ 250.170677] perf: interrupt took too long (8087 > 8056), lowering kernel.perf_event_max_sample_rate to 24500 +[ 285.391451] perf: interrupt took too long (10126 > 10108), lowering kernel.perf_event_max_sample_rate to 19750 +[ 778.588911] perf: interrupt took too long (12770 > 12657), lowering kernel.perf_event_max_sample_rate to 15500 +[ 1554.825129] perf: interrupt took too long (15982 > 15962), lowering kernel.perf_event_max_sample_rate to 12500 +[ 1622.838910] hrtimer: interrupt took 14758063 ns +[ 1712.932777] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 0.000 msecs +[ 1712.932780] perf: interrupt took too long (59793 > 19977), lowering kernel.perf_event_max_sample_rate to 3250 + + +System details: + +OS: Ubuntu 20.04 +QEMU emulator version 4.2.0 (Debian 1:4.2-3ubuntu6.3) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1890290 b/results/classifier/deepseek-r1:14b/output/KVM/1890290 new file mode 100644 index 00000000..28533a79 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1890290 @@ -0,0 +1,71 @@ + +PowerPC L2(nested virt) kvm guest fails to boot with ic-mode=dual,kernel-irqchip=on - `KVM is too old to support ic-mode=dual,kernel-irqchip=on` + +Env: +HW: Power 9 DD2.3 +Host L0: 5.8.0-rc5-g8ba4ffcd8 +Qemu: 5.0.50 (v5.0.0-533-gdebe78ce14) +Libvirt: 6.4.0 +L1: 5.8.0-rc5-ge9919e11e +qemu_version': '5.0.50 (v5.1.0-rc2-dirty) +libvirt_version': '6.4.0' +L2: 5.8.0-rc7-g6ba1b005f + + +1. boot a L2 KVM guest with `ic-mode=dual,kernel-irqchip=on` + +/usr/bin/virt-install --connect=qemu:///system --hvm --accelerate --name 'vm1' --machine pseries --memory=8192 --vcpu=8,maxvcpus=8,sockets=1,cores=2,t +hreads=4 --import --nographics --serial pty --memballoon model=virtio --disk path=/home/tests/data/avocado-vt/images/f31-ppc64le.qcow2,bus=virtio,size=10,format=qcow2 --network +=bridge=virbr0,model=virtio,mac=52:54:00:e6:fe:f6 --mac=52:54:00:e6:fe:f6 --boot emulator=/usr/share/avocado-plugins-vt/bin/qemu,kernel=/tmp/linux/vmlinux,kernel_args="root=/de +v/vda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug selinux=0" --noautoconsole --qemu-commandline=" -M pseries,ic-mode=dual,kernel-irqchip=on" + + +ERROR internal error: process exited while connecting to monitor: 2020-08-04T11:12:53.304482Z qemu: KVM is too old to support ic-mode=dual,kernel-irqchip=on + + + + +Qemu Log: +``` +/usr/share/avocado-plugins-vt/bin/qemu \ +-name guest=vm1,debug-threads=on \ +-S \ +-object secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-5-vm1/master-key.aes \ +-machine pseries-5.1,accel=kvm,usb=off,dump-guest-core=off \ +-cpu POWER9 \ +-m 8192 \ +-overcommit mem-lock=off \ +-smp 8,sockets=1,dies=1,cores=2,threads=4 \ +-uuid 20a3351b-2776-4e75-9059-c070fe3dd44b \ +-display none \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=34,server,nowait \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot strict=on \ +-kernel /tmp/linux/vmlinux \ +-append 'root=/dev/vda2 rw console=tty0 console=ttyS0,115200 init=/sbin/init initcall_debug selinux=0' \ +-device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x2 \ +-device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x3 \ +-blockdev '{"driver":"file","filename":"/home/tests/data/avocado-vt/images/f31-ppc64le.qcow2","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-1-format","read-only":false,"driver":"qcow2","file":"libvirt-1-storage","backing":null}' \ +-device virtio-blk-pci,bus=pci.0,addr=0x4,drive=libvirt-1-format,id=virtio-disk0,bootindex=1 \ +-netdev tap,fd=37,id=hostnet0,vhost=on,vhostfd=38 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:e6:fe:f6,bus=pci.0,addr=0x1 \ +-chardev pty,id=charserial0 \ +-device spapr-vty,chardev=charserial0,id=serial0,reg=0x30000000 \ +-chardev socket,id=charchannel0,fd=39,server,nowait \ +-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 \ +-M pseries,ic-mode=dual,kernel-irqchip=on \ +-msg timestamp=on +2020-08-04 11:12:53.169+0000: Domain id=5 is tainted: custom-argv +2020-08-04 11:12:53.179+0000: 11120: info : libvirt version: 6.4.0, package: 1.fc31 (Unknown, 2020-06-02-05:09:40, ltc-wspoon4.aus.stglabs.ibm.com) +2020-08-04 11:12:53.179+0000: 11120: info : hostname: atest-guest +2020-08-04 11:12:53.179+0000: 11120: info : virObjectUnref:347 : OBJECT_UNREF: obj=0x7fff0c117c40 +char device redirected to /dev/pts/0 (label charserial0) +2020-08-04T11:12:53.304482Z qemu: KVM is too old to support ic-mode=dual,kernel-irqchip=on +2020-08-04 11:12:53.694+0000: shutting down, reason=failed +``` \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1894869 b/results/classifier/deepseek-r1:14b/output/KVM/1894869 new file mode 100644 index 00000000..32d39571 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1894869 @@ -0,0 +1,21 @@ + +Chelsio T4 has old MSIX PBA offset bug + +There exists a bug with Chelsio NICs T4 that causes the following error: + +kvm: -device vfio-pci,host=0000:83:00.7,id=hostpci1.7,bus=pci.0,addr=0x11.7: vfio 0000:83:00.7: hardware reports invalid configuration, MSIX PBA outside of specified BAR + +I was working with a downstream Proxmox developer to try to fix this issue, and they provided me with the following change to make from line 1484 of hw/vfio/pci.c: + +static void vfio_msix_early_setup(VFIOPCIDevice *vdev, Error **errp) + * is 0x1000, so we hard code that here. + */ + if (vdev->vendor_id == PCI_VENDOR_ID_CHELSIO && +- (vdev->device_id & 0xff00) == 0x5800) { ++ ((vdev->device_id & 0xff00) == 0x5800 || ++ (vdev->device_id & 0xff00) == 0x1425)) { + msix->pba_offset = 0x1000; + } else if (vdev->msix_relo == OFF_AUTOPCIBAR_OFF) { + error_setg(errp, "hardware reports invalid configuration, " + +However, I found that this did not fix the issue, so the bug appears to work differently than the one that was present on the T5 NICs which has already been patched. I have attached the output of my lspci -nnkvv \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1903 b/results/classifier/deepseek-r1:14b/output/KVM/1903 new file mode 100644 index 00000000..acb52416 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1903 @@ -0,0 +1,42 @@ + +qemu/kvm are instantly SIGKILLed by systemd on shutdown, without wait. +Description of problem: +systemd assumes it cannot terminate qemu, and SIGKILLs it. Instantly. +Steps to reproduce: +1. Start qemu on a systemd managed host +2. Shutdown/Reboot +Additional information: +Nothing on qemu's own log, besides that it is starting a vnc server. + +```plaintext +# journalctl -b -1 +... +Sep 22 18:38:04 local kernel: kvm_amd: TSC scaling supported +Sep 22 18:38:04 local kernel: kvm_amd: Nested Virtualization enabled +Sep 22 18:38:04 local kernel: kvm_amd: Nested Paging enabled +Sep 22 18:38:04 local kernel: kvm_amd: Virtual VMLOAD VMSAVE supported +Sep 22 18:38:04 local kernel: kvm_amd: Virtual GIF supported +Sep 22 18:38:04 local kernel: kvm_amd: LBR virtualization supported +... +Sep 22 18:38:50 local systemd-logind[721]: The system will reboot now! +Sep 22 18:38:50 local systemd-logind[721]: System is rebooting. +Sep 22 18:38:50 local sddm-helper[850]: Signal received: SIGTERM +... +Sep 22 18:38:50 local systemd[1]: Stopping User Manager for UID 1000... +Sep 22 18:38:50 local systemd-logind[721]: Removed session 1. +Sep 22 18:38:50 local systemd[854]: Activating special unit Exit the Session... +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1708 (qemu-system-x86) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Killing process 1712 (kvm-nx-lpage-recovery-1708) with signal SIGKILL. +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Failed to kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/> +Sep 22 18:38:50 local systemd[854]: Stopped Konsole - Terminal. +... (some other applications terminanting normally ) +Sep 22 18:38:50 local systemd[854]: app-org.kde.konsole-1ab3dac6a1db4b29b55899b477b32975.scope: Consumed 10.068s CPU time. +Sep 22 18:38:50 local systemd[854]: Removed slice User Background Tasks Slice. +Sep 22 18:38:50 local systemd[854]: background.slice: Consumed 2.960s CPU time. +... +``` + +I cannot explain why it sends SIGKILL to qemu/kvm... it is the same second as the shutdown started, their docs says there's a delay for that. + +Also, other processes owned by the user received a single SIGTERM after qemu was SIGKILLed. Some even take a couple seconds to exit and are not SIGKILLed. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1912777 b/results/classifier/deepseek-r1:14b/output/KVM/1912777 new file mode 100644 index 00000000..4425a493 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1912777 @@ -0,0 +1,96 @@ + +KVM_EXIT_MMIO has increased in Qemu4.0.0 when compared to Qemu 2.11.0 + +I was able to generate trace dump in Qemu for kvm_run_exit event in both QEMU 2.11.0 and QEMU 4.0.0 +From the trace i noticed that the number of KVM_KXIT_MMIO calls has increased alot and is causing delay in testcase execution. + +I executed same testcase from Qemu 2.11 and Qemu4. +Inside Virtual machine when using qemu 2.11 testcase got completed in 11 seconds +but the same testcase when executed on Qemu 4.0.0 got executed in 26 seconds. + + +I did a bit of digging and extracted the kvm_run_exit to figure out whats going on. + +Please find +Stats from Qemu2.11: + +KVM_EXIT_UNKNOWN : 0 +KVM_EXIT_EXCEPTION : 0 +KVM_EXIT_IO : 182513 +KVM_EXIT_HYPERCALL : 0 +KVM_EXIT_DEBUG : 0 +KVM_EXIT_HLT : 0 +KVM_EXIT_MMIO : 216701 +KVM_EXIT_IRQ_WINDOW_OPEN : 0 +KVM_EXIT_SHUTDOWN : 0 +KVM_EXIT_FAIL_ENTRY : 0 +KVM_EXIT_INTR : 0 +KVM_EXIT_SET_TPR : 0 +KVM_EXIT_TPR_ACCESS : 0 +KVM_EXIT_S390_SIEIC : 0 +KVM_EXIT_S390_RESET : 0 +KVM_EXIT_DCR : 0 +KVM_EXIT_NMI : 0 +KVM_EXIT_INTERNAL_ERROR : 0 +KVM_EXIT_OSI : 0 +KVM_EXIT_PAPR_HCALL : 0 +KVM_EXIT_S390_UCONTROL : 0 +KVM_EXIT_WATCHDOG : 0 +KVM_EXIT_S390_TSCH : 0 +KVM_EXIT_EPR : 0 +KVM_EXIT_SYSTEM_EVENT : 0 +KVM_EXIT_S390_STSI : 0 +KVM_EXIT_IOAPIC_EOI : 0 +KVM_EXIT_HYPERV : 0 + +KVM_RUN_EXIT : 399214 (Total in Qemu 2.11 for a testcase) + + +Stats For Qemu 4.0.0: + +VM_EXIT_UNKNOWN : 0 +KVM_EXIT_EXCEPTION : 0 +KVM_EXIT_IO : 163729 +KVM_EXIT_HYPERCALL : 0 +KVM_EXIT_DEBUG : 0 +KVM_EXIT_HLT : 0 +KVM_EXIT_MMIO : 1094231 +KVM_EXIT_IRQ_WINDOW_OPEN : 46 +KVM_EXIT_SHUTDOWN : 0 +KVM_EXIT_FAIL_ENTRY : 0 +KVM_EXIT_INTR : 0 +KVM_EXIT_SET_TPR : 0 +KVM_EXIT_TPR_ACCESS : 0 +KVM_EXIT_S390_SIEIC : 0 +KVM_EXIT_S390_RESET : 0 +KVM_EXIT_DCR : 0 +KVM_EXIT_NMI : 0 +KVM_EXIT_INTERNAL_ERROR : 0 +KVM_EXIT_OSI : 0 +KVM_EXIT_PAPR_HCALL : 0 +KVM_EXIT_S390_UCONTROL : 0 +KVM_EXIT_WATCHDOG : 0 +KVM_EXIT_S390_TSCH : 0 +KVM_EXIT_EPR : 0 +KVM_EXIT_SYSTEM_EVENT : 0 +KVM_EXIT_S390_STSI : 0 +KVM_EXIT_IOAPIC_EOI : 464 +KVM_EXIT_HYPERV : 0 + +KVM_RUN_EXIT : 1258470 (Total in qemu 4.0.0 for same testcase) + + + +From above analysis i found that the number of KVM_EXIT_MMIO has increased by 4.x. + +Could someone from qemu community help me understand as to why the MMIO exits have increased in qemu4 ? + +The results i obtained are after running same testcase. +On Qemu2.11 testcase gets completed in : 11seconds +on Qemu4.11 testcase gets completed in : 26 seconds + +VM Qcow2 used in Ubuntu 16.04 +VM kernel OS is : 4.4 generic + + +Let me know incase more information is required . \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1914748 b/results/classifier/deepseek-r1:14b/output/KVM/1914748 new file mode 100644 index 00000000..98c9acef --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1914748 @@ -0,0 +1,16 @@ + +Confuse error message when KVM can not start requested CPU + +As of commit 1ba089f2255, on Cavium CN8890 (ThunderX cores): + +$ qemu-system-aarch64 -display none -accel kvm -M virt,gic-version=3 -accel kvm -cpu cortex-a57 --trace \*kvm_vcpu\* +kvm_vcpu_ioctl cpu_index 0, type 0x4020aeae, arg 0xffff9b7f9b18 +qemu-system-aarch64: kvm_init_vcpu: kvm_arch_init_vcpu failed (0): Invalid argument + +(same using "-cpu cortex-a53" or cortex-a72). + +Explanation from Peter Maydell on IRC: +> using a specific cpu type will only work with KVM if the host CPU really is that +> exact CPU type, otherwise, use "-cpu host" or "-cpu max" + +Having a better error description would help to understand the reason. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1914986 b/results/classifier/deepseek-r1:14b/output/KVM/1914986 new file mode 100644 index 00000000..b1597d77 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1914986 @@ -0,0 +1,56 @@ + +KVM internal error. Suberror: 1 - OVMF / Audio related + +This is latest release QEMU-5.2.0 on Arch Linux running kernel 5.10.13, latest OVMF etc. + +I'm seeing the following crash when loading an audio driver from the OpenCore[1] project in the UEFI shell: + +KVM internal error. Suberror: 1 +emulation failure +RAX=0000000000000000 RBX=0000000000000000 RCX=0000000000000000 RDX=0000000000000000 +RSI=0000000000000000 RDI=000000007e423628 RBP=000000007fee6a90 RSP=000000007fee6a08 +R8 =0000000000000000 R9 =0000000000000080 R10=0000000000000000 R11=0000000000000000 +R12=000000007eeaf828 R13=0000000000000000 R14=0000000000000000 R15=000000007fee6a67 +RIP=00000000000b0000 RFL=00000246 [---Z-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0 +ES =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] +CS =0038 0000000000000000 ffffffff 00a09b00 DPL=0 CS64 [-RA] +SS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] +DS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] +FS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] +GS =0030 0000000000000000 ffffffff 00c09300 DPL=0 DS [-WA] +LDT=0000 0000000000000000 0000ffff 00008200 DPL=0 LDT +TR =0000 0000000000000000 0000ffff 00008b00 DPL=0 TSS64-busy +GDT= 000000007f9ee698 00000047 +IDT= 000000007f27a018 00000fff +CR0=80010033 CR2=0000000000000000 CR3=000000007fc01000 CR4=00000668 +DR0=0000000000000000 DR1=0000000000000000 DR2=0000000000000000 DR3=0000000000000000 +DR6=00000000ffff0ff0 DR7=0000000000000400 +EFER=0000000000000d00 +Code=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <ff> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff + + +Here's the QEMU command line I'm using: + +qemu-system-x86_64 \ +-machine q35,accel=kvm \ +-cpu host,+topoext,+invtsc \ +-smp 4,sockets=1,cores=2 \ +-m 4096 \ +-drive file=/usr/share/edk2-ovmf/x64/OVMF_CODE.fd,if=pflash,format=raw,readonly=on \ +-drive file=OVMF_VARS.fd,if=pflash,format=raw \ +-usb -device usb-tablet -device usb-kbd \ +-drive file=OpenCore-0.6.6.img,format=raw \ +-device ich9-intel-hda,bus=pcie.0,addr=0x1b \ +-device hda-micro,audiodev=hda \ +-audiodev pa,id=hda,server=/run/user/1000/pulse/native + +The driver loads fine when using the "no connect" switch. eg: + +Shell> load -nc fs0:\efi\oc\drivers\audiodxe.efi +Shell> Image 'fs0:\EFI\OC\Drivers\AudioDxe.efi' loaded at 7E3C7000 - Success + +However, the crash occurs when loading normally. + +Any ideas? Thanks. + +[1]: https://github.com/acidanthera/OpenCorePkg/releases \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1915 b/results/classifier/deepseek-r1:14b/output/KVM/1915 new file mode 100644 index 00000000..c6b2e893 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1915 @@ -0,0 +1,12 @@ + +whpx causes a blue screen on guest windows +Description of problem: +i wanted to install windows 7 with qemu, but qunad i tried i got a blue screen . Then I downgraded to version 5.0.2 and it worked perfectly, I also tried with windows 10 and it didn't boot. + + +Steps to reproduce: +1. install windows 7 iso +2. run the setup +3. and the bsod.. +Additional information: +I tried it with qemu 5.0.2 and it worked perfectly. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1919169 b/results/classifier/deepseek-r1:14b/output/KVM/1919169 new file mode 100644 index 00000000..c66f2a29 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1919169 @@ -0,0 +1,21 @@ + +[git]Startup crash when trying to use an EFI enabled VM in accel/kvm/kvm-all.c + +Hello. + +I build a git version based on commit 6157b0e19721aadb4c7fdcfe57b2924af6144b14. + +When I try to launch an EFI enabled VM, it crashes on start. Here is the command line used: + +qemu-system-x86_64 -bios /usr/share/edk2-ovmf/x64/OVMF.fd -enable-kvm -smp 4 -soundhw all -k fr -m 4096 -vga qxl -hda disk.img -cdrom archlinux-2021.03.01-x86_64.iso -boot cd & + +Here is the log I get: + +``` +qemu-system-x86_64: ../accel/kvm/kvm-all.c:690: kvm_log_clear_one_slot: Assertion `QEMU_IS_ALIGNED(start | size, psize)' failed. +``` + + +ed2k-ovmf version: 202102 + +I tried an older version, edk2-ovmf 202011, same crash on start. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1921468 b/results/classifier/deepseek-r1:14b/output/KVM/1921468 new file mode 100644 index 00000000..a7dad8fb --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1921468 @@ -0,0 +1,47 @@ + +[UBUNTU 20.04] KVM guest fails to find zipl boot menu index + +---Problem Description--- +A KVM guest fails to find the zipl boot menu index if the "zIPL" magic value is listed at the end of a disk block. + +---System Hang--- +System sits in disabled wait, last console display +LOADPARM=[ ] +Using virtio-blk. +Using ECKD scheme (block size 4096), CDL +VOLSER=[0X0067] + + +---Steps to Reproduce--- +1. Install Distro KVM guest from ISO on a DASD, e.g. using virt-install, my invocation was +$ virt-install --name secguest2 --memory 2048 --disk path=/dev/disk/by-path/ccw-0.0.af6a --cdrom /var/lib/libvirt/images/xxxxxx.iso + +2. Select DHCP networking and ASCII console, and accept all defaults of the installer + +3. Let the installer reboot after the installation completes + +It is possible to recover by editing the domain XML with an explicit loadparm to select a boot menu entry. E.g. I changed the disk definition to + <disk type='block' device='disk'> + <driver name='qemu' type='raw' cache='none' io='native'/> + <source dev='/dev/disk/by-path/ccw-0.0.af6a'/> + <target dev='vda' bus='virtio'/> + <boot order='1' loadparm='1'/> + <address type='ccw' cssid='0xfe' ssid='0x0' devno='0xaf6a'/> + </disk> + +The patches are now upstream: +5f97ba0c74cc ("pc-bios/s390-ccw: fix off-by-one error") +468184ec9024 ("pc-bios/s390-ccw: break loop if a null block number is reached") + +Current versions of qemu within Ubuntu + +focal (20.04LTS) 1:4.2-3ubuntu6 [ports]: arm64 armhf ppc64el s390x +focal-updates (metapackages): 1:4.2-3ubuntu6.14: amd64 arm64 armhf ppc64el s390x + +groovy (20.10) (metapackages): 1:5.0-5ubuntu9 [ports]: arm64 armhf ppc64el s390x +groovy-updates (metapackages): 1:5.0-5ubuntu9.6: amd64 arm64 armhf ppc64el s390x + +hirsute (metapackages): 1:5.2+dfsg-9ubuntu1: amd64 arm64 armhf ppc64el s390x + + +git-commits will apply seamlessley for the requested levels if not already integrated \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/1936 b/results/classifier/deepseek-r1:14b/output/KVM/1936 new file mode 100644 index 00000000..daeac91b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/1936 @@ -0,0 +1,2 @@ + +Pass file descriptor to /dev/kvm device node? diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2007 b/results/classifier/deepseek-r1:14b/output/KVM/2007 new file mode 100644 index 00000000..0a5627b1 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2007 @@ -0,0 +1,30 @@ + +Unable to update APIC_TPR when x2APIC is enabled and -global kvm-pit.lost_tick_policy=discard parameter provided +Description of problem: +I am developing a custom OS and I wanted to implement x2APIC support. I was able to enable x2APIC, read and write some registers, like APIC_VER and APIC_SIVR. Everything looks good, except that I cannot update APIC_TPR register. Reading it always returns 0. The code I wrote works properly on bare metal. Below some observations: + +Scenario 1: +1. Enable x2APIC +2. Write to CR8 - success +3. Read from CR8 - gives correct value +4. Read from APIC_TPR - gives correct value + +Scenario 2: +1. Enable x2APIC +2. Read from APIC_TPR - gives 0 +3. Write to APIC_TPR +4. Read from APIC_TPR - gives 0 again + +Scenario 3: +1. Initialize APIC (LAPIC or xAPIC) +2. Write to APIC_TPR +3. Read from APIC_TPR - gives correct value +4. Switch to x2APIC +5. Read from APIC_TPR - gives correct value stored in pt. 2 +6. Write to APIC_TPR +7. Read from APIC_TPR - gives values stored in pt.2, not in point 6! + +Looks like APIC_TPR is stuck at value stored there before switching to x2APIC and it cannot be updated with MSR. Only update CR8 works. +I have checked parameters I passed to qemu. After removing `-global kvm-pit.lost_tick_policy=discard` problem is gone and APIC_TPR is updated correctly. +Additional information: +Please let me know if you need additional information. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2041 b/results/classifier/deepseek-r1:14b/output/KVM/2041 new file mode 100644 index 00000000..130135f4 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2041 @@ -0,0 +1,28 @@ + +RISC-V KVM build error with Alpine Linux +Description of problem: +Native build of qemu fails on alpine linux riscv64. +Steps to reproduce: +1. install alpine on riscv or set up a container with qemu-riscv64 +2. build qemu 8.1.3 from source +3. +Additional information: +``` +kvm.c:(.text+0xc50): undefined reference to `strerrorname_np' +/usr/lib/gcc/riscv64-alpine-linux-musl/13.2.1/../../../../riscv64-alpine-linux-musl/bin/ld: libqemu-riscv64-softmmu.fa.p/target_riscv_kvm.c.o: in function `.L0 ': +kvm.c:(.text+0xcda): undefined reference to `strerrorname_np' +/usr/lib/gcc/riscv64-alpine-linux-musl/13.2.1/../../../../riscv64-alpine-linux-musl/bin/ld: libqemu-riscv64-softmmu.fa.p/target_riscv_kvm.c.o: in function `.L111': +kvm.c:(.text+0xd02): undefined reference to `strerrorname_np' +``` + +The `strerrorname_np` is a GNU specific non-portable function (that what _np stands for). This is the only place where it is use in the entire qemu codebase: +``` +$ rg strerrorname_np +target/riscv/kvm/kvm-cpu.c +837: strerrorname_np(errno)); +899: strerrorname_np(errno)); +909: strerrorname_np(errno)); +932: strerrorname_np(errno)); +``` + +Seems like other places uses `strerror(errno)`. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2110 b/results/classifier/deepseek-r1:14b/output/KVM/2110 new file mode 100644 index 00000000..33a12f7d --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2110 @@ -0,0 +1,12 @@ + +live migrations fail qemu-kvm +Description of problem: +live migrations fail between two identical hosts +``` +2024-01-18T00:16:31.582070Z qemu-kvm: Missing section footer for 0000:00:01.3/piix4_pm +2024-01-18T00:16:31.582169Z qemu-kvm: load of migration failed: Invalid argument +2024-01-18 00:16:31.611+0000: shutting down, reason=failed +``` +Additional information: +source log for vm [source.log](/uploads/5816f929a5e543f423bb909a0df23fb7/source.log) +dest log for vm [dest.log](/uploads/a1b6ae02e4c8235536e740b86d16ddd6/dest.log) diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2219 b/results/classifier/deepseek-r1:14b/output/KVM/2219 new file mode 100644 index 00000000..7264b6ae --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2219 @@ -0,0 +1,2 @@ + +Core dump instead of error when starting on nohz_full system with enable-membarrier diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2247 b/results/classifier/deepseek-r1:14b/output/KVM/2247 new file mode 100644 index 00000000..396c8510 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2247 @@ -0,0 +1,7 @@ + +virsh qemu-monitor-command --hmp help information missing inject-nmi for watchdog_action +Description of problem: +watchdog_action missing inject-nmi which already supported in Commit [795dc6e4](https://gitlab.com/qemu-project/qemu/-/commit/795dc6e46d953d70b4b7ddd3f4956f8f4b9d8565) +Steps to reproduce: +1. virsh qemu-monitor-command <id> --hmp help |grep watchdog +2. change watchdog action to inject-nmi diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2285 b/results/classifier/deepseek-r1:14b/output/KVM/2285 new file mode 100644 index 00000000..26a4a8ef --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2285 @@ -0,0 +1,2 @@ + +cross-i686-tci job intermittent timeouts diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2321 b/results/classifier/deepseek-r1:14b/output/KVM/2321 new file mode 100644 index 00000000..6f9dbd77 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2321 @@ -0,0 +1,41 @@ + +Segfault when hibernating a KVM VM with QEMU 8.2.3 +Description of problem: +Attempting to hibernate the machine crashes QEMU. +Steps to reproduce: +This involves Nix, please tell me if you want a reproducer that doesn't. + +1. nix build github:NixOS/nixpkgs#nixosTests.hibernate.driver +2. ./result/bin/nixos-test-driver +3. Observe crash +Additional information: +Backtrace: + +``` +#0 kvm_virtio_pci_vq_vector_release (proxy=0x55bd979fd130, vector=<optimized out>) at ../hw/virtio/virtio-pci.c:834 +#1 kvm_virtio_pci_vector_release_one (proxy=proxy@entry=0x55bd979fd130, queue_no=queue_no@entry=0) at ../hw/virtio/virtio-pci.c:965 +#2 0x000055bd9380c430 in virtio_pci_set_vector (vdev=0x55bd97a05500, proxy=0x55bd979fd130, queue_no=0, old_vector=1, new_vector=65535) + at ../hw/virtio/virtio-pci.c:1445 +#3 0x000055bd939c5490 in memory_region_write_accessor (mr=0x55bd979fdc70, addr=26, value=<optimized out>, size=2, shift=<optimized out>, + mask=<optimized out>, attrs=...) at ../system/memory.c:497 +#4 0x000055bd939c4d56 in access_with_adjusted_size (addr=addr@entry=26, value=value@entry=0x7ff49d1ff3e8, size=size@entry=2, + access_size_min=<optimized out>, access_size_max=<optimized out>, access_fn=0x55bd939c5410 <memory_region_write_accessor>, mr=<optimized out>, + attrs=...) at ../system/memory.c:573 +#5 0x000055bd939c5081 in memory_region_dispatch_write (mr=mr@entry=0x55bd979fdc70, addr=addr@entry=26, data=<optimized out>, op=<optimized out>, + attrs=attrs@entry=...) at ../system/memory.c:1528 +#6 0x000055bd939ccb0c in flatview_write_continue (fv=fv@entry=0x7ff4445771c0, addr=addr@entry=61572651286554, attrs=..., attrs@entry=..., + ptr=ptr@entry=0x7ff4a082d028, len=len@entry=2, addr1=<optimized out>, l=<optimized out>, mr=0x55bd979fdc70) at ../system/physmem.c:2714 +#7 0x000055bd939ccd83 in flatview_write (fv=0x7ff4445771c0, addr=addr@entry=61572651286554, attrs=attrs@entry=..., buf=buf@entry=0x7ff4a082d028, + len=len@entry=2) at ../system/physmem.c:2756 +#8 0x000055bd939d0099 in address_space_write (len=2, buf=0x7ff4a082d028, attrs=..., addr=61572651286554, as=0x55bd94a4e720 <address_space_memory>) + at ../system/physmem.c:2863 +#9 address_space_rw (as=0x55bd94a4e720 <address_space_memory>, addr=61572651286554, attrs=attrs@entry=..., buf=buf@entry=0x7ff4a082d028, len=2, + is_write=<optimized out>) at ../system/physmem.c:2873 +#10 0x000055bd93a24548 in kvm_cpu_exec (cpu=cpu@entry=0x55bd9628a3e0) at ../accel/kvm/kvm-all.c:2915 +#11 0x000055bd93a25795 in kvm_vcpu_thread_fn (arg=arg@entry=0x55bd9628a3e0) at ../accel/kvm/kvm-accel-ops.c:51 +#12 0x000055bd93bb5fa8 in qemu_thread_start (args=0x55bd96294940) at ../util/qemu-thread-posix.c:541 +#13 0x00007ff4a19fd272 in start_thread (arg=<optimized out>) at pthread_create.c:447 +#14 0x00007ff4a1a78dcc in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78 +``` + +Bisected to https://gitlab.com/qemu-project/qemu/-/commit/fcbb086ae590e910614fe5b8bf76e264f71ef304, reverting that change seems to make things work again. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2325 b/results/classifier/deepseek-r1:14b/output/KVM/2325 new file mode 100644 index 00000000..1b0bbd07 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2325 @@ -0,0 +1,12 @@ + +[Performance Regression] Constant freezes on Alder lake and Raptor lake CPUs. +Description of problem: +Strangely, no logs are recorded. The guest just freezes. It can however be rescued by a simple pause and unpause. + +This issue only happens when using the KVM hypervisor. Other hypervisors are fine. + +This issue does NOT happen when I tested my Intel Core i7 8700K. +Steps to reproduce: +1. Create a basic virtual machine for Windows 11 (Or 10). +2. Run it for about 5 - 30 minutes (Sometimes it happens in 20 seconds or even less). +3. The problem should occur. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2339 b/results/classifier/deepseek-r1:14b/output/KVM/2339 new file mode 100644 index 00000000..7b4f5a22 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2339 @@ -0,0 +1,2 @@ + +VM Crash is observed while deploying an ubuntu VM with OS version 18.04 on host with ubuntu version 24.04 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2363 b/results/classifier/deepseek-r1:14b/output/KVM/2363 new file mode 100644 index 00000000..bc83725b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2363 @@ -0,0 +1,2 @@ + +How can I enable MBI support in QEMU when running in KVM mode? diff --git a/results/classifier/deepseek-r1:14b/output/KVM/239 b/results/classifier/deepseek-r1:14b/output/KVM/239 new file mode 100644 index 00000000..e4b090fb --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/239 @@ -0,0 +1,2 @@ + +Confusing error message when KVM can not start requested ARM CPU diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2392 b/results/classifier/deepseek-r1:14b/output/KVM/2392 new file mode 100644 index 00000000..2f99e425 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2392 @@ -0,0 +1,2 @@ + +Ability to use KVM on Windows diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2394 b/results/classifier/deepseek-r1:14b/output/KVM/2394 new file mode 100644 index 00000000..19c18347 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2394 @@ -0,0 +1,30 @@ + +kvm-unit-tests vmx failed +Description of problem: +On the Sierra Forest platform, the vmx test in kvm-unit-tests failed. But this issue cannot be replicated on Emerald Rapids platform. + +The first bad commit is ba6780905943696d790cc880c8e5684b51f027fe. +Steps to reproduce: +1.git clone https://gitlab.com/kvm-unit-tests/kvm-unit-tests.git + +2.cd kvm-unit-tests; ./configure + +3.make standalone + +4.rmmod kvm_intel + +5.modprobe kvm_intel nested=Y allow_smaller_maxphyaddr=Y + +6.cd tests; ./vmx +Additional information: +... +FAIL: HOST_CR3 2000000001007000: vmlaunch fails + +FAIL: HOST_CR3 4000000001007000: vmlaunch fails +... + +SUMMARY: 430013 tests, 2 unexpected failures, 2 expected failures, 5 skipped + +FAIL vmx (430013 tests, 2 unexpected failures, 2 expected failures, 5 skipped) + +[error.log](/uploads/02456b40f2736c0bf34d3f4b3a0c872a/error.log) diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2469 b/results/classifier/deepseek-r1:14b/output/KVM/2469 new file mode 100644 index 00000000..4d21d429 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2469 @@ -0,0 +1,2 @@ + +/s390x/migration/precopy/tcp/plain/switchover-ack may hang diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2509 b/results/classifier/deepseek-r1:14b/output/KVM/2509 new file mode 100644 index 00000000..abbc5829 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2509 @@ -0,0 +1,27 @@ + +With qemu-system-i386 certain iso images cause looping crashes +Description of problem: +Soon after start seabios tries to boot, a crash followed by a loop occurs. Last line seen before crash and loop: + ``` +Booting from DVD/CD... + ``` +Steps to reproduce: +1. Download https://www.qemu-advent-calendar.org/2018/download/day10.tar.xz +2. Execute QEMU command line +Additional information: +Starting VM with qemu-system-x86_64 works + ``` + qemu-system-x86_64 -cdrom gamebro.iso + ``` +Starting VM with qemu-system-i386 using KVM causes looping + ``` + qemu-system-i386 -accel kvm -cdrom gamebro.iso + ``` +Starting VM with qemu-system-i386 on Windows using WHPX works + ``` + qemu-system-i386.exe -accel whpx -cdrom gamebro.iso + ``` +Starting other iso images works, e.g. https://cdimage.debian.org/mirror/cdimage/archive/10.8.0/i386/iso-cd/debian-10.8.0-i386-netinst.iso + ``` + qemu-system-i386 -cdrom debian-10.8.0-i386-netinst.iso + ``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2517 b/results/classifier/deepseek-r1:14b/output/KVM/2517 new file mode 100644 index 00000000..0defd7e8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2517 @@ -0,0 +1,2 @@ + +destroying a vCPU will leak its AddressSpaces diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2555 b/results/classifier/deepseek-r1:14b/output/KVM/2555 new file mode 100644 index 00000000..0a4fd3a8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2555 @@ -0,0 +1,21 @@ + +Can't start a guest with 2 IOAPICs +Description of problem: +For a host with multiple IOAPICs, I want to start a guest with 2 IOAPICs. I saw this commit about this function: **[x86: add support for second ioapic]**: + https://gitlab.com/qemu-project/qemu/-/commit/94c5a606379ddd04beecdb11fb34b51b4b28c7f2 + +But after I started a guest in a host with multiple IOAPICs, there was still only one IOAPIC in guest. How should I enable this feature? +Additional information: +Host IOAPICs Info: + ``` +[ 1.268280] IOAPIC[0]: apic_id 0, version 33, address 0xfec00000, GSI 0-23 +[ 1.268286] IOAPIC[1]: apic_id 1, version 33, address 0xfec20000, GSI 24-55 +[ 1.268291] IOAPIC[2]: apic_id 2, version 33, address 0xd9000000, GSI 56-87 +[ 4.415313] ACPI: Using IOAPIC for interrupt routing + ``` + +Guest IOAPIC Info: + ``` +[ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23 +[ 0.255045] ACPI: Using IOAPIC for interrupt routing + ``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2557 b/results/classifier/deepseek-r1:14b/output/KVM/2557 new file mode 100644 index 00000000..963c7c69 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2557 @@ -0,0 +1,2 @@ + +balloon size startup parameter needed diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2692 b/results/classifier/deepseek-r1:14b/output/KVM/2692 new file mode 100644 index 00000000..921625bd --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2692 @@ -0,0 +1,2 @@ + +Using the ldp instruction to access the I/O address space in KVM mode causes an exception diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2706 b/results/classifier/deepseek-r1:14b/output/KVM/2706 new file mode 100644 index 00000000..e5098048 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2706 @@ -0,0 +1,2 @@ + +MigrationCapability "dirty-bitmaps off" diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2710 b/results/classifier/deepseek-r1:14b/output/KVM/2710 new file mode 100644 index 00000000..3bfbf7c4 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2710 @@ -0,0 +1,127 @@ + +QEMU can't detect guest debug support on older (pre v5.7) x86 host kernels due to missing KVM_CAP_SET_GUEST_DEBUG +Description of problem: +``` +qemu-system-x86_64: -s: gdbstub: current accelerator doesn't support guest debugging +``` +Additional information: +I initially located the QEMU source code to determine whether KVM supports gdbstub by checking for `KVM_CAP_SET_GUEST_DEBUG`. The corresponding code can be found at: +```c +// qemu/accel/kvm/kvm-all.c:2695 +#ifdef TARGET_KVM_HAVE_GUEST_DEBUG + kvm_has_guest_debug = + (kvm_check_extension(s, KVM_CAP_SET_GUEST_DEBUG) > 0); +#endif +``` +It can be observed that if the return value is <= 0 (in practice, this function only returns 0 on failure), the debug_flag is set to false. + +Upon further investigation of the Linux 4.15 kernel code, I discovered that in earlier versions, support for checking VM debugging capabilities via `KVM_CAP_SET_GUEST_DEBUG` was almost non-existent (it was only supported on arm64). However, for x86_64, VM debugging is supported on the 4.15 kernel. + +```c +// linu4.15/arch/x86/kvm/x86.c:2672 +int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext) +{ + int r; + + switch (ext) { + case KVM_CAP_IRQCHIP: + case KVM_CAP_HLT: + case KVM_CAP_MMU_SHADOW_CACHE_CONTROL: + case KVM_CAP_SET_TSS_ADDR: + case KVM_CAP_EXT_CPUID: + case KVM_CAP_EXT_EMUL_CPUID: + case KVM_CAP_CLOCKSOURCE: + case KVM_CAP_PIT: + case KVM_CAP_NOP_IO_DELAY: + case KVM_CAP_MP_STATE: + case KVM_CAP_SYNC_MMU: + case KVM_CAP_USER_NMI: + case KVM_CAP_REINJECT_CONTROL: + case KVM_CAP_IRQ_INJECT_STATUS: + case KVM_CAP_IOEVENTFD: + case KVM_CAP_IOEVENTFD_NO_LENGTH: + case KVM_CAP_PIT2: + case KVM_CAP_PIT_STATE2: + case KVM_CAP_SET_IDENTITY_MAP_ADDR: + case KVM_CAP_XEN_HVM: + case KVM_CAP_VCPU_EVENTS: + case KVM_CAP_HYPERV: + case KVM_CAP_HYPERV_VAPIC: + case KVM_CAP_HYPERV_SPIN: + case KVM_CAP_HYPERV_SYNIC: + case KVM_CAP_HYPERV_SYNIC2: + case KVM_CAP_HYPERV_VP_INDEX: + case KVM_CAP_PCI_SEGMENT: + case KVM_CAP_DEBUGREGS: + case KVM_CAP_X86_ROBUST_SINGLESTEP: + case KVM_CAP_XSAVE: + case KVM_CAP_ASYNC_PF: + case KVM_CAP_GET_TSC_KHZ: + case KVM_CAP_KVMCLOCK_CTRL: + case KVM_CAP_READONLY_MEM: + case KVM_CAP_HYPERV_TIME: + case KVM_CAP_IOAPIC_POLARITY_IGNORED: + case KVM_CAP_TSC_DEADLINE_TIMER: + case KVM_CAP_ENABLE_CAP_VM: + case KVM_CAP_DISABLE_QUIRKS: + case KVM_CAP_SET_BOOT_CPU_ID: + case KVM_CAP_SPLIT_IRQCHIP: + case KVM_CAP_IMMEDIATE_EXIT: + r = 1; + break; + case KVM_CAP_ADJUST_CLOCK: + r = KVM_CLOCK_TSC_STABLE; + break; + case KVM_CAP_X86_GUEST_MWAIT: + r = kvm_mwait_in_guest(); + break; + case KVM_CAP_X86_SMM: + /* SMBASE is usually relocated above 1M on modern chipsets, + * and SMM handlers might indeed rely on 4G segment limits, + * so do not report SMM to be available if real mode is + * emulated via vm86 mode. Still, do not go to great lengths + * to avoid userspace's usage of the feature, because it is a + * fringe case that is not enabled except via specific settings + * of the module parameters. + */ + r = kvm_x86_ops->cpu_has_high_real_mode_segbase(); + break; + case KVM_CAP_VAPIC: + r = !kvm_x86_ops->cpu_has_accelerated_tpr(); + break; + case KVM_CAP_NR_VCPUS: + r = KVM_SOFT_MAX_VCPUS; + break; + case KVM_CAP_MAX_VCPUS: + r = KVM_MAX_VCPUS; + break; + case KVM_CAP_NR_MEMSLOTS: + r = KVM_USER_MEM_SLOTS; + break; + case KVM_CAP_PV_MMU: /* obsolete */ + r = 0; + break; + case KVM_CAP_MCE: + r = KVM_MAX_MCE_BANKS; + break; + case KVM_CAP_XCRS: + r = boot_cpu_has(X86_FEATURE_XSAVE); + break; + case KVM_CAP_TSC_CONTROL: + r = kvm_has_tsc_control; + break; + case KVM_CAP_X2APIC_API: + r = KVM_X2APIC_API_VALID_FLAGS; + break; + default: + r = 0; + break; + } + return r; + +} +``` + +I attempted to bypass this check in QEMU and verified that the QEMU gdbstub works normally on the 4.15 kernel. + +For modifications related to this part in QEMU, you can refer to the email: https://lore.kernel.org/all/20211111110604.207376-5-pbonzini@redhat.com/. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2736 b/results/classifier/deepseek-r1:14b/output/KVM/2736 new file mode 100644 index 00000000..0f1b81de --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2736 @@ -0,0 +1,11 @@ + +assert_fail in vmstate_load_state (icount related) +Description of problem: +qemu crashes with an assert failure. +Steps to reproduce: +- Run qemu-system-sparc with "-i count auto -rtc clock=vm" + - Create a snapshot. Exit qemu. + - Run qemu-system-sparc without "-i count auto -rtc clock-vm" + - Try to load the snapshot via the monitor +Additional information: +[gdb.out](/uploads/d08539ce9eb6b599918513e279f13453/gdb.out) diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2837 b/results/classifier/deepseek-r1:14b/output/KVM/2837 new file mode 100644 index 00000000..54cf3399 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2837 @@ -0,0 +1,2 @@ + +qcow2 corruption MinGW64 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/2925 b/results/classifier/deepseek-r1:14b/output/KVM/2925 new file mode 100644 index 00000000..2a2897cb --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/2925 @@ -0,0 +1,26 @@ + +Cannot exec certain QMP guest commands using unix socket but Virsh can +Description of problem: +There are two channels configured to communicate the guest. + - a) qemu.guest_agent.0 + - b) unix socket: -qmp unix:/tmp/qmp_win7-101.sock,server,nowait + + +**For unix socket connection, certain commands like ```guest-info``` and other guest functions are missing.** However, invoking guest-xx functions successfully in Virsh (through qemu.guest_agent.0). +Steps to reproduce: +``` +$sudo socat unix-connect:/tmp/qmp_win7-101.sock readline +{"QMP": {"version": {"qemu": {"micro": 0, "minor": 2, "major": 4}, "package": "qemu-kvm-4.2.0-59.module_el8.5.0+1063+c9b9feff.1"}, "capabilities": ["oob"]}} + +{"execute":"qmp_capabilities"} +{"return": {}} + +{"execute": "guest-info"} +{"error": {"class": "CommandNotFound", "desc": "The command guest-info has not been found"}} +``` + +I checked ```/etc/sysconfig/qemu-ga``` and unmarked blacklist functions, but it did not solve this problem. +``` +# original contents of qemu-ga +#BLACKLIST_RPC=guest-file-open,guest-file-close,guest-file-read,guest-file-write,guest-file-seek,guest-file-flush,guest-exec,guest-exec-status +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/391879 b/results/classifier/deepseek-r1:14b/output/KVM/391879 new file mode 100644 index 00000000..bbdc5037 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/391879 @@ -0,0 +1,25 @@ + +migrate exec ignores exit status + +Binary package hint: kvm + +Using + + migrate "exec:cat > foo; false" + +in the monitor results in the state of the VM being written to foo, as expected, and the VM then being stopped. This is surprising, as I think it stands to reason that in case of a failed migrate-exec process, which is what a non-zero exit status implies to me, the VM should continue. + +== Version information + +$ lsb_release -rd +Description: Ubuntu 9.04 +Release: 9.04 + +$ apt-cache policy kvm +kvm: + Installed: 1:84+dfsg-0ubuntu11 + Candidate: 1:84+dfsg-0ubuntu11 + Version table: + *** 1:84+dfsg-0ubuntu11 0 + 500 http://gb.archive.ubuntu.com jaunty/main Packages + 100 /var/lib/dpkg/status \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/391880 b/results/classifier/deepseek-r1:14b/output/KVM/391880 new file mode 100644 index 00000000..5a1694d8 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/391880 @@ -0,0 +1,12 @@ + +migrate exec hangs for several minutes if the pipe is closed before all its data is written + +Binary package hint: kvm + +Using + + migrate "exec:true" + +in the monitor hangs the VM for several minutes. What I expect is that the VM stops attempting to migrate after the pipe has been closed. + +Indicating a background migrate with -d doesn't help. Presumably the migration is not backgrounded until a certain amount of data is written to the pipe, or the migration times out What I expect is that the migration is backgrounded immediately. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/477 b/results/classifier/deepseek-r1:14b/output/KVM/477 new file mode 100644 index 00000000..22af621b --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/477 @@ -0,0 +1,13 @@ + +Nested kvm-svm does not work since f5cc5a5c16 +Description of problem: +Nested SVM virtualization seems to not work. I bisected this to f5cc5a5c16. +Steps to reproduce: +1. Boot up a Linux guest such as the Debian Live CD with -accel kvm -cpu host +2. ```dmesg | grep kvm; ls /dev/kvm```; # Shows that KVM is disabled within the guest +Additional information: +Details about my AMD host: +``` +model name : AMD Ryzen 5 2600 Six-Core Processor +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/490484 b/results/classifier/deepseek-r1:14b/output/KVM/490484 new file mode 100644 index 00000000..69c32260 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/490484 @@ -0,0 +1,42 @@ + +running 64bit client in 64bit host with intel crashes + +Binary package hint: qemu-kvm + +running windows 7 VM halts on early boot with + +kvm: unhandled exit 80000021 +kvm_run returned -22 + +ProblemType: Bug +Architecture: amd64 +Date: Mon Nov 30 21:28:54 2009 +DistroRelease: Ubuntu 9.10 +KvmCmdLine: Error: command ['ps', '-C', 'kvm', '-F'] failed with exit code 1: UID PID PPID C SZ RSS PSR STIME TTY TIME CMD +MachineType: System manufacturer P5Q-PRO +NonfreeKernelModules: fglrx +Package: kvm (not installed) +ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=UUID=17a8e181-fac7-461e-8cad-8aea97be2536 ro quiet splash +ProcEnviron: + LANGUAGE=en_US:en + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash +ProcVersionSignature: Ubuntu 2.6.31-14.48-generic +SourcePackage: qemu-kvm +Uname: Linux 2.6.31-14-generic x86_64 +dmi.bios.date: 07/10/2008 +dmi.bios.vendor: American Megatrends Inc. +dmi.bios.version: 1004 +dmi.board.asset.tag: To Be Filled By O.E.M. +dmi.board.name: P5Q-PRO +dmi.board.vendor: ASUSTeK Computer INC. +dmi.board.version: Rev 1.xx +dmi.chassis.asset.tag: Asset-1234567890 +dmi.chassis.type: 3 +dmi.chassis.vendor: Chassis Manufacture +dmi.chassis.version: Chassis Version +dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1004:bd07/10/2008:svnSystemmanufacturer:pnP5Q-PRO:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: +dmi.product.name: P5Q-PRO +dmi.product.version: System Version +dmi.sys.vendor: System manufacturer \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/497273 b/results/classifier/deepseek-r1:14b/output/KVM/497273 new file mode 100644 index 00000000..aa40acde --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/497273 @@ -0,0 +1,66 @@ + +winxp.64 fails to install in -rc2 with kvm + +Host: Fedora11, 64-bit +Kernel: 2.6.30.9-96.fc11.x86_64 +KVM modules: + +# modinfo kvm +filename: /lib/modules/2.6.30.9-96.fc11.x86_64/kernel/arch/x86/kvm/kvm.ko +license: GPL +author: Qumranet +srcversion: 23A53503602E48217AC12F1 +depends: +vermagic: 2.6.30.9-96.fc11.x86_64 SMP mod_unload +parm: oos_shadow:bool +parm: msi2intx:bool + +]# modinfo kvm-intel +filename: /lib/modules/2.6.30.9-96.fc11.x86_64/kernel/arch/x86/kvm/kvm-intel.ko +license: GPL +author: Qumranet +srcversion: 5DD68E0B8497DC4518A8797 +depends: kvm +vermagic: 2.6.30.9-96.fc11.x86_64 SMP mod_unload +parm: bypass_guest_pf:bool +parm: enable_vpid:bool +parm: flexpriority_enabled:bool +parm: enable_ept:bool +parm: emulate_invalid_guest_state:bool + +Host CPU: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz + +Guest commandline: +sudo ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios -name 'vm1' -monitor stdio -drive file=~/work/images/winXP-64.qcow2,if=ide,cache=writeback -net nic,vlan=0,model=rtl8139,macaddr=52:54:00:12:34:56 -net user,vlan=0 -m 512 -cdrom ~/work/isos/en_windows_xp_professional_x64.iso -enable-kvm -redir tcp:5000::22 + +Steps to reproduce: + +1. git checkout -b 12rc2 v0.12.0-rc2 +2. ./configure --target-list=x86_64-softmmu +3. make +4. qemu-img create -f qcow2 ~/work/images/winXP-64.qcow2 20G +5. sudo ./x86_64-softmmu/qemu-system-x86_64 -L pc-bios -name 'vm1' -monitor stdio -drive file=~/work/images/winXP-64.qcow2,if=ide,cache=writeback -net nic,vlan=0,model=rtl8139,macaddr=52:54:00:12:34:56 -net user,vlan=0 -m 512 -cdrom ~/work/isos/en_windows_xp_professional_x64.iso -enable-kvm -redir tcp:5000::22 + +Guest boots XP.64 installer, loads some files and then hangs at "Starting Windows XP" + +Reverting to -rc1 and XP installs just fine. Git bisect points to: + +commit 066263f37701687c64af9d8825e3376d069ebfd4 +Author: Andre Przywara <email address hidden> +Date: Mon Dec 7 11:58:02 2009 +0100 + +cpuid: Fix multicore setup on Intel + + +Reverting this fixes the problem. + +Different kvm modules seem to affect this install as well. Switching +to different kvm-kmod packages: + +2.6.32 modules work fine with 0.12.0-rc2, no issues at all + +2.6.30 modules fail, reverting the above commit doesn't help, seems to +be in the same boat as 2.6.28 modules + +2.6.31.5 (roughly equivalent to Fedora11 modules) work on -rc1, fail on +rc2, reverting above commit fixes -rc2. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/504 b/results/classifier/deepseek-r1:14b/output/KVM/504 new file mode 100644 index 00000000..c11c0806 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/504 @@ -0,0 +1,19 @@ + +kvm_log_clear_one_slot: KVM_CLEAR_DIRTY_LOG failed +Description of problem: +``` + $ ./qemu-system-i386 -enable-kvm -cdrom ubuntu-20.04.2.0-desktop-amd64.iso +qemu-system-i386: kvm_log_clear_one_slot: KVM_CLEAR_DIRTY_LOG failed, slot=9, start=0x0, size=0x10, errno=-14 +qemu-system-i386: kvm_log_clear: kvm log clear failed: mr=vga.vram offset=10000 size=10000 +Aborted + + $ ./qemu-system-x86_64 -enable-kvm -cdrom ubuntu-20.04.2.0-desktop-amd64.iso +qemu-system-x86_64: kvm_log_clear_one_slot: KVM_CLEAR_DIRTY_LOG failed, slot=9, start=0x0, size=0x10, errno=-14 +qemu-system-x86_64: kvm_log_clear: kvm log clear failed: mr=vga.vram offset=0 size=10000 +Aborted +``` +Steps to reproduce: +1. qemu crashes right at start +Additional information: +- last successfully used qemu version: 5.2.0 + - first seen failing qemu version: 6.0 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/506 b/results/classifier/deepseek-r1:14b/output/KVM/506 new file mode 100644 index 00000000..5f8fe97a --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/506 @@ -0,0 +1,2 @@ + +ga: auto-discover virtio port using sysfs diff --git a/results/classifier/deepseek-r1:14b/output/KVM/521202 b/results/classifier/deepseek-r1:14b/output/KVM/521202 new file mode 100644 index 00000000..9b1e926f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/521202 @@ -0,0 +1,8 @@ + +Windows XP x64 / 2008 Server x64 broken on 32-bit hosts with QEMU > 0.9.0 + +QEMU >0.9.0 fails to install/run 64-bit Windows XP guests on 32-bit hosts. This is mentioned here: http://qemu-forum.ipi.fi/viewtopic.php?f=5&t=4625 . As explained there, 0.9.0 manages to install and run XP64 fine, if somewhat slowly. The host is an actual 32-bit CPU (Athlon XP), although I've tested it and confirmed the bug to occur on a Core2 Duo CPU running in 32-bit mode with KVM disabled. It's impossible to test with KVM enabled, as this causes Windows to detect a 32-bit CPU and refuse to run. + +When installing, the installer hangs at the "Setup is starting Windows" step. An attempt at running a converted VBox image reveals the problem lies somewhere in the ACPI -- in safe mode, the boot sequence gets to loading ACPI tables, then hangs indefinitely. Interestingly enough, the emulator itself runs fine, you can interact with the monitor etc., but the virtual CPU appears to stop; there's a marked point in "log cpu" output after which nothing comes. Disabling ACPI predictably does nothing to help, as in this case Windows refuses to run. + +I've tested with several versions, and 0.9.1 is the first one to break. The bug is still present in 0.11 and 0.12 as packaged by Ubuntu. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/563 b/results/classifier/deepseek-r1:14b/output/KVM/563 new file mode 100644 index 00000000..2d383bc9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/563 @@ -0,0 +1,2 @@ + +KVM ubuntu 20 VPS on Ryzen 9 5950X diff --git a/results/classifier/deepseek-r1:14b/output/KVM/568445 b/results/classifier/deepseek-r1:14b/output/KVM/568445 new file mode 100644 index 00000000..c899dc94 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/568445 @@ -0,0 +1,12 @@ + +LVM backed drives should default to cache='none' + +Binary package hint: virt-manager + +KVM guests using LVM backed drives appear to experience fairly high iowait times on the host system if the guest has even a moderate amount of disk I/O. This translates to poor performance for the host and all guests running on the host, and appears to be due to caching as KVM defaults to using writethrough caching when nothing is specified. Explicitly disabling KVM's caching appears to result in significantly better host and guest performance. + +This is recommended in at least a few places: +http://<email address hidden>/msg17492.html +http://permalink.gmane.org/gmane.comp.emulators.kvm.devel/48471 +http://<email address hidden>/msg30425.html +http://virt.kernelnewbies.org/XenVsKVM \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/584516 b/results/classifier/deepseek-r1:14b/output/KVM/584516 new file mode 100644 index 00000000..fb0b3361 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/584516 @@ -0,0 +1,48 @@ + +opensuse 11.2 guest hangs after live migration with clocksource=kvm-clock + +i would like to debug a problem that I encountered some time ago with opensuse 11.2 and also +with Ubuntu (karmic/lucid). + +If I run an opensuse guest 64-bit and do not touch the clocksource settings the guest almost +everytime hangs after live migration at: + +(gdb) thread apply all bt + +Thread 2 (Thread 0x7f846782a950 (LWP 27356)): +#0 0x00007f8467d24cd7 in ioctl () from /lib/libc.so.6 +#1 0x000000000042b945 in kvm_run (env=0x2468170) + at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:921 +#2 0x000000000042cea2 in kvm_cpu_exec (env=0x2468170) + at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1651 +#3 0x000000000042d62c in kvm_main_loop_cpu (env=0x2468170) + at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1893 +#4 0x000000000042d76d in ap_main_loop (_env=0x2468170) + at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:1943 +#5 0x00007f8468caa3ba in start_thread () from /lib/libpthread.so.0 +#6 0x00007f8467d2cfcd in clone () from /lib/libc.so.6 +#7 0x0000000000000000 in ?? () + +Thread 1 (Thread 0x7f84692d96f0 (LWP 27353)): +#0 0x00007f8467d25742 in select () from /lib/libc.so.6 +#1 0x000000000040c25a in main_loop_wait (timeout=1000) + at /usr/src/qemu-kvm-0.12.4/vl.c:3994 +#2 0x000000000042dcf1 in kvm_main_loop () + at /usr/src/qemu-kvm-0.12.4/qemu-kvm.c:2126 +#3 0x000000000040c98c in main_loop () at /usr/src/qemu-kvm-0.12.4/vl.c:4212 +#4 0x000000000041054b in main (argc=31, argv=0x7fffa91351c8, + envp=0x7fffa91352c8) at /usr/src/qemu-kvm-0.12.4/vl.c:6252 + +If I run the same guest with kernel parameter clocksource=acpi_pm, the migration succeeds reliably. + +The hosts runs: +/kernel: /2.6.33.3, /bin: /qemu-kvm-0.12.4, /mod: /2.6.33.3 + +I invoke qemu-kvm with: +/usr/bin/qemu-kvm-0.12.4 -net none -drive file=/dev/sdb,if=ide,boot=on,cache=none,aio=native -m 1024 -cpu qemu64,model_id='Intel(R) Xeon(R) CPU E5430 @ 2.66GHz' -monitor tcp:0:4001,server,nowait -vnc :1 -name 'test' -boot order=dc,menu=on -k de -pidfile /var/run/qemu/vm-149.pid -mem-path /hugepages -mem-prealloc -rtc base=utc,clock=vm -usb -usbdevice tablet + +The Guest is: +OpenSuse 11.2 64-bit with Kernel 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 +The clocksource automatically choosen is kvm-clock. + +Feedback appreciated. I have observed the same problem with 0.12.2 and also with old binaries provided by Ubuntu Karmic (kvm-88). \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/599574 b/results/classifier/deepseek-r1:14b/output/KVM/599574 new file mode 100644 index 00000000..61e51623 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/599574 @@ -0,0 +1,6 @@ + +qemu-kvm: -no-reboot option broken in 12.x + +When using the "-no-reboot" qemu option with kvm, qemu does nothing and immediately exits with no output or error message. If I add the --no-kvm option to the command line, it works as expected. + +It works fine in 11.0 and 11.1, but I tested all versions of 12.X, and they all have this problem. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/608 b/results/classifier/deepseek-r1:14b/output/KVM/608 new file mode 100644 index 00000000..2049eece --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/608 @@ -0,0 +1,2 @@ + +incremental_live_backup: Error prompt info when do incremental backup with an invalid "bitmap-mode" diff --git a/results/classifier/deepseek-r1:14b/output/KVM/628 b/results/classifier/deepseek-r1:14b/output/KVM/628 new file mode 100644 index 00000000..80ff28af --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/628 @@ -0,0 +1,9 @@ + +nested virtualization on whpx +Additional information: +Depends on, first needs fixing of, Issue #346 / Issue #430 , Essentially accel=whpx is not working/is broken/has regression. +``` +PS J:\> E:\scoopg\shims\qemu-system-x86_64.exe --version +QEMU emulator version 6.1.0 (v6.1.0-11882-g7deea770bf-dirty) +Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/642304 b/results/classifier/deepseek-r1:14b/output/KVM/642304 new file mode 100644 index 00000000..0a35bac4 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/642304 @@ -0,0 +1,10 @@ + +Solaris/x86 v10 hangs under KVM + +Solaris/x86 10 guest hangs when running under KVM with the message "Running Configuration Assistant". It runs fine when -enable-kvm isn't given as a command option. + +Host OS: Linux/x86_64 +Guest OS: Solaris/x86 +Command Line: qemu -hda solaris.img -m 192 -boot c -enable-kvm +Build Configure: ./configure --enable-linux-aio --enable-io-thread --enable-kvm +GIT commit: 58aebb946acff82c62383f350cab593e55cc13dc \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/643430 b/results/classifier/deepseek-r1:14b/output/KVM/643430 new file mode 100644 index 00000000..ea0c2906 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/643430 @@ -0,0 +1,18 @@ + +system_powerdown NOT working in qemu-kvm with KVM enabled for FreeBSD guests + +system_powerdown stops working in qemu-kvm for FreeBSD guests if KVM is enabled. + +How to reproduce: + +1. qemu -cdrom ~/.VirtualBox/libvirt/FreeBSD-8.1-RELEASE-i386-bootonly.iso +2. Enter system_powerdown in the qemu console +3. Nothing happens. + +Adding --no-kvm option makes system_powerdown work: + +1. qemu --no-kvm -cdrom ~/.VirtualBox/libvirt/FreeBSD-8.1-RELEASE-i386-bootonly.iso +2. system_powerdown +3. FreeBSD installer shows the shutdown dialog as expected + +Tested on FreeBSD 6.4, 7.2, and 8.0 with qemu-kvm 0.12.5 and older versions. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/674 b/results/classifier/deepseek-r1:14b/output/KVM/674 new file mode 100644 index 00000000..59cbf3ac --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/674 @@ -0,0 +1,15 @@ + +Windows 7 fails with blue screen when KVM is enabled. +Description of problem: +The problem appeared immediately after a full system update of Arch Linux (The first for several months). Windows 7 images that had been running normally would fail with a blue screen and Error 0x7E immediately after displaying "Starting Windows". The same error would occur with a Windows 7 installation image, as in the command line above. When the "-enable-kvm" option was removed Windows would run normally but slowly. An old Clonezilla image booted without apparent problems. + +The final line on the blue screen reads: +*** STOP: 0x0000007E (0xC0000005,0x8BA3CA36,0x85186AA0,0x85186680) + +After getting the problem with the Arch package I cloned the source and built the latest version, getting the same error. However, when I build version 5.2.95 (v6.0.0-rc5-dirty) I found that this would run my existing Windows images (qcow2) and the installation ISO image. +Steps to reproduce: +1. +2. +3. +Additional information: + diff --git a/results/classifier/deepseek-r1:14b/output/KVM/735 b/results/classifier/deepseek-r1:14b/output/KVM/735 new file mode 100644 index 00000000..2f1610d9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/735 @@ -0,0 +1,27 @@ + +softmmu 'at' not behaving +Description of problem: +This looks like a bug to me, please correct if I'm wrong. The execution context is EL2 here and we run KVM vms on top of the system emulation. Anyway, here we have stopped in the EL2 and want to translate a virtual address '0' with 'at'. While the '0' itself is not mapped, something in the first gigabyte is, and the softmmu refuses to walk to it: + +0x0000000100004a3c <at_s12e1r+8>: 80 78 0c d5 at s12e1r, x0 +0x0000000100004a40 <at_s12e1r+12>: 01 74 38 d5 mrs x1, par_el1 + +(gdb) info registers x0 x1 +x0 0x0 0 +x1 0x809 2057 + +So that would be translation fault level 0, stage 1 if I'm not mistaken. + +(gdb) info all-registers TCR_EL1 VTCR_EL2 TTBR1_EL1 +TCR_EL1 0x400035b5503510 18014629184681232 +VTCR_EL2 0x623590 6436240 +TTBR1_EL1 0x304000041731001 217298683118686209 + +(gdb) p print_table(0x41731000) +000:0x000000ffff9803 256:0x000000fffff803 507:0x00000041fbc803 +508:0x000000ff9ef803 + +The first gigabyte is populated, yet the 'at' knows nothing about it. Did I miss something? This seems to be working fine on the hardware. +Steps to reproduce: +1. Stop in the EL2 while the linux is running (GDB) +2. Use something along the lines of this function to translate any kernel virtual address: https://github.com/jkrh/kvms/blob/4c26c786be9971613b3b7f56121c1a1aa3b9585a/core/helpers.h#L74 diff --git a/results/classifier/deepseek-r1:14b/output/KVM/741887 b/results/classifier/deepseek-r1:14b/output/KVM/741887 new file mode 100644 index 00000000..964768b9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/741887 @@ -0,0 +1,80 @@ + +virsh snapshot-create too slow (kvm, qcow2, savevm) + +Action +====== +# time virsh snapshot-create 1 + +* Taking snapshot of a running KVM virtual machine + +Result +====== +Domain snapshot 1300983161 created +real 4m46.994s +user 0m0.000s +sys 0m0.010s + +Expected result +=============== +* Snapshot taken after few seconds instead of minutes. + +Environment +=========== +* Ubuntu Natty Narwhal upgraded from Lucid and Meerkat, fully updated. + +* Stock natty packages of libvirt and qemu installed (libvirt-bin 0.8.8-1ubuntu5; libvirt0 0.8.8-1ubuntu5; qemu-common 0.14.0+noroms-0ubuntu3; qemu-kvm 0.14.0+noroms-0ubuntu3). + +* Virtual machine disk format is qcow2 (debian 5 installed) +image: /storage/debian.qcow2 +file format: qcow2 +virtual size: 10G (10737418240 bytes) +disk size: 1.2G +cluster_size: 65536 +Snapshot list: +ID TAG VM SIZE DATE VM CLOCK +1 snap01 48M 2011-03-24 09:46:33 00:00:58.899 +2 1300979368 58M 2011-03-24 11:09:28 00:01:03.589 +3 1300983161 57M 2011-03-24 12:12:41 00:00:51.905 + +* qcow2 disk is stored on ext4 filesystem, without RAID or LVM or any special setup. + +* running guest VM takes about 40M RAM from inside, from outside 576M are given to that machine + +* host has fast dual-core pentium cpu with virtualization support, around 8G of RAM and 7200rpm harddrive (dd from urandom to file gives about 20M/s) + +* running processes: sshd, atd (empty), crond (empty), libvirtd, tmux, bash, rsyslogd, upstart-socket-bridge, udevd, dnsmasq, iotop (python) + +* networking is done by bridging and bonding + + +Detail description +================== + +* Under root, command 'virsh create-snapshot 1' is issued on booted and running KVM machine with debian inside. + +* After about four minutes, the process is done. + +* 'iotop' shows two 'kvm' processes reading/writing to disk. First one has IO around 1500 K/s, second one has around 400 K/s. That takes about three minutes. Then first process grabs about 3 M/s of IO and suddenly dissapears (1-2 sec). Then second process does about 7.5 M/s of IO for around a 1-2 minutes. + +* Snapshot is successfuly created and is usable for reverting or extracting. + +* Pretty much the same behaviour occurs when command 'savevm' is issued directly from qemu monitor, without using libvirf44bfb7fb978c9313ce050a1c4149bf04aa0a670t at all (actually, virsh snapshot-create just calls 'savevm' to the monitor socket). + +* This behaviour was observed on lucid, meerkat, natty and even with git version of libvirt (f44bfb7fb978c9313ce050a1c4149bf04aa0a670). Also slowsave packages from https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/524447 gave this issue. + + +Thank you for helping to solve this issue! + +ProblemType: Bug +DistroRelease: Ubuntu 11.04 +Package: libvirt-bin 0.8.8-1ubuntu5 +ProcVersionSignature: Ubuntu 2.6.38-7.38-server 2.6.38 +Uname: Linux 2.6.38-7-server x86_64 +Architecture: amd64 +Date: Thu Mar 24 12:19:41 2011 +InstallationMedia: Ubuntu-Server 10.04.2 LTS "Lucid Lynx" - Release amd64 (20110211.1) +ProcEnviron: + LANG=en_US.UTF-8 + SHELL=/bin/bash +SourcePackage: libvirt +UpgradeStatus: No upgrade log present (probably fresh install) \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/744856 b/results/classifier/deepseek-r1:14b/output/KVM/744856 new file mode 100644 index 00000000..510913aa --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/744856 @@ -0,0 +1,11 @@ + +can't boot when using more than 6 disks since qemu-kvm-0.13 + +It's not possible to pass more than 6 disks to a guest since qemu-kvm-0.13 (also tested with 0.14). +If I pass more than 6 disks (as shown below) the machine complains that their is no bootable disk, + +The problem occurs with virtio and without virtio. + +eg. + +/usr/bin/qemu-system-x86_64 --enable-kvm -boot c -drive file=/dev/vgr5/fs-01,if=virtio -drive file=/dev/vgr5/fs-01_srv_workspace,if=virtio -drive file=/dev/vgr5/fs-01_srv_media,if=virtio -drive file=/dev/vgr5/fs-01_srv_company,if=virtio -drive file=/dev/vgr5/fs-01_srv_tmp,if=virtio -drive file=/dev/vgr5/fs-01_srv_download,if=virtio -drive file=/dev/vgr5/fs-01_srv_share,if=virtio -drive file=/dev/vgr5/fs-01_srv_backup,if=virtio -drive file=/dev/vgr5/fs-01_srv_private,if=virtio -drive file=/dev/vgr5/fs-01_srv_build,if=virtio -drive file=/dev/vgr5/fs-01_srv_dev,if=virtio -drive file=/dev/vgr5/fs-01_srv_backup2,if=virtio -drive file=/dev/vgr5/fs-01_srv_ftp,if=virtio -cpu qemu64 -smp 2 -m 4G -append root=/dev/vda -usbdevice tablet -net nic,macaddr=90:e6:ba:9d:00:0,model=e1000 -net tap,ifname=tap0,script=/usr/sbin/qemu-ifup,downscript=/usr/sbin/qemu-ifdown -monitor unix:/var/run/kvm/fs-01/monitor,server,nowait -pidfile /var/run/kvm/fs-01/pid -k de -kernel /srv/kvm/kernel/linux-2.6.38-gentoo -append root=/dev/vda -vnc :0 -name fs-01,process=fs-01 -vga std \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/747583 b/results/classifier/deepseek-r1:14b/output/KVM/747583 new file mode 100644 index 00000000..38fc7f3d --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/747583 @@ -0,0 +1,23 @@ + +Windows 2008 Time Zone Change Even When Using -locatime + +* What cpu model : Intel(R) Xeon(R) CPU E5620 @ 2.40GHz +* What kvm version you are using. : qemu-kvm-0.12.3 +* The host kernel version : 2.6.32-30-server +* What host kernel arch you are using (i386 or x86_64) : x86_64 +* What guest you are using, including OS type: Windows 2008 Enterprise x86_64 +* The qemu command line you are using to start the guest : /usr/bin/kvm -S -M pc-0.12 -enable-kvm -m 1024 -smp 1 -name 2-6176 -uuid 4d1d56b1-d0b7-506b-31a5-a87c8cb0560b -chardev socket,id=monitor,path=/var/lib/libvirt/qemu/2-6176.monitor,server,nowait -monitor chardev:monitor -localtime -boot c -drive file=/dev/disk/by-id/scsi-3600144f05c11090000004d9602950073,if=virtio,index=0,boot=on,format=raw -drive file=/dev/disk/by-id/scsi-3600144f0eae8810000004c7bb0920037,if=ide,media=cdrom,index=2,format=raw -net nic,macaddr=00:00:d1:d0:3f:5e,vlan=0,name=nic.1 -net tap,fd=212,vlan=0,name=tap.1 -net nic,macaddr=00:00:0a:d0:3f:5e,vlan=1,name=nic.1 -net tap,fd=213,vlan=1,name=tap.1 -chardev pty,id=serial0 -serial chardev:serial0 -parallel none -usb -usbdevice tablet -vnc 0.0.0.0:394,password -k en-us -vga cirrus +* Whether the problem goes away if using the -no-kvm-irqchip or -no-kvm-pit switch. : Unable to test +* Whether the problem also appears with the -no-kvm switch. : Unable to test + +Host time zone: EDT Guest time zone: PDT + +Steps to reproduce: +1) Set time zone to (GMT-08:00) Pacific Time (US & Canada) on guest +2) Power off Windows 2008 Enterprise x86_64 guest completely. Ensure the kvm process exits. +3) Power on Windows 2008 Enterprise x86_64 guest using virsh start <domain> +4) Server will show EDT time but have the time zone still set to (GMT-08:00) Pacific Time (US & Canada). + +Syncing the time after stopping and starting the kvm process using Windows "Internet Time" ntp time sync will sync the time to the correct PDT time. + +Doing a reboot from within the guest's operating system where kvm does not exit will not cause the timezone shift to happen. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/755 b/results/classifier/deepseek-r1:14b/output/KVM/755 new file mode 100644 index 00000000..97788ed7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/755 @@ -0,0 +1,60 @@ + +Qemu is stuck on the startup intermittently. +Description of problem: +Qemu is stuck on the startup intermittently. + +We are using kubevirt to launch the VM in kubernetes env. We have compiled qemu with a few flags enabled and using it. +All things are working as expected except we are seeing qemu stuck issue during VM startup. Please find logs from system in additional information + +Qemu version: qemu-system-x86-core-5.1.0-9.fc32.x86_64.rpm +Libvirtd version: 6.6.0 +Steps to reproduce: +1. Create and start a VM. +Additional information: +TOP OUTPUT: +-------------- +``` + PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND + **125 qemu 0 -20 8519896 73392 15412 R 99.9 0.1 85:27.96 CPU 0/KVM ** + 113 qemu 20 0 8519896 73392 15412 S 0.0 0.1 0:00.14 qemu-system-ori + 121 qemu 20 0 8519896 73392 15412 S 0.0 0.1 0:00.00 qemu-system-ori + 122 qemu 20 0 8519896 73392 15412 S 0.0 0.1 0:00.00 IO iothread1 + 124 qemu 20 0 8519896 73392 15412 S 0.0 0.1 0:00.23 IO mon_iothread + 126 qemu 0 -20 8519896 73392 15412 S 0.0 0.1 0:00.00 CPU 1/KVM + 128 qemu 20 0 8519896 73392 15412 S 0.0 0.1 0:00.00 vnc_worker +``` + +qemu logs on error: +------------------- +``` +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +KVM: injection failed, MSI lost (Operation not permitted) +``` + +dmesg logs from host:- +---------------------- +``` +[ 7853.643187] kvm: apic: phys broadcast and lowest prio +[ 7853.643265] kvm: apic: phys broadcast and lowest prio +[ 7853.643341] kvm: apic: phys broadcast and lowest prio +[ 7853.643413] kvm: apic: phys broadcast and lowest prio +[ 7853.643486] kvm: apic: phys broadcast and lowest prio +[ 7853.643559] kvm: apic: phys broadcast and lowest prio +[ 7853.643631] kvm: apic: phys broadcast and lowest prio +[ 7853.643703] kvm: apic: phys broadcast and lowest prio +[ 7853.643776] kvm: apic: phys broadcast and lowest prio +[ 7853.643848] kvm: apic: phys broadcast and lowest prio +[ 7853.643920] kvm: apic: phys broadcast and lowest prio +[ 7853.643992] kvm: apic: phys broadcast and lowest prio +[ 7853.644065] kvm: apic: phys broadcast and lowest prio +[ 7853.644137] kvm: apic: phys broadcast and lowest prio +[ 7853.644209] kvm: apic: phys broadcast and lowest prio +[ 7853.644289] kvm: apic: phys broadcast and lowest prio +``` + +--> diff --git a/results/classifier/deepseek-r1:14b/output/KVM/772 b/results/classifier/deepseek-r1:14b/output/KVM/772 new file mode 100644 index 00000000..6847b45e --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/772 @@ -0,0 +1,13 @@ + +Pop!_OS 20.10 host + RHEL 8.5 guest = Oh no! Something has gone wrong. +Description of problem: +Whenever starting the Qemu VM, there is an error covering the whole desktop "Oh no! Something has gone wrong. A problem has occurred and the system can't recover. Please log out and try again." After clicking the "Log Out" button and waiting for hours, the guest RHEL may or may not recover, based on your luck and other qemu options used. +Steps to reproduce: +1. Build qemu using the following `./configure` options: +``` +--prefix=$HOME/.bin --target-list=x86_64-softmmu --enable-kvm --enable-vnc --enable-gtk --enable-vte --enable-xkbcommon --enable-sdl --enable-spice --enable-spice-protocol --enable-virglrenderer --enable-opengl --enable-guest-agent --enable-avx2 --enable-avx512f --enable-hax --enable-system --enable-linux-user --enable-libssh --enable-linux-aio --enable-linux-io-uring --enable-modules --enable-gio --enable-fuse --enable-fuse-lseek +``` +2. Install Red Hat Enterprise Linux 8.5 in qemu +3. Run qemu using the above command line. +Additional information: + diff --git a/results/classifier/deepseek-r1:14b/output/KVM/797905 b/results/classifier/deepseek-r1:14b/output/KVM/797905 new file mode 100644 index 00000000..a83a0b0f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/797905 @@ -0,0 +1,20 @@ + +virsh live migration + +Hi, +i do not manage to do a virsh migrate live command. +Using Ubuntu Server 10.04 x64 + +root@svr50abl:~# virsh list + Id Nome Estado +---------------------------------- + 18 Winxp executando + 19 teste executando + +root@svr50abl:~# sudo virsh migrate --live 19 qemu+ssh://10.1.5.1/system +root@10.1.5.1's password: +erro: unable to set user and group to '116:127' on '/var/lib/libvirt/images/teste.img': No such file or directory + +teste.img has root:root (xrw) + +10.1.5.1 is a functional kvm host too \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/808 b/results/classifier/deepseek-r1:14b/output/KVM/808 new file mode 100644 index 00000000..b2e98382 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/808 @@ -0,0 +1,19 @@ + +virtio-scsi in Windows guests cause QEMU to abort/crash +Description of problem: +* Attempting to load the virtio-scsi drivers in a Windows guest causes the VM to abort/crash. +Steps to reproduce: +* `qemu-system-x86_64 -accel kvm -m 4G -device virtio-scsi-pci,id=scsi0 -drive media=cdrom,file=windows7-x64.iso -drive media=cdrom,file=virtio-win-0.1.173.iso` + * Boot the installer ISO, click through all the menus to eventually get to Custom Install + * In "Where do you want to install" click Load driver + * Browse E: drive and pick the first amd64/w7 folder + * Should show "Red Had VirtIO SCSI pass-through controller" + * Click Next + * Abort/crash + +Same thing happens with VM's that used to work already running the virtio-scsi drivers. When they boot the VM aborts. +Additional information: +``` +qemu-system-x86_64: ../accel/kvm/kvm-all.c:1760: kvm_irqchip_commit_routes: Assertion `ret == 0' failed. +Aborted (core dumped) +``` diff --git a/results/classifier/deepseek-r1:14b/output/KVM/823733 b/results/classifier/deepseek-r1:14b/output/KVM/823733 new file mode 100644 index 00000000..9a8a35b9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/823733 @@ -0,0 +1,105 @@ + +Solaris can't be powered off with ACPI shutdown/poweroff + +Thank you forgive my poor English. + +It seems KVM can’t poweroff solairs 10 or sloalrs 11 VM. +I have created solaris 10 and 11 as usual. Everything in VM is running OK, but finally I use shell command ‘poweroff’ or ‘init 5’, the solaris VM (both 10 & 11) system could’t be poweroff but with promoting me the message: perss any key to reboot ….. ,I pressed any key in vnc client, solaris VM reboot immediately. Endless reboot loop above. + +the solaris 10 & 11 from oracle iso file name : +sol-10-u9-ga-x86-dvd.iso +sol-11-exp-201011-text-x86.iso + +the solaris 10 & 11 from oracle iso file name : +sol-10-u9-ga-x86-dvd.iso +sol-11-exp-201011-text-x86.iso + +1. On my real physical machine,the solaris can be poweroff +2. On vmware ,the solaris can be poweroff +3. On my real physical machine,I have try to disbale the ACPI opiton in BOIS, then the solaris can't be poweroff,Like the problem I have described above +so ,I doubt the KVM has a little problem in ACPI + +I have try the suggestion as follows, but I can’t solve the problem. +7.2 Solaris reboot all the time on grub menu +• Run through the installer as usual +• On completion and reboot, the VM will perpetually reboot. "Stop" the VM. +• Start it up again, and immediately open a vnc console and select the Safe Boot from the options screen +• When prompted if you want to try and recover the boot block, say yes +• You should now have a Bourne terminal with your existing filesystem mounted on /a +• Run /a/usr/bin/bash (my preferred shell) +• export TERM=xterm +• vi /a/boot/grub/menu.1st (editing the bootloader on your mounted filesystem), to add "kernel/unix" to the kernel options for the non-safe-mode boot. Ex : +Config File : /a/boot/grub/menu.lst +kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS kernel/unix + +According to KVM requirements, I collected the following information: +CPU model name +model name : Intel(R) Xeon(R) CPU X3450 @ 2.67GHz + +kvm -version +QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3), Copyright (c) 2003-2008 Fabrice Bellard + +Host kernel version +Ubuntu 10.04.1 LTS 2.6.32-25-server + +What host kernel arch you are using (i386 or x86_64) +X86_64 + +Guest OS +Solaris 10 and Solaris 11，both can not shutdown + +The qemu command line you are using to start the guest + +First, I used the command line as follows: +kvm -m 1024 -drive file=solaris10.img,cache=writeback -net nic -net user -nographic -vnc :1 +then I try to use -no-kvm-irqchip or -no-kvm ,but the problem also appears! + +Secondly, have created and run solaris 10&11 by using Virsh, still solaris can't be poweroff, the XML file content is : +<domain type='kvm'> + <name>solairs</name> + <uuid>85badf15-244d-4719-a2da-8c3de064137d</uuid> + <memory>1677721</memory> + <currentMemory>1677721</currentMemory> + <vcpu>1</vcpu> + <os> + <type arch='i686' machine='pc-0.12'>hvm</type> + <boot dev='hd'/> + </os> + <features> + <acpi/> + <apic/> + </features> + <clock offset='utc'/> + <on_poweroff>destroy</on_poweroff> + <on_reboot>restart</on_reboot> + <on_crash>destroy</on_crash> + <devices> + <emulator>/usr/bin/kvm</emulator> + <disk type='file' device='disk'> + <driver name='qemu' type='qcow2' cache='writeback'/> + <source file='/opt/GuestOS/solaris10.img'/> + <target dev='hda' bus='ide'/> + </disk> + <interface type='bridge'> + <mac address='00:0c:29:d0:36:c3'/> + <source bridge='br1'/> + <target dev='vnet0'/> + </interface> + <input type='mouse' bus='ps2'/> + <graphics type='vnc' port='5901' autoport='no' keymap='en-us'/> + <video> + <model type='vga' vram='65536' heads='1'/> + </video> + </devices> + <seclabel type='dynamic' model='apparmor'> + <label>libvirt-f36f5289-692e-6f1c-fe71-c6ed19453e2f</label> + <imagelabel>libvirt-f36f5289-692e-6f1c-fe71-c6ed19453e2f</imagelabel> + </seclabel> + </domain> + + + + + + + diff --git a/results/classifier/deepseek-r1:14b/output/KVM/846 b/results/classifier/deepseek-r1:14b/output/KVM/846 new file mode 100644 index 00000000..490fc9e7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/846 @@ -0,0 +1,2 @@ + +Why qemu crashes and calling SYS_SECCOMP function diff --git a/results/classifier/deepseek-r1:14b/output/KVM/855800 b/results/classifier/deepseek-r1:14b/output/KVM/855800 new file mode 100644 index 00000000..f122749c --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/855800 @@ -0,0 +1,40 @@ + +KVM crashes when attempting to restart migration + +Operations performed: +Sequence to trigger crash: + + * Start two kvm systems, one on gerph (primary), one on nbuild2 (listening for incoming migration) - do not use -daemonize + * On gerph, connect to monitor. + * "migrate -d -b tcp:nbuild2:4444" + * "info migrate" + * "migrate_cancel" + * "info migrate" + * "migrate -d -b tcp:nbuild2:4444" + * crashed with assertion: +kvm: block-migration.c:355: flush_blks: Assertion `block_mig_state.read_done >= 0' failed. + Connection closed by foreign host. +[1]+ Aborted (core dumped) kvm -drive file=./copy-disk2.img,boot=on -m 4096 -serial mon:telnet::23023,server,nowait -balloon virtio -vnc :99 -usbdevice tablet -net nic,macaddr=f6:a6:31:53:89:9a,model=rtl8139,vlan=0 -net tap,vlan=0 + + +Repeating the operations above often dies in different places; just repeat the cancel and restart the operation. Because the KVM system dies, the underlying VM is obviously terminated. + +Distribution: + +jfletcher@gerph:~$ lsb_release -rd +Description: Ubuntu 10.04.3 LTS +Release: 10.04 + +Package: + +jfletcher@gerph:~$ apt-cache policy kvm +kvm: + Installed: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.15 + Candidate: 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.15 + Version table: + *** 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9.15 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages + 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages + 100 /var/lib/dpkg/status + 1:84+dfsg-0ubuntu16+0.12.3+noroms+0ubuntu9 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/862 b/results/classifier/deepseek-r1:14b/output/KVM/862 new file mode 100644 index 00000000..5b9ca236 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/862 @@ -0,0 +1,50 @@ + +Using qemu+kvm is slower than using qemu in rv6(xv6 rust porting) +Description of problem: +Using qemu+kvm is slower than using qemu in rv6(xv6 rust porting) +Steps to reproduce: +``` +git clone https://github.com/kaist-cp/rv6 +cd rv6 +make clean +TARGET=arm GIC_VERSION=3 KVM=yes make qemu +``` +Additional information: +We are currently working on the [rv6 project](https://github.com/kaist-cp/rv6) which is porting MIT's educational operating system [xv6](https://github.com/mit-pdos/xv6-public) to Rust.<br> Our code is located [here](https://github.com/kaist-cp/rv6/tree/main/kernel-rs). +We use qemu and [qemu's virt platform](https://qemu.readthedocs.io/en/latest/system/arm/virt.html) to execute rv6, and it works well with using qemu. +Executing command on arm machine is this: +``` +RUST_MODE=release TARGET=arm KVM=yes GIC_VERSION=3 +qemu-system-aarch64 -machine virt -kernel kernel/kernel -m 128M -smp 80 -nographic -drive file=fs.img,if=none,format=raw,id=x0,copy-on-read=off -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -cpu cortex-a53 -machine gic-version=3 -net none +``` +To make some speed boost experiment with KVM, we made rv6 support the arm architecture on arm machine. The arm architecture's driver code locates in [here](https://github.com/kaist-cp/rv6/tree/main/kernel-rs/src/arch/arm). +The problem is, when we use qemu with kvm, the performance is significantly reduced. +Executing command on arm machine with KVM is this: +``` +qemu-system-aarch64 -machine virt -kernel kernel/kernel -m 128M -smp 80 -nographic -drive file=fs.img,if=none,format=raw,id=x0,copy-on-read=off -device virtio-blk-device,drive=x0,bus=virtio-mmio-bus.0 -cpu host -enable-kvm -machine gic-version=3 -net none +``` +We repeated +1. Write 500 bytes syscall 10,000 times and the result was: kvm disable: 4,500,000 us, kvm enable: 29,000,000 us. (> 5 times) +2. Open/Close syscall 10,000 times result: kvm disable: 12,000,000 us, kvm enable: 29,000,000 us. (> 5 times) +3. Getppid syscall 10,000 times result: kvm disable: 735,000 us, kvm enable: 825,000 us. (almost same) +4. Simple calculation(a = a * 1664525 + 1013904223) 100 million times result: kvm disable: 2,800,000 us, kvm enable: 65,000,000 us. (> 20 times) + +And the elapsed time was estimated by [uptime_as_micro](https://github.com/kaist-cp/rv6/blob/90b84b60931327ae8635875b788b10280e47b99c/kernel-rs/src/arch/arm/timer.rs#L17) syscall in rv6. +These results were so hard to understand. <br>So first we tried to find the bottleneck on rv6's booting process, because finding bottleneck during processing user program was so difficult. +We found that the first noticeable bottleneck on rv6 booting process was [here](https://github.com/kaist-cp/rv6/blob/main/kernel-rs/src/kalloc.rs#L107-L108): +``` +run.as_mut().init(); +self.runs().push_front(run.as_ref()); +``` +As far as we know, this part is just kind of "list initialization and push element" part. So we thought that by some reason, the KVM is not actually working and it makes worse result. And also this part is even before turn on some interrupts, so we thought [arm's GIC](https://developer.arm.com/documentation/dai0492/b/) or interrupt related thing is not related with problem. + +So, how can I get better performance when using kvm with qemu? + +To solve this problem, we tried these already: +1. change qemu(4.2, 6.2), virt version, change [some command for qemu-kvm](https://linux.die.net/man/1/qemu-kvm) like cpu, drive cache, copy-on-read something, kernel_irqchip.., cpu core.. etc +2. find some kvm hypercall to use - but not exists on arm64 +3. Run [lmbench](http://lmbench.sourceforge.net/) by ubuntu on qemu with kvm to check KVM itself is okay. - We found KVM with ubuntu is super faster than only using qemu. +4. Check [16550a UART print code](https://github.com/kaist-cp/rv6/blob/main/kernel-rs/src/arch/arm/uart.rs) is really slow on enabling KVM which makes incorrect result on benchmark - Without bottleneck code, we found the progress time of rv6 booting were almost same with KVM enabled or not. +5. Check other people who suffer same situation like us - but [this superuser page](https://superuser.com/questions/1317948/qemu-enable-kvm-slower-than-pure-emulation-for-x86-64) not works. Our clocksource is arch_sys_counter. + +Thank you for your help. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/899961 b/results/classifier/deepseek-r1:14b/output/KVM/899961 new file mode 100644 index 00000000..6000ff3f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/899961 @@ -0,0 +1,4 @@ + +qemu/kvm locks up when run 32bit userspace with 64bit kernel + +Applies to both qemu and qemu-kvm 1.0, but only when kernel is 64bit and userspace is 32bit, on x86. Did not happen with previous released versions, such as 0.15. Not all guests triggers this issue - so far, only (32bit) windows 7 guest shows it, but does that quite reliable: first boot of an old guest with new qemu (or qemu-kvm), windows finds a new CPU and suggests rebooting - hit "Reboot" and in a few seconds it will be locked up (including the monitor), with 100% CPU usage. Killable with -9. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/916 b/results/classifier/deepseek-r1:14b/output/KVM/916 new file mode 100644 index 00000000..9d17c26d --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/916 @@ -0,0 +1,12 @@ + +QEMU system emulators immediately crash on AMD hosts when KVM is used +Description of problem: +``` +$ qemu-system-x86_64 -accel kvm +qemu-system-x86_64: ../target/i386/kvm/kvm-cpu.c:105: kvm_cpu_xsave_init: Assertion `esa->size == eax' failed. +Aborted (core dumped) +``` + +This is a regression introduced in + +https://lists.gnu.org/archive/html/qemu-devel/2022-03/msg04312.html diff --git a/results/classifier/deepseek-r1:14b/output/KVM/920772 b/results/classifier/deepseek-r1:14b/output/KVM/920772 new file mode 100644 index 00000000..54fff66f --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/920772 @@ -0,0 +1,38 @@ + +Win98SE glitches RHEL6.2/CentOS6.2 QEMU + +I'm not sure if this is something anyone will be interested in, +but I ran into some glitches setting up a Windows 98 SE +QEMU VM with a relatively recent version. Needed this +to restore an ancient backup and got it working well +enough to get the job done. + +Versions +======== + +Distro: CentOS 6.2 + +Kernel: upstream 3.1.8 + +QEMU: +gpxe-roms-qemu-0.9.7-6.9.el6.noarch +qemu-img-0.12.1.2-2.209.el6_2.1.x86_64 +qemu-kvm-0.12.1.2-2.209.el6_2.1.x86_64 + +Glitches: + +1) Doesn't work in KVM mode, screen goes black +just after installer is finishing up and switching to +Win98. Saw this issue has been around for awhile. + +2) Got it working in QEMU mode, but BIOS plug-n-play +driver fails. This prevents other devices from working. + +a) CDROM not recognized + +b) Realtek 8139C driver (installed separately after +Win98) not recognized. + +I don't need these issues fixed, just reporting the +in case it's of interest and/or helpful. Can provide +more detail on request. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/921208 b/results/classifier/deepseek-r1:14b/output/KVM/921208 new file mode 100644 index 00000000..e8fccef7 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/921208 @@ -0,0 +1,45 @@ + +win7/x64 installer hangs on startup with 0x0000005d. + +hi, + +during booting win7/x64 installer i'm observing a bsod with 0x0000005d ( msdn: unsupported_processor ). + +used command line: qemu-system-x86_64 -m 2048 -hda w7-system.img -cdrom win7_x64.iso -boot d + +adding '-machine accel=kvm' instead of default tcg accel helps to boot. + + +installed software: + +qemu-1.0 +linux-3.2.1 +glibc-2.14.1 +gcc-4.6.2 + +hw cpu: + +processor : 0..7 +vendor_id : GenuineIntel +cpu family : 6 +model : 42 +model name : Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz +stepping : 7 +microcode : 0x14 +cpu MHz : 1995.739 +cache size : 6144 KB +physical id : 0 +siblings : 8 +core id : 3 +cpu cores : 4 +apicid : 7 +initial apicid : 7 +fpu : yes +fpu_exception : yes +cpuid level : 13 +wp : yes +flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat epb xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid +bogomips : 3992.23 +clflush size : 64 +cache_alignment : 64 +address sizes : 36 bits physical, 48 bits virtual \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/922355 b/results/classifier/deepseek-r1:14b/output/KVM/922355 new file mode 100644 index 00000000..2a81d6fa --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/922355 @@ -0,0 +1,10 @@ + +qemu crashes when invoked on Pandaboard + +root@omap:~# uname -a +Linux omap 3.1.6-x6 #1 SMP Thu Dec 22 11:17:51 UTC 2011 armv7l armv7l +armv7l GNU/Linux + +root@omap:~# qemu +Could not initialize KVM, will disable KVM support +/build/buildd/qemu-kvm-0.14.1+noroms/tcg/arm/tcg-target.c:848: tcg fatal error \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/945 b/results/classifier/deepseek-r1:14b/output/KVM/945 new file mode 100644 index 00000000..5b6a4ca9 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/945 @@ -0,0 +1,11 @@ + +For QEMU 7.0.0-rc1, nbd-server-add fails with qcow2 image with iothread in migration context +Description of problem: +Upon adding the drive for NBD (via QMP), there is an error message +````kvm: ../block.c:3657: bdrv_open_child: Assertion `qemu_in_main_thread()' failed.```` +and then the process aborts. +Steps to reproduce: +1. Create image: `qemu-img create -f qcow2 /root/target-disk.qcow2 4G` +2. Start QEMU as mentioned above. +3. Issue `nbd-server-start` QMP command (I used type unix). +4. Issue `nbd-server-add` command for the single disk. diff --git a/results/classifier/deepseek-r1:14b/output/KVM/961 b/results/classifier/deepseek-r1:14b/output/KVM/961 new file mode 100644 index 00000000..db5103d2 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/961 @@ -0,0 +1,2 @@ + +Property not found when using aarch64 `-machine=virt,secure=on` with KVM enabled diff --git a/results/classifier/deepseek-r1:14b/output/KVM/977391 b/results/classifier/deepseek-r1:14b/output/KVM/977391 new file mode 100644 index 00000000..5a0a1ce0 --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/977391 @@ -0,0 +1,11 @@ + +BUG: soft lockup - CPU#8 stuck for 61s! [kvm:*] in lucid + +Two days back my KVM base machine got hung up all of a sudden. +Not sure what exactly happened. + +cat /proc/version_signature +Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12 + + +-Rahul N. \ No newline at end of file diff --git a/results/classifier/deepseek-r1:14b/output/KVM/992067 b/results/classifier/deepseek-r1:14b/output/KVM/992067 new file mode 100644 index 00000000..349633aa --- /dev/null +++ b/results/classifier/deepseek-r1:14b/output/KVM/992067 @@ -0,0 +1,23 @@ + +Windows 2008R2 very slow cold boot when >4GB memory + +I've been having a consistent problem booting 2008R2 guests with 4096MB of RAM or greater. On the initial boot the KVM process starts out with a ~200MB memory allocation and will use 100% of all CPU allocated to it. The RES memory of the KVM process slowly rises by around 200mb every few minutes until it reaches it's memory allocation (several hours in some cases). Whilst this is happening the guest will usually blue screen with the message of - + +A clock interrupt was not received on a secondary processor within the allocated time interval + +If I let the KVM process continue to run it will eventually allocate the required memory the guest will run at full speed, usually restarting after the blue screen and booting into startup repair. From here you can restart it and it will boot perfectly. Once booted the guest has no performance issues at all. + +I've tried everything I could think of. Removing PAE, playing with huge pages, different kernels, different userspaces, different systems, different backing file systems, different processor feature set, with or without Virtio etc. My best theory is that the problem is caused by Windows 2008 zeroing out all the memory on boot and something is causing this to be held up or slowed to a crawl. The hosts always have memory free to boot the guest and are not using swap at all. + +Nothing so far has solved the issue. A few observations I've made about the issue are - +Large memory 2008R2 guests seem to boot fine (or with a small delay) when they are the first to boot on the host after a reboot +Sometimes dropping the disk cache (echo 1 > /proc/sys/vm/drop_caches) will cause them to boot faster + + +The hosts I've tried are - +All Nehalem based (5540, 5620 and 5660) +Host ram of 48GB, 96GB and 192GB +Storage on NFS, Gluster and local (ext4, xfs and zfs) +QED, QCOW and RAW formats +Scientific Linux 6.1 with the standard kernel 2.6.32, 2.6.38 and 3.3.1 +KVM userspaces 0.12, 0.14 and (currently) 0.15.1 \ No newline at end of file |