1 files changed, 96 insertions, 0 deletions
diff --git a/results/classifier/118/none/1333216 b/results/classifier/118/none/1333216
new file mode 100644
index 000000000..def690838
--- /dev/null
+++ b/results/classifier/118/none/1333216
@@ -0,0 +1,96 @@
+virtual: 0.786
+device: 0.766
+hypervisor: 0.674
+semantic: 0.658
+architecture: 0.626
+peripherals: 0.569
+graphic: 0.559
+mistranslation: 0.526
+socket: 0.466
+performance: 0.454
+vnc: 0.441
+x86: 0.433
+PID: 0.432
+ppc: 0.415
+arm: 0.398
+user-level: 0.365
+risc-v: 0.356
+VMM: 0.314
+register: 0.313
+debug: 0.291
+KVM: 0.289
+permissions: 0.282
+kernel: 0.280
+network: 0.258
+TCG: 0.211
+files: 0.211
+boot: 0.205
+assembly: 0.187
+i386: 0.131
+
+Xen 4.4 with qemu 1.6.2 VGA passthru NVIDIA
+
+Hi!
+
+Please, give me an advice.
+
+I try use VGA passthough NVidia k40 on SuperMicro Server, but server is having error.
+My Xen is using qemu (a9e8aeb3755bccb7b51174adcf4a3fc427e0d147)2.0.0
+
+My VirtualMachine is have config:
+device_model_version = "qemu-xen"
+device_model_override = "/opt/sources/qemu-a9e8aeb/x86_64-softmmu/qemu-system-x86_64"
+
+When I start VM:
+dmesg
+[    0.906181] pci 0000:00:05.0: BAR 1: can't assign mem pref (size 0x100000000)
+[    0.906187] pci 0000:00:05.0: BAR 1: trying firmware assignment [mem 0x100000000-0x1ffffffff 64bit pref]
+[    0.906193] pci 0000:00:05.0: BAR 1: assigned [mem 0x100000000-0x1ffffffff 64bit pref]
+and lspci -s 00:05.0 -vvv
+        Region 0: Memory at 85000000 (32-bit, non-prefetchable) [size=16M]
+        Region 1: Memory at 100000000 (64-bit, prefetchable) [size=4G]
+        Region 3: Memory at 82000000 (64-bit, prefetchable) [size=32M]
+
+Why?
+
+This is message in DOM0:
+lspci -s 03:00.0 -vvv
+....
+Region 0: Memory at de000000 (32-bit, non-prefetchable) [size=16M]
+Region 1: Memory at 5800000000 (64-bit, prefetchable) [size=16G]
+Region 3: Memory at 5c00000000 (64-bit, prefetchable) [size=32M]
+
+
+Why Qemu don`t mapping BAR1?
+Thanks!
+Regards!
+
+
+
+Can you still reproduce this problem with the latest version of QEMU? If so, have you already tried to report it to the folks from the Xen project?
+
+Hi!
+
+Sorry, I solved this problem. I used another project(qemu-kvm). I don't have a hardware for this.
+
+:(
+
+Thomas Huth @ 2017-07-19 11:27 GMT:
+
+> Can you still reproduce this problem with the latest version of QEMU? If
+> so, have you already tried to report it to the folks from the Xen
+> project?
+>
+> ** Changed in: qemu
+>        Status: New => Incomplete
+
+
+--
+С уважением,
+
+Гордеев Максим Николаевич!
++7 (495) 777-13-10, доб.510
+
+
+Thanks for the answer! So I'm closing this bug ticket now...
+