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/
Home Products Support Community News


[Xen-bugs] [Bug 984] New: vif order


           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-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: Tobias.Lindinger@xxxxxx

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

Best Regards,

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>