You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently using windows-imaging-tools to create images for an Openstack infrastructure. However, I'm hitting a little quirk that proves to be annoying. I am trying to generate a MAAS image with a QCOW2 format, to prevent conversion from RAW to QCOW2 by the Nova service. However, the following lines in the script are preventing me from doing so :
...
# Select between VHD, VHDX, QCOW2, VMDK or RAW formats.virtual_disk_format=QCOW2
# This parameter allows to choose between MAAS, KVM, VMware and Hyper-V specific images.# For HYPER-V, cloudbase-init will be installed and the generated image should be in vhd or vhdx format.# For MAAS, in addition to cloudbase-init, the curtin tools are installed# and the generated image should be in raw.tgz format.# For KVM, in addition to cloudbase-init, the VirtIO drivers are installed# and the generated image should be in qcow2 format.image_type=MAAS
...
A possible solution to this specific problem would be to add a new parameter, called force_virtual_disk_format, which would bypass this implicit conversion.
Thanks in advance for your response !
The text was updated successfully, but these errors were encountered:
Hello,
I am currently using windows-imaging-tools to create images for an Openstack infrastructure. However, I'm hitting a little quirk that proves to be annoying. I am trying to generate a MAAS image with a QCOW2 format, to prevent conversion from RAW to QCOW2 by the Nova service. However, the following lines in the script are preventing me from doing so :
windows-imaging-tools/WinImageBuilder.psm1
Lines 1919 to 1953 in 58b91df
Here's a snippet of my config :
A possible solution to this specific problem would be to add a new parameter, called
force_virtual_disk_format
, which would bypass this implicit conversion.Thanks in advance for your response !
The text was updated successfully, but these errors were encountered: