Re: [Xen-devel] 3rd party drivers in domU or dom0

[mdlabriola@xxxxxxxxx]

I booted the hypervizor with dom0_vcpu_pin set, dom0's kernel with nosmp set, 
then pinned my domUs to the second core.  It worked!  I'm now sending my 50Hz 
data well within my spec, even with two other domUs working away.  :-)

Now, I still would rather pass my PCI cards into a domU, but I'm pretty happy 
to be working at all.

I remember noticing an option to select one of 3 available PCI passthrough 
methods for pciback when I configured my kernel...  What's the difference 
between the three?

-Mike

------Original Message------
From: Keir Fraser
To: Michael Labriola
To: xen-devel
Subject: Re: [Xen-devel] 3rd party drivers in domU or dom0
Sent: Apr 15, 2009 08:01

On 15/04/2009 12:56, "mdlabriola@xxxxxxxxx" <mdlabriola@xxxxxxxxx> wrote:

> I tried to hide the PCI cards from dom0, to see what the behavior is like in a
> domU, but I can't get that to work either.  The pciback new_slot/bind stuff
> appears to work (I don't get errors), but when I try to create my domU, I get
> errors listing other devices that must also be sent to domU (looks like
> everything on that PCI bus)
> 
> Do you guys think there's a better chance of getting these boards working on
> domU or dom0?

Doesn't matter which as Xen schedules them the same. The safest way would be
to run a uniproc dom0 or domU, and dedicate a cpu to it (by setting affinity
masks of all domains).

 -- Keir





---
Michael D Labriola
21 Rip Van Winkle Cir
Warwick, RI 02886
401-316-9844

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel