diff options
Diffstat (limited to 'results/classifier/deepseek-2-tmp/output/socket')
31 files changed, 735 insertions, 0 deletions
diff --git a/results/classifier/deepseek-2-tmp/output/socket/1020484 b/results/classifier/deepseek-2-tmp/output/socket/1020484 new file mode 100644 index 000000000..4aa3fe341 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1031920 b/results/classifier/deepseek-2-tmp/output/socket/1031920 new file mode 100644 index 000000000..315d58477 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1031920 @@ -0,0 +1,38 @@ + +Linux user gdbserver does not respond to remote `Ctrl-C' interrupts + +The bug was reproduce in a recent mainline build for ARM Linux by starting emulation with a gdbserver: + +$ qemu-arm -g 1234 a.out + +and then connecting from gdb: + +(gdb) target remote :1234 +Remote debugging using :1234 +[New Remote target] +[Switching to Remote target] +0x00008ba8 in _start () +(gdb) b main +Breakpoint 1 at 0x8cb0: file hello.c, line 5. +(gdb) cont +Continuing. + +Breakpoint 1, main (argc=1, argv=0xf6fff24c) at hello.c:5 +5 int n = 0; +(gdb) l +1 #include <stdio.h> +2 +3 int main (int argc, char **argv) +4 { +5 int n = 0; +6 +7 for (;;) { +8 printf ("Hello, World!\n"); +9 sleep (5); +10 } +(gdb) cont +Continuing. +^C^CInterrupted while waiting for the program. +Give up (and stop debugging it)? (y or n) y + +Notice that the `Ctrl-C' interrupts are ignored. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1055 b/results/classifier/deepseek-2-tmp/output/socket/1055 new file mode 100644 index 000000000..fe95dc428 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1064631 b/results/classifier/deepseek-2-tmp/output/socket/1064631 new file mode 100644 index 000000000..1c917b501 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1075339 b/results/classifier/deepseek-2-tmp/output/socket/1075339 new file mode 100644 index 000000000..ad8e3a4d5 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1090726 b/results/classifier/deepseek-2-tmp/output/socket/1090726 new file mode 100644 index 000000000..f5ece7ba1 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1156632 b/results/classifier/deepseek-2-tmp/output/socket/1156632 new file mode 100644 index 000000000..07b6c70aa --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1264 b/results/classifier/deepseek-2-tmp/output/socket/1264 new file mode 100644 index 000000000..b21c8e627 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1264 @@ -0,0 +1,2 @@ + +socket chardev loses data when remote end closes the connection diff --git a/results/classifier/deepseek-2-tmp/output/socket/1316 b/results/classifier/deepseek-2-tmp/output/socket/1316 new file mode 100644 index 000000000..9d43c587b --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1327608 b/results/classifier/deepseek-2-tmp/output/socket/1327608 new file mode 100644 index 000000000..c87114229 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1504513 b/results/classifier/deepseek-2-tmp/output/socket/1504513 new file mode 100644 index 000000000..cb0ec2072 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/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/deepseek-2-tmp/output/socket/1555452 b/results/classifier/deepseek-2-tmp/output/socket/1555452 new file mode 100644 index 000000000..f51604085 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1555452 @@ -0,0 +1,10 @@ + +GDB server does not work in Windows + +I build qemu with msys2, MINGW64. After fix the socket_error() problem, and manually specify to use IPv4, GDB server still does not work. The related qemu command is +"-monitor none -nographic -gdb tcp::1234 -S" +GDB reports "Timed out" + +There's a message at https://<email address hidden>/msg357981.html. +I've fixed the socket_error() problem. +I see that qio_channel_create_socket_watch is called. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1605443 b/results/classifier/deepseek-2-tmp/output/socket/1605443 new file mode 100644 index 000000000..cd41f2349 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1605443 @@ -0,0 +1,12 @@ + +QEMU epoll for i386-linux-user on arm host is broken in 2.6 + +I'm trying to get wine running on qemu-i386 on arm. + +I found that 2.5.1 is OK, but 2.6 is not. + +By bisecting, I found commit 928bed6a057cedd6110e634865e021a24029785a is the problem. + +I reverted this commit, and then epoll is OK now. + +It seems that the commit broke epoll of qemu-i386 on arm. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1663079 b/results/classifier/deepseek-2-tmp/output/socket/1663079 new file mode 100644 index 000000000..84a5fc291 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1663079 @@ -0,0 +1,23 @@ + +socket network not working + +The socket network type is no longer working in 2.8.0. + +When trying to establish a network between 2 qemu instances: + +The listening host: +qemu-system-x86_64 -netdev socket,id=in0,listen=127.0.0.1:9999 -device virtio-net-pci,netdev=in0 + +works fine, but for the second one: + +qemu-system-x86_64 -netdev socket,id=in0,connect=127.0.0.1:9999 -device virtio-net-pci,netdev=in0 + +It fails with: + +qemu-system-x86_64: -device virtio-net-pci,netdev=in0: Property 'virtio-net-device.netdev' can't find value 'in0' + +netstat shows a new connection to port 9999 in time_wait state every time. + +host: kernel 4.4.38, 64bits. + +It was working fine with previous version. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1686390 b/results/classifier/deepseek-2-tmp/output/socket/1686390 new file mode 100644 index 000000000..251d360fd --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1686390 @@ -0,0 +1,19 @@ + +vnc server closed socket after arrow "down" keyevent + +This is a rewrite for https://bugs.launchpad.net/qemu/+bug/1670377 + +QEMU 2.6 or later +tigervncviwer 1.6 + +Once get into grub boot interface(choose boot os, or recovery mode), keep pressing arrow down button for couple times, qemu will close the connection, vnc used zrle mode. + +Interesting place: +1. when stopped at grub interface, only arrow up and down key could trigger it, +2. only in zrle or tight mode, could work well in raw mode +2. it only triggered by remote connection, not happen if local vncviewer and vnc server + + +A trace is attached. + +Thanks \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1701808 b/results/classifier/deepseek-2-tmp/output/socket/1701808 new file mode 100644 index 000000000..318fa8b2e --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1701808 @@ -0,0 +1,17 @@ + +stack smashing in or after recvmsg system call in aarch64 user mode + +A program that invokes recvmsg aborts with "*** stack smashing detected ***" when run in qemu-aarch64 (user mode), but works fine when running on native aarch64 hardware. + +How to reproduce: +$ aarch64-linux-gnu-gcc-5 -O -Wall /media/develdata/devel/qemu-bug/testpassfd.c -static -DEXTRA_SPACE=0 +$ QEMU_LD_PREFIX=/usr/aarch64-linux-gnu ~/inst-qemu/2.9.0/bin/qemu-aarch64 ./a.out +*** stack smashing detected ***: ./a.out terminated +qemu: uncaught target signal 6 (Aborted) - core dumped + +On native aarch64 hardware: +$ ./a.out +$ echo $? +0 + +The parameter EXTRA_SPACE can be used to add additional space to the array that receives the recvmsg data. With -DEXTRA_SPACE=9 (or larger), the program runs fine. Which suggests that recvmsg is storing up to 9 bytes more than allowed in memory. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1781280 b/results/classifier/deepseek-2-tmp/output/socket/1781280 new file mode 100644 index 000000000..466ec5ee5 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1781280 @@ -0,0 +1,10 @@ + +QEMU ignores all but the first control message sent over a Unix socket + +I've written a test program that sends both an SCM_CREDENTIALS and an SCM_RIGHTS cmsg in the same sendmsg call. On native x86-64, armv6 and armv7 Linux, this works as expected (the recvmsg receives both control messages). On QEMU (both qemu-x86_64 and qemu-arm), only the first message is received. + +I've traced the problem back to a glibc bug: https://sourceware.org/bugzilla/show_bug.cgi?id=13500 + +This means that writing control messages into an uninitialized buffer makes CMSG_NXTHDR erroneously return NULL even though there's still space inside the allocated buffer. QEMU's logic inside `target_to_host_cmsg` is a bit questionable here, since it stops encoding cmsgs as soon as *either* the host or the target buffer reaches its end, so we lose the target's cmsgs when the host's buffer runs out. However, the host buffer should *never* reach its end before the target buffer does, so an assertion might be more useful there. Anyway, the actual fix for this bug is simply zeroing out the buffer created for the host. I've attached a patch doing that and verified that it fixes the issue. + +The test program I used can be found here: https://gist.github.com/jonas-schievink/cb6e6584a055539d2113f22d91068e2d \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1796754 b/results/classifier/deepseek-2-tmp/output/socket/1796754 new file mode 100644 index 000000000..d8f302240 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1796754 @@ -0,0 +1,18 @@ + +ioctl SIOCGIFCONF causes qemu-aarch64-static to crash with "received signal outside vCPU context" + +To reproduce it, compile the attached crash.c under aarch64 to a.out and execute on x86_64 +qemu-aarch64-static ./a.out + +It will print the following and crash: + +socket=3 +qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x60038cd6 +qemu:handle_cpu_signal received signal outside vCPU context @ pc=0x6000157a + +The version of qemu-aarch64-static is + +qemu-aarch64 version 3.0.0 (qemu-3.0.0-1.fc29) +Copyright (c) 2003-2017 Fabrice Bellard and the QEMU Project developers + +But it did also happen in previous versions so it is not a regression but a bug existed ever since. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1828608 b/results/classifier/deepseek-2-tmp/output/socket/1828608 new file mode 100644 index 000000000..7ab30bd4b --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1828608 @@ -0,0 +1,8 @@ + +Chardev websocket might not support pasting more than a few chars + +When sending more than 4-5 characters on the websocket serial console (with pasting for example), the guest might not receive all of them, or worse interpret the input as Magic SysRq keys. + +This might be due to the io loop not checking the backend readiness before calling the read function. + +Attached patched fixes the problem on my system. I'm not sure it's the proper approach, this is just to start discussion. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1829779 b/results/classifier/deepseek-2-tmp/output/socket/1829779 new file mode 100644 index 000000000..2eb9024f0 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1829779 @@ -0,0 +1,36 @@ + +qemu-system-arm and qemu-system-aarch64 QMP hangs after kernel boots + +After booting a Linux kernel on both arm and aarch64, the QMP sockets gets unresponsive. Initially, this was thought to be limited to "quit" commands, but it reproduced with others (such as in this +reproducer). This is a partial log output: + + >>> {'execute': 'qmp_capabilities'} + <<< {'return': {}} + Booting Linux on physical CPU 0x0000000000 [0x410fd034] + Linux version 4.18.16-300.fc29.aarch64 (<email address hidden>) (gcc version 8.2.1 20180801 (Red Hat 8.2.1-2) (GCC)) #1 SMP Sat Oct 20 23:12:22 UTC 2018 + ... + Policy zone: DMA32 + Kernel command line: printk.time=0 console=ttyAMA0 + >>> {'execute': 'stop'} + <<< {'timestamp': {'seconds': 1558370331, 'microseconds': 470173}, 'event': 'STOP'} + <<< {'return': {}} + >>> {'execute': 'cont'} + <<< {'timestamp': {'seconds': 1558370331, 'microseconds': 470849}, 'event': 'RESUME'} + <<< {'return': {}} + >>> {'execute': 'stop'} + +Sometimes it takes just the first "stop" command. Overall, I was able to reproduce 100% of times when applied on top of 6d8e75d41c58892ccc5d4ad61c4da476684c1c83. + +The reproducer test can be seen/fetched at: + - https://github.com/clebergnu/qemu/commit/c778e28c24030c4a36548b714293b319f4bf18df + +And test results from Travis CI can be seen at: + - https://travis-ci.org/clebergnu/qemu/jobs/534915669 + +For convenience purposes, here's qemu-system-aarch64 launching and hanging on the first "stop": + - https://travis-ci.org/clebergnu/qemu/jobs/534915669#L3615 + - https://travis-ci.org/clebergnu/qemu/jobs/534915669#L3645 + +And here's qemu-system-arm hanging the very same way: + - https://travis-ci.org/clebergnu/qemu/jobs/534915669#L3780 + - https://travis-ci.org/clebergnu/qemu/jobs/534915669#L3800 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1837 b/results/classifier/deepseek-2-tmp/output/socket/1837 new file mode 100644 index 000000000..72846ad8d --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1837 @@ -0,0 +1,36 @@ + +Support IP_MULTICAST_IF socket option in linux-user +Additional information: +I've run into this limitation in qemu-aarch64-static version Debian 1:6.2+dfsg-2ubuntu6.12, but from the link above, it doesn't seem to be implemented on master yet. + +Here's some source code that demonstrates the failure: +``` +#include <sys/socket.h> +#include <arpa/inet.h> +#include <netinet/ip.h> +#include <unistd.h> +#include <assert.h> +#include <stdio.h> + +int main() +{ + int fd, ret; + struct in_addr addr = {htonl(INADDR_LOOPBACK)}; + + fd = socket(AF_INET, SOCK_DGRAM, IPPROTO_UDP); + assert(fd >= 0); + ret = setsockopt(fd, IPPROTO_IP, IP_MULTICAST_IF, &addr, sizeof(addr)); + if (ret < 0) + { + perror("setsockopt failed"); + return 1; + } + close(fd); + printf("Success!\n"); + return 0; +} +``` + +When run under qemu, it gives the error `setsockopt failed: Protocol not available`. + +It doesn't look like it should be too hard to support (certainly no worse than IP_ADD_MEMBERSHIP). Let me know if I can help with a patch. diff --git a/results/classifier/deepseek-2-tmp/output/socket/1840252 b/results/classifier/deepseek-2-tmp/output/socket/1840252 new file mode 100644 index 000000000..50b19dae7 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1840252 @@ -0,0 +1,61 @@ + +Infinite loop over ERANGE from getsockopt + +Host system: Ubuntu 18.04.3 AMD64 +Qemu Version: qemu-arm-static --version +qemu-arm version 2.11.1(Debian 1:2.11+dfsg-1ubuntu7.17) + +Emulated System: +Root file system taken from RaspberryPi 3 image +ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img +from http://cdimage.ubuntu.com/releases/18.04/release/ubuntu-18.04.3-preinstalled-server-armhf+raspi3.img.xz. + +Then using system-nspawn with with /usr/bin/qemu-arm-static copied in. + +When executing commands like + dpkg -i (--force-all) <...>.deb +or + tar tvf .. +or + tar xvf .. +the hosting qemu-arm-static process goes into an infinite loop of getsockopt calls of the form: +getsockopt(12, SOL_SOCKET, SO_PEERSEC, 0x7fff7cac49d8, [4]) = -1 ERANGE (Numerical result out of range) +I assume that this is because of an infinite retry without checking the actual error code of the call. + +strace: +openat(AT_FDCWD, "/lib/arm-linux-gnueabihf/librt.so.1", O_RDONLY|O_CLOEXEC) = 12 +read(12, "\177ELF\1\1\1\3\0\0\0\0\0\0\0\0\3\0(\0\1\0\0\0\20\30\0\0004\0\0\0"..., 512) = 512 +lseek(12, 21236, SEEK_SET) = 21236 +read(12, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 1240) = 1240 +lseek(12, 20856, SEEK_SET) = 20856 +read(12, "A2\0\0\0aeabi\0\1(\0\0\0\0057-A\0\6\n\7A\10\1\t\2\n\4\22"..., 51) = 51 +fstat(12, {st_mode=S_IFREG|0644, st_size=22476, ...}) = 0 +mmap(0x7f419952c000, 90112, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_DENYWRIT +E, -1, 0) = 0x7f419952c000 +mmap(0x7f419952c000, 90112, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0) = 0x +7f419952c000 +mprotect(0x7f4199531000, 61440, PROT_NONE) = 0 +mmap(0x7f4199540000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 12, 0x4000) + = 0x7f4199540000 +close(12) = 0 +mprotect(0x7f4199540000, 4096, PROT_READ) = 0 +mprotect(0x7f4199578000, 8192, PROT_READ) = 0 +mmap(0x7f419957b000, 28672, PROT_NONE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) += 0x7f419957b000 +rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], NULL, 8) = 0 +rt_sigprocmask(SIG_SETMASK, ~[RTMIN RT_1], NULL, 8) = 0 +rt_sigprocmask(SIG_SETMASK, [HUP USR1 USR2 PIPE ALRM CHLD TSTP URG VTALRM PROF WINCH IO], NULL, 8 +) = 0 +access("/etc/systemd/dont-synthesize-nobody", F_OK) = -1 ENOENT (No such file or directory) +getpid() = 26 +socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 12 +getsockopt(12, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0 +setsockopt(12, SOL_SOCKET, SO_RCVBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) +setsockopt(12, SOL_SOCKET, SO_RCVBUF, [8388608], 4) = 0 +getsockopt(12, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0 +setsockopt(12, SOL_SOCKET, SO_SNDBUFFORCE, [8388608], 4) = -1 EPERM (Operation not permitted) +setsockopt(12, SOL_SOCKET, SO_SNDBUF, [8388608], 4) = 0 +connect(12, {sa_family=AF_UNIX, sun_path="/run/dbus/system_bus_socket"}, 29) = 0 +getsockopt(12, SOL_SOCKET, SO_PEERCRED, {pid=0, uid=0, gid=0}, [12]) = 0 +getsockopt(12, SOL_SOCKET, SO_PEERSEC, 0x7fff7cac49d8, [4]) = -1 ERANGE (Numerical result out of +range) \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1867601 b/results/classifier/deepseek-2-tmp/output/socket/1867601 new file mode 100644 index 000000000..af9527c1e --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1867601 @@ -0,0 +1,16 @@ + +test-char not concurrent with unix socket + +'make check-unit' might fail when running multiple tests in parallel. + +Apparently occurred on OSX CI: +https://travis-ci.org/github/philmd/qemu/jobs/662357430 + +Guess is same unix path used: + +static SocketAddress unixaddr = { + .type = SOCKET_ADDRESS_TYPE_UNIX, + .u.q_unix.path = (char *)"test-char.sock", +}; + +Note, other tests in this file use g_dir_make_tmp(). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1898084 b/results/classifier/deepseek-2-tmp/output/socket/1898084 new file mode 100644 index 000000000..559b0d091 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1898084 @@ -0,0 +1,24 @@ + +Assertion failed: (buf_len != 0), function soread, file socket.c, line 183. + +I have a virtual raspberry py that I am running qemu 5.1.0 for MacOS. + +Here is the command line I used: + +qemu-system-arm \ + -M versatilepb \ + -cpu arm1176 \ + -m 256 \ + -drive file=2020-08-20-raspios-buster-armhf-lite.img,if=none,index=0,media=disk,format=raw,id=disk0 \ + -device virtio-blk-pci,drive=disk0,disable-modern=on,disable-legacy=off \ + -net nic -net user,hostfwd=tcp::5022-:22 \ + -dtb versatile-pb-buster-5.4.51.dtb \ + -kernel kernel-qemu-5.4.51-buster \ + -append "root=/dev/vda2 panic=1" \ + -no-reboot \ + -serial stdio + +When trying to ssh from another machine while docker was running inside the VM, I got the following error: + +Assertion failed: (buf_len != 0), function soread, file /private/tmp/qemu-20200813-13289-1g95loa/qemu-5.1.0/slirp/src/socket.c, line 183 +../boot.sh: line 12: 8592 Abort trap: 6 \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1903470 b/results/classifier/deepseek-2-tmp/output/socket/1903470 new file mode 100644 index 000000000..7462c8dbc --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1903470 @@ -0,0 +1,10 @@ + +qemu 5.1.0: Add UNIX socket support for netdev socket + +qemu has a way to connect instances using a socket: + +-netdev socket,id=str[,fd=h][,listen=[host]:port][,connect=host:port] + +This can also be used to connect a qemu instance to something else using a socket connection, however there is no authentication or security to the connection, so rather than using a port which can be accessed by any user on the machine, having the ability to use or connect to UNIX sockets would be helpful, and adding this option should be fairly trivial. + +UNIX sockets can be found in various parts of qemu (monitor, etc) so I believe having this on network would make sense. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/1923692 b/results/classifier/deepseek-2-tmp/output/socket/1923692 new file mode 100644 index 000000000..cc9e798a6 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/1923692 @@ -0,0 +1,8 @@ + +qemu 5.2.0: Add reconnect option support for netdev socket + +Most of qemu socket accepting options (such as chardev) accept among other things a "reconnect" option. + +netdev socket however returns: Invalid parameter 'reconnect' + +It would make sense that available options for socket links be at least partially normalized (also see issue https://bugs.launchpad.net/qemu/+bug/1903470 which was closed without resolution). \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/2065579 b/results/classifier/deepseek-2-tmp/output/socket/2065579 new file mode 100644 index 000000000..b86b29a74 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/2065579 @@ -0,0 +1,77 @@ + +[UBUNTU 22.04] OS guest boot issues on 9p filesystem + +=== Reported by <email address hidden> - 2024-05-13 03:53:01 === + +---Problem Description--- +OS guest boot issues on 9p filesystem due to unix domain sockets open failure + +Contact Information = <email address hidden> + +Machine Type = 3931-7G4 + +---uname output--- +5.15.0-92-generic #102-Ubuntu SMP Wed Jan 10 09:35:24 UTC 2024 s390x s390x s390x GNU/Linux + +---Steps to Reproduce--- + #!/bin/bash + +# Cleanup target dir +[ -d ./target ] && rm -rf target +mkdir target + +# Add configuration updates +mkdir -p ./target/etc/initramfs-tools/ +echo 9p >> ./target/etc/initramfs-tools/modules +echo 9pnet_virtio >> ./target/etc/initramfs-tools/modules + +# Add the test script +cat > ./target/test_init << EOF +#!/bin/bash + +echo "Test for unix domain sockets" + +nc -Ul /socket & +sleep 1 +echo "Sockets work" | nc -UN /socket || echo "Sockets fail" + +echo o > /proc/sysrq-trigger +sleep 999 +EOF +chmod 700 ./target/test_init + +# Create an Ubuntu 23.10 around it +echo "Creating Ubuntu target OS" +debootstrap --variant=minbase\ + --include=udev,kmod,initramfs-tools,systemd,netcat-openbsd,linux-image-generic \ + --exclude=man,bash-completion \ + mantic ./target > /dev/null || exit 1 + +# Run the test in 9p forwarded filesystem +echo "Running OS in qemu" +qemu-system-s390x \ + -m 8192 \ + -smp 4 \ + -nodefaults -nographic -no-reboot -no-user-config \ + -kernel ./target/boot/vmlinuz \ + -initrd ./target/boot/initrd.img \ + -append 'root=fsRoot rw rootfstype=9p rootflags=trans=virtio,version=9p2000.L,msize=512000,cache=mmap,posixacl console=ttysclp0 init=/test_init quiet' \ + -fsdev local,security_model=passthrough,multidevs=remap,id=fsdev-fsRoot,path=./target \ + -device virtio-9p-pci,id=fsRoot,fsdev=fsdev-fsRoot,mount_tag=fsRoot \ + -device virtio-serial-ccw -device sclpconsole,chardev=console \ + -chardev stdio,id=console,signal=off + + +---Debugger--- +A debugger is not configured + +Userspace rpm: qemu-(current).deb + +Userspace tool common name: qemu + +Userspace tool obtained from project website: na + +The userspace tool has the following bit modes: both + +*Additional Instructions for <email address hidden>: +-Attach ltrace and strace of userspace application. \ No newline at end of file diff --git a/results/classifier/deepseek-2-tmp/output/socket/2292 b/results/classifier/deepseek-2-tmp/output/socket/2292 new file mode 100644 index 000000000..2cbd890b6 --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/2292 @@ -0,0 +1,20 @@ + +UNIX socket path is too long +Description of problem: +At [Unikraft](https://unikraft.org) we facilitate the construction and also runtime lifecycle management of ultra-lightweight virtual machine unikernels. We have developed [`kraft`](https://github.com/unikraft/kraftkit), an open-source tool which facilitates this across a number of different virtual machine monitors, [including QEMU](https://github.com/unikraft/kraftkit/tree/staging/machine/qemu). + +We are receiving increased reports of the following error from our users: + +``` +could not start and wait for QEMU process: qemu-system-x86_64: -qmp unix:/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock,server,nowait: UNIX socket path '/Users/__USERNAME__/.local/share/kraftkit/runtime/37a7691a-d402-4760-b493-692bb8d0460a/qemu_control.sock' is too long +``` + +We systematically build the relevant QEMU process command line and arguments with flags [via our Go SDK](https://github.com/unikraft/kraftkit/blob/staging/machine/qemu/v1alpha1.go#L180-L229) and include what has become an erroneously long UNIX path for the QAPI control socket which we use to manage instantiated VM instances. + +This issue tracks the increasing of maximum path length for the `-qmp` (and maybe other) flags which accept paths. +Steps to reproduce: +1. Install [`kraft`](https://github.com/unikraft/kraftkit), [Unikraft](https://unikraft.org)'s companion command-line client; +2. Update KraftKit's config file to include an arbitrarily long path for `runtime_dir` by editing `~/.config/kraftkit/config.yaml`; +3. Start a QEMU unikernel instance with `kraft run --arch x86_64 --plat qemu unikraft.org/helloworld:latest` +Additional information: + diff --git a/results/classifier/deepseek-2-tmp/output/socket/2337 b/results/classifier/deepseek-2-tmp/output/socket/2337 new file mode 100644 index 000000000..2ed2073db --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/2337 @@ -0,0 +1,63 @@ + +Os boot issues on 9p filesystem due to unix domain sockets open failure +Description of problem: +Unix filesystem API is broken, unix domain socket special files return an error at open() +Steps to reproduce: +Simple script. Tries to use netcat to get data through a local unix domain socket file +``` +#!/bin/bash + +# Cleanup target dir +[ -d ./target ] && rm -rf target +mkdir target + +# Add configuration updates +mkdir -p ./target/etc/initramfs-tools/ +echo 9p >> ./target/etc/initramfs-tools/modules +echo 9pnet_virtio >> ./target/etc/initramfs-tools/modules + +# Add the test script +cat > ./target/test_init << EOF +#!/bin/bash + +echo "Test for unix domain sockets" + +nc -Ul /socket & +sleep 1 +echo "Sockets work" | nc -UN /socket || echo "Sockets fail" + +echo o > /proc/sysrq-trigger +sleep 999 +EOF +chmod 700 ./target/test_init + +# Create an Ubuntu 23.10 around it +echo "Creating Ubuntu target OS" +debootstrap --variant=minbase\ + --include=udev,kmod,initramfs-tools,systemd,netcat-openbsd,linux-image-generic \ + --exclude=man,bash-completion \ + mantic ./target > /dev/null || exit 1 + +# Run the test in 9p forwarded filesystem +echo "Running OS in qemu" +qemu-system-s390x \ + -m 8192 \ + -smp 4 \ + -nodefaults -nographic -no-reboot -no-user-config \ + -kernel ./target/boot/vmlinuz \ + -initrd ./target/boot/initrd.img \ + -append 'root=fsRoot rw rootfstype=9p rootflags=trans=virtio,version=9p2000.L,msize=512000,cache=mmap,posixacl console=ttysclp0 init=/test_init quiet' \ + -fsdev local,security_model=passthrough,multidevs=remap,id=fsdev-fsRoot,path=./target \ + -device virtio-9p-pci,id=fsRoot,fsdev=fsdev-fsRoot,mount_tag=fsRoot \ + -device virtio-serial-ccw -device sclpconsole,chardev=console \ + -chardev stdio,id=console,signal=off +``` +Additional information: +Test output: +``` +Test for unix domain sockets +qemu-system-s390x: 9p: broken or compromised client detected; attempt to open special file (i.e. neither regular file, nor directory) +nc: No such device or address +nc: /socket: No such file or directory +Sockets fail +``` diff --git a/results/classifier/deepseek-2-tmp/output/socket/607 b/results/classifier/deepseek-2-tmp/output/socket/607 new file mode 100644 index 000000000..21d14140a --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/607 @@ -0,0 +1,60 @@ + +socket_sockaddr_to_address_unix: Assertion `salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un)' failed. +Description of problem: + +Steps to reproduce: +1. Run Qemu command line +2. Start console in virt-manager +Additional information: +_/var/log/libvirt/qemu_ + +``` +2021-09-08 13:08:22.003+0000: starting up libvirt version: 7.6.0, qemu version: 6.1.0, kernel: 5.4.143-1-MANJARO, hostname: pjehrsohmehj +LC_ALL=C \ +PATH=/usr/local/sbin:/usr/local/bin:/usr/bin \ +HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default \ +XDG_DATA_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.local/share \ +XDG_CACHE_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.cache \ +XDG_CONFIG_HOME=/var/lib/libvirt/qemu/domain-81-Vagrant_default/.config \ +/usr/bin/qemu-system-x86_64 \ +-name guest=Vagrant_default,debug-threads=on \ +-S \ +-object '{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvirt/qemu/domain-81-Vagrant_default/master-key.aes"}' \ +-machine pc-i440fx-6.1,accel=kvm,usb=off,dump-guest-core=off,memory-backend=pc.ram \ +-cpu Snowridge,ss=on,vmx=on,hypervisor=on,tsc-adjust=on,mpx=on,rdpid=on,md-clear=on,stibp=on,xsaves=on,ibpb=on,ibrs=on,amd-stibp=on,amd-ssbd=on,rdctl-no=on,ibrs-all=on,skip-l1dfl-vmentry=on,mds-no=on,pschange-mc-no=on,clwb=off,gfni=off,cldemote=off,movdiri=off,movdir64b=off,core-capability=off,split-lock-detect=off \ +-m 512 \ +-object '{"qom-type":"memory-backend-ram","id":"pc.ram","size":536870912}' \ +-overcommit mem-lock=off \ +-smp 1,sockets=1,cores=1,threads=1 \ +-uuid cde944bb-cfc2-473b-b605-580382c3f944 \ +-no-user-config \ +-nodefaults \ +-chardev socket,id=charmonitor,fd=32,server=on,wait=off \ +-mon chardev=charmonitor,id=monitor,mode=control \ +-rtc base=utc \ +-no-shutdown \ +-boot strict=on \ +-device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/Zelec-VAGRANTSLASH-manjarolinux_vagrant_box_image_20210901.1551100290_box.img","node-name":"libvirt-2-storage","auto-read-only":true,"discard":"unmap"}' \ +-blockdev '{"node-name":"libvirt-2-format","read-only":true,"driver":"qcow2","file":"libvirt-2-storage","backing":null}' \ +-blockdev '{"driver":"file","filename":"/var/lib/libvirt/images/Vagrant_default.img","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":"libvirt-2-format"}' \ +-device virtio-blk-pci,bus=pci.0,addr=0x3,drive=libvirt-1-format,id=virtio-disk0,bootindex=1 \ +-netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=35 \ +-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:cf:27:78,bus=pci.0,addr=0x5 \ +-chardev pty,id=charserial0 \ +-device isa-serial,chardev=charserial0,id=serial0 \ +-audiodev id=audio1,driver=none \ +-vnc 127.0.0.1:0,audiodev=audio1 \ +-k en-us \ +-device cirrus-vga,id=video0,bus=pci.0,addr=0x2 \ +-device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 \ +-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ +-msg timestamp=on +char device redirected to /dev/pts/0 (label charserial0) +2021-09-08T13:08:22.188784Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(48FH).vmx-exit-load-perf-global-ctrl [bit 12] +2021-09-08T13:08:22.188905Z qemu-system-x86_64: warning: host doesn't support requested feature: MSR(490H).vmx-entry-load-perf-global-ctrl [bit 13] +qemu-system-x86_64: ../qemu-6.1.0/util/qemu-sockets.c:1348: socket_sockaddr_to_address_unix: Assertion `salen >= sizeof(su->sun_family) + 1 && salen <= sizeof(struct sockaddr_un)' failed. +2021-09-08 13:08:28.059+0000: shutting down, reason=crashed +2 +``` diff --git a/results/classifier/deepseek-2-tmp/output/socket/872 b/results/classifier/deepseek-2-tmp/output/socket/872 new file mode 100644 index 000000000..801a0d68d --- /dev/null +++ b/results/classifier/deepseek-2-tmp/output/socket/872 @@ -0,0 +1,2 @@ + +linux-user getsockopt(fd, SOL_SOCKET, SO_ERROR) returns host errno to target |