yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #91769
[Bug 2017358] Re: VM doesn't boot after qemu-img convert from VMDK to RAW/QCOW2
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/2017358
Title:
VM doesn't boot after qemu-img convert from VMDK to RAW/QCOW2
Status in OpenStack Compute (nova):
Invalid
Bug description:
I'm trying to migrate a Windows Server (2016/2019) VM from
vSphere/VMWare to OpenStack (KVM-QEMU). I followed these instructions:
https://platform9.com/docs/openstack/tutorials-migrate-windows-vm-
vmware-kvm without success.
After downloading the VMDK file vCenter/vSphere in an Ubuntu Server
with GUI installed (a server used for this purpose), I used this
command:
```
~# qemu-img convert -O qcow2 win2016-copy-flat.vmdk win2016.qcow2
~# qemu-img convert -O raw win2016-copy-flat.vmdk win2016.qcow2
```
I tried with both formats, RAW and QCOW2, and after importing into my
controller node that image with the next command:
```
~# openstack image create --insecure --container-format bare "win2016-raw" --disk-format raw --file /tmp/win2016.qcow2
~# openstack image create --insecure --container-format bare
"win2016-qcow2" --disk-format qcow2 --file /tmp/win2016.qcow2
```
Finally, I tested creating a new instance and I obtain this error message:
Booting from Hard Disk...
Boot failed: not a bootable disk
No bootable device.
(Exactly like this issue: https://github.com/cloudbase/windows-imaging-tools/issues/324)
After googling a lot and a couple of days, I tried another way, to
change the chipset of the image from i440fx to q35, also, enabling the
boot menu and secure boot, like in this link:
https://bugzilla.redhat.com/show_bug.cgi?id=1663212 following the
documentation about the properties of images
(https://docs.openstack.org/ocata/cli-reference/glance-property-
keys.html).
Then, my instance continues without booting, with a different message but with the same result, something link this: https://github.com/ipxe/pipxe/issues/14 and a similar screenshot of this thread https://forums.freebsd.org/threads/i-got-error-bdsdxe-failed-to-load-boot0001-when-i-boot-kali-linux-vm-via-uefi-firmware.82773/
Also, I explored the possibility of the partition table being
corrupted and I tried to repair it with `gdisk` command; with the same
result. So, which other way can I test?
Context, I have my services of OpenStack running over a Ubuntu Servers
cluster with 3 nodes and 1 controller, deployed with kolla-ansible
over docker to have high availability, and CEPH as storage, configured
with rbd (rados) to work with Glance/Cinder.
I have tested different Windows Server editions from scratch,
installing the S.O. locally with KVM and VirtManager, then uploading
the QCOW2 disk to OpenStack, and works fine, and other Linux
distributions. But this specific scenario migrating with Windows
Server from vSphere to OpenStack crashes on that point, with the
bootable device.
Thank you for reading and for your time.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/2017358/+subscriptions
References