Hi Timothy,
I have mounted SS on the slave host manually (didn't restart anything
yet), but the next VM started on the primary node has also failed with the same
error. I don't think this is connected to host's mount points. Primary node has
had this mount from the beggining and new VM fails on the primary as well.
At the same time templates (that are also located at SS) are executed
correctly and VM-s are created on any host. I don't understand which way ISO
and template are different ?
Vadim.
________________________________________
From: Timothy Lothering [[email protected]]
Sent: Saturday, April 25, 2015 16:19
To: [email protected]
Cc: [email protected]
Subject: RE: CS 4.5.1: Unable to start a VM due to insufficient capacity
Hi Vadim,
Can you manually mount the SS on the Cluster Slave Node?
I had a similar issue, and in the end needed to reboot the host. Don't know if
this would resolve your issue?
Regards,
Timothy Lothering
Solutions Architect
Managed Services
T: +27877415535
F: +27877415100
C: +27824904099
E: [email protected]
DISCLAIMER NOTICE:
Everything in this e-mail and any attachments relating to the official business
of Datacentrix Holdings Ltd. and its subsidiaries
('Datacentrix') is proprietary to Datacentrix. It is confidential, legally
privileged and protected by law. Datacentrix does not
own and endorse any other content. Views and opinions are those of the sender
unless clearly stated as being that of Datacentrix.
The person addressed in the e-mail is the sole authorised recipient. Please
notify the sender immediately if it has unintentionally
reached you and do not read, disclose or use the content in any way.
Datacentrix cannot assure that the integrity of this communication
has been maintained nor that it is free of errors, virus, interception or
interference.
-----Original Message-----
From: Vadim Kimlaychuk [mailto:[email protected]]
Sent: 25 April 2015 07:49 AM
To: [email protected]
Cc: [email protected]
Subject: CS 4.5.1: Unable to start a VM due to insufficient capacity
Hello all,
After fresh install for subj. Got problem creating new VM from ISO.
Installing VM from templates is working. Management log said that :
2015-04-25 08:36:32,066 DEBUG [c.c.a.m.DirectAgentAttache]
(DirectAgent-185:ctx-9207cdf3) Seq 2-635851972389374824: Executing request
2015-04-25 08:36:32,071 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-185:ctx-9207cdf3) 1. The VM i-2-13-VM is in Starting state.
2015-04-25 08:36:32,089 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-185:ctx-9207cdf3) Created VM 834101d6-e316-3fc9-5f8d-6c55f641d986
for i-2-13-VM
2015-04-25 08:36:32,107 DEBUG [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-185:ctx-9207cdf3) VBD 0524ba7b-dcd9-f227-349e-caa83d486939 created
for com.cloud.agent.api.to.DiskTO@5213a905
2015-04-25 08:36:32,254 WARN [c.c.h.x.r.CitrixResourceBase]
(DirectAgent-185:ctx-9207cdf3) createIsoSRbyURI failed! mountpoint:
secondary.storage.ant.ee/export/secondary/template/tmpl/2/206 due to
SR_BACKEND_FAILURE_222Could not mount the directory specified in Device
Configuration SR_BACKEND_FAILURE_222Could not mount the directory specified in
Device Configuration
at com.xensource.xenapi.Types.checkResponse(Types.java:2021)
ISO file in storage present and uploaded using cloudstack UI. Secondary
storage was mounted on the cluster node, but not on slave node. I have created
the same mount point on the slave, but problem still exists. I have separate
network for secondary storage -- may be this is a problem? Please, give me a
hint
Thanks,
Vadim.
