RE: [Xen-devel] Does physdev_dom0_hide work with the unstable builds?

["Neugebauer, Rolf" <rolf.neugebauer@xxxxxxxxx>]

> -----Original Message-----
> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of malahal@xxxxxxxxxx
> Sent: 14 July 2005 23:39
> To: Ian Pratt
> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Does physdev_dom0_hide work with the unstable
> builds?
> 
> So, how do I use my second Ethernet PCI card directly by a guest OS?
> I am a rookie, would appreciate if someone gives me all the relevant
> instructions.

As Ian said, this is currently broken in -unstable

The reason is that PCI enumeration was moved from Xen into dom0 and dom0
currently doesn't export the PCI config space to other domains. What
needs to happen for -unstable is that dom0 needs to stop device drivers
being started for specified devices and have a frontend/backend
combination to allow other guests to scan "their" portion of the PCI
config space. In 2.x this is done by Xen itself.

In 2.x this should work. you need to hide the PCI device from dom0 and
in the guest OS config file need to specify the PCI ID that domain
should have access to.

rolf

> Thanks, Malahal.
> 
> Ian Pratt [m+Ian.Pratt@xxxxxxxxxxxx] wrote:
> >
> >
> > > I used physdev_dom0_hide='(01:00.0)' but the device still
> > > shows up in the domain0. Is not supposed to work with the
> > > unstable builds?
> >
> > I'm afraid this feature is currently unavailable in unstable -- it
was
> > broken by the ACPI changes. I hope we can get it back before the
final
> > 3.0.0 release, but to my knowledge no-one is currently working on
it.
> >
> > Ian
> >
> > > I am trying to use an Ethernet PCI card directly by a user domain.
> > > What is the easiest way to do that? Thanks in advance.
> > >
> > > Thanks, Malahal.
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > > http://lists.xensource.com/xen-devel
> > >
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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