[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] using domu as network backend

  • To: Xen Users Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: Czakó Krisztián <slapic@xxxxxxxxxxx>
  • Date: Fri, 27 May 2005 19:32:46 +0200
  • Delivery-date: Fri, 27 May 2005 17:32:26 +0000
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

2005-05-20, p keltezéssel 09.10-kor Mark Williamson ezt írta:
> > The first steps are ok. I hide the network devices from dom0, give domu
> > access to the pci devices, and use a kernel with hw access and network
> > backend compiled in.
> > I can start a domu that can use a network card, but how can I configure
> > an other domu to use this domain as network backend instead of dom0?
> You need to set some config file options.
> For the backend domain, set "netif=1" to tell Xend it's an authorised backend.
> In the frontend, for each VIF you declare you need to add a "backend=dom" in 
> the config list item for each vif, to connect that vif to the backend.  
> Writing "dom" as a domain number will certainly work, I'm not sure if a 
> textual domain name will work.

Thanx. Textual name works fine, the vif interface is created in the
right netif backend domain.
However, the vif interface isn't added to the specified bridge. If I add
it to the bridge by hand it works. How can I make it automatic (like in


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.