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.
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: 0.3.2-i386- disk.img -O vmdk cirros- 0.3.2-i386- disk.vmdk
qemu-img convert -f qcow2 cirros-
Does not work: 0.3.2-x86_ 64-disk. img -O vmdk -o adapter_ type=lsilogic cirros- 0.3.2-x86_ 64-disk. vmdk
qemu-img convert -f qcow2 cirros-