No eth0 when booting as vmdk in VMware

[Ryan Hsu]

I've converted the cirros image, cirros-0.3.0-x86_64-disk.img to vmdk format using "qemu-img convert" and the image boots up fine in Openstack using the VMwareVCDriver, however, the eth0 interface seems to be missing. Excuting ifconfig only shows the loopback interface. When doing "sudo ifup eth0", the following error is displayed:

ip: can't find device 'eth0'
ip: SIOCGIFFLAGS: No such device

[Scott Moser (smoser)]

This is either
 a.) just a missing driver
 b.) a missing driver and some necessary other things like described in bug 1099611.

Can you boot a ubuntu instance and find out what modules provide the network and block device drivers?

I can then add them to the list for inclusion.

[Ryan Hsu (rhsu)]

Scott, we followed this [1] blog post and was able to get networking working. It seems the author just added these 2 modules:

    mptbase
    mptscsih

[1] http://romans-it.blogspot.com/2013/06/rebuild-cirros-tiny-cloud-image-for.html?showComment=1381556852157#c6513109009214320747

[Eric Brown (ericwb)]

My issue is similar. If I use qemu-img to convert cirros-0.3.2-i386-disk.img to a vmdk, preserving the adapter type as 'ide', everything works fine (both configdrive and eth0 networking). However, if I use qemu-img version 1.7 that allows me to convert the same image with adapter_type=lsilogic, then both eth0 networking is broke (no eth0 interface) and configdrive doesn't work. I'm at a loss to explain why. Seems strange the HD adapter type is affecting the networking and cd-rom drive. In both cases the hard disk works fine and the OS boots.

Works:
qemu-img convert -f qcow2 cirros-0.3.2-i386-disk.img -O vmdk cirros-0.3.2-i386-disk.vmdk

Does not work:
qemu-img convert -f qcow2 cirros-0.3.2-x86_64-disk.img -O vmdk -o adapter_type=lsilogic cirros-0.3.2-x86_64-disk.vmdk