From d0c85e36e4de67af628d54e9ab577cc3fad7796a Mon Sep 17 00:00:00 2001 From: Christian Krinitsin Date: Thu, 3 Jul 2025 07:27:52 +0000 Subject: add deepseek and gemma results --- results/classifier/gemma3:12b/socket/1020484 | 4 + results/classifier/gemma3:12b/socket/1055 | 17 ++ results/classifier/gemma3:12b/socket/1064631 | 14 ++ results/classifier/gemma3:12b/socket/1075272 | 14 ++ results/classifier/gemma3:12b/socket/1075339 | 4 + results/classifier/gemma3:12b/socket/1090726 | 49 ++++++ results/classifier/gemma3:12b/socket/1156632 | 25 +++ results/classifier/gemma3:12b/socket/1264 | 2 + results/classifier/gemma3:12b/socket/1316 | 2 + results/classifier/gemma3:12b/socket/1327608 | 24 +++ results/classifier/gemma3:12b/socket/1353149 | 20 +++ results/classifier/gemma3:12b/socket/1381879 | 34 ++++ results/classifier/gemma3:12b/socket/1426 | 39 +++++ results/classifier/gemma3:12b/socket/1471 | 17 ++ results/classifier/gemma3:12b/socket/1472083 | 28 ++++ results/classifier/gemma3:12b/socket/1478360 | 133 ++++++++++++++++ results/classifier/gemma3:12b/socket/1495 | 7 + results/classifier/gemma3:12b/socket/1504513 | 26 +++ results/classifier/gemma3:12b/socket/1542965 | 6 + results/classifier/gemma3:12b/socket/1549 | 96 ++++++++++++ results/classifier/gemma3:12b/socket/1553 | 13 ++ results/classifier/gemma3:12b/socket/1581695 | 19 +++ results/classifier/gemma3:12b/socket/1586756 | 53 +++++++ results/classifier/gemma3:12b/socket/1605443 | 12 ++ results/classifier/gemma3:12b/socket/1612908 | 8 + results/classifier/gemma3:12b/socket/1643619 | 33 ++++ results/classifier/gemma3:12b/socket/1668273 | 65 ++++++++ results/classifier/gemma3:12b/socket/1701808 | 17 ++ results/classifier/gemma3:12b/socket/1711602 | 28 ++++ results/classifier/gemma3:12b/socket/1713328 | 10 ++ results/classifier/gemma3:12b/socket/1754605 | 15 ++ results/classifier/gemma3:12b/socket/1777 | 2 + results/classifier/gemma3:12b/socket/1781280 | 10 ++ results/classifier/gemma3:12b/socket/1807052 | 226 +++++++++++++++++++++++++++ results/classifier/gemma3:12b/socket/1816819 | 52 ++++++ results/classifier/gemma3:12b/socket/1823790 | 22 +++ results/classifier/gemma3:12b/socket/1829779 | 36 +++++ results/classifier/gemma3:12b/socket/1837 | 36 +++++ results/classifier/gemma3:12b/socket/1840252 | 61 ++++++++ results/classifier/gemma3:12b/socket/1843590 | 24 +++ results/classifier/gemma3:12b/socket/1862619 | 15 ++ results/classifier/gemma3:12b/socket/1867601 | 16 ++ results/classifier/gemma3:12b/socket/1881 | 16 ++ results/classifier/gemma3:12b/socket/1890395 | 137 ++++++++++++++++ results/classifier/gemma3:12b/socket/1892684 | 25 +++ results/classifier/gemma3:12b/socket/1898084 | 24 +++ results/classifier/gemma3:12b/socket/2065579 | 77 +++++++++ results/classifier/gemma3:12b/socket/2197 | 59 +++++++ results/classifier/gemma3:12b/socket/2230 | 142 +++++++++++++++++ results/classifier/gemma3:12b/socket/2254 | 2 + results/classifier/gemma3:12b/socket/2292 | 20 +++ results/classifier/gemma3:12b/socket/2337 | 63 ++++++++ results/classifier/gemma3:12b/socket/2346 | 73 +++++++++ results/classifier/gemma3:12b/socket/2390 | 64 ++++++++ results/classifier/gemma3:12b/socket/2410 | 93 +++++++++++ results/classifier/gemma3:12b/socket/2592 | 38 +++++ results/classifier/gemma3:12b/socket/2720 | 71 +++++++++ results/classifier/gemma3:12b/socket/284 | 2 + results/classifier/gemma3:12b/socket/2925 | 26 +++ results/classifier/gemma3:12b/socket/347 | 2 + results/classifier/gemma3:12b/socket/602 | 14 ++ results/classifier/gemma3:12b/socket/607 | 60 +++++++ results/classifier/gemma3:12b/socket/676029 | 19 +++ results/classifier/gemma3:12b/socket/717929 | 24 +++ results/classifier/gemma3:12b/socket/764 | 46 ++++++ results/classifier/gemma3:12b/socket/833 | 43 +++++ results/classifier/gemma3:12b/socket/834 | 60 +++++++ results/classifier/gemma3:12b/socket/845 | 60 +++++++ results/classifier/gemma3:12b/socket/872 | 2 + results/classifier/gemma3:12b/socket/885 | 2 + results/classifier/gemma3:12b/socket/916720 | 11 ++ results/classifier/gemma3:12b/socket/988128 | 29 ++++ 72 files changed, 2638 insertions(+) create mode 100644 results/classifier/gemma3:12b/socket/1020484 create mode 100644 results/classifier/gemma3:12b/socket/1055 create mode 100644 results/classifier/gemma3:12b/socket/1064631 create mode 100644 results/classifier/gemma3:12b/socket/1075272 create mode 100644 results/classifier/gemma3:12b/socket/1075339 create mode 100644 results/classifier/gemma3:12b/socket/1090726 create mode 100644 results/classifier/gemma3:12b/socket/1156632 create mode 100644 results/classifier/gemma3:12b/socket/1264 create mode 100644 results/classifier/gemma3:12b/socket/1316 create mode 100644 results/classifier/gemma3:12b/socket/1327608 create mode 100644 results/classifier/gemma3:12b/socket/1353149 create mode 100644 results/classifier/gemma3:12b/socket/1381879 create mode 100644 results/classifier/gemma3:12b/socket/1426 create mode 100644 results/classifier/gemma3:12b/socket/1471 create mode 100644 results/classifier/gemma3:12b/socket/1472083 create mode 100644 results/classifier/gemma3:12b/socket/1478360 create mode 100644 results/classifier/gemma3:12b/socket/1495 create mode 100644 results/classifier/gemma3:12b/socket/1504513 create mode 100644 results/classifier/gemma3:12b/socket/1542965 create mode 100644 results/classifier/gemma3:12b/socket/1549 create mode 100644 results/classifier/gemma3:12b/socket/1553 create mode 100644 results/classifier/gemma3:12b/socket/1581695 create mode 100644 results/classifier/gemma3:12b/socket/1586756 create mode 100644 results/classifier/gemma3:12b/socket/1605443 create mode 100644 results/classifier/gemma3:12b/socket/1612908 create mode 100644 results/classifier/gemma3:12b/socket/1643619 create mode 100644 results/classifier/gemma3:12b/socket/1668273 create mode 100644 results/classifier/gemma3:12b/socket/1701808 create mode 100644 results/classifier/gemma3:12b/socket/1711602 create mode 100644 results/classifier/gemma3:12b/socket/1713328 create mode 100644 results/classifier/gemma3:12b/socket/1754605 create mode 100644 results/classifier/gemma3:12b/socket/1777 create mode 100644 results/classifier/gemma3:12b/socket/1781280 create mode 100644 results/classifier/gemma3:12b/socket/1807052 create mode 100644 results/classifier/gemma3:12b/socket/1816819 create mode 100644 results/classifier/gemma3:12b/socket/1823790 create mode 100644 results/classifier/gemma3:12b/socket/1829779 create mode 100644 results/classifier/gemma3:12b/socket/1837 create mode 100644 results/classifier/gemma3:12b/socket/1840252 create mode 100644 results/classifier/gemma3:12b/socket/1843590 create mode 100644 results/classifier/gemma3:12b/socket/1862619 create mode 100644 results/classifier/gemma3:12b/socket/1867601 create mode 100644 results/classifier/gemma3:12b/socket/1881 create mode 100644 results/classifier/gemma3:12b/socket/1890395 create mode 100644 results/classifier/gemma3:12b/socket/1892684 create mode 100644 results/classifier/gemma3:12b/socket/1898084 create mode 100644 results/classifier/gemma3:12b/socket/2065579 create mode 100644 results/classifier/gemma3:12b/socket/2197 create mode 100644 results/classifier/gemma3:12b/socket/2230 create mode 100644 results/classifier/gemma3:12b/socket/2254 create mode 100644 results/classifier/gemma3:12b/socket/2292 create mode 100644 results/classifier/gemma3:12b/socket/2337 create mode 100644 results/classifier/gemma3:12b/socket/2346 create mode 100644 results/classifier/gemma3:12b/socket/2390 create mode 100644 results/classifier/gemma3:12b/socket/2410 create mode 100644 results/classifier/gemma3:12b/socket/2592 create mode 100644 results/classifier/gemma3:12b/socket/2720 create mode 100644 results/classifier/gemma3:12b/socket/284 create mode 100644 results/classifier/gemma3:12b/socket/2925 create mode 100644 results/classifier/gemma3:12b/socket/347 create mode 100644 results/classifier/gemma3:12b/socket/602 create mode 100644 results/classifier/gemma3:12b/socket/607 create mode 100644 results/classifier/gemma3:12b/socket/676029 create mode 100644 results/classifier/gemma3:12b/socket/717929 create mode 100644 results/classifier/gemma3:12b/socket/764 create mode 100644 results/classifier/gemma3:12b/socket/833 create mode 100644 results/classifier/gemma3:12b/socket/834 create mode 100644 results/classifier/gemma3:12b/socket/845 create mode 100644 results/classifier/gemma3:12b/socket/872 create mode 100644 results/classifier/gemma3:12b/socket/885 create mode 100644 results/classifier/gemma3:12b/socket/916720 create mode 100644 results/classifier/gemma3:12b/socket/988128 (limited to 'results/classifier/gemma3:12b/socket') diff --git a/results/classifier/gemma3:12b/socket/1020484 b/results/classifier/gemma3:12b/socket/1020484 new file mode 100644 index 000000000..4aa3fe341 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1020484 @@ -0,0 +1,4 @@ + +RFE: Support spice via unix domain socket + +According to the man page, spice can be only used via TCP/IP in opposite to VNC, which can also be configured to listen on a unix domain socket. To make it easy to use spice without exposing the interface, please support unix domain sockets as well. I can try to provide a patch, if you can point me to the source code where TCP/IP socket is opened. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1055 b/results/classifier/gemma3:12b/socket/1055 new file mode 100644 index 000000000..fe95dc428 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1055 @@ -0,0 +1,17 @@ + +QEMU does not close listening socket for incoming migration when post-copy migration breaks +Description of problem: +QEMU keeps listening on the incoming port even after breaking a post-copy +migration using "migrate-pause" QMP command. And even once migration is +finished after recovering it "migrate-recover" using a different port number. +If "migrate-recover" is called with a URI specifying the original port (which +is still in LISTEN state), QEMU reports "Failed to find an available port: +Address already in use". +Steps to reproduce: +1. start migration +2. wait for the first iteration to finish +3. switch to post-copy using "migrate-start-postcopy" +3. break migration with "migrate-pause" +4. check lsof -p $QEMU_PID +Additional information: + diff --git a/results/classifier/gemma3:12b/socket/1064631 b/results/classifier/gemma3:12b/socket/1064631 new file mode 100644 index 000000000..1c917b501 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1064631 @@ -0,0 +1,14 @@ + +Feature request: tls for chardev socket (telnet,tcp,udp) + +Hello, + +it would be nice if chardev socket (telnet,tcp,udp) could have tls support as vnc does. + +This way we could have encrypted access to virtual character devices over network, +for example in setup: conserver -> socat+tls <-> qemu+chardev+tls. + +The best would be both direction - server even client, so even the client should +trust remote server (trustfile, fingeprint...?). + +Thank you. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1075272 b/results/classifier/gemma3:12b/socket/1075272 new file mode 100644 index 000000000..bf9ee5bb1 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1075272 @@ -0,0 +1,14 @@ + +socket type mapping wrong for mips app-level emulation + +linux-user/syscall.c's do_socket function contains socket type remapping to work around the nonsensically-permuted MIPS socket types. However, it fails to account for the SOCK_NONBLOCK and SOCK_CLOEXEC flags that may be or'd onto the type. Thus, a call from the application such as: + +socket(AF_INET, SOCK_STREAM, IPPROTO_TCP) + +will fail to have the type permutation performed, and will be passed to the system as: + +socket(AF_INET, SOCK_DGRAM, IPPROTO_TCP) + +resulting in EPROTONOSUPPORT. + +To fix this, the flag bits should be masked off of the type before the permutation. They also need remapping themselves (since MIPS uses different values for these flags bits). \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1075339 b/results/classifier/gemma3:12b/socket/1075339 new file mode 100644 index 000000000..ad8e3a4d5 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1075339 @@ -0,0 +1,4 @@ + +linux-user emulation of setsockopt ignores optlen + +setsockopt always treats the argument as a 4-byte int. This breaks timeout options (for which it's an 8- or 16-byte timeval structure, depending on word size) and possibly other socket options. int is probably a safe default, but options whose values are other types need special-case conversion code. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1090726 b/results/classifier/gemma3:12b/socket/1090726 new file mode 100644 index 000000000..f5ece7ba1 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1090726 @@ -0,0 +1,49 @@ + +qemu does not generate guest cpu topology properly + +Adding the option + +-smp 12,sockets=2,cores=6,threads=1 + +exposes + + +Machine (12GB) + Socket #0 + L2 L#0 (512KB) + L1 L#0 (64KB) + Core L#0 + PU L#0 (P#0) + L2 L#1 (512KB) + L1 L#1 (64KB) + Core L#1 + PU L#1 (P#1) + L2 L#2 (512KB) + L1 L#2 (64KB) + Core L#2 + PU L#2 (P#2) + L2 L#3 (512KB) + L1 L#3 (64KB) + Core L#3 + PU L#3 (P#3) + L2 L#4 (512KB) + L1 L#4 (64KB) + Core L#4 + PU L#4 (P#4) + L2 L#5 (512KB) + L1 L#5 (64KB) + Core L#5 + PU L#5 (P#5) + L2 L#6 (512KB) + L1 L#6 (64KB) + Core L#6 + PU L#6 (P#6) + L2 L#7 (512KB) + L1 L#7 (64KB) + Core L#7 + PU L#7 (P#7) + Socket #1 + L2 L#8 (512KB) + L1 L#8 (64KB) + Core L#8 + PU L#8 (P#8) + L2 L#9 (512KB) + L1 L#9 (64KB) + Core L#9 + PU L#9 (P#9) + L2 L#10 (512KB) + L1 L#10 (64KB) + Core L#10 + PU L#10 (P#10) + L2 L#11 (512KB) + L1 L#11 (64KB) + Core L#11 + PU L#11 (P#11) + + +Rather than: + +Machine (12GB) + Socket #0 + L2 L#0 (512KB) + L1 L#0 (64KB) + Core L#0 + PU L#0 (P#0) + L2 L#1 (512KB) + L1 L#1 (64KB) + Core L#1 + PU L#1 (P#1) + L2 L#2 (512KB) + L1 L#2 (64KB) + Core L#2 + PU L#2 (P#2) + L2 L#3 (512KB) + L1 L#3 (64KB) + Core L#3 + PU L#3 (P#3) + L2 L#4 (512KB) + L1 L#4 (64KB) + Core L#4 + PU L#4 (P#4) + L2 L#5 (512KB) + L1 L#5 (64KB) + Core L#5 + PU L#5 (P#5) + Socket #1 + L2 L#6 (512KB) + L1 L#6 (64KB) + Core L#6 + PU L#6 (P#6) + L2 L#7 (512KB) + L1 L#7 (64KB) + Core L#7 + PU L#7 (P#7) + L2 L#8 (512KB) + L1 L#8 (64KB) + Core L#8 + PU L#8 (P#8) + L2 L#9 (512KB) + L1 L#9 (64KB) + Core L#9 + PU L#9 (P#9) + L2 L#10 (512KB) + L1 L#10 (64KB) + Core L#10 + PU L#10 (P#10) + L2 L#11 (512KB) + L1 L#11 (64KB) + Core L#11 + PU L#11 (P#11) + + +Here is a cpuid dump from inside the guest and dump from more recent version of cpuid, in which you can see a bit more detail. The later contains data for a single CPU, because the others are the same. + +Reproducible on qemu 1.0 and 1.2. with guest os Fedora 17, Debian 6, Debian Squeeze and Windows 2008 R2. \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1156632 b/results/classifier/gemma3:12b/socket/1156632 new file mode 100644 index 000000000..07b6c70aa --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1156632 @@ -0,0 +1,25 @@ + +not receiving RESET event after system_reset command causes QMP connection to die + +I have written my own implementation to control machine running KVM instances with the QMP protocol. Its a pretty basic implementation that sends/receives in the same thread. This means that all of the events QEMU sents are received only when the application expects a reply from a command. In the following scenario, i'm unable to (re)connect to the QMP socket from QEMU after I closed the connection: + +1) Connect to QMP +2) Sent qmp_capabilities +3) Receive reply +4) Send system_reset +5) Receive reply +6) close socket +7) Connect to socket -> connection refused + +However, in the following scenario, I am able to connect after I disconnect the socket because I have read the two RESET events: +1) Connect to QMP +2) Sent qmp_capabilities +3) Receive reply +4) Send system_reset +5) Receive reply +6) Receive reply (is a RESET event) +7) Receive reply (is a RESET event) +8) close socket +9) Connect to socket -> ok + +I don't know if this is a bug or expected behavior. I can't find any proper way to disconnect the socket documentated. Am I doïng something wrong, or is this a bug in the QMP implementation of QEMU? \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1264 b/results/classifier/gemma3:12b/socket/1264 new file mode 100644 index 000000000..b21c8e627 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1264 @@ -0,0 +1,2 @@ + +socket chardev loses data when remote end closes the connection diff --git a/results/classifier/gemma3:12b/socket/1316 b/results/classifier/gemma3:12b/socket/1316 new file mode 100644 index 000000000..9d43c587b --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1316 @@ -0,0 +1,2 @@ + +qemu.qmp.protocol.ConnectError: Failed to establish connection: AF_UNIX path too long (on Darwin) diff --git a/results/classifier/gemma3:12b/socket/1327608 b/results/classifier/gemma3:12b/socket/1327608 new file mode 100644 index 000000000..c87114229 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1327608 @@ -0,0 +1,24 @@ + +monitor socked path is cut a 105 characters + +Starting a VM like so: + +/usr/bin/qemu-system-x86_64 -machine accel=kvm -monitor unix:/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/gentoo-summerschool.img.monitor,server,nowait -name gentoo-summerschool -chardev socket,id=monitor,path=/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/monitor.sock,server,nowait -monitor chardev:monitor -chardev socket,id=serial0,path=/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/console.sock,server,nowait -serial chardev:serial0 -enable-kvm -cpu kvm64 -smp 2 -netdev tap,id=net0,script=/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/qemu-ifup.bash -device e1000,netdev=net0,mac=00:00:00:00:00:02 -drive id=disk,file=/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/gentoo-summerschool.img,if=none -device ahci,id=ahci -device ide-drive,drive=disk,bus=ahci.0 -m 2048 -vga qxl -spice port=2002,addr=192.168.4.2,password=NO-thats-not-my-pwd -device virtio-serial-pci -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent + + +The path: + +unix:/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/gentoo-summerschool.img.monitor + +...is cut like so when I try to shutdown: + +pink ~ # echo system_powerdown | socat - UNIX-CONNECT:/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschool/gentoo-summerschool.img.monitor +2014/06/08 06:39:01 socat[2344] E connect(3, AF=1 "/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/lv-gentoosummerschool/gentoo-summerschoo", 110): No such file or directory +pink ~ # + + +It does work with a sorter path like: +pink ~ # echo system_powerdown | socat - UNIX-CONNECT:'/srv/localfs/Samsung_SSD_840_PRO_Series_S1AXNSAF320206J/vg-virt/my.img.monitor' +QEMU 1.5.3 monitor - type 'help' for more information +(qemu) system_powerdown +(qemu) pink ~ # \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1353149 b/results/classifier/gemma3:12b/socket/1353149 new file mode 100644 index 000000000..92a1c4c8a --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1353149 @@ -0,0 +1,20 @@ + +qemu 2.1.0 fails to start if number of cores is greater than 1. + +qemu (kvm) 2.1.0 (built from sources) fails to start if number of cores is greater than 1. + +relevant part of commandline arguments: + +/usr/bin/qemu-system-x86_64 -name test3 -S -machine pc-i440fx-2.1,accel=kvm,usb=off -cpu Westmere -m 4096 -realtime mlock=off -smp 1,maxcpus=4,sockets=1,cores=4,threads=1 + +the error reported is: + +qemu-system-x86_64: /home/asavah/pkgbuild/qemu-2.1.0/hw/i386/smbios.c:825: smbios_get_tables: Assertion `smbios_smp_sockets >= 1' failed. +2014-08-05 21:45:35.825+0000: shutting down + +however setting 4 sockets with 1 core each allows me to start the machine just fine. + +the system is debian wheezy +Linux hostname 3.16.0-hostname2 #2 SMP Mon Aug 4 17:02:16 EEST 2014 x86_64 GNU/Linux + +libvirt 1.2.7 (built from sources) \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1381879 b/results/classifier/gemma3:12b/socket/1381879 new file mode 100644 index 000000000..56fc25aaf --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1381879 @@ -0,0 +1,34 @@ + +can not run vm with a serial port + +environment: +server: centOS 6.5, 3.14.19, x86_64 +qemu-kvm: QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2), Copyright (c) 2003-2008 Fabrice Bellard +qemu-system-x86_64 :QEMU emulator version 1.2.0 (qemu-kvm-1.2.0), Copyright (c) 2003-2008 Fabrice Bellard +virt-manager: 0.9.0 + +VM: centOS 6.5, 3.12.30, x86_64 + +reproduce step: +1. add serial device +2. select device type: unix socket + device parameters: path=/dev/ttyS0 + mode=client mode(connect) +3. run the VM + +phenomenon: +Error starting domain: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use +qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed + + +Traceback (most recent call last): + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper + callback(asyncjob, *args, **kwargs) + File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb + callback(*args, **kwargs) + File "/usr/share/virt-manager/virtManager/domain.py", line 1114, in startup + self._backend.create() + File "/usr/lib64/python2.6/site-packages/libvirt.py", line 678, in create + if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) +libvirtError: internal error process exited while connecting to monitor: qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: socket bind failed: Address already in use +qemu-kvm: -chardev socket,id=charserial0,path=/dev/ttyS0,server,nowait: chardev: opening backend "socket" failed \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1426 b/results/classifier/gemma3:12b/socket/1426 new file mode 100644 index 000000000..51c2b1c75 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1426 @@ -0,0 +1,39 @@ + +On windows, display spice-app is not able to initialize, start spice-server and consequently can't use spice-client +Description of problem: +I want to try windows spice-client / virt-viewer.exe (v11.0.256) instead of gtk client. +Windows spice client virtviewer won't start like it does under Linux. +The error message indicaes that the spice-server itself failed to open spice sockets +The registry to handle ```spice://``` URI handler is configured. +Steps to reproduce: +1. just run command +Additional information: +URI handler in registry is configure using a regestry import file ```spiceproto.reg``` +``` +Windows Registry Editor Version 5.00 + +[HKEY_CLASSES_ROOT\spice] +"URL Protocol"="" + +[HKEY_CLASSES_ROOT\spice\DefaultIcon] +@="C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe,1" + +[HKEY_CLASSES_ROOT\spice\Extensions] +[HKEY_CLASSES_ROOT\spice\shell] +[HKEY_CLASSES_ROOT\spice\shell\open] +[HKEY_CLASSES_ROOT\spice\shell\open\command] +@="\"C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe\" \"%1\"" + +[HKEY_CLASSES_ROOT\spice+unix] +"URL Protocol"="" + +[HKEY_CLASSES_ROOT\spice+unix\DefaultIcon] +@="C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe,1" + +[HKEY_CLASSES_ROOT\spice+unix\Extensions] +[HKEY_CLASSES_ROOT\spice+unix\shell] +[HKEY_CLASSES_ROOT\spice+unix\shell\open] +[HKEY_CLASSES_ROOT\spice+unix\shell\open\command] +@="\"C:\\Program Files\\VirtViewer v11.0-256\\bin\\remote-viewer.exe\" \"%1\"" +``` +This URI handler is working, and can be seen to work by typing ```spice://abcdefg``` in firefox. diff --git a/results/classifier/gemma3:12b/socket/1471 b/results/classifier/gemma3:12b/socket/1471 new file mode 100644 index 000000000..9d99e1307 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1471 @@ -0,0 +1,17 @@ + +16fc5726a6 breaks curl SSL connections +Description of problem: +`./qemu-x86_64 /path/to/curl-amd64 https://news.bbc.co.uk` should work, just as `./qemu-aarch64 /path/to/curl-aarch64 https://news.bbc.co.uk` does. However, commit 16fc5726a6e296b3f63acec537c299c1dc49d6c4 broke this (determined via `git bisect`). +Steps to reproduce: +1. Checkout and build `qemu` commit 16fc5726a6e296b3f63acec537c299c1dc49d6c4 +2. On an aarch64 host system, download the amd64 build of `curl` from https://github.com/moparisthebest/static-curl/releases/tag/v7.87.0 +3. Run `./qemu-x86_64 /path/to/curl-amd64 https://news.bbc.co.uk` +4. Observe the following error message: + +``` +curl: (35) error:1416D07B:SSL routines:tls_process_key_exchange:bad signature +``` + +Note that the `aarch64` equivalent works just fine. As does the previous commit using `amd64`. + +Also note, this bug is also present at current tip (13356edb87506c148b163b8c7eb0695647d00c2a). diff --git a/results/classifier/gemma3:12b/socket/1472083 b/results/classifier/gemma3:12b/socket/1472083 new file mode 100644 index 000000000..ccabf8f61 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1472083 @@ -0,0 +1,28 @@ + +Qemu 2.1.2 hang when stop command + +Qemu 2.1.2, Linux kernel 3.13.6, this is the stack. + +#0 in ppoll () from /lib/x86_64-linux-gnu/libc.so.6 +#1 in qemu_poll_ns (fds=0x7fa82a8de380, nfds=1, timeout=-1) at qemu-timer.c:314 +#2 in aio_poll (ctx=0x7fa82a8b5000, blocking=true) at aio-posix.c:250 +#3 in bdrv_drain_all () at block.c:1924 +#4 in do_vm_stop (state=RUN_STATE_PAUSED) at /qemu-2.1.2/cpus.c:544 +#5 in vm_stop (state=RUN_STATE_PAUSED) at /qemu-2.1.2/cpus.c:1227 +#6 in qmp_stop (errp=0x7ffffb6dcaf8) at qmp.c:98 +#7 in qmp_marshal_input_stop (mon=0x7fa82a8e0970, qdict=0x7fa830295020, ret=0x7ffffb6dcb48) at qmp-marshal.c:2806 +#8 in qmp_call_cmd (mon=0x7fa82a8e0970, cmd=0x7fa8290558a0, params=0x7fa830295020) at /qemu-2.1.2/monitor.c:5038 +#9 in handle_qmp_command (parser=0x7fa82a8e0a28, tokens=0x7fa82a8d9b50) at /qemu-2.1.2/monitor.c:5104 +#10 in json_message_process_token (lexer=0x7fa82a8e0a30, token=0x7fa830122b60, type=JSON_OPERATOR, x=39, y=17865) at qobject/json-streamer.c:87 +#11 in json_lexer_feed_char (lexer=0x7fa82a8e0a30, ch=125 '}', flush=false) at qobject/json-lexer.c:303 +#12 in json_lexer_feed (lexer=0x7fa82a8e0a30, buffer=0x7ffffb6dcdb0 "}\315m\373\377\177", size=1) at qobject/json-lexer.c:356 +#13 in json_message_parser_feed (parser=0x7fa82a8e0a28, buffer=0x7ffffb6dcdb0 "}\315m\373\377\177", size=1) at qobject/json-streamer.c:111 +#14 in monitor_control_read (opaque=0x7fa82a8e0970, buf=0x7ffffb6dcdb0 "}\315m\373\377\177", size=1) at /qemu-2.1.2/monitor.c:5125 +#15 in qemu_chr_be_write (s=0x7fa82a8c2020, buf=0x7ffffb6dcdb0 "}\315m\373\377\177", len=1) at qemu-char.c:213 +#16 in tcp_chr_read (chan=0x7fa82a8c4ba0, cond=G_IO_IN, opaque=0x7fa82a8c2020) at qemu-char.c:2729 +#17 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 +#18 in glib_pollfds_poll () at main-loop.c:190 +#19 in os_host_main_loop_wait (timeout=24000000) at main-loop.c:235 +#20 in main_loop_wait (nonblocking=0) at main-loop.c:484 +#21 in main_loop () at vl.c:2034 +#22 in main (argc=55, argv=0x7ffffb6de338, envp=0x7ffffb6de4f8) at vl.c:4583 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1478360 b/results/classifier/gemma3:12b/socket/1478360 new file mode 100644 index 000000000..7d21d45ba --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1478360 @@ -0,0 +1,133 @@ + +Cant compile on ubuntu 14.04 x64 + +./configure --static +Install prefix /usr/local +BIOS directory /usr/local/share/qemu +binary directory /usr/local/bin +library directory /usr/local/lib +module directory /usr/local/lib/qemu +libexec directory /usr/local/libexec +include directory /usr/local/include +config directory /usr/local/etc +local state directory /usr/local/var +Manual directory /usr/local/share/man +ELF interp prefix /usr/gnemul/qemu-%M +Source path /home/slobodan/qemu +C compiler cc +Host C compiler cc +C++ compiler c++ +Objective-C compiler cc +ARFLAGS rv +CFLAGS -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -pthread -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -g +QEMU_CFLAGS -I/usr/include/pixman-1 -Werror -m64 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers -Wold-style-declaration -Wold-style-definition -Wtype-limits -fstack-protector-all -I/usr/include/p11-kit-1 -I/usr/include/libpng12 +LDFLAGS -Wl,--warn-common -m64 -static -g +make make +install install +python python -B +smbd /usr/sbin/smbd +module support no +host CPU x86_64 +host big endian no +target list aarch64-softmmu alpha-softmmu arm-softmmu cris-softmmu i386-softmmu lm32-softmmu m68k-softmmu microblaze-softmmu microblazeel-softmmu mips-softmmu mips64-softmmu mips64el-softmmu mipsel-softmmu moxie-softmmu or32-softmmu ppc-softmmu ppc64-softmmu ppcemb-softmmu s390x-softmmu sh4-softmmu sh4eb-softmmu sparc-softmmu sparc64-softmmu tricore-softmmu unicore32-softmmu x86_64-softmmu xtensa-softmmu xtensaeb-softmmu aarch64-linux-user alpha-linux-user arm-linux-user armeb-linux-user cris-linux-user i386-linux-user m68k-linux-user microblaze-linux-user microblazeel-linux-user mips-linux-user mips64-linux-user mips64el-linux-user mipsel-linux-user mipsn32-linux-user mipsn32el-linux-user or32-linux-user ppc-linux-user ppc64-linux-user ppc64abi32-linux-user ppc64le-linux-user s390x-linux-user sh4-linux-user sh4eb-linux-user sparc-linux-user sparc32plus-linux-user sparc64-linux-user unicore32-linux-user x86_64-linux-user +tcg debug enabled no +gprof enabled no +sparse enabled no +strip binaries yes +profiler no +static build yes +pixman system +SDL support no +GTK support yes +GNUTLS support yes +GNUTLS hash yes +GNUTLS gcrypt yes +GNUTLS nettle no () +VTE support no +curses support no +curl support no +mingw32 support no +Audio drivers oss +Block whitelist (rw) +Block whitelist (ro) +VirtFS support no +VNC support yes +VNC TLS support no +VNC SASL support no +VNC JPEG support yes +VNC PNG support yes +xen support no +brlapi support no +bluez support yes +Documentation no +GUEST_BASE yes +PIE no +vde support no +netmap support no +Linux AIO support no +ATTR/XATTR support yes +Install blobs yes +KVM support yes +RDMA support no +TCG interpreter no +fdt support yes +preadv support yes +fdatasync yes +madvise yes +posix_madvise yes +sigev_thread_id yes +uuid support yes +libcap-ng support no +vhost-net support yes +vhost-scsi support yes +Trace backends nop +spice support no +rbd support no +xfsctl support no +nss used no +libusb no +usb net redir no +OpenGL support no +libiscsi support no +libnfs support no +build guest agent yes +QGA VSS support no +QGA w32 disk info no +seccomp support no +coroutine backend ucontext +coroutine pool yes +GlusterFS support no +Archipelago support no +gcov gcov +gcov enabled no +TPM support yes +libssh2 support no +TPM passthrough yes +QOM debugging yes +vhdx yes +lzo support no +snappy support no +bzip2 support no +NUMA host support no +tcmalloc support no + +:~/qemu$ make + GEN config-host.h + GEN qemu-options.def + GEN qmp-commands.h + GEN qapi-types.h + GEN qapi-visit.h + GEN qapi-event.h + GEN trace/generated-events.h + GEN trace/generated-tracers.h + GEN trace/generated-tcg-tracers.h + GEN trace/generated-helpers-wrappers.h + GEN trace/generated-helpers.h + GEN tests/test-qapi-types.h + GEN tests/test-qapi-visit.h + GEN tests/test-qmp-commands.h + GEN tests/test-qapi-event.h + CC tests/qemu-iotests/socket_scm_helper.o + LINK tests/qemu-iotests/socket_scm_helper +c++: error: unrecognized command line option ‘-R’ +make: *** [tests/qemu-iotests/socket_scm_helper] Error 1 \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1495 b/results/classifier/gemma3:12b/socket/1495 new file mode 100644 index 000000000..2454b0d82 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1495 @@ -0,0 +1,7 @@ + +MacOS fails check-unit for test-io-channel-command for some reason +Description of problem: +While adding the socat dependency to the CI system it triggers a failure on the ARM MacOS build, eg: https://gitlab.com/stsquad/qemu/-/jobs/3769189709 +Steps to reproduce: +1. install socat +2. make check-unit diff --git a/results/classifier/gemma3:12b/socket/1504513 b/results/classifier/gemma3:12b/socket/1504513 new file mode 100644 index 000000000..cb0ec2072 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1504513 @@ -0,0 +1,26 @@ + +Socket leak on each call to qemu_socket() + +On any host platform where SOCK_CLOEXEC is defined (Linux at least), a socket is leaked on each call to qemu_socket() AND the socket returned hasn't been created with the desired SOCK_CLOEXEC attribute. The qemu_socket routine is: + +Line 272 of util/osdep.c: +/* + * Opens a socket with FD_CLOEXEC set + */ +int qemu_socket(int domain, int type, int protocol) +{ + int ret; + +#ifdef SOCK_CLOEXEC + ret = socket(domain, type | SOCK_CLOEXEC, protocol); + if (ret != -1 || errno != EINVAL) { + return ret; + } +#endif + ret = socket(domain, type, protocol); + if (ret >= 0) { + qemu_set_cloexec(ret); + } + + return ret; +} \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1542965 b/results/classifier/gemma3:12b/socket/1542965 new file mode 100644 index 000000000..9367f38a3 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1542965 @@ -0,0 +1,6 @@ + +Failed to set NBD socket ubuntu 15.10 & nbd client 3.10 + +Running command to mount using nbd fails +with error +/build/qemu-YZq7uh/qemu-2.3+dfsg/nbd.c:nbd_init():L670: Failed to set NBD socket \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1549 b/results/classifier/gemma3:12b/socket/1549 new file mode 100644 index 000000000..b85147d3f --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1549 @@ -0,0 +1,96 @@ + +8.0.0rc0 Regression: spicy windows doesn't open +Description of problem: +Soon after start the qemu process outputs +``` +qemu-system-x86_64.exe: fd=900 is not a socket, AIO implementation is missing +qemu-system-x86_64.exe: fd=800 is not a socket, AIO implementation is missing +``` +On connecting with `spicy -h localhost -p 5905 --spice-debug` spicy stops progress after writing this line +``` +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.406: ../spice-gtk-0.42/src/spice-channel.c:1415 main-1:0: channel type 1 id 0 num common caps 1 num caps 1 +``` +Steps to reproduce: +1. Start qemu with `qemu-system-x86_64 -m 1536 -vga qxl -spice port=5905,addr=127.0.0.1,disable-ticketing=on -cdrom openSUSE-Leap-15.3-GNOME-Live-x86_64-Media.iso` in first MSYS2 MinGW64 terminal +2. Start spice with `spicy -h localhost -p 5905 --spice-debug` in second MSYS2 MinGW64 terminal +Additional information: +Final output of `git bisect` +``` +abe34282b088499f4e86fff9bb6d6dafd57ae1d0 is the first bad commit +commit abe34282b088499f4e86fff9bb6d6dafd57ae1d0 +Author: Marc-André Lureau +Date: Tue Feb 21 16:47:59 2023 +0400 + + win32: avoid mixing SOCKET and file descriptor space + + Until now, a win32 SOCKET handle is often cast to an int file + descriptor, as this is what other OS use for sockets. When necessary, + QEMU eventually queries whether it's a socket with the help of + fd_is_socket(). However, there is no guarantee of conflict between the + fd and SOCKET space. Such conflict would have surprising consequences, + we shouldn't mix them. + + Also, it is often forgotten that SOCKET must be closed with + closesocket(), and not close(). + + Instead, let's make the win32 socket wrapper functions return and take a + file descriptor, and let util/ wrappers do the fd/SOCKET conversion as + necessary. A bit of adaptation is necessary in io/ as well. + + Unfortunately, we can't drop closesocket() usage, despite + _open_osfhandle() documentation claiming transfer of ownership, testing + shows bad behaviour if you forget to call closesocket(). + + Signed-off-by: Marc-André Lureau + Reviewed-by: Stefan Berger + Message-Id: <20230221124802.4103554-15-marcandre.lureau@redhat.com> + + include/sysemu/os-win32.h | 4 +- + io/channel-watch.c | 6 +- + util/aio-win32.c | 9 +- + util/oslib-win32.c | 219 +++++++++++++++++++++++++++++++++++++++------- + 4 files changed, 197 insertions(+), 41 deletions(-) +``` +Complete spicy output +``` +$ spicy -h localhost -p 5905 --spice-debug +(spicy.exe:5584): GSpice-DEBUG: 18:43:52.890: ../spice-gtk-0.42/src/spice-session.c:288 New session (compiled from package spice-gtk 0.42) +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.872: ../spice-gtk-0.42/src/spice-session.c:292 Supported channels: main, display, inputs, cursor, playback, record, smartcard, usbredir, webdav +(spicy.exe:5584): GSpice-WARNING **: 18:43:53.877: SpiceSession:gl-scanout is only available on Unix +(spicy.exe:5584): GSpice-WARNING **: 18:43:53.881: UsbDk driver is not installed +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.908: ../spice-gtk-0.42/src/usb-device-manager.c:393 auto-connect filter set to 0x03,-1,-1,-1,0|-1,-1,-1,-1,1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.913: ../spice-gtk-0.42/src/usb-backend.c:440 spice_usb_backend_new >> +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.918: ../spice-gtk-0.42/src/usb-backend.c:462 spice_usb_backend_new << +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.995: ../spice-gtk-0.42/src/usb-backend.c:207 adding 04F2:B43C at 1:1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:53.998: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C26 at 3:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.000: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C2D at 1:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.003: ../spice-gtk-0.42/src/usb-backend.c:207 adding 0BDA:B728 at 1:4 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.006: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e280, usblib dev 00000148d27a2590 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.010: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8086:8C31 at 2:0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.014: ../spice-gtk-0.42/src/usb-backend.c:207 adding 05E3:0608 at 3:5 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.017: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8087:8008 at 1:5 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.020: ../spice-gtk-0.42/src/usb-backend.c:207 adding 0BDA:0129 at 1:3 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.023: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e140, usblib dev 00000148d27a2b30 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.027: ../spice-gtk-0.42/src/usb-backend.c:207 adding 8087:8000 at 3:4 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.030: ../spice-gtk-0.42/src/usb-backend.c:207 adding 045E:00DB at 3:1 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.033: ../spice-gtk-0.42/src/usb-backend.c:207 adding 17EF:6019 at 3:2 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.035: ../spice-gtk-0.42/src/usb-backend.c:158 created dev 00000148d2a9e190, usblib dev 00000148d27a5460 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.074: ../spice-gtk-0.42/tools/spicy.c:1881 connection_new (1) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.074: ../spice-gtk-0.42/src/usb-backend.c:469 handle_libusb_events >> +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.081: ../spice-gtk-0.42/src/spice-session.c:1835 no migration in progress +Spice-INFO: 18:43:54.086: ../spice-gtk-0.42/src/channel-main.c:342:spice_main_set_property: SpiceMainChannel::color-depth has been deprecated. Property is ignored +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.090: ../spice-gtk-0.42/src/spice-channel.c:142 main-1:0: spice_channel_constructed +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.093: ../spice-gtk-0.42/src/spice-session.c:2330 main-1:0: new main channel, switching +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.097: ../spice-gtk-0.42/tools/spicy.c:1758 new channel (#0) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.099: ../spice-gtk-0.42/tools/spicy.c:1761 new main channel +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.102: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 0bda:b728 (00000148d2a9e280) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.105: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 0bda:0129 (00000148d2a9e140) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.108: ../spice-gtk-0.42/src/usb-device-manager.c:800 device added 17ef:6019 (00000148d2a9e190) +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.113: ../spice-gtk-0.42/src/spice-channel.c:2763 main-1:0: Open coroutine starting 00000148d2a403f0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.116: ../spice-gtk-0.42/src/spice-channel.c:2587 main-1:0: Started background coroutine 00000148d2a402b0 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.120: ../spice-gtk-0.42/src/spice-session.c:2267 main-1:0: Using plain text, port 5905 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.124: ../spice-gtk-0.42/src/spice-session.c:2198 open host localhost:5905 +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.136: ../spice-gtk-0.42/src/spice-session.c:2120 main-1:0: connecting 000000010f1ffc90... +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.402: ../spice-gtk-0.42/src/spice-session.c:2104 main-1:0: connect ready +(spicy.exe:5584): GSpice-DEBUG: 18:43:54.406: ../spice-gtk-0.42/src/spice-channel.c:1415 main-1:0: channel type 1 id 0 num common caps 1 num caps 1 +``` diff --git a/results/classifier/gemma3:12b/socket/1553 b/results/classifier/gemma3:12b/socket/1553 new file mode 100644 index 000000000..5a4b82dd4 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1553 @@ -0,0 +1,13 @@ + +Build error: implicit declaration of function 'qemu_close_to_socket' +Description of problem: +When build the latest master code with MSYS2 on Windows 10, GCC reports: +../ui/spice-core.c: In function 'watch_remove': +../ui/spice-core.c:152:5: error: implicit declaration of function 'qemu_close_to_socket' [-Werror=implicit-function-declaration] + 152 | qemu_close_to_socket(watch->fd); + | ^~~~~~~~~~~~~~~~~~~~ +../ui/spice-core.c:152:5: error: nested extern declaration of 'qemu_close_to_socket' [-Werror=nested-externs] +Steps to reproduce: +1. ./configure --enable-sdl --enable-gtk --target-list=arm-softmmu,aarch64-softmmu +2. cd build +3. make diff --git a/results/classifier/gemma3:12b/socket/1581695 b/results/classifier/gemma3:12b/socket/1581695 new file mode 100644 index 000000000..e2569a290 --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1581695 @@ -0,0 +1,19 @@ + +getifaddrs: Address family not supported by protocol + +Calling ip addr fails with the following error message: +Cannot open netlink socket: Address family not supported by protocol + + +My use case is running a docker raspberry pi arm container on Ubuntu 14.04 x64 with qemu-static. + +My steps to reproduce are the following: + +# docker pull philipz/rpi-raspbian:latest +# docker run -it --rm -v /usr/bin/qemu-arm-static:/usr/bin/qemu-arm-static philipz/rpi-raspbian bash +root@3b4ddc174279:/# ip addr +Cannot open netlink socket: Address family not supported by protocol + +A fix or an workaround would be awesome. + +note: we are also working with a embedded arm distro which has no package manager available, would be nice if the workaround would not depend on apt-get \ No newline at end of file diff --git a/results/classifier/gemma3:12b/socket/1586756 b/results/classifier/gemma3:12b/socket/1586756 new file mode 100644 index 000000000..ebd2e853b --- /dev/null +++ b/results/classifier/gemma3:12b/socket/1586756 @@ -0,0 +1,53 @@ + +"-serial unix:" option of qemu-system-arm is broken in qemu 2.6.0 + +I found a bug of "-serial unix:PATH_TO_SOCKET" in qemu 2.6.0 (qemu 2.5.1 works fine). +Occasionally, a part of the output of qemu disappears in the bug. + +It looks like following commit is the cause: + +char: ensure all clients are in non-blocking mode (Author: Daniel P. Berrange