cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sebastian Trampler <sebastian.tramp...@iisys.de>
Subject Re: SSVM won't start
Date Wed, 04 Dec 2013 09:14:52 GMT
Hello again,

it still doesn't work. But many thanks for the hints.

Here are the facts:
- Cloudstack 4.2 is installed on Ubuntu 12.04.
- Primary and secondary storage are NFS share on Cloudstack server
- Xenserver 6.2
- vhd-util is downloaded from 
http://download.cloud.com.s3.amazonaws.com/tools/vhd-util
- I copied vhd-util on cloudstack server in following directories with 
permission 0755
  1) /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver
  2) 
/usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60
  3) 
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/vm/hypervisor/xenserver
  4) 
/usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60
- On Xen Server I copied the vhd-util to /opt/xensource/bin

I suppose that the Exception has nothing to do with the vhd-util because 
I had an other exception before I copied the vhd-utils to the mentioned 
directories.

Regards

Sebastian

On 12/04/2013 03:16 AM, Amin Samir wrote:
> Hello,
> Two three paths that vhd-util needs to be in place.1) /usr/share/cloudstack-management/webapps/client/WEB-INF/classes/scripts/vm/hypervisor/xenserver/xenserver60/
(depends on your xen server version you may want to place also under /xenserver56FP1 or /xenserver56).
> 2) cd
> /usr/share/cloudstack-common/scripts/vm/hypervisor/xenserver/xenserver60  (depends on
your xen server version you may want to place also under /xenserver56FP1 or /xenserver56).
> 3) On the xen server it self, /opt/xensource/bin.
> Try destroying the system vm's they will be created automatically.
>
> Amin
>> Subject: Re: SSVM won't start
>> From: creategui@gmail.com
>> Date: Tue, 3 Dec 2013 12:41:32 -0600
>> To: users@cloudstack.apache.org
>>
>> Try the vhd-util that the docs tell you to download. Put that one in /opt/xensource/bin
>>
>>> On Dec 3, 2013, at 9:20 AM, Sebastian Trampler <sebastian.trampler@iisys.de>
wrote:
>>>
>>> Hello again,
>>>
>>> after copying the vhd-util on the XenServer to /opt/xensource/bin it first seems
to work, but the ssvm still won't come up.
>>> After reading the log-messages I found the exception below. Any suggestions?
>>>
>>> Regards
>>>
>>> Sebastian
>>>
>>>
>>> 2013-12-03 16:08:34,861 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
VBD a6598c97-b54f-8d12-6785-a9eb1baff098 created for com.cloud.agent.api.to.DiskTO@422d7ffa
>>> 2013-12-03 16:08:34,882 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Creating VIF for s-4-VM on nic [Nic:Guest-XXX.XXX.XXX.XXX-vlan://untagged]
>>> 2013-12-03 16:08:34,902 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Created a vif 940b3765-dd22-a488-4391-25ef188a4ef9 on 2
>>> 2013-12-03 16:08:34,902 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Creating VIF for s-4-VM on nic [Nic:Control-169.254.1.83-null]
>>> 2013-12-03 16:08:34,929 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
already have a vif on dom0 for link local network
>>> 2013-12-03 16:08:35,208 DEBUG [network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
>>> 2013-12-03 16:08:35,210 DEBUG [network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
>>> 2013-12-03 16:08:35,217 DEBUG [network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 routers to update status.
>>> 2013-12-03 16:08:35,219 DEBUG [network.router.VirtualNetworkApplianceManagerImpl]
(RouterStatusMonitor-1:null) Found 0 networks to update RvR status.
>>> 2013-12-03 16:08:35,355 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Created a vif 4919c69e-b711-1ae4-7276-903cffd0524e on 0
>>> 2013-12-03 16:08:35,355 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Creating VIF for s-4-VM on nic [Nic:Management-XXX.XXX.XXX.XXX-null]
>>> 2013-12-03 16:08:35,376 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Created a vif 4ae05ccd-a0b3-5586-4542-9e4dde9250c2 on 1
>>> 2013-12-03 16:08:35,377 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Creating VIF for s-4-VM on nic [Nic:Storage-XXX.XXX.XXX.XXX-null]
>>> 2013-12-03 16:08:35,398 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Created a vif 5f2d5aee-18c0-4c61-af26-edbbd50c7bed on 3
>>> 2013-12-03 16:08:39,453 WARN  [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Task failed! Task record: uuid: bc1b04c5-b891-357c-6151-73f68806c136
>>>            nameLabel: Async.VM.start_on
>>>      nameDescription:
>>>    allowedOperations: []
>>>    currentOperations: {}
>>>              created: Tue Dec 03 16:08:35 CET 2013
>>>             finished: Tue Dec 03 16:08:38 CET 2013
>>>               status: failure
>>>           residentOn: com.xensource.xenapi.Host@8bc3a55e
>>>             progress: 1.0
>>>                 type: <none/>
>>>               result:
>>>            errorInfo: [INTERNAL_ERROR, xenopsd internal error: XenguestHelper.Xenctrl_dom_linux_build_failure(2,
" panic: xc_dom_core.c:609: xc_dom_find_loader: no loader\\\"")]
>>>          otherConfig: {}
>>>            subtaskOf: com.xensource.xenapi.Task@aaf13f6f
>>>             subtasks: []
>>>
>>> 2013-12-03 16:08:39,456 WARN  [xen.resource.CitrixResourceBase] (DirectAgent-472:null)
Unable to start VM(s-4-VM) on host(7c86321f-788d-4a4a-9837-8553b432d738) due to Task failed!
Task record:                 uuid: bc1b04c5-b891-357c-6151-73f68806c136
>>>            nameLabel: Async.VM.start_on
>>>      nameDescription:
>>>    allowedOperations: []
>>>    currentOperations: {}
>>>              created: Tue Dec 03 16:08:35 CET 2013
>>>             finished: Tue Dec 03 16:08:38 CET 2013
>>>               status: failure
>>>           residentOn: com.xensource.xenapi.Host@8bc3a55e
>>>             progress: 1.0
>>>                 type: <none/>
>>>               result:
>>>            errorInfo: [INTERNAL_ERROR, xenopsd internal error: XenguestHelper.Xenctrl_dom_linux_build_failure(2,
" panic: xc_dom_core.c:609: xc_dom_find_loader: no loader\\\"")]
>>>          otherConfig: {}
>>>            subtaskOf: com.xensource.xenapi.Task@aaf13f6f
>>>             subtasks: []
>>>
>>> Task failed! Task record:                 uuid: bc1b04c5-b891-357c-6151-73f68806c136
>>>            nameLabel: Async.VM.start_on
>>>      nameDescription:
>>>    allowedOperations: []
>>>    currentOperations: {}
>>>              created: Tue Dec 03 16:08:35 CET 2013
>>>             finished: Tue Dec 03 16:08:38 CET 2013
>>>               status: failure
>>>           residentOn: com.xensource.xenapi.Host@8bc3a55e
>>>             progress: 1.0
>>>                 type: <none/>
>>>               result:
>>>            errorInfo: [INTERNAL_ERROR, xenopsd internal error: XenguestHelper.Xenctrl_dom_linux_build_failure(2,
" panic: xc_dom_core.c:609: xc_dom_find_loader: no loader\\\"")]
>>>          otherConfig: {}
>>>            subtaskOf: com.xensource.xenapi.Task@aaf13f6f
>>>             subtasks: []
>>>
>>>     at com.cloud.hypervisor.xen.resource.CitrixResourceBase.checkForSuccess(CitrixResourceBase.java:3605)
>>>     at com.cloud.hypervisor.xen.resource.CitrixResourceBase.startVM(CitrixResourceBase.java:3717)
>>>     at com.cloud.hypervisor.xen.resource.CitrixResourceBase.execute(CitrixResourceBase.java:1640)
>>>     at com.cloud.hypervisor.xen.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:557)
>>>     at com.cloud.hypervisor.xen.resource.XenServer56Resource.executeRequest(XenServer56Resource.java:73)
>>>     at com.cloud.hypervisor.xen.resource.XenServer610Resource.executeRequest(XenServer610Resource.java:104)
>>>     at com.cloud.agent.manager.DirectAgentAttache$Task.run(DirectAgentAttache.java:186)
>>>     at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
>>>     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
>>>     at java.util.concurrent.FutureTask.run(FutureTask.java:166)
>>>     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)
>>>     at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)
>>>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
>>>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>>>     at java.lang.Thread.run(Thread.java:679)
>   		 	   		


Mime
View raw message