WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

I assumed you meant Xen0 in domU. That worked. Thanks for the help. :)

Can this tidbit be added to the user docs? I'm sure it would be useful
to others.

On Fri, 2005-07-15 at 01:28 +0100, Mark Williamson wrote:
> > The physdev_dom0_hide seems to work ok for me on 2.0.6, but I still
> > haven't gotten a domU kernel to boot with physical access compiled in
> > yet. Let me know if you figure it out.
> 
> Try using a Xen0 kernel in the dom0 - that should get you started.  There are 
> no security implications of this.  The only difference is that xen0 kernel 
> has more stuff compiled in, so it's bigger.
> 
> Cheers,
> Mark
> 
> > Thanks,
> > Kevin
> >
> > On Thu, 2005-07-14 at 15:38 -0700, malahal@xxxxxxxxxx wrote:
> > > 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.
> > >
> > > 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

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