You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Donal Lafferty (JIRA)" <ji...@apache.org> on 2013/12/11 15:33:07 UTC
[jira] [Created] (CLOUDSTACK-5462) Hyper-V Agent confused by
existing volume of different image type
Donal Lafferty created CLOUDSTACK-5462:
------------------------------------------
Summary: Hyper-V Agent confused by existing volume of different image type
Key: CLOUDSTACK-5462
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5462
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Hypervisor Controller
Reporter: Donal Lafferty
VolumeObjectTO objects do not specify the image format.
Hyper-V infers the format from files with the same name as that specified in the VolumeObjectTO.name field. This fails when a name is reused for a different image type.
E.g. if the agent finds a ROOT2-1.vhd, it will assume that the VolumeObjectTO is a VHD. However, if the VolumeObjectTO is actually a VHDX, then the disk will appear to be corrupt to the hypervisor.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)