6 files changed, 350 insertions, 0 deletions
diff --git a/results/classifier/118/none/89 b/results/classifier/118/none/89
new file mode 100644
index 00000000..8598063c
--- /dev/null
+++ b/results/classifier/118/none/89
@@ -0,0 +1,31 @@
+device: 0.686
+peripherals: 0.392
+performance: 0.341
+i386: 0.295
+user-level: 0.245
+virtual: 0.221
+architecture: 0.218
+network: 0.208
+semantic: 0.198
+mistranslation: 0.187
+x86: 0.182
+arm: 0.126
+boot: 0.104
+VMM: 0.074
+TCG: 0.072
+KVM: 0.051
+PID: 0.043
+debug: 0.042
+hypervisor: 0.041
+ppc: 0.038
+vnc: 0.032
+graphic: 0.029
+risc-v: 0.028
+kernel: 0.019
+socket: 0.013
+permissions: 0.010
+files: 0.009
+register: 0.009
+assembly: 0.005
+
+Documentation for mtdblock, option-rom, and pflash is non-existent
diff --git a/results/classifier/118/none/891 b/results/classifier/118/none/891
new file mode 100644
index 00000000..076f76eb
--- /dev/null
+++ b/results/classifier/118/none/891
@@ -0,0 +1,31 @@
+device: 0.690
+semantic: 0.474
+graphic: 0.411
+debug: 0.325
+files: 0.294
+mistranslation: 0.292
+boot: 0.275
+user-level: 0.234
+performance: 0.232
+register: 0.172
+virtual: 0.126
+assembly: 0.111
+peripherals: 0.066
+network: 0.064
+i386: 0.045
+ppc: 0.042
+architecture: 0.038
+x86: 0.027
+VMM: 0.026
+permissions: 0.022
+vnc: 0.017
+arm: 0.016
+TCG: 0.011
+PID: 0.010
+KVM: 0.008
+hypervisor: 0.008
+risc-v: 0.003
+socket: 0.003
+kernel: 0.003
+
+how to know  jpeg-wan-compression  is in force
diff --git a/results/classifier/118/none/891625 b/results/classifier/118/none/891625
new file mode 100644
index 00000000..32aafa8f
--- /dev/null
+++ b/results/classifier/118/none/891625
@@ -0,0 +1,69 @@
+mistranslation: 0.659
+device: 0.644
+graphic: 0.570
+semantic: 0.567
+user-level: 0.523
+virtual: 0.473
+PID: 0.445
+ppc: 0.444
+files: 0.441
+network: 0.438
+permissions: 0.419
+architecture: 0.413
+register: 0.412
+KVM: 0.392
+performance: 0.382
+debug: 0.375
+socket: 0.375
+arm: 0.333
+risc-v: 0.330
+TCG: 0.325
+VMM: 0.319
+vnc: 0.312
+boot: 0.306
+i386: 0.303
+peripherals: 0.303
+hypervisor: 0.296
+assembly: 0.289
+x86: 0.278
+kernel: 0.253
+
+[qemu-kvm] add vhost-net to kvm group udev rules 65-kvm.rules
+
+Please consider authorizing the kvm group to access vhost-net device, similar to the kvm device.
+Thanks!
+
+
+
+I wonder if it really belongs to kvm group, -- maybe a separate "vhost_net" group should be used instead.  Yes it can only be used with qemu/kvm currently, but maybe some other tool will use it in the future, and looking at how many security issues /dev/kvm access had, maybe vhost_net shold be restricted more...
+
+How other distributions are doing this?  I'm not sure we want to introduce our own naming here...
+
+Well, at Gentoo we have kvm group, and I think that this comes from
+upstream rule.
+Doing vhost_net is good, anything that may be assigned to regular users.
+Thanks!
+
+
+Since there is no udev file in upstream QEMU, I guess this bug was meant for the qemu Ubuntu package instead?
+
+The attachment "udef.diff" seems to be a patch.  If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
+
+[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]
+
+Thank you for taking the time to report this bug and helping to make Ubuntu better.
+
+I'm not sure if it would be appropriate to make this change, but it is clear what you're requesting so I'm setting the bug status to Triaged.
+
+Hi,
+I'm currently parsing through bug that are dormant way too long.
+
+These days the content still exists, but is in debian/qemu-system-common.udev
+
+But vhost-net is working fine without that change, so I wonder what it was back then that failed without that - so that we can verify if that actually is an issue today.
+
+Until then setting incomplete.
+
+
+[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/none/893 b/results/classifier/118/none/893
new file mode 100644
index 00000000..5c255d59
--- /dev/null
+++ b/results/classifier/118/none/893
@@ -0,0 +1,31 @@
+device: 0.798
+architecture: 0.751
+performance: 0.598
+debug: 0.502
+semantic: 0.404
+graphic: 0.360
+peripherals: 0.333
+permissions: 0.315
+mistranslation: 0.264
+files: 0.245
+network: 0.244
+PID: 0.178
+register: 0.145
+user-level: 0.120
+socket: 0.116
+kernel: 0.097
+assembly: 0.084
+boot: 0.061
+vnc: 0.060
+i386: 0.055
+x86: 0.054
+virtual: 0.048
+ppc: 0.047
+risc-v: 0.033
+arm: 0.033
+TCG: 0.029
+VMM: 0.027
+hypervisor: 0.014
+KVM: 0.003
+
+Cannot boot and set rhel7 or 8 s390x on Redhat 8(Host OS) using qemu-system-s390x
diff --git a/results/classifier/118/none/897193 b/results/classifier/118/none/897193
new file mode 100644
index 00000000..22ed7d19
--- /dev/null
+++ b/results/classifier/118/none/897193
@@ -0,0 +1,103 @@
+peripherals: 0.656
+user-level: 0.633
+device: 0.617
+mistranslation: 0.616
+register: 0.591
+graphic: 0.591
+semantic: 0.581
+virtual: 0.579
+network: 0.575
+performance: 0.569
+permissions: 0.568
+risc-v: 0.567
+PID: 0.566
+x86: 0.563
+kernel: 0.561
+files: 0.558
+arm: 0.548
+architecture: 0.545
+ppc: 0.545
+assembly: 0.540
+socket: 0.536
+KVM: 0.533
+boot: 0.529
+debug: 0.528
+hypervisor: 0.520
+VMM: 0.487
+vnc: 0.481
+TCG: 0.460
+i386: 0.417
+
+virtfs: kernel compile fails
+
+I am trying to compile a kernel under virtfs, and am getting an error.  The error does not occur when compiling outside of the virtfs mount.
+
+Both guest and host are running the 3.0.4 kernel.
+QEMU is latest from git: bc75c9e50d308b2ec6623a40179c5cdc84b63dae
+
+QEMU command line:
+/usr/local/bin/qemu-system-x86_64 -nographic -boot c -m 1024 -machine type=pc,accel=kvm -drive file=/root/hdd1.img,if=virtio -drive file=/root/test1.img,if=virtio -drive file=/root/test2.img,if=virtio -virtfs local,path=/mnt/virtfs,security_model=none,mount_tag=virtfs -net nic,model=virtio,macaddr=DE:AD:BE:EF:AA:BB -net tap,ifname=qtap0,script=no
+
+virtfs line in /etc/fstab:
+virtfs                  /mnt/virtfs             9p      defaults,noauto,trans=virtio    0 0
+
+Steps to reproduce and output:
+
+[root@guest linux-3.0.4]# make mrproper
+  CLEAN   scripts/basic
+  CLEAN   scripts/kconfig
+  CLEAN   include/config include/generated
+  CLEAN   .config .config.old
+[root@guest linux-3.0.4]# make defconfig
+  HOSTCC  scripts/basic/fixdep
+  HOSTCC  scripts/kconfig/conf.o
+  SHIPPED scripts/kconfig/zconf.tab.c
+  SHIPPED scripts/kconfig/lex.zconf.c
+  SHIPPED scripts/kconfig/zconf.hash.c
+  HOSTCC  scripts/kconfig/zconf.tab.o
+  HOSTLD  scripts/kconfig/conf
+*** Default configuration is based on 'x86_64_defconfig'
+#
+# configuration written to .config
+#
+[root@guest linux-3.0.4]# make
+scripts/kconfig/conf --silentoldconfig Kconfig
+
+*** Error during update of the configuration.
+
+make[2]: *** [silentoldconfig] Error 1
+make[1]: *** [silentoldconfig] Error 2
+make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'.  Stop.
+
+
+Please let me know if you need any other information.  Thanks!
+
+uname -a on host:
+Linux host 3.0.4 #1 SMP Mon Oct 17 11:54:45 IST 2011 x86_64 x86_64 x86_64 GNU/Linux
+
+uname -a on guest:
+Linux guest 3.0.4 #2 SMP Wed Nov 23 12:39:03 IST 2011 x86_64 x86_64 x86_64 GNU/Linux
+
+Hi Avishay,
+
+Are you running qemu as a normal user? In that case, could you please check whether normal user has rw access to the kernel source?
+
+Also could you please attach the output of strace scripts/kconfig/conf --silentoldconfig Kconfig ?
+
+Hi,
+
+I am running qemu as root.
+
+The output from strace for the command that you requested shows that this is the problem:
+rename(".tmpconfig.h", "include/generated/autoconf.h") = -1 ENOENT (No such file or directory)
+
+The command fails because the directory 'include/generated' doesn't exist because I ran only the command you mentioned, and not 'make'.
+
+So I attached the output for: strace -f make &> /tmp/strace.out
+
+Hope that helps, and thanks!
+
+Triaging old bug tickets ... can you still reproduce this problem with the latest version of QEMU?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/118/none/897466 b/results/classifier/118/none/897466
new file mode 100644
index 00000000..93da6a54
--- /dev/null
+++ b/results/classifier/118/none/897466
@@ -0,0 +1,85 @@
+mistranslation: 0.556
+user-level: 0.520
+debug: 0.517
+semantic: 0.510
+risc-v: 0.486
+TCG: 0.474
+VMM: 0.466
+permissions: 0.442
+hypervisor: 0.428
+performance: 0.416
+peripherals: 0.413
+virtual: 0.387
+graphic: 0.361
+ppc: 0.357
+i386: 0.357
+KVM: 0.349
+vnc: 0.344
+PID: 0.334
+arm: 0.332
+register: 0.316
+architecture: 0.310
+assembly: 0.307
+device: 0.290
+boot: 0.274
+socket: 0.255
+network: 0.240
+kernel: 0.212
+files: 0.194
+x86: 0.116
+
+UHCI Host Controller no longer present with -usb
+
+If on an up to date 12.04 install and I start a VM with:
+$ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
+
+Then use the 'info usbhost' in the monitor, I get:
+$ echo 'info usbhost' | nc -q 1 127.0.0.1 4444
+(qemu) info usbhost
+husb: using sys file-system with /dev/bus/usb
+$
+
+In Oneiric and eariler, 'info usbhost' would should a UHCI Host Controller. Eg:
+$ qemu -m 192 -serial none -chardev null,id=chardevmon -pidfile /tmp/pid -daemonize -nographic -monitor tcp:127.0.0.1:4444,server,nowait -net user,hostfwd=tcp:127.0.0.1:4422-:22 -usb -rtc base=utc -name qatest-vm -uuid ded3a46b-bb60-43f4-8113-d041aeb93cdf -hda libvirt/qatest/qatest.qcow2
+echo 'info usbhost' | nc -q 1 127.0.0.1 4444
+QEMU 0.14.1 monitor - type 'help' for more information
+(qemu) info usbhost
+husb: using sys file-system with /dev/bus/usb
+  Device 1.1, speed 12 Mb/s
+    Hub: USB device 1d6b:0001, UHCI Host Controller
+
+This breaks QRT/scripts/test-qemu.py and appears to be a regression, but I am not sure if it is a 3.2 kernel issue or a 0.14.1 vs 0.15 issue.
+
+hm, i couldn't reproduce this with 0.15.0+noroms-0ubuntu2 on top of 3.2.0-1-generic
+
+also couldn't reproduce it after an upgrade just now.
+
+I did a dist-upgrade and this is still reproducible:
+$ uname -a
+Linux sec-precise-i386 3.2.0-2-generic #5-Ubuntu SMP Mon Nov 28 18:09:32 UTC 2011 i686 i686 i386 GNU/Linux
+$ dpkg -l | grep qemu
+ii  qemu-common                     0.15.0+noroms-0ubuntu6                  qemu common functionality (bios, documentation, etc)
+ii  qemu-kvm                             0.15.0+noroms-0ubuntu6                  Full virtualization on i386 and amd64 hardware
+ii  qemu-utils                             0.15.0+noroms-0ubuntu6                  qemu utilities
+
+My testing is: my amd64 Oneiric kvm laptop boots an i386 12.04 non-kvm guest which boots a minimal install i386 6.06 image. All of this is verified to work when booting an i386 11.10 non-kvm guest (which boots the same 6.06 image).
+
+oh, sorry, i'll try without kvm.
+
+Ok, I see now - other usb devices are there, but not the EHCI or UHCI controller.
+
+there have been quite a few changes upstream to the usb code.  I'm building latest qemu-kvm to test with.
+
+Latest qemu-kvm from upstream has the same problem.
+
+Reproduced with today's qemu git head as well.
+
+Looking through old bug tickets... is this still an issue with the latest version of QEMU, or could we close this ticket nowadays?
+
+
+[Expired for qemu-kvm (Ubuntu) because there has been no activity for 60 days.]
+
+[Expired for qemu-kvm (Ubuntu Precise) because there has been no activity for 60 days.]
+
+[Expired for QEMU because there has been no activity for 60 days.]
+