Revision history [back]

For what is worth, you can use Hyper-V compute nodes with OpenStack. I assume you're using KVM now, since you've mentioned virtio.

Anyway, the fact that the instance boots when using IDE makes me think there's something wrong with the virtio drivers. Double check that those are properly installed (especially viostor/vioscsi). If so, you can try a different version.

however i can't attach any secondary volume to the instance since it will only attach as /dev/hda/ instead of "/dev/vdb" and windows guest cannot see it.

I think that's because your guest cannot use virtio block devices, not because of the device path.

Here are some more ideas: - check the libvirt domain xml by doing "virsh dumpxml <vm_name>". - use bcdedit to enable boot logging

Feel free to post any meaningful logs (but please use pastebin or similar services).

Regards, Lucian

For what is worth, you can use Hyper-V compute nodes with OpenStack. I assume you're using KVM now, since you've mentioned virtio.

Anyway, the fact that the instance boots when using IDE makes me think there's something wrong with the virtio drivers. Double check that those are properly installed (especially viostor/vioscsi). If so, you can try a different version.

however i can't attach any secondary volume to the instance since it will only attach as /dev/hda/ instead of "/dev/vdb" and windows guest cannot see it.

I think that's because your guest cannot use virtio block devices, not because of the device path.

Here are some more ideas: - ideas:

• check the libvirt domain xml by doing "virsh dumpxml <vm_name>". - <vm_name>".

• use bcdedit to enable boot logging

Feel free to post any meaningful logs (but please use pastebin or similar services).

Regards, Lucian