[
https://issues.apache.org/jira/browse/CLOUDSTACK-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13572184#comment-13572184
]
Devdeep Singh commented on CLOUDSTACK-647:
------------------------------------------
The issue is that while backing up a snapshot when cloudstack tries to update
the parent (of the backed up vhd), vhd-util isn't present at the desired
location and setParent function in vmopsSnapshot fails. This issue is observed
only on Xenserver 6.1. The reason for this is, when CloudStack connects to a
Xenserver and executes the SetupCommand, it copies vhd-util tool to
/opt/xensource/bin directory on the host. However, in vmopsSnapshot python file
'VHD_UTIL' is initialized to /usr/sbin/. The issue is not observed on 6.0.2
(and I guess previous versions) because vhd-util is present in /usr/sbin/
directory by default (after a clean install). Whereas, in Xenserver 6.1,
vhd-util is present in '/usr/bin'. Fixed the issue by updating VHD_UTIL to
point to /opt/xensource/bin/vhd-util in vmopsSnapshot file.
> Snapshot failing on XenServer 6.1
> ---------------------------------
>
> Key: CLOUDSTACK-647
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-647
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Devdeep Singh
> Assignee: Devdeep Singh
>
> On XenServer 6.1 launch an instance and take a snapshot of a any volume.
> It'll go through successfully. Try taking another snapshot of the same
> volume, it'll fail.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
