From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Cinco, Dante" <Dante.Cinco@lsi.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified
Date: Tue, 13 Oct 2009 13:01:18 -0400 [thread overview]
Message-ID: <20091013170118.GA21615@phenom.dumpdata.com> (raw)
In-Reply-To: <20091013142038.GA19950@phenom.dumpdata.com>
On Tue, Oct 13, 2009 at 10:20:38AM -0400, Konrad Rzeszutek Wilk wrote:
> On Mon, Oct 12, 2009 at 06:48:11PM -0600, Cinco, Dante wrote:
> > I followed the procedure for "binding devices to pci-stub" but when I ran "xm pci-list-assignable-devices," no device showed up. I can see the device though in /sys/bus/pci/drivers/pci-stub/ and "lspci -v -s 0:07:0.1" reports the driver in use as pci-stub. When I tried to bringup the domU (Linux 2.6.30.1), I get an error message:
>
> What is the Dom0 you are using? There is no support yet in 2.6.30.1 for the pciback (I am working on this
> right now, testing it to be exact).
>
> Nor is there a pci-front in the 2.6.31.1.
>
> Why use pci-stub? It just hides devices, but does not do anything else?
Ahh, n/m. QEMU uses those devices to do the PCI emulation along with
pass-through for the devices. Obviously it only works for HVM guests.
next prev parent reply other threads:[~2009-10-13 17:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 0:48 Problem with pv-ops dom0 and pci-stub to hide devices: improper device assignment specified Cinco, Dante
2009-10-13 2:50 ` Han, Weidong
2009-10-13 5:44 ` Bruce Edge
2009-10-13 6:21 ` Han, Weidong
2009-10-13 17:15 ` Cinco, Dante
2009-10-13 14:20 ` Konrad Rzeszutek Wilk
2009-10-13 16:12 ` Bruce Edge
2009-10-13 16:36 ` Keir Fraser
2009-10-13 17:07 ` Konrad Rzeszutek Wilk
2009-10-13 17:01 ` Konrad Rzeszutek Wilk [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-10-13 22:56 Cinco, Dante
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=20091013170118.GA21615@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Dante.Cinco@lsi.com \
--cc=xen-devel@lists.xensource.com \
/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.