[Users] net device initialization order

Antoni Segura Puimedon asegurap at redhat.com
Tue Jan 8 09:25:31 UTC 2013


Which OS is the guest running? Cause I reported a bug where the systemd
based initialization systems, due to a bug/design of biosdevname get their
order eth0-n randomized on each boot.

----- Original Message -----
> From: "Jonathan Horne" <jhorne at skopos.us>
> To: "Jonathan Horne" <jhorne at skopos.us>, "users" <users at ovirt.org>
> Sent: Monday, January 7, 2013 10:37:42 PM
> Subject: Re: [Users] net device initialization order
> 
> 
> 
> 
> 
> actually what i am finding is, its not consistent what order it adds
> nic1 and nic2 to the guest when its created. sometimes nic1 is eth0,
> sometimes nic2 is eth0.
> 
> 
> 
> 
> From: Jonathan Horne < jhorne at skopos.us >
> Date: Monday, January 7, 2013 3:02 PM
> To: users < users at ovirt.org >
> Subject: [Users] net device initialization order
> 
> 
> 
> 
> 
> 
> 
> i just did my first 3.2 install, i have a single manager and a single
> node.
> 
> 
> i have also just created my first VM, and it has 2 network
> interfaces.
> 
> 
> nic1 0aa9 – ovirtmgmt network
> nic2 0aa7 – iscsi network
> 
> 
> in the configuration dialog, nic2/0aa7 was the first one that was
> actually added, and that was the one i wanted in the ovirtmgmt
> network (and subsequently i will have to reverse my network cards,
> and i will have to see nic2 as my mgmt/eth0 and nic1 as my iscsi in
> the web page), but it looks like the guests are initializing their
> pci devices in backwards order.
> 
> 
> is this something i can set somewhere, or is this a bug?
> 
> 
> 
> 
> 
> This is a PRIVATE message. If you are not the intended recipient,
> please delete without copying and kindly advise us by e-mail of the
> mistake in delivery. NOTE: Regardless of content, this e-mail shall
> not operate to bind SKOPOS to any order or other contract unless
> pursuant to explicit written agreement or government initiative
> expressly permitting the use of e-mail for such purpose.
> 
> This is a PRIVATE message. If you are not the intended recipient,
> please delete without copying and kindly advise us by e-mail of the
> mistake in delivery. NOTE: Regardless of content, this e-mail shall
> not operate to bind SKOPOS to any order or other contract unless
> pursuant to explicit written agreement or government initiative
> expressly permitting the use of e-mail for such purpose.
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 



More information about the Users mailing list