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 <fulc...@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)
>
>
>
>
