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-users

[Xen-users] Create VM with missing bridge

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Create VM with missing bridge
From: Roy <onion@xxxxxxxxxx>
Date: Thu, 14 May 2009 22:39:39 -0700
Cc:
Delivery-date: Thu, 14 May 2009 22:40:24 -0700
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.21 (Windows/20090302)
I have been using CentOS with the bundled XEN (3.0) for some time.  I
just switched a test box to Xen 3.3.1.

I tried to start a VM that wanted an ethernet interface on xenbr0.  It
started running.  eth0 existed on the VM but was didn't go anywhere. 
The glitch was that bridge xenbr0 is now bridge eth0.

The issue is that the VM started without xenbr0.  If I did that under
the older version of xen, the "xm create" would have failed with an
error that xenbr0 couldn't be found.

Is this an expected behavior to ignore the error that xenbr0 doesn't
exist and start the VM anyway?



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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Create VM with missing bridge, Roy <=