Marcus/Edison,
I've been looking at CLOUDSTACK-6460 to see if I could figure out why CLVM
volumes are being seen as format QCOW2 rather than RAW when attempting a
primary storage migration. I've found that when a new volume gets attached to a
VM, it seems that QCOW2 is being set as the format in the volumes table for
that volume.
Upon allocation, it's NULL, then once you attach it, it changes to QCOW2.
Here's a log snippet that shows this happening:
org.apache.cloudstack.storage.command.AttachCommand":
{"disk":
{"data":
{"org.apache.cloudstack.storage.to.VolumeObjectTO":
{"uuid":"558b0140-8d98-429c-9de3-44dc7ec96f51","volumeType":"DATADISK","dataStore":
{"org.apache.cloudstack.storage.to.PrimaryDataStoreTO":
{"uuid":"076d1cd7-9c80-4302-8e13-ea8187a9a96b","id":201,"poolType":"CLVM","host":"localhost","path":"/csstore01","port":0,"url":"CLVM://localhost//csstore01/?ROLE=Primary&STOREUUID=076d1cd7-9c80-4302-8e13-ea8187a9a96b"
}
},"name":"test7_2","size":5368709120,"path":"558b0140-8d98-429c-9de3-44dc7ec96f51","volumeId":17456,"accountId":6,"format":"QCOW2","id":17456,"hypervisorType":"KVM"
}
}
,"diskSeq":5,"path":"558b0140-8d98-429c-9de3-44dc7ec96f51","type":"DATADISK","_details":
{"managed":"false","storagePort":"0","storageHost":"localhost","volumeSize":"5368709120"
}
},"vmName":"i-6-22370-VM","inSeq":false,"wait":0}}]
}?
I've been working through the code for a couple of days now, and I'd appreciate
if you could point me in the right direction in terms of how a volume format is
determined at attachment to a VM. There's a lot of legacy unused methods
littered through the code that tie hypervisors to particular disk formats, so
any expert advice would help me narrow down where to look.
Thanks in advance,
Simon
