summary refs log tree commit diff stats
path: root/results/classifier/118/all/1708551
diff options
context:
space:
mode:
Diffstat (limited to 'results/classifier/118/all/1708551')
-rw-r--r--results/classifier/118/all/1708551172
1 files changed, 172 insertions, 0 deletions
diff --git a/results/classifier/118/all/1708551 b/results/classifier/118/all/1708551
new file mode 100644
index 00000000..22e00352
--- /dev/null
+++ b/results/classifier/118/all/1708551
@@ -0,0 +1,172 @@
+PID: 0.955
+architecture: 0.945
+permissions: 0.940
+graphic: 0.940
+arm: 0.939
+socket: 0.934
+user-level: 0.934
+boot: 0.934
+register: 0.929
+device: 0.929
+performance: 0.928
+assembly: 0.924
+network: 0.923
+virtual: 0.923
+semantic: 0.918
+files: 0.917
+debug: 0.916
+risc-v: 0.914
+peripherals: 0.910
+vnc: 0.899
+hypervisor: 0.898
+KVM: 0.896
+ppc: 0.887
+kernel: 0.875
+x86: 0.868
+TCG: 0.853
+mistranslation: 0.846
+VMM: 0.838
+i386: 0.718
+
+macOS Guest Reading USB 3.0 Bus as USB 2.0
+
+Description:
+I'm having trouble with USB Passthrough. Running `system_profiler SPUSBDataType` on macOS guest confirms that the system "sees" my device, and that qemu is passing *something* through. However, the system sees my connection as USB 2.0, even though i'm passing through XHCI controllers (nec-usb-xhci/qemu-xhci). I suspect this is the reason why my guest is unable to recognize my iPhone in XCode & iTunes.
+
+Parameters:
+QEMU release version: 2.10.0-rc0
+Bios: [patched version of OVMF](https://github.com/gsomlo/edk2/tree/macboot)]
+Command Line: https://pastebin.com/pBSYbrW1
+Host: Arch Linux
+Guest: macOS v10.12.6
+Guest System Info: https://pastebin.com/U1Tihxei
+
+Notes:
+1. Observed sometime after late-May-early-June of this year.
+
+2. Due to [a defect in qemu v2.8 which affected GTK users](https://bugs.launchpad.net/qemu/+bug/1578192), and [a recent change to macOS' booting process conflicting with qemu v2.9](https://lists.nongnu.org/archive/html/qemu-devel/2017-03/msg06366.html), i'm forced to use qemu v2.10.0-rc0 (as -rc1 fails to load OVMF right now).
+
+Could you please try to run QEMU without the "-usb" option here? "-usb" automatically creates an EHCI and UHCI controller on the q35 machine, so that might be the reason that your USB devices get connected as USB 2.0 instead.
+
+Doing so returns:
+`qemu-system-x86_64: -device usb-tablet,bus=usb-bus.0: Bus 'usb-bus.0' not found`
+
+> On Aug 4, 2017, at 2:31 AM, Thomas Huth <email address hidden> wrote:
+> 
+> Could you please try to run QEMU without the "-usb" option here? "-usb"
+> automatically creates an EHCI and UHCI controller on the q35 machine, so
+> that might be the reason that your USB devices get connected as USB 2.0
+> instead.
+> 
+> ** Changed in: qemu
+>       Status: New => Incomplete
+> 
+> -- 
+> You received this bug notification because you are subscribed to the bug
+> report.
+> https://bugs.launchpad.net/bugs/1708551
+> 
+> Title:
+>  macOS Guest Reading USB 3.0 Bus as USB 2.0
+> 
+> Status in QEMU:
+>  Incomplete
+> 
+> Bug description:
+>  Description:
+>  I'm having trouble with USB Passthrough. Running `system_profiler SPUSBDataType` on macOS guest confirms that the system "sees" my device, and that qemu is passing *something* through. However, the system sees my connection as USB 2.0, even though i'm passing through XHCI controllers (nec-usb-xhci/qemu-xhci). I suspect this is the reason why my guest is unable to recognize my iPhone in XCode & iTunes.
+> 
+>  Parameters:
+>  QEMU release version: 2.10.0-rc0
+>  Bios: [patched version of OVMF](https://github.com/gsomlo/edk2/tree/macboot)]
+>  Command Line: https://pastebin.com/pBSYbrW1
+>  Host: Arch Linux
+>  Guest: macOS v10.12.6
+>  Guest System Info: https://pastebin.com/U1Tihxei
+> 
+>  Notes:
+>  1. Observed sometime after late-May-early-June of this year.
+> 
+>  2. Due to [a defect in qemu v2.8 which affected GTK
+>  users](https://bugs.launchpad.net/qemu/+bug/1578192), and [a recent
+>  change to macOS' booting process conflicting with qemu
+>  v2.9](https://lists.nongnu.org/archive/html/qemu-
+>  devel/2017-03/msg06366.html), i'm forced to use qemu v2.10.0-rc0 (as
+>  -rc1 fails to load OVMF right now).
+> 
+> To manage notifications about this bug go to:
+> https://bugs.launchpad.net/qemu/+bug/1708551/+subscriptions
+
+
+Then simply omit the "bus=usb-bus.0" here - the devices then should be put onto the XHCI bus automatically.
+
+Removing the `bus=usb-bus.0` param from everything, [as shown here](https://pastebin.com/x0Cp70XD), boots fine; but completely breaks mouse functionality. To mitigate, i tried passing through a Logitech mousepad I own--in similar fashion to the iPhone; but Host complained about permissions & `libusb` requiring "write access to USB device nodes".
+
+FWIW, I vaguely recall the `usb-tablet` parameter being "a whole thing" with virtual macOS; however, I'll need to check my records to refresh my memory.
+
+
+> On Aug 4, 2017, at 11:29 AM, Thomas Huth <email address hidden> wrote:
+> 
+> Then simply omit the "bus=usb-bus.0" here - the devices then should be
+> put onto the XHCI bus automatically.
+> 
+> -- 
+> You received this bug notification because you are subscribed to the bug
+> report.
+> https://bugs.launchpad.net/bugs/1708551
+> 
+> Title:
+>  macOS Guest Reading USB 3.0 Bus as USB 2.0
+> 
+> Status in QEMU:
+>  Incomplete
+> 
+> Bug description:
+>  Description:
+>  I'm having trouble with USB Passthrough. Running `system_profiler SPUSBDataType` on macOS guest confirms that the system "sees" my device, and that qemu is passing *something* through. However, the system sees my connection as USB 2.0, even though i'm passing through XHCI controllers (nec-usb-xhci/qemu-xhci). I suspect this is the reason why my guest is unable to recognize my iPhone in XCode & iTunes.
+> 
+>  Parameters:
+>  QEMU release version: 2.10.0-rc0
+>  Bios: [patched version of OVMF](https://github.com/gsomlo/edk2/tree/macboot)]
+>  Command Line: https://pastebin.com/pBSYbrW1
+>  Host: Arch Linux
+>  Guest: macOS v10.12.6
+>  Guest System Info: https://pastebin.com/U1Tihxei
+> 
+>  Notes:
+>  1. Observed sometime after late-May-early-June of this year.
+> 
+>  2. Due to [a defect in qemu v2.8 which affected GTK
+>  users](https://bugs.launchpad.net/qemu/+bug/1578192), and [a recent
+>  change to macOS' booting process conflicting with qemu
+>  v2.9](https://lists.nongnu.org/archive/html/qemu-
+>  devel/2017-03/msg06366.html), i'm forced to use qemu v2.10.0-rc0 (as
+>  -rc1 fails to load OVMF right now).
+> 
+> To manage notifications about this bug go to:
+> https://bugs.launchpad.net/qemu/+bug/1708551/+subscriptions
+
+
+Ok, could you maybe try something like this instead:
+
+ qemu-system-x86_64 ... -usb \
+    -device qemu-xhci,id=xhci \
+    -device usb-tablet,bus=usb-bus.0 \
+    -device usb-kbd,bus=usb-bus.0 \
+    -device usb-host,bus=xhci.0,vendorid=0x05ac,productid=0x12a8
+
+i.e. use "bus=xhci.0" for the usb-host device?
+
+In doing so, the device is now unseen by the system.
+
+
+xhci doesn't work with macos because macos has a white list of supported xhci controllers and ignores the xhci adapters emulated by qemu.
+
+
+This is an automated cleanup. This bug report has been moved to QEMU's
+new bug tracker on gitlab.com and thus gets marked as 'expired' now.
+Please continue with the discussion here:
+
+ https://gitlab.com/qemu-project/qemu/-/issues/146
+
+