[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742034#comment-13742034
 ] 

Donal Lafferty commented on CLOUDSTACK-4082:
--------------------------------------------

Sorry for the delay, 'watch' was not working as expected.

The vhd-util affects XenAPI calls.  XenAPI uses vhd-util during vdi_create, and 
it expects the -S to be available.  On my 6.0.2, CloudStack replaced the 
orginal vhd-util, and made a /opt/xensource/bin/vhd-util a symlink.  E.g.

[root@camctxlabs-svr05 ~]# ls -al /opt/xensource/bin/vhd-util
lrwxrwxrwx 1 root root 18 Nov 23  2012 /opt/xensource/bin/vhd-util -> 
/usr/sbin/vhd-util

I was running with Master, but I don't know where the symlink came from.  For 
this reason, I could not rule out problems with 4.2

SMlog attached.





                
> vhd-utils download used by developers is stale
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-4082
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4082
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: XenServer
>    Affects Versions: 4.1.1, 4.2.0
>         Environment: XenServer 6.0.2  (and possibly later versions)
>            Reporter: Donal Lafferty
>            Assignee: Donal Lafferty
>         Attachments: info_SMlog
>
>
> vhd-utils is downloaded separately to the Apache CloudStack source code base.
> See 
> https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-BuildingCloudStack
> This version of vhd-utils lacks the '-S' option used by XenServer 6.0.2 (and 
> possibly above).  As a consequence, it will not create VDIs

--
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

Reply via email to