cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-10197) XenServer 7.1: Cannot mount xentool iso from cloudstack on VMs
Date Wed, 03 Jan 2018 18:28:01 GMT


ASF GitHub Bot commented on CLOUDSTACK-10197:

rafaelweingartner commented on issue #2365: CLOUDSTACK-10197: Rename xentools iso for XenServer
   What are the assumptions here?
   I mean, is it possible to have clusters/hosts with different versions of XenServer at the
same time?
   If so, we should work with both naming conventions at the same time, right?
   What about something different? The user does not need to know the version of XenServer
the cloud providers use. We could present a “dummy” ISO option called “XenServer tools.
Then, underneath, when plugging the ISO to the VM, we check the host the VM is running and
select/find/discover the right VDI that represent the XenServer tools ISO to be connected
to the VM (according to host’s XenServer version). This would require only a single entry
for any type of XenServer tools.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> XenServer 7.1: Cannot mount  xentool iso from cloudstack on VMs
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-10197
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions:
>         Environment: XenServer 7.0+
>            Reporter: Khosrow Moossavi
>             Fix For: Future
> In XenServer 7.0+ xentools iso has been renamed from *xs-tools* to *guest-tools* so CloudStack
fails to attach it to any VM.
> {code}
> (acs-admin) > attach iso virtualmachineid=d13eeff1-2d99-46a9-8fc5-3510df6e9f5e id=e8a56540-0fc3-44de-9911-635d2d8f25c4
> errorcode = 530
> errortext = Failed to attach iso
> {code}

This message was sent by Atlassian JIRA

View raw message