I understand that actually mapping a device name from hypervisor to
guest is actually impossible, but hopefully we can come up with a better
guess.
Its unfortunate that libvirt doesn't even seem to be using the "dev=" as
a suggestion of device ordering along the virtio bus. Instead, I'm
guessing it is using order present in xml. I was hoping at very least
that suggesting 'vda', 'vdb', 'vdc' would render in kvm command line to
addr=0x4, addr=0x5, addr=0x6 respectively.
Since libvirt seems to be relying on order in the xml, is it possible to
specify the "correct" order and also sane "dev=" attributes?
Ie, what would happen if you had xml like:
| <disk type='file'>
| <driver type='qcow2'/>
| <source file='/var/lib/nova/instances/instance-000000e4/disk'/>
| <target dev='vda' bus='virtio'/>
| </disk>
| <disk type='block'>
| <driver type='qcow2'/>
| <source dev='/var/lib/nova/instances/instance-000000e4/disk.eph0 '/>
| <target dev='vdb' bus='virtio'/>
| </disk>
| <disk type='block'>
| <driver type='raw'/>
| <source dev='/dev/mapper/nova--volumes-volume--00000040'/>
| <target dev='vdc' bus='virtio'/>
| </disk>
And then specified block device mapping like:
{
'ami': 'vda',
'root': '/dev/vda',
'ephemeral0': '/dev/vdb'
'vol0': '/dev/vdc'
}
Again, I understand, you can't force the guest to name devices in any
way, but hopefully we can at least map "vda" to "first device on virtio
bus", and "vdb" to "second disk on virtio bus".
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/827590
Title:
cloud-init does not mount ephemeral0 on /mnt in nova
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/827590/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
