[Lxc-users] unexpected device renaming behavior with phys network.types

[Amy Fong]

Hi,

I'm using 2.6.34 with patches applied from:

http://www.kernel.org/pub/linux/kernel/people/gregkh/driver_core/2.6/2.6.34/

It seem that when I try to create a container where I rename the
device

e.g.

lxc-execute --name net -s lxc.network.type=phys -s lxc.network.link=eth0 -work.name=eth1 -s lxc.network.flags=up bash

When I exit the container, my eth0 becomes renamed to something else
(in this case, dev2)

root at localhost:/root> ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dev2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:15:17:dd:a7:32 brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:15:17:dd:a7:33 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:15:17:d8:08:14 brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether 00:15:17:d8:08:15 brd ff:ff:ff:ff:ff:ff
6: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

I tried this out in 2.6.39, and I don't see the same behaviour. Is there
a certain patch or set of patches that I need to fix this unexpected
behaviour?

Thanks!