From: James Neave <roboj1m@gmail.com>
To: kvm@vger.kernel.org
Subject: Re: PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2
Date: Tue, 10 May 2011 17:00:00 +0100 [thread overview]
Message-ID: <BANLkTiki3dHAivQp5e9QKs6GZYB-NdndKA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=ZHpHU=Gd+tTcLysTD3duGY8PPjQ@mail.gmail.com>
On Mon, Feb 28, 2011 at 3:31 PM, Chris Wright <chrisw@sous-sol.org> wrote:
>
> * James Neave (roboj1m@gmail.com) wrote:
> > HOLY CRAP IT WORKS!!!! 8@
>
>
> Hey, great! ;)
>
> > ...almost...
> >
> > OK, "clear_emulator_capabilities=0" solved the IRQ problem (which was,
> > as it turns out, the rawio problem)
> > My VM came up, both the tuners were there and after the firmware
> > install I was able to tune and watch the slowest TV in the world over
> > VNC.
> >
> > Thank god for that, i was really starting to believe that slashing out
> > a lot of cash on my 890FX board and the fancy DDR3 ram it needed was a
> > collosal waste of money.
> > "Sigh of relief"
> >
> > Well, thank you all so much for helping me to get to this point!
> >
> > And yes, I did say "almost works"
> >
> > Looks like I've run straight into Chris' ref counting problem when
> > shutting the guest down.
> > Some sort of critical error barf was on the servers' screen when I
> > shut down the guest, appeared to be very similar to Chris' example, in
> > amd_iommu.c
> >
> > I'd post it but the server locks up after it's been shown and needed
> > resetting. No idea how I would post that bit of dmesg as it gets reset
> > after each boot.
> >
> > Is there a solution for this at the moment or will I have to wait for
> > it to be patched?
>
> No solution at the moment. Will keep you posted.
>
> thanks,
> -chris
Hello all,
Just wondering if there has been any movement on this problem of
detaching PCI devices behind PCI-PCI bridges?
(Resent as I forgot to switch to plain text)
Regards,
James.
next prev parent reply other threads:[~2011-05-10 16:00 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
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 [this message]
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=BANLkTiki3dHAivQp5e9QKs6GZYB-NdndKA@mail.gmail.com \
--to=roboj1m@gmail.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 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).