3 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 984] New: vif order
FromSent OnAttachments
bugz...@lists.xensource.com24 May 2007 01:47 
bugz...@lists.xensource.com24 May 2007 01:52 
bugz...@lists.xensource.com24 May 2007 01:56 
Subject:[Xen-bugs] [Bug 984] New: vif order
From:bugz...@lists.xensource.com (bugz@lists.xensource.com)
Date:05/24/2007 01:47:47 AM
List:com.xensource.lists.xen-bugs

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=984

Summary: vif order Product: Xen Version: 3.0.4 Platform: x86-64 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Hypervisor AssignedTo: xen-@lists.xensource.com ReportedBy: Tobi@web.de

I have a problem regarding to the order of the creation of virtual network cards in my dom0. My domUs have between two and three (virtual) network cards. In former versions of Xen that I was using the first nic entry in the domU configuration script became eth0 in the domU and was linked to vifX.0 in the dom0. The second entry became eth1, linked to vifX.1 and so on. Now I am using Xen 3.0.4_1 (built from source) on a SLES 10.1 host and the order of the nic entrys in the dumU configuration script seems to be not relevant at all. The vif devices are created in a randoom order, which is quite bad for automatic firewall rule generation and other automatisation stuff. So the first nic entry becomes vifX.2 and is shown as eth2 in the domU one time and as vifX.1/eth1 another time. How can I switch back to the old deterministic order?

Best Regards, Tobias