qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Howard Spoelstra <hsp.cat7@gmail.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: 1850570@bugs.launchpad.net, qemu Developers <qemu-devel@nongnu.org>
Subject: Re: [Bug 1850570] Re: Cannot use usb-host on Mac OS
Date: Fri, 1 Nov 2019 13:18:07 +0100	[thread overview]
Message-ID: <CABLmASGTRF3OJRh0QvmND8Nr=2OiUQnQcJK+ru1PUc2oW0A_Mw@mail.gmail.com> (raw)
In-Reply-To: <47A92732-E94E-4DD9-8D47-E8DCF4E364B1@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4622 bytes --]

On Fri, Nov 1, 2019 at 11:35 AM Programmingkid <programmingkidx@gmail.com>
wrote:

>
> > On Oct 31, 2019, at 7:35 PM, qemu-devel-request@nongnu.org wrote:
> >
> > Message: 10
> > Date: Thu, 31 Oct 2019 18:39:11 -0000
> > From: John Canada <1850570@bugs.launchpad.net>
> > To: qemu-devel@nongnu.org
> > Subject: [Bug 1850570] Re: Cannot use usb-host on Mac OS
> > Message-ID:
> >       <157254715118.3076.2379100780378521691.malone@gac.canonical.com>
> > Content-Type: text/plain; charset="utf-8"
> >
> > Yes, I tried running as root.  I also tried it on a different computer
> > that is running Mac OS 10.13, and it gave the same errors.
> >
> > --
> > You received this bug notification because you are a member of qemu-
> > devel-ml, which is subscribed to QEMU.
> > https://bugs.launchpad.net/bugs/1850570
> >
> > Title:
> >  Cannot use usb-host on Mac OS
> >
> > Status in QEMU:
> >  New
> >
> > Bug description:
> >  Usb-host will not work on Mac OS 10.15.  Qemu runs, though it gives
> >  these errors and the drive does not show up.  Also, when Qemu is
> >  starting the drive ejects and remounts twice. Qemu built with
> >  ./configure --target-list=i386-softmmu,x86_64-softmmu --enable-sdl
> >  --disable-cocoa --enable-sdl-image.
> >
> >  qemu-system-i386 image.qcow -usb -device usb-kbd  -device
> usb-host,vendorid=0x0781,productid=0x5571
> >  libusb: error [darwin_claim_interface] USBInterfaceOpen: another
> process has device opened for exclusive access
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] USBInterfaceOpen: another
> process has device opened for exclusive access
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >  libusb: error [darwin_claim_interface] interface not found
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/qemu/+bug/1850570/+subscriptions
>
>
> Try this. Unplug the USB device. Plug it back in, and as fast as you can
> start QEMU.
>
> My theory is another program might be using the device. This could be
> Spotlight trying to index the drive.
>
> Another possibility is libusb is not compatible with Mac OS 10.13 yet.
>
> Do you have another computer that runs Mac OS 10.12 or under that you can
> test on?
>
>
I guess the longstanding issue with libusb and OSX is that some kext has
already claimed the device. A solution would be to unload the kext
currently claiming the device before starting Qemu. If possible.
Also see here:
https://apple.stackexchange.com/questions/363491/how-to-disable-usb-mass-storage-in-mojave-to-free-up-device-for-libusb
and the links from that page:
https://github.com/libusb/libusb/wiki/FAQ#How_can_I_run_libusb_applications_under_Mac_OS_X_if_there_is_already_a_kernel_extension_installed_for_the_device
https://stackoverflow.com/questions/33545656/codeless-kext-for-usb-storage-device

Best,
Howard

[-- Attachment #2: Type: text/html, Size: 6467 bytes --]

  parent reply	other threads:[~2019-11-01 12:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.214.1572564951.13345.qemu-devel@nongnu.org>
2019-11-01 10:34 ` [Bug 1850570] Re: Cannot use usb-host on Mac OS Programmingkid
2019-11-01 10:34   ` John Arbuckle
2019-11-01 12:18   ` Howard Spoelstra [this message]
     [not found] <mailman.89.1572425520.22191.qemu-devel@nongnu.org>
2019-10-31 16:01 ` [Bug 1850570] [NEW] " G 3
2019-10-31 16:01   ` John Arbuckle
2019-10-30  1:46 John Canada
2019-10-31 18:39 ` [Bug 1850570] " John Canada
2021-04-04 18:20 ` John Arbuckle
2021-04-04 20:27   ` Howard Spoelstra
2021-04-04 20:27     ` Howard Spoelstra
2021-05-05 14:29 ` Thomas Huth

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CABLmASGTRF3OJRh0QvmND8Nr=2OiUQnQcJK+ru1PUc2oW0A_Mw@mail.gmail.com' \
    --to=hsp.cat7@gmail.com \
    --cc=1850570@bugs.launchpad.net \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).