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

To:	Czakó Krisztián <slapic@xxxxxxxxxxx>, "Xen Users Mailing List" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject:	RE: [Xen-users] using domu as network backend
From:	"Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date:	Sun, 29 May 2005 22:10:14 +0100
Cc:	ian.pratt@xxxxxxxxxxxx
Delivery-date:	Sun, 29 May 2005 21:09:41 +0000
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-users-request@lists.xensource.com?subject=help>
List-id:	Xen user discussion <xen-users.lists.xensource.com>
List-post:	<mailto:xen-users@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcVi4jdFuY/C850nShKigNwyNNRFxABsE2Qg
Thread-topic:	[Xen-users] using domu as network backend

> 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 dom0)?

That's a problem right now: we need to execute the vif-bridge script in another 
domain. Once we have hotplug or rtnetlink events plumbed through we should be 
able to solve this.

[I think (hope :-) Jeremy might be working on part of this.]

Ian

 

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

WARNING - OLD ARCHIVES

xen-users

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