From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: "Fan, Huaxiang" <hufan@websense.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: RE: Xen enviroment consultation
Date: Tue, 24 May 2011 09:54:53 -0400 [thread overview]
Message-ID: <20110524135453.GC10926@dumpdata.com> (raw)
In-Reply-To: <E71FC5D6F96C3C4B93FC8FF942D924C64026A99E@SSDEXCH1B.websense.com>
On Mon, May 23, 2011 at 08:54:19AM +0000, Fan, Huaxiang wrote:
> Hi Konrad,
> Thanks, the problem solved when I pass in 'iommu=soft' in the PV guests. Could you elaborate on the link between this option and the problem?
You mean why you need 'iommu=soft' when doing PCI passthrough in PV guests? I would
suggest you google for Xen SWIOTLB. I probably wrote the explanation in one of those
links - but I don't remember which one.
>
> And this option also raised another minor issue. For example, I have 4 domus, and the PCI passthru situation as below:
> Domu_name passthru_pci_number_in_dom0
> 1 04:00.0 04:00.1
> 2 02:00.0 02:00.1
> 3 01:00.1
> 4 <none>
>
> I passed in 'iommu=soft' in 1,2,3 domu. The order I should boot the domus is 1,2,3,4. Otherwise, the domu might fail to boot due to the error:
> Pciback 0000:04:00.1: device has been assigned to another domain! Over-writing the ownership, but beware.
Looks like a bug in the pciback code. It somehow things that you had 04:00.1 assigned to another
domain and hadn't cleaned it up probably.
For right I would ignore that - as it is not failing the bootup - just warning you. And are
you using xen-pciback.hide as an option to "hide" the devices from Dom0?
prev parent reply other threads:[~2011-05-24 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E71FC5D6F96C3C4B93FC8FF942D924C63799999B@SSDEXCH1B.websense.com>
2011-05-20 10:54 ` Xen enviroment consultation Fan, Huaxiang
2011-05-20 15:10 ` Konrad Rzeszutek Wilk
2011-05-23 8:54 ` Fan, Huaxiang
2011-05-24 13:54 ` Konrad Rzeszutek Wilk [this message]
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=20110524135453.GC10926@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=hufan@websense.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@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.