summary refs log tree commit diff stats
path: root/results/classifier/108/other/1643
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/108/other/164316
-rw-r--r--results/classifier/108/other/164334241
-rw-r--r--results/classifier/108/other/164353747
-rw-r--r--results/classifier/108/other/164361969
4 files changed, 173 insertions, 0 deletions
diff --git a/results/classifier/108/other/1643 b/results/classifier/108/other/1643
new file mode 100644
index 000000000..1e4b263c0
--- /dev/null
+++ b/results/classifier/108/other/1643
@@ -0,0 +1,16 @@
+device: 0.848
+network: 0.840
+performance: 0.648
+vnc: 0.428
+PID: 0.343
+semantic: 0.296
+boot: 0.249
+permissions: 0.232
+files: 0.203
+graphic: 0.173
+debug: 0.144
+socket: 0.123
+other: 0.105
+KVM: 0.075
+
+Connect to MACVTAP by name
diff --git a/results/classifier/108/other/1643342 b/results/classifier/108/other/1643342
new file mode 100644
index 000000000..8a71a12e2
--- /dev/null
+++ b/results/classifier/108/other/1643342
@@ -0,0 +1,41 @@
+performance: 0.743
+device: 0.697
+files: 0.635
+semantic: 0.617
+graphic: 0.608
+boot: 0.563
+PID: 0.537
+KVM: 0.399
+socket: 0.389
+other: 0.379
+debug: 0.310
+permissions: 0.288
+vnc: 0.234
+network: 0.189
+
+not able to passthrough mouse / keyboard
+
+After upgrading from qemu version 2.6.2 to 2.7.9 I can't boot my vm anymore. I get this error:
+
+qemu-system-x86_64: -usbdevice host:046d:c227: could not add USB device 'host:046d:c227'
+
+This happens with every usb-device I tried. Works 2.6.2 without any errors. (also tried in 2.7.0, same error)
+I use the following script:
+
+
+qemu-system-x86_64 \
+-enable-kvm \
+-m 16392 \
+-cpu host,kvm=off \
+-smp 4,sockets=1,cores=2,threads=2,maxcpus=4 \
+-usb -usbdevice host:046d:c227 -usbdevice host:046d:c226 \
+-vga none \
+-device vfio-pci,host=01:00.0,multifunction=on \
+-device vfio-pci,host=01:00.1 \
+-drive if=pflash,format=raw,readonly,file=/usr/share/edk2.git/ovmf-x64/OVMF_CODE-pure-efi.fd \
+-drive if=pflash,format=raw,file=/tmp/my_vars.fd \
+-device virtio-scsi-pci,id=scsi \
+-drive file=/var/iso/win10.iso,id=isocd,format=raw,if=none -device scsi-cd,drive=isocd \
+-drive file=/home/marius/images/windows10.img,id=disk,format=raw,if=none,cache=writeback -device scsi-hd,drive=disk \
+-drive file=/var/iso/virtio-win-0.1.126.iso,id=virtiocd,if=none,format=raw -device ide-cd,bus=ide.1,drive=virtiocd
+
diff --git a/results/classifier/108/other/1643537 b/results/classifier/108/other/1643537
new file mode 100644
index 000000000..1132d652b
--- /dev/null
+++ b/results/classifier/108/other/1643537
@@ -0,0 +1,47 @@
+semantic: 0.714
+files: 0.702
+graphic: 0.699
+device: 0.693
+network: 0.640
+socket: 0.622
+performance: 0.572
+vnc: 0.547
+permissions: 0.538
+other: 0.522
+boot: 0.473
+PID: 0.469
+debug: 0.441
+KVM: 0.363
+
+target-ppc/int_helper.c: 2 * bad array index
+
+1.
+
+[qemu/target-ppc/int_helper.c:2575]: (error) Array 'reg.u16[8]' accessed at index 8, which is out of bounds.
+
+Source code is
+
+   return reg->u16[8 - n];
+
+and
+
+qemu/target-ppc/cpu.h:    uint16_t u16[8];
+
+but at least once, n is zero, for example line 2725 in the int_helper.c file:
+
+    uint16_t sgnb = get_national_digit(b, 0);
+
+2.
+
+[qemu/target-ppc/int_helper.c:2584]: (error) Array 'reg.u16[8]' accessed at index 8, which is out of bounds.
+
+Duplicate
+
+Thanks for the bug report! Jose posted a patch:
+marc.info/?<email address hidden>
+
+Fix has been committed:
+http://git.qemu.org/?p=qemu.git;a=commitdiff;h=a813fe73621e1221a09
+
+Released with version 2.8
+
diff --git a/results/classifier/108/other/1643619 b/results/classifier/108/other/1643619
new file mode 100644
index 000000000..12d7aa6b7
--- /dev/null
+++ b/results/classifier/108/other/1643619
@@ -0,0 +1,69 @@
+debug: 0.827
+other: 0.789
+socket: 0.784
+performance: 0.783
+device: 0.776
+network: 0.775
+graphic: 0.773
+semantic: 0.762
+permissions: 0.762
+PID: 0.747
+boot: 0.706
+vnc: 0.668
+files: 0.662
+KVM: 0.568
+
+netlink broken on big-endian mips
+
+Debian QEMU version 2.7.0, but the bug also appears in current git master (commit c36ed06e9159)
+
+As the summary says, netlink is completely broken on big-endian mips running qemu-user.
+
+Running 'ip route' from within a Debian chroot with QEMU simply hangs. Running amd64 strace on qemu-mips-static shows that it's waiting for a netlink response from the kernel which never comes.
+
+[...]
+[pid 11249] socket(AF_NETLINK, SOCK_RAW|SOCK_CLOEXEC, NETLINK_ROUTE) = 3
+[pid 11249] setsockopt(3, SOL_SOCKET, SO_SNDBUF, [32768], 4) = 0
+[pid 11249] setsockopt(3, SOL_SOCKET, SO_RCVBUF, [1048576], 4) = 0
+[pid 11249] bind(3, {sa_family=AF_NETLINK, nl_pid=0, nl_groups=00000000}, 12) = 0
+[pid 11249] getsockname(3, {sa_family=AF_NETLINK, nl_pid=11249, nl_groups=00000000}, [12]) = 0
+[pid 11249] time([1479745823])          = 1479745823
+[pid 11249] sendto(3, {{len=671088640, type=0x1a00 /* NLMSG_??? */, flags=NLM_F_REQUEST|NLM_F_MULTI|0x100, seq=539046744, pid=0}, "\2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\35\0\0\0\1"}, 40, 0, NULL, 0) = 40
+[pid 11249] recvmsg(3,
+
+Notice the len in the buffer passed to the kernel is 0x28000000 which looks byteswapped.
+
+Removing the call to fd_trans_unregister in the NR_socket syscall in do_syscall fixes this for me, but I don't understand why the fd translation was immediately unregistered after being registered just before in do_socket - presumably it was added for a reason.
+
+--- a/linux-user/syscall.c
++++ b/linux-user/syscall.c
+@@ -9331,7 +9331,6 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
+ #ifdef TARGET_NR_socket
+     case TARGET_NR_socket:
+         ret = do_socket(arg1, arg2, arg3);
+-        fd_trans_unregister(ret);
+         break;
+ #endif
+ #ifdef TARGET_NR_socketpair
+
+I also notice fd_trans_unregister does not appear in the socketcall implementation which seems like an oversight.
+
+Same here. While running qemu-debootstrap using Debian qemu 2.7, debootstrap hangs on groupadd calls. Reproduction on amd64 host, running jessie, on a failed qemu-debootstrap but sufficiently working jessie mips chroot. See attached strace of groupadd. Problem reproduces with compiled qemu from git master, commit 00227fefd2059464cd2f59aed29944874c630e2f.
+
+...
+[pid 31008] socket(PF_NETLINK, SOCK_RAW, NETLINK_AUDIT) = 3
+[pid 31008] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
+...
+[pid 31008] sendto(3, "\0\0\0x\4\\\0\5\0\0\0\1\0\0\0\0op=adding group "..., 120, 0, {sa_family=AF_NETLINK, pid=0, groups=00000000}, 12) = 120
+[pid 31008] ppoll([{fd=3, events=POLLIN}], 1, {0, 500000000}, NULL, 0) = 0 (Timeout)
+[pid 31008] recvfrom(3, 0x7facef9e1504, 8988, 66, 0x7fff0138c9b0, 0x7fff0138c9f4) = -1 EAGAIN (Resource temporarily unavailable)
+[pid 31008] ppoll([{fd=3, events=POLLIN}], 1, {0, 500000000}, NULL, 0) = 0 (Timeout)
+[pid 31008] recvfrom(3, 0x7facef9e1504, 8988, 66, 0x7fff0138c9b0, 0x7fff0138c9f4) = -1 EAGAIN (Resource temporarily unavailable)
+...etc ... etc...
+
+Strace jessie mips groupadd.
+
+Patch applied by James works for me as well. Dropping a qemu-user static binary from Debian qemu 2.1 into the mips chroot can also be used as workaround.
+
+This has been fixed by 40493c5f2b0f124c9b2581e539bba14522e51269, which is exactly the same diff as given here.
+