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

[Xen-devel] HVM vif without bridge

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] HVM vif without bridge
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Thu, 27 Dec 2007 14:26:13 +0100
Delivery-date: Thu, 27 Dec 2007 05:27:26 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Hello,

When using xen without a bridge but NAT or routing, HVM domains can't
boot, and qemu-dm-n.log contains:

config qemu network with xen bridge for  tap0 xenbr0
bridge xenbr0 does not exist!

That's because the qemu-ifup script always tries to add the vif to
a default-named xenbr0 bridge. On the contrary, PV domains just work
fine with the same configuration file except HVM parameters.

I can see several solutions:

- The attached "patch" just ignores brctl failure. Far from elegant, but
  works fine
- The attached "patch2" drops the default xenbr0 bridge, and then people
  have to set bridge=xenbr0 in their configuration file.
- move qemu-ifup into three bridge, nat and route scripts, and add
  another xend-config parameter, along network-script and vif-script,
  which should point to either of those according to the values of
  network-script and vif-script.

It looks to me like the first solution could be used as a workaround for
now and the last one would be preferable for the long run.

Samuel

Signed-off-by: Samuel Thibault <samuel.thibault@xxxxxxxxxx>

Attachment: patch
Description: Text document

Attachment: patch2
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] HVM vif without bridge, Samuel Thibault <=