You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by fulc927 <fu...@gmail.com> on 2018/10/24 22:40:53 UTC
Unable to create a deployment for VM
Hello,
First my environment is built following this tutorial
https://www.shapeblue.com/virtualbox-test-env/
I am trying to setup properly Cloudstack as a proof-of-concept and
eventually adopting it in more sophisticated configuration
I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0
I successfully create a zone and a primary storage, bad things are
coming next, once SystemVMs have to boot.
System VMs nevers successfully boot, they are stuck in an endless loop
cycle (start-stop-start…)
logs attached to this email report:
> Deploy avoids pods: null, clusters: null, hosts: null
> Unable to create a deployment for VM
My config has enough ressources to run the management server and the xen
one in an virtualyzed environment
I highly suspect a network misconfiguration, everything should be OK
since i replicate the config from shapeblue:
PRI STORAGE 10.10.100.11
SECONDARY STORAGE 10.10.101.11
MGMT TRAFFIC SERVER 192.168.56.11
XEN 192.168.56.101
POD SETTINGS 192.168.56.1 (21 - 30)
PUBLIC TRAFFIC 172.30.0.(21 - 30 )
Maybe something is wrong on the MGMT network ? but since i can ping IPs
properly I suspect something more tricky.
If someone could help me giving a look faulty parameters, I can'f figure
out why my cluster and pod load as null value and make the next
processes messy
Thanks
Xen hypervisor seems good regarding
storage:10.10.100.11:/exports/primary/ on
/run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs
(rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11)
10.10.101.11:/exports/secondary on
/var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4
(rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
RE: Unable to create a deployment for VM
Posted by Yordan Kostov <Yo...@worldsupport.info>.
Hi
I went over your log file. Here are some memorable mentions:
- Checking resources in Cluster: 1 under Pod: 1 <- Tries to find resources for the VM
- Looking for speed=500Mhz, Ram=1024
- Host name: xenserver, hostId: 1 is in avoid set, skipping this and trying other available hosts <- For some reason the host is skipped so no vms will be deployed on it.
- Host Allocator returning 0 suitable hosts <- you do not have other hosts to deploy the VM
- Could not find suitable Deployment Destination for this VM under any clusters, returning. <- no other cluster or hosts exist so the VM cannot be deployed
- Listing clusters in order of aggregate capacity, that have (atleast one host with) enough CPU and RAM capacity under this Pod: 1 <<--- searching for resources
- Removing from the clusterId list these clusters from avoid set: [1] <<-- removing clusters that are set in avoid mode. I guess your cluster may be in "disabled" state so it is excluded as VMs will not be deployed on disabled entities.
- No clusters found after removing disabled clusters and clusters in avoid list, returning. <<- Same comment from the previous line.
- VM state transitted from :Starting to Stopped with event: OperationFailedvm's original host id: null new host id: null host id before state transition: 1 <--- Not sure if this is what it really means but HOST ID: NULL means that there was no chosen host the VM to be started anyway so starting operation got canceled.
- Hosts's actual total CPU: 4416 and CPU after applying overprovisioning: 17664 <- Your host resoruces that CD sees. Not sure why CPU count is so high.
- Hosts's actual total RAM: 2627446912 and RAM after applying overprovisioning: 2627446784 - This is the amount of RAM the host have (2.5 GB)
- Invocation exception, caused by: com.cloud.exception.InsufficientServerCapacityException: Unable to create a deployment for VM[ConsoleProxy|v-2-VM]Scope=interface com.cloud.dc.DataCenter; id=1 <<-- You can see the error - Insufficient server capacity.
Check if your cluster or host is in disabled state.
May be this is why the system excludes him as a resource and ultimately decides that there are not enough resources.
Best regards,
Jordan
-----Original Message-----
From: fulc927 [mailto:fulc927@gmail.com]
Sent: Thursday, October 25, 2018 1:41 AM
To: users@cloudstack.apache.org
Subject: Unable to create a deployment for VM
Hello,
First my environment is built following this tutorial https://www.shapeblue.com/virtualbox-test-env/
I am trying to setup properly Cloudstack as a proof-of-concept and eventually adopting it in more sophisticated configuration
I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0
I successfully create a zone and a primary storage, bad things are coming next, once SystemVMs have to boot.
System VMs nevers successfully boot, they are stuck in an endless loop cycle (start-stop-start…)
logs attached to this email report:
> Deploy avoids pods: null, clusters: null, hosts: null > Unable to create a deployment for VM
My config has enough ressources to run the management server and the xen one in an virtualyzed environment
I highly suspect a network misconfiguration, everything should be OK since i replicate the config from shapeblue:
PRI STORAGE 10.10.100.11
SECONDARY STORAGE 10.10.101.11
MGMT TRAFFIC SERVER 192.168.56.11
XEN 192.168.56.101
POD SETTINGS 192.168.56.1 (21 - 30)
PUBLIC TRAFFIC 172.30.0.(21 - 30 )
Maybe something is wrong on the MGMT network ? but since i can ping IPs properly I suspect something more tricky.
If someone could help me giving a look faulty parameters, I can'f figure out why my cluster and pod load as null value and make the next processes messy
Thanks
Xen hypervisor seems good regarding
storage:10.10.100.11:/exports/primary/ on /run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs
(rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11)
10.10.101.11:/exports/secondary on
/var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4
(rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
Re: Unable to create a deployment for VM
Posted by ful crap <fu...@gmail.com>.
Hello dear list,
@Andrija @Yordan thanks for these insightful informations! I did check with
attention pieces of information you brought up about my setup. I am still
sticking with XenServer because I feel It is more appealing for me.
Applying your precious information I got rid of previous misconfigured
setting but still get stuck with my a bit old shapeblue "build a virtual
environment test with VirtualBox" because of HVM which is, I guess, a
mandatory feature since XenServer7.5 and recent hotfixes.
I am saying that because it looks nowadays, to contain a Meltdown-spectre
attack from a guest VM, CS architecture dictates the use of HVM for system
VMs .and that makes the usual below command quite useless:
mysql -p[password] [account] -e \ "INSERT INTO cloud.configuration
> (category, instance, component, name, value, description) VALUES
> ('Advanced', 'DEFAULT', 'management-server', '*xen.check.hvm*', '*false*',
> 'Shoud we allow only the XenServers support HVM');"
Despise the use of the disabled flag for HVM in my templates and
everything, I still have in my logs:
2018-10-27 01:17:50,744 DEBUG [c.c.h.x.r.w.x.CitrixStartCommandWrapper]
> (DirectAgent-3:ctx-a86f4b56) (logid:a337009d) 1. *The VM v-328-VM is in
> Starting state*.
> 2018-10-27 01:17:50,747 DEBUG [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-3:ctx-a86f4b56) (logid:a337009d) no guest OS type, *start it
> as HVM guest*
>
and systemVMs still refusing to boot with:
2018-10-27 01:17:54,340 WARN [c.c.h.x.r.CitrixResourceBase]
> (DirectAgent-10:ctx-e406da5d) (logid:512ff438) *Task failed! Task record:*
> uuid: d910a1bc-9801-b017-eafe-b3d03768aae1
> nameLabel: Async.VM.start_on
> nameDescription:
> allowedOperations: []
> currentOperations: {}
> created: Sat Oct 27 01:17:52 CEST 2018
> finished: Sat Oct 27 01:17:52 CEST 2018
> status: failure
> residentOn: com.xensource.xenapi.Host@32106b38
> progress: 1.0
> type: <none/>
> result:
> errorInfo: [*VM_HVM_REQUIRED*,
> OpaqueRef:44a24e77-39a5-472c-af8a-d7607e57714a]
> otherConfig: {}
> subtaskOf: com.xensource.xenapi.Task@aaf13f6f
> subtasks: []
>
I am writing you here to know if there is a workaround to keep using
virtualbox as an working environment for Xenserver7.5 with CS 4.11 ?
Since Virtuabox does not plan to support HVM by any means, is it still
doable running a recent CS + Xen with that software, what are my options ?
- Can I downgrade to XenServer 6.5 and still use CS4.11.1 ?
- Would the removal of every Xen hotfixes (XS75E001 XS75E002 XS75E003
XS75E004 XS75E005) make systemVMs launchable ?
- Would the building of my own system Templates makes the situation better ?
Does XenServer7.5 implement HVM as a die-hard, not deactivable feature, or
can i work around?
thanks you for your attention
PS please find my recent management log attached
Le mer. 24 oct. 2018 à 23:41, fulc927 <fu...@gmail.com> a écrit :
> Hello,
>
> First my environment is built following this tutorial
> https://www.shapeblue.com/virtualbox-test-env/
>
> I am trying to setup properly Cloudstack as a proof-of-concept and
> eventually adopting it in more sophisticated configuration
>
> I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0
>
> I successfully create a zone and a primary storage, bad things are
> coming next, once SystemVMs have to boot.
>
> System VMs nevers successfully boot, they are stuck in an endless loop
> cycle (start-stop-start…)
>
> logs attached to this email report:
>
> > Deploy avoids pods: null, clusters: null, hosts: null
> > Unable to create a deployment for VM
>
> My config has enough ressources to run the management server and the xen
> one in an virtualyzed environment
>
> I highly suspect a network misconfiguration, everything should be OK
> since i replicate the config from shapeblue:
>
> PRI STORAGE 10.10.100.11
>
> SECONDARY STORAGE 10.10.101.11
>
> MGMT TRAFFIC SERVER 192.168.56.11
>
> XEN 192.168.56.101
>
> POD SETTINGS 192.168.56.1 (21 - 30)
>
> PUBLIC TRAFFIC 172.30.0.(21 - 30 )
>
> Maybe something is wrong on the MGMT network ? but since i can ping IPs
> properly I suspect something more tricky.
>
> If someone could help me giving a look faulty parameters, I can'f figure
> out why my cluster and pod load as null value and make the next
> processes messy
>
> Thanks
>
>
> Xen hypervisor seems good regarding
> storage:10.10.100.11:/exports/primary/ on
> /run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs
>
> (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11)
> 10.10.101.11:/exports/secondary on
> /var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4
>
> (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
>
>
>
>
Re: Unable to create a deployment for VM
Posted by ful crap <fu...@gmail.com>.
Hi there :-)
I want to bring up the shapeBlue tutorial (
https://www.shapeblue.com/virtualbox-test-env/ ) a last time
Even if this tutorial is a bit old, I get it working flawlessly on my
laptop with Apache Cloudstack 4.11.1.0
That's pretty neat to have a sandbox environment for novice like me, to
take a good start on a sophisticated environment like Cloudstack
I chose XenServer because my company has a great focus on this hypervisor
to get things virtualized.
And the only cheap trick regarding this tutorial was to stick to an old
XenServer version (6.5) to get Paravirtualization (PV) working for SystemVMs
That's really cool to have an advanced zone up and running on a cheap but
powerful enough CPU like my i7-8750H (hexacore) with 8GB of RAM
[image: image.png]
[image: image.png]
Some tricks aside, the shapeblue tutorial is still very relevant and
up-to-date, that's amazing ! and I feel it is because the CS architecture
from its ground is firm and rock-solid
I actually don't know the shortcomings (beside security vulnerability) to
run an old version of Xen but truth be told, it rocks!
Happy cloud'in ! I am very glad to join an community like yours ;-)
Feel free to ask me if you want some help for a virtualbox (5.2.18)
Cloudstack-in-a-Box install
Yours
Le jeu. 25 oct. 2018 à 01:13, Andrija Panic <an...@gmail.com> a
écrit :
> Hi,
>
> that is the famous setup article from one of CloudStack conferences, if I'm
> not mistaken - but since things have changed "a bit" during last 4 years
> (both cloudstack and the XenServer versions), that means that probably some
> steps might be missing (just a guess)
>
> Anyway, since system VM is not starting at all - I would suggest to take a
> look into systemVM template - which you should have preseeded during the
> installation process with the "*cloud-install-sys-tmplt*" script - check
> template state in GUI if it says "OK" under "Ready" section (go to specific
> template, click on Zones, and there you will read it). Alternatively, make
> sure that HOST is in connected/up/routing state - can be observer from
> Infrastructure-->Hosts.
>
> Otherwise, is systemVM template is OK, than the HOST (xenserver) should be
> able to mount Secondary Storage (your emails says it works fine...) and
> start the VM from the template (later patch systemVM etc etc...)
>
> I would also suggest perhaps trying a more up to date tutorial, from the
> original documentation for 4.11 release (http://docs.cloudstack.apache.org
> )
> and check your steps with XenServer.
>
> Alternatively, if you are willing to play with KVM, there is also a very
> Quick Installation Guide for CenOS6 (outdated, being updated as we speak) -
> while updated version (not final but with some comments) can be found here:
>
> https://github.com/apache/cloudstack-documentation/blob/cae56e460902b7b4efde426b9cc88e512a1c9076/source/quickinstallationguide/qig.rst
>
>
> If nothing helps, please share management.log file content (pastebean or
> similar) so we can check.
> I'm personally not aware of specific agent logs on XenServer, but I assume
> there are some logs from XenServer itself which you could collect as well.
>
> Cheers
> Andrija
>
> On Thu, 25 Oct 2018 at 00:41, fulc927 <fu...@gmail.com> wrote:
>
> > Hello,
> >
> > First my environment is built following this tutorial
> > https://www.shapeblue.com/virtualbox-test-env/
> >
> > I am trying to setup properly Cloudstack as a proof-of-concept and
> > eventually adopting it in more sophisticated configuration
> >
> > I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0
> >
> > I successfully create a zone and a primary storage, bad things are
> > coming next, once SystemVMs have to boot.
> >
> > System VMs nevers successfully boot, they are stuck in an endless loop
> > cycle (start-stop-start…)
> >
> > logs attached to this email report:
> >
> > > Deploy avoids pods: null, clusters: null, hosts: null
> > > Unable to create a deployment for VM
> >
> > My config has enough ressources to run the management server and the xen
> > one in an virtualyzed environment
> >
> > I highly suspect a network misconfiguration, everything should be OK
> > since i replicate the config from shapeblue:
> >
> > PRI STORAGE 10.10.100.11
> >
> > SECONDARY STORAGE 10.10.101.11
> >
> > MGMT TRAFFIC SERVER 192.168.56.11
> >
> > XEN 192.168.56.101
> >
> > POD SETTINGS 192.168.56.1 (21 - 30)
> >
> > PUBLIC TRAFFIC 172.30.0.(21 - 30 )
> >
> > Maybe something is wrong on the MGMT network ? but since i can ping IPs
> > properly I suspect something more tricky.
> >
> > If someone could help me giving a look faulty parameters, I can'f figure
> > out why my cluster and pod load as null value and make the next
> > processes messy
> >
> > Thanks
> >
> >
> > Xen hypervisor seems good regarding
> > storage:10.10.100.11:/exports/primary/ on
> > /run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs
> >
> >
> (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11)
> > 10.10.101.11:/exports/secondary on
> > /var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4
> >
> >
> (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
> >
> >
> >
> >
>
> --
>
> Andrija Panić
>
Re: Unable to create a deployment for VM
Posted by Andrija Panic <an...@gmail.com>.
Hi,
that is the famous setup article from one of CloudStack conferences, if I'm
not mistaken - but since things have changed "a bit" during last 4 years
(both cloudstack and the XenServer versions), that means that probably some
steps might be missing (just a guess)
Anyway, since system VM is not starting at all - I would suggest to take a
look into systemVM template - which you should have preseeded during the
installation process with the "*cloud-install-sys-tmplt*" script - check
template state in GUI if it says "OK" under "Ready" section (go to specific
template, click on Zones, and there you will read it). Alternatively, make
sure that HOST is in connected/up/routing state - can be observer from
Infrastructure-->Hosts.
Otherwise, is systemVM template is OK, than the HOST (xenserver) should be
able to mount Secondary Storage (your emails says it works fine...) and
start the VM from the template (later patch systemVM etc etc...)
I would also suggest perhaps trying a more up to date tutorial, from the
original documentation for 4.11 release (http://docs.cloudstack.apache.org)
and check your steps with XenServer.
Alternatively, if you are willing to play with KVM, there is also a very
Quick Installation Guide for CenOS6 (outdated, being updated as we speak) -
while updated version (not final but with some comments) can be found here:
https://github.com/apache/cloudstack-documentation/blob/cae56e460902b7b4efde426b9cc88e512a1c9076/source/quickinstallationguide/qig.rst
If nothing helps, please share management.log file content (pastebean or
similar) so we can check.
I'm personally not aware of specific agent logs on XenServer, but I assume
there are some logs from XenServer itself which you could collect as well.
Cheers
Andrija
On Thu, 25 Oct 2018 at 00:41, fulc927 <fu...@gmail.com> wrote:
> Hello,
>
> First my environment is built following this tutorial
> https://www.shapeblue.com/virtualbox-test-env/
>
> I am trying to setup properly Cloudstack as a proof-of-concept and
> eventually adopting it in more sophisticated configuration
>
> I am using cloudstack-management-4.11 and Citrix XenServer Host 7.5.0
>
> I successfully create a zone and a primary storage, bad things are
> coming next, once SystemVMs have to boot.
>
> System VMs nevers successfully boot, they are stuck in an endless loop
> cycle (start-stop-start…)
>
> logs attached to this email report:
>
> > Deploy avoids pods: null, clusters: null, hosts: null
> > Unable to create a deployment for VM
>
> My config has enough ressources to run the management server and the xen
> one in an virtualyzed environment
>
> I highly suspect a network misconfiguration, everything should be OK
> since i replicate the config from shapeblue:
>
> PRI STORAGE 10.10.100.11
>
> SECONDARY STORAGE 10.10.101.11
>
> MGMT TRAFFIC SERVER 192.168.56.11
>
> XEN 192.168.56.101
>
> POD SETTINGS 192.168.56.1 (21 - 30)
>
> PUBLIC TRAFFIC 172.30.0.(21 - 30 )
>
> Maybe something is wrong on the MGMT network ? but since i can ping IPs
> properly I suspect something more tricky.
>
> If someone could help me giving a look faulty parameters, I can'f figure
> out why my cluster and pod load as null value and make the next
> processes messy
>
> Thanks
>
>
> Xen hypervisor seems good regarding
> storage:10.10.100.11:/exports/primary/ on
> /run/sr-mount/3473326c-6813-97dc-fd85-9f221d59892f type nfs
>
> (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=100,retrans=12,sec=sys,mountaddr=10.10.100.11,mountvers=3,mountport=892,mountproto=tcp,local_lock=none,addr=10.10.100.11)
> 10.10.101.11:/exports/secondary on
> /var/cloud_mount/fb486192-aa16-30d2-9278-c5704f273389 type nfs4
>
> (rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,soft,proto=tcp,port=0,timeo=133,retrans=1,sec=sys,clientaddr=10.10.101.101,local_lock=none,addr=10.10.101.11)
>
>
>
>
--
Andrija Panić