The copy operation invoke through VC is intentionally passed a null copy_spec. That in itself should not be the cause of the failure. Can you confirm the image you used in a monolithic sparse image. I tested with an ide sparse vmdk, and the embedded descriptor information (you can get that by doing head -20 mysparse.vmkd) reads:
KDM6
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=1e521528
parentCID=ffffffff
isNativeSnapshot="no"
createType="monolithicSparse"
I used the following to import the image:
glance image-create --name=msp_ide --disk-format=vmdk --container-format=bare --is-public=True --property vmware_adaptertype="ide" --property vmware_disktype="sparse" < msp_ide.vmdk
This is verified on upstream master code today. Please verify the image format and glance properties.
If the problem still persists, we may have to look into the VC/ESX logs to understand the root cause.
Hi,
The copy operation invoke through VC is intentionally passed a null copy_spec. That in itself should not be the cause of the failure. Can you confirm the image you used in a monolithic sparse image. I tested with an ide sparse vmdk, and the embedded descriptor information (you can get that by doing head -20 mysparse.vmkd) reads:
KDM6
# Disk DescriptorFile t="no" "monolithicSpar se"
version=1
encoding="UTF-8"
CID=1e521528
parentCID=ffffffff
isNativeSnapsho
createType=
# Extent description
RW 524288 SPARSE "dsl-disk1.vmdk"
# The Disk Data Base
#DDB
ddb.adapterType = "ide"
This disk spawns fine for me.
I used the following to import the image: format= bare --is-public=True --property vmware_ adaptertype= "ide" --property vmware_ disktype= "sparse" < msp_ide.vmdk
glance image-create --name=msp_ide --disk-format=vmdk --container-
This is verified on upstream master code today. Please verify the image format and glance properties.
If the problem still persists, we may have to look into the VC/ESX logs to understand the root cause.