CloudStack 4.2.1 and XenServer 6.2

[Hugues Lepesant <hu...@lepesant.com>]

Hi all,

 
I spent a couple of days to make Cloudstack 4.2.1 working with XenServer 6.2, with the option to use local storage for systemVM.

 
To do so I follow this steps :

 
1. Do not download vhd-util as said in CloudStack 4.2 install guide, but use one provided by the XenServer 6.2 ISO (/usr/bin/vhd-util).

This version have the "-S" option, and resolv the issue https://issues.apache.org/jira/browse/CLOUDSTACK-5671

 
2. Use "xe network-param-set" to set network label.

Exemple : 

xe network-param-set uuid=<xenbrX uuid> name-label=Management/Guest/Public

 

And if you want to use Local SR for systemVM (my personal choice).

 
3. On XenServer host convert local storage from LVM to ext.

I followed this tutorail : http://xmodulo.com/2012/10/how-to-change-xenservers-local-storage.html

 
The local SR was 100% used. So no systemVM template can be copied, and the systemVM failed to start.

In /var/log/SMlog on the Xen host, with a full Local SR you can see :

 
xenserver-01 SM: [8005] ['/usr/bin/vhd-util', 'create', '--debug', '-n', '/dev/VG_XenStorage-3a1471bc-9362-84e2-
d6ff-483bc4681140/VHD-1a6ba480-26be-4a38-8c26-f5a7a839ae67', '-s', '2000', '-S', '2097152']
[...]

xenserver-01 SM: [13150] Not enough space! free space: 1493172224, need: 2109734912
Mar 14 22:19:01 xenserver-01 SM: [13150] Raising exception [44, There is insufficient space]
 
And the command 

 
/usr/bin/vhd-util create --debug -n /dev/VG_XenStorage-3a1471bc-9362-84e2-d6ff-483bc4681140/VHD-683585b9-a45f-4b96-b4d6-cedbecf7c0de -s 2000 -S 2097152

 
will failed with error not enough space on SR.

 
 
Now you can add your XenServer to Cloudstack, systemVM will be deployed and started.

 
My "first" two pences ;-)

Hug

Re: CloudStack 4.2.1 and XenServer 6.2

[elenhil <do...@gmail.com>]

Hugues Lepesant <hu...@...> writes:

> 
> Hi all,
> Hug
> 
> 


Hey! thanks for notes.
Also i want to mention that CS4.2.1 works well with XenServer local storages
based on LVM, not ext3.
I didn't configure this from the very beginning - firstly I hosted systemVMs
on iSCSI\NFS share, then i just enabled "system.vm.use.local.storage" in
global configuration and VMs just migrated without anything else

At least it worked for me