From: James Neave <roboj1m@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2
Date: Tue, 8 Feb 2011 09:13:21 +0000 [thread overview]
Message-ID: <AANLkTinE0SEa5bELXTFHtz65u-_9Gyp-xg90VvmG2q8A@mail.gmail.com> (raw)
In-Reply-To: <20110207132641.GD2665@redhat.com>
On Mon, Feb 7, 2011 at 1:26 PM, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Sat, Feb 05, 2011 at 04:34:01PM +0000, James Neave wrote:
>> Hi,
>>
>> I'm trying to pass a NOVA-T-500 TV Tuner card through to a gust VM.
>> I'm getting the error "The driver 'pci-stub' is occupying your device
>> 0000:08:06.2"
>
> This is a rather misleading error message. It is *expected* that
> pci-stub will occupy the device. Unfortunately the rest of the
> error messages QEMU is printing aren't much help either, but
> ultimately something is returning -EBUSY in the PCI device assign
> step
>
> Regards,
> Daniel
That's what I figured, but sadly I'm just a "user". Paucity of google
results suggests that this problem is new and unknown/unfixed.
I had a quick stab at this with Xen last night, but it seems Ubuntu
and Xen are no longer friends.
The only thing left I can think to try is to check out the latest code
and try that.
Is it "normal" with qemu-kvm? Do I just get the code with git, faf
around with dependencies and then ./configure, make and make install?
Regards,
James.
next prev parent reply other threads:[~2011-02-08 9:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-05 16:34 PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2 James Neave
2011-02-07 13:26 ` Daniel P. Berrange
2011-02-08 9:13 ` James Neave [this message]
2011-02-08 9:59 ` Kenni Lund
2011-02-08 10:17 ` James Neave
2011-02-12 16:04 ` James Neave
2011-02-14 17:48 ` Alex Williamson
2011-02-21 20:31 ` James Neave
2011-02-21 21:01 ` Alex Williamson
2011-02-21 22:25 ` James Neave
2011-02-21 22:49 ` James Neave
2011-02-21 22:55 ` James Neave
2011-02-21 23:05 ` James Neave
2011-02-22 1:51 ` Chris Wright
2011-02-22 9:18 ` James Neave
2011-02-22 9:53 ` Roedel, Joerg
2011-02-22 10:11 ` James Neave
2011-02-23 0:11 ` Chris Wright
2011-02-23 19:44 ` James Neave
2011-02-23 20:09 ` James Neave
2011-02-24 9:26 ` James Neave
2011-02-25 0:13 ` Chris Wright
2011-02-25 0:06 ` Chris Wright
2011-02-25 22:47 ` James Neave
2011-02-25 23:02 ` James Neave
2011-02-25 23:09 ` James Neave
2011-02-25 23:31 ` Chris Wright
2011-02-28 13:42 ` James Neave
2011-02-28 15:31 ` Chris Wright
2011-02-28 20:25 ` James Neave
2011-03-01 20:54 ` James Neave
[not found] ` <BANLkTi=ZHpHU=Gd+tTcLysTD3duGY8PPjQ@mail.gmail.com>
2011-05-10 16:00 ` James Neave
2011-02-25 23:14 ` Chris Wright
2011-02-24 23:59 ` Chris Wright
2011-02-21 23:28 ` Chris Wright
2011-02-21 23:50 ` James Neave
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=AANLkTinE0SEa5bELXTFHtz65u-_9Gyp-xg90VvmG2q8A@mail.gmail.com \
--to=roboj1m@gmail.com \
--cc=berrange@redhat.com \
--cc=kvm@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.