Public bug reported:
http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
The link above has an "I don't like this, how do I disable this?" section that
shows how to disable.
If you boot a disk1.img of wily (I did 20150808) with the default
network device for qemu-system-x86, then the device is named 'ens3'
rather than 'eth0', which causes timeout on the network bringup.
The default model for me on wily qemu-system-x86 seems to be e1000.
Fun
1.) download disk1.img
2.) create seed image
$ cat > user-data <<EOF
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
EOF
$ echo "instance-id: $(uuidgen || echo i-abcdefg)" > meta-data
$ cloud-localds my-seed.img my-user-data my-meta-data
3.) boot cloud image
$ kvm -net nic -net user,hostfwd=tcp::2222-:2 \
-drive file=disk1.img,if=virtio -drive file=my-seed.img,if=virtio
You'll see a timeout waiting for network to come up.
You'll be able to log in and see that you have an unconfigured ens3 network
device ('ifconfig -a' or 'ip link').
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: cloud-images
** Tags added: cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1483457
Title:
non-virtio devices get named with systemd "predictable network
interface names"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1483457/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
