PLD, One thing to add to your testing is template management. When I was doing all the Packer stuff with XS 6.5 and 7, ACS needed to know if the template was PV or HVM to provision properly. No idea if the ACS template logic has changed since then, but something to be aware of.
>From a performance perspective with XS 6.5 started having newer XS templates follow an HVM model. e.g. CentOS 7 on XS 6.5 was HVM not PV. iirc, the performance difference was negligible on reasonably new CPUs (Sandy Bridge+ I think). -tim On Mon, Jan 8, 2018 at 9:39 PM, Ivan Kudryavtsev <kudryavtsev...@bw-sw.com> wrote: > Hi. Every kind of virtualization is affected according to qemu developers. > > 9 янв. 2018 г. 9:32 пользователь "Pierre-Luc Dion" <pd...@cloudops.com> > написал: > > > Hi, > > > > From recent blog post, I've read that system using full virtualization > such > > as KVM, VMware or Xen-HVM are not affected? Anyhow, from the latest > hotfix > > of XenServer 7.1cu1 hf8, it look like they systematically convert VM from > > PV to HVM, so in the case of a VM stop/start by CloudStack, a PV vm would > > be restarted as HVM. > > > > Look like this could be problematic if your VM kernel does not support > > both, we've just starting tested and so far look like our Debian systemvm > > template work fine, it can be created as HVM. > > > > Another point is that Citrix released an hotfix for xs7.2, 7.3 but not > for > > 7.1, you need to cumulative update to remain on 7.1 which is LTS. > > > > And last, does anyone did some benchmark before and after the kernel fix > > for Meltdown ? Some report state 30-35% cpu usage increase (not > hypervisor > > specific) and Lucian [1] might indicate it would depend on the cpu > model. > > Any metrics to share ? We are doing some tests on our side we should be > > able to share some stuff soon... > > > > Regards, > > > > [1] http://markmail.org/thread/wkzze3n24mns274x > > >
