On Thu, 2024-05-09 at 11:22 -0700, melanie witt wrote:
On 5/9/24 02:31, luckydog xf wrote:
hi, list,
I'm going to boot an instance from an existing volume, and it is a Windows 2016 migrated from VMware. So the bus must be set to 'ide' mode, otherwise it fails to boot up.
Let's assume this volume UUID is xyz and it's bootable. I cloned it by clonezilla from VMware ESXI. since virtio drive wasn't installed in Windows, so it must be set to ide.
So what's the right way to boot it from this volume and set it to IDE? i would at least try setting it to sata rather then ide for performace reasons
I have tried lots of ways, like
---
openstack server create test-windows --flavor 4 --nic net- id=7b57ee99-136f-4aa7-b3fe-a4958ec8c644 --block-device id=xxxx:disk_bus=ide
you coudl do that or you could set the hw_disk_bus image propperty in the volume image properties to sata ide or any other bus that the windows guest supprots sata will perform better then ide even usb will likely be better.
and ... --block-device-mapping.
But unfortunately, none of them work.
And there are too many outdated docs like disk_bus=ide and bus=ide. Not sure which one works. This is fairly frustrating.
I'm still struggling with this issue and need your help.
Thanks a lot.
I think it would be something like this at a minimum [1]:
openstack server create test-windows --flavor 4 --nic net-id=7b57ee99-136f-4aa7-b3fe-a4958ec8c644 --block-device uuid=xxxx,source_type=volume,destination_type=volume,disk_bus=ide,boot_index=0
source_type is needed to interpret what uuid is referring to
destination_type not sure if it's required but it makes it clear that the boot disk is a volume rather than a local disk
boot_index=0 is needed to indicate it's a boot volume
-melwitt
[1] https://docs.openstack.org/python-openstackclient/latest/cli/command-objects...