[openstack]Problem with launching instances from VMDK
Hello I am trying create instance from vmdk but I have this error: The image format was claimed to be 'vmdk' but the image data appears to be in a different format. My cloud is Openstack 2023.1. This happened when We applied patches for CVE-2024-40767. Nguyen Huu Khoi
Hi On Fri, Sep 27, 2024 at 5:00 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hello
I am trying create instance from vmdk but I have this error:
The image format was claimed to be 'vmdk' but the image data appears to be in a different format.
Before booting an instance you need to convert the vmdk file to a supported format by Openstack (qcow2 for example). There is tooling for doing that (v2v) or even my team has created an ansible collection to migrate vmdk volume from esxi to Openstack.
My cloud is Openstack 2023.1. This happened when We applied patches for CVE-2024-40767.
Nguyen Huu Khoi
Hello. I did it by creating images with vmdk and it worked in the past. I also convert vmdk to qcow2 but my instances stucked at boot. It is weird. Nguyen Huu Khoi On Fri, Sep 27, 2024 at 1:30 PM Mathieu Bultel <mbultel@redhat.com> wrote:
Hi
On Fri, Sep 27, 2024 at 5:00 AM Nguyễn Hữu Khôi <nguyenhuukhoinw@gmail.com> wrote:
Hello
I am trying create instance from vmdk but I have this error:
The image format was claimed to be 'vmdk' but the image data appears to be in a different format.
Before booting an instance you need to convert the vmdk file to a supported format by Openstack (qcow2 for example). There is tooling for doing that (v2v) or even my team has created an ansible collection to migrate vmdk volume from esxi to Openstack.
My cloud is Openstack 2023.1. This happened when We applied patches for CVE-2024-40767.
Nguyen Huu Khoi
I did it by creating images with vmdk and it worked in the past. I also convert vmdk to qcow2 but my instances stucked at boot. It is weird.
Right, part of the problem that the CVE fixes addressed was our willingness to accept any image *content* regardless of what the metadata on the image was. That led to the security issue and that is what is fixed (i.e. no longer allowed). If you're using libvirt hypervisors, you need to use an image format that is supported by that driver. The most similar format would be qcow2. You can technically use qemu-img to convert between the two, but virt-v2v[1] should do a better job. --Dan [1] https://libguestfs.org/virt-v2v.1.html
Hi. Thank you very much. I will try. On Fri, Sep 27, 2024, 8:40 PM Dan Smith <dms@danplanet.com> wrote:
I did it by creating images with vmdk and it worked in the past. I also convert vmdk to qcow2 but my instances stucked at boot. It is weird.
Right, part of the problem that the CVE fixes addressed was our willingness to accept any image *content* regardless of what the metadata on the image was. That led to the security issue and that is what is fixed (i.e. no longer allowed).
If you're using libvirt hypervisors, you need to use an image format that is supported by that driver. The most similar format would be qcow2. You can technically use qemu-img to convert between the two, but virt-v2v[1] should do a better job.
--Dan
participants (3)
-
Dan Smith
-
Mathieu Bultel
-
Nguyễn Hữu Khôi