Sebastian, XenServer 7.1 and 7.2 aren't supported in 4.9.x - the main fix is to add the guest OS mappings to the database. These have been added for 4.11, but there seems to be a slight change in behaviour in XS7.1 when adding a host to a cluster which is confusing CloudStack.
Kind regards, Paul Angus [email protected] www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -----Original Message----- From: Sebastian Gomez [mailto:[email protected]] Sent: 28 December 2017 08:08 To: [email protected] Subject: Re: Upgrading to XenServer 7.x Hi all. I had a similar problem, but usign XenServer 7.2. It was a fresh installation from scratch. The system vms where created, but them *could'nt get the local link IP*, so the cloudstack agent never went up. After that, I found the compatibility matrix, where its specified that the compatible versions of XenServer are up to 7.0... http://docs.cloudstack.apache.org/projects/cloudstack-release-notes/en/4.9.2.0/compat.html#supported-hypervisor-versions That's the point where I'm, trying to configure them with XS 7.0, but unfortunately XS 7.0 does not provide drivers for our Broadcom BCM57412 10Gb network eth adapters. Here we are, working on how to add the drivers... Good luck! Atentamente, Sebastián Gómez On Tue, Dec 26, 2017 at 5:12 PM, Pierre-Luc Dion <[email protected]> wrote: > Hi, > > Just as FYI, we recently upgrade from 6.5 to xs 7.1, so far everthing > is good. Then we add some hosts to Pool or reinstall some XenServer to > have proper new filesystem on dom0 which have more disk space for /var/log! > then we ran into the situation where CloudStack fail to create > Virtual Router in a XenServer cluster. Turns out that for some unknown > reason, adding a fresh installed xenserver to a cluster can create new > SR and VDI for xs-tools iso, this break cloudstack VR creation for > some reason. So the easy fix is to forget non-shared SR containing xs-tools > VDI. > > Basically, if "xe vdi-list is-tools-iso=true" return more than one > iso, CloudStack should fail to create Virtual-Router. >
