summary refs log tree commit diff stats
path: root/results/classifier/108/other/1196
diff options
context:
space:
mode:
Diffstat (limited to '')
-rw-r--r--results/classifier/108/other/119627
-rw-r--r--results/classifier/108/other/119614540
-rw-r--r--results/classifier/108/other/119649844
-rw-r--r--results/classifier/108/other/119677329
4 files changed, 140 insertions, 0 deletions
diff --git a/results/classifier/108/other/1196 b/results/classifier/108/other/1196
new file mode 100644
index 00000000..fc338075
--- /dev/null
+++ b/results/classifier/108/other/1196
@@ -0,0 +1,27 @@
+device: 0.882
+graphic: 0.870
+vnc: 0.763
+network: 0.676
+PID: 0.675
+performance: 0.559
+boot: 0.444
+semantic: 0.416
+socket: 0.384
+debug: 0.332
+KVM: 0.297
+files: 0.271
+permissions: 0.250
+other: 0.033
+
+Guest could not enable pci AtomicOp requests for passthrough device
+Description of problem:
+Guest could not enable pci AtomicOp requests for passthrough device. 
+
+sudo setpci -v -d *:706t 8c.b=40 // enable pci AtomicOp requests bit in the guest os.
+
+Host could not see the bit by command "sudo lspci -vvv -s 03:00.0".
+Steps to reproduce:
+1. sudo setpci -v -d *:706t 8c.b=40 // in the guest os
+2. sudo lspci -vvv -s 03:00.0 // in the host os
+Additional information:
+
diff --git a/results/classifier/108/other/1196145 b/results/classifier/108/other/1196145
new file mode 100644
index 00000000..696e17b5
--- /dev/null
+++ b/results/classifier/108/other/1196145
@@ -0,0 +1,40 @@
+semantic: 0.898
+other: 0.845
+device: 0.804
+graphic: 0.786
+network: 0.662
+socket: 0.631
+debug: 0.627
+performance: 0.587
+PID: 0.581
+permissions: 0.574
+vnc: 0.550
+files: 0.490
+boot: 0.454
+KVM: 0.330
+
+usb-host: hostaddr=0XX is parsed as octal number
+
+when doing
+
+device_add usb-host,hostaddr=010
+
+taking 010 in the format of both lsusb or udev, qemu parses an octal number and assumes hostaddr=8.
+(i used a 2.0 device on the ehci.0 bus)
+at least to me that is confusing.
+
+also:
+
+when adding a non-existent usb device (bogus hostaddr), the following is created according to 'usb info':
+
+  Device 1.0, Port 1, Speed 1.5 Mb/s, Product USB Host Device
+
+in usb_qdev_init():
+usb_claim_port is called but usb_device_init does not report an error and thus usb_release_port is not called.
+
+ps: when using host-libusb.c and tested on 1.5.1.tgz
+
+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 because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1196498 b/results/classifier/108/other/1196498
new file mode 100644
index 00000000..0fd0a5f6
--- /dev/null
+++ b/results/classifier/108/other/1196498
@@ -0,0 +1,44 @@
+debug: 0.867
+boot: 0.837
+KVM: 0.820
+semantic: 0.806
+device: 0.801
+graphic: 0.790
+files: 0.774
+network: 0.748
+performance: 0.743
+other: 0.661
+socket: 0.593
+permissions: 0.585
+PID: 0.554
+vnc: 0.540
+
+Failed to create COM port in Windows Guest VM
+
+Hi,
+
+Tried to establish virtual serial connection between two Windows Guest VMs(Windows 2008 Server).
+
+As it mentioned under the link,
+http://www.linux-kvm.org/page/WindowsGuestDrivers/UpdatedGuestDebugging
+
+Started VM using the below command with serial device as TCP port.
+# qemu-system-x86_64 -smp 1 -enable-kvm -m 512 -boot c -serial tcp:127.0.0.1:50001,server,nowait -hda /mnt/sda5/var/lib/libvirt/images/win2008host.img
+
+And started WinDbg in the Windows VM, with serial port:COM1 and Baudrate:115200.
+
+It throws the error "Could not start kernel debugging using com:port:COM1,baudrate:115200 parameters, Win32 error 0n2. The system cannot find the file specified."
+
+Checked under Device Manager and there is no COM1 port.
+Does the -serial tcp:127.0.0.01:50001 creates COM1 port? I doubt.
+If no what are the parameters I should pass to WinDbg for serial port?
+
+Please help me how to solve this issue.
+
+Thanks
+Venkatesh
+
+Triaging old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
+
+[Expired for QEMU because there has been no activity for 60 days.]
+
diff --git a/results/classifier/108/other/1196773 b/results/classifier/108/other/1196773
new file mode 100644
index 00000000..68bab1ed
--- /dev/null
+++ b/results/classifier/108/other/1196773
@@ -0,0 +1,29 @@
+graphic: 0.807
+boot: 0.490
+network: 0.436
+performance: 0.425
+vnc: 0.366
+semantic: 0.332
+device: 0.271
+debug: 0.231
+socket: 0.224
+PID: 0.210
+other: 0.186
+permissions: 0.124
+files: 0.031
+KVM: 0.018
+
+pci_add auto nic failed on qemu monitor
+
+hello!
+execute "qemu-system-x86_64 -M pc -m 256 -hda pc/img.qcow2 -nographic -net nic,vlan=0,macaddr=00:e0:fc:00:00:01 -net tap,vlan=0,ifname=tap0,script=no -serial tcp::3333,server,nowait -boot c"
+and then
+(qemu) pci_add auto nic vlan=1,macaddr=00:e0:fc:40:20:02
+Property 'e1000.netdev' can't take value 'hub0port0', it's in use
+
+the qemu version is 1.4.1
+
+thx!
+
+The pci_add command has been remove since QEMU 2.3.0 ... so I'm closing this bug now - sorry that nobody picked this up in 2013! If you still can reproduce this problem with device_add, please feel free to open this ticket again.
+