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: Fw: [Xen-devel] Xen on /. again

On Fri, Jan 21, 2005 at 11:22:20AM +0000, Mark A. Williamson wrote:
> > The only thing right now is that i can't see how to get the backend 
> > interface to be created anywhere other than dom0. I can set up a domain as
> > a network interface backend ok, and i can create a domain with a vif
> > pointing at that domain, but no new vif appears in the network backend dom.
> 
> Are you specifying what backend the frontend should be connected to in the 
> frontend's config file?

Yes

> Are you specifying that the backend is a backend in its config file?

Yes

> > NB2: Again, i don't know if it's still the case, but the network backend
> > driver can't be built without physical device access enabled, but there
> > isn't a dependency for that in the kernel config system.
> 
> Currently backends are built iff physical device access is enabled, since the 
> assumption is that they will run in a privileged domain and virtualise a real 
> device.

What i was meaning, was that the network backend can be chosen in the config
without physical device access enabled, but the kernel won't then build.


J

-- 
Jody Belka
knew (at) pimb (dot) org


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel