Well, it turns out it was just a noob mistake. When I downloaded vhd-util, I 
didn't chmod +x. I should have known to do that, but maybe we can add something 
to INSTALL.md as a reminder for others?

Chris

On Jul 11, 2013, at 9:58 AM, "SuichII, Christopher" <chris.su...@netapp.com> 
wrote:

> Since I'm building CS from source, I downloaded vhd-util into:
> 
> <csroot>/scripts/vm/hypervisor/xenserver/
> 
> and then it gets deployed to:
> 
> <csroot>/client/target/cloud-client-ui-4.2.0-SNAPSHOT/WEB-INF/classes/scripts/vm/hypervisor/xenserver/
>  and
> <csroot>/client/target/generated-webapp/WEB-INF/classes/scripts/vm/hypervisor/xenserver/
> 
> After your email, I also put vhd-util onto XenServer at:
> 
> /opt/xensource/bin/
> 
> and I am still seeing the same issue.
> 
> On Jul 11, 2013, at 6:11 AM, Srikanteswararao Talluri 
> <srikanteswararao.tall...@citrix.com> wrote:
> 
>> If you have a look at xensource.log
>> 
>> Value for virtual-size=MiB, it expects an integer. This is a problem with
>> vhd-util not present in /opt/xensource/bin
>> 
>> Where did you place vhd-util ?
>> 
>> Thanks,
>> ~Talluri
>> 
>> 1. Jul 10 17:54:33 cirrus xapi: [ info|cirrus|59579 UNIX
>> /var/xapi/xapi||cli] xe vdi-create password=null
>> sr-uuid=dcfdd1b5-36d8-deaa-dfb4-188e093fa57c virtual-size=MiB type=user
>> name-label=cloud-3155bd82-ba6f-49fc-9adf-190515536b91 username=root
>> .
>> .
>> .
>> .
>> 
>> 
>> 10. Jul 10 17:54:33 cirrus xapi: [debug|cirrus|59579 UNIX
>> /var/xapi/xapi||cli] Xapi_cli.exception_handler: Got exception
>> INTERNAL_ERROR: [ Record_util.Record_failure("Failed to parse field
>> 'virtual-size': expecting an integer (possibly with suffix)") ]
>> 
>> 11. Jul 10 17:54:33 cirrus xapi: [debug|cirrus|59579 UNIX
>> /var/xapi/xapi||cli] Raised at string.ml:150.25-34
>> 
>> 
>> 
>> 
>> 
>> On 11/07/13 3:41 AM, "SuichII, Christopher" <chris.su...@netapp.com> wrote:
>> 
>>> I'm working on setting up a CS installation with a single XenServer host.
>>> However, once I add the primary and secondary storage, the system vms
>>> fail to start up.
>>> 
>>> For readability, I've put several logs and traces here:
>>> 
>>> http://pastebin.com/eb51JDHF <--- CS Mgmt Log 1
>>> http://pastebin.com/mbfRCei3 <--- XenServer Log from the same time as CS
>>> Mgmt Log 1
>>> 
>>> http://pastebin.com/Sm56N5ZX <--- Another CS Mgmt log that is likely
>>> related. This one clearly states that the host is placed on the avoid
>>> list and therefore no suitable hosts were found, but I can't figure out
>>> why the host is on the avoid list.
>>> 
>>> http://pastebin.com/21R9auwb <--- Another CS Mgmt log indicating it was
>>> 'Unable to acquire lock on VMTemplateStoragePool'
>>> 
>>> 
>>> 
>>> Those 4 groups of logs just repeat over and over.
>>> 
>>> I know that is a lot to read through, but can anyone provide any insight
>>> here? I've been stuck on this for quite a while today. I'm building CS
>>> from the latest code as of this morning with the following commands:
>>> 
>>> mvn -e -Dmaven.test.skip=true -P systemvm,developer clean install
>>> mvn -e -Dmaven.test.skip=true -P developer -pl developer,tools/devcloud
>>> -Ddeploydb
>>> mvn -e -pl :cloud-client-ui jetty:run
>>> 
>>> and I have downloaded and placed the vhd-util accordingly. Is there some
>>> obvious step I'm missing?
>>> 
>>> Thanks!
>>> Chris
>> 
> 

Reply via email to