We used to provide 2016 template for our users, with VirtIO preinstalled
inside OS (during building template), and then we simply choose OS type of
"Windows PV" - not related to Xen (we use KVM), but just FYI as parallel.

On 12 April 2017 at 15:57, Pierre-Luc Dion <pdion@cloudops.com> wrote:

> Hi David,
>
> When using pre xenserver 7, CloudStack deploy Windows 2016 vm as "Other (64
> bit)".
> I've made some test with XenServer 7.1  and Windows 2016 are default HVM
> when using the new xenserver template  for Windows 2016.
> My understanding is that if you run a VM in XenServer as HVM and you have
> xentools installed and up-to-date, your VM run in PVHVM mode which seems to
> be the best of both world.
>
> The coming release of ACS (4.10) should have updated ostype so windows 2016
> wouid use Windows 2016 template in xenserver 7+ instead of "Other (64
> bit)".
>
>
>
>
>
> On Wed, Apr 12, 2017 at 4:14 AM, David Amorín <
> david.amorin@adderglobal.com>
> wrote:
>
> > Hi all,
> > In our test environment based on CS 4.9.2 and XS 7.0, we are deploying
> VMs
> > with Windows Server 2016 as guest installation, using OS Type: "Other
> > (64-bit)" and so far everything is working fine. We understand that using
> > this option we are deploying full virtualized (HVM)
> >
> >
> > Do you know if there is any issue (error, performance, etc.) for using
> > "Other (64-bit))=HVM for Windows Server 2016 VMs?
> >
> >
> > Do you know when will be available Windows Server 2016 as OS Type?
> >
> >
> > Thanks
> >
> >
> > David
> >
> >
>



-- 

Andrija Panić