Hi Lucian and all, Just a quick update, the problem was resolved after I added below lines into the host's agent.properties:
=== guest.cpu.mode=custom guest.cpu.model=core2duo === and restarted CloudStack agent. The VM is now able to boot-up from the Windows Server 2016 ISO without experiencing the BSOD issue. Many thanks for all the help in pointing me to the right direction! :) Cheers. -ip- On Thu, Aug 3, 2017 at 12:04 PM, Cloud List <cloud-l...@sg.or.id> wrote: > Hi Lucian, > > Good day to you, and thank you for your reply. > > From what I understand, once the hypervisor is managed by CloudStack > (using cloudstack-agent), we shouldn't use virt-manager to create VMs and > all VMs will have to be created through CloudStack, correct? > > I read further and based on below documentation: > > https://social.technet.microsoft.com/Forums/en-US/695c8997-52cf-4c30-a3f7- > f26a40dc703a/failed-install-of-build-10041-in-the-kvm- > virtual-machine-system-thread-exception-not-handled?forum= > WinPreview2014Setup > > I am using Sandy Bridge CPU and based on the above, it seems that we can > resolve the problem by setting the CPU type as follows: 'core2duo'. > > The question is how to change it through CloudStack, can I confirm that we > can do so by following the "Configure CPU model for KVM guest (Optional)" > instruction at below URL? > > http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.8/ > hypervisor/kvm.html > > Based on the above instruction, I would need to add some lines on > agent.properties file as follows: > > === > guest.cpu.mode=custom > guest.cpu.model=core2duo > === > > and then restart CloudStack agent for the changes to take affect. Is it > correct? Please correct me if I'm wrong. > > Looking forward to your reply, thank you. > > Cheers. > > -ip- > > > > > > On Tue, Aug 1, 2017 at 11:26 PM, Nux! <n...@li.nux.ro> wrote: > >> Hello, >> >> I am not in a position to test, but it should be fairly easy to; just >> power up virt-manager on the said Ubuntu hypervisor and try to create a >> Windows 2016 VM with <feature name='erms' policy='require'/> >> >> Let us know how it went :) >> >> -- >> Sent from the Delta quadrant using Borg technology! >> >> Nux! >> www.nux.ro >> >> ----- Original Message ----- >> > From: "Cloud List" <cloud-l...@sg.or.id> >> > To: "users" <us...@cloudstack.apache.org> >> > Cc: "dev" <dev@cloudstack.apache.org> >> > Sent: Tuesday, 1 August, 2017 04:11:06 >> > Subject: Re: Windows Server 2016 - unable to boot ISO for installation >> >> > Hi Lucian, >> > >> > Nice to hear from you again. Below is the KVM version (QEMU version, to >> be >> > exact) I am using: >> > >> > # kvm --version >> > QEMU emulator version 2.4.1, Copyright (c) 2003-2008 Fabrice Bellard >> > >> > I am using Ubuntu instead of CentOS for the KVM host, may I know if this >> > affects KVM running on Ubuntu as well? I am using Intel Xeon E5 series >> for >> > the hypervisor hosts, not too sure if it's supported and part of the >> Xeon E >> > series on the list? >> > >> > Looking forward to your reply, thank you. >> > >> > Cheers. >> > >> > -ip- >> > >> > >> > On Tue, Aug 1, 2017 at 12:45 AM, Nux! <n...@li.nux.ro> wrote: >> > >> >> It could be this >> >> https://access.redhat.com/documentation/en-US/Red_Hat_ >> >> Enterprise_Linux/6/html/6.8_Release_Notes/known_issues_virtu >> alization.html >> >> >> >> -- >> >> Sent from the Delta quadrant using Borg technology! >> >> >> >> Nux! >> >> www.nux.ro >> >> >> >> ----- Original Message ----- >> >> > From: "Nux!" <n...@li.nux.ro> >> >> > To: "users" <us...@cloudstack.apache.org> >> >> > Cc: "dev" <dev@cloudstack.apache.org> >> >> > Sent: Monday, 31 July, 2017 16:54:51 >> >> > Subject: Re: Windows Server 2016 - unable to boot ISO for >> installation >> >> >> >> > What version of KVM? >> >> > >> >> > -- >> >> > Sent from the Delta quadrant using Borg technology! >> >> > >> >> > Nux! >> >> > www.nux.ro >> >> > >> >> > ----- Original Message ----- >> >> >> From: "Cloud List" <cloud-l...@sg.or.id> >> >> >> To: "users" <us...@cloudstack.apache.org> >> >> >> Cc: "dev" <dev@cloudstack.apache.org> >> >> >> Sent: Monday, 31 July, 2017 03:31:45 >> >> >> Subject: Windows Server 2016 - unable to boot ISO for installation >> >> > >> >> >> Dear all, >> >> >> >> >> >> I am using CloudStack 4.8.1.1 with KVM hypervisor. I have downloaded >> >> >> Windows Server 2016 ISO but when I tried to boot up the ISO for >> >> >> installation and template creation, it immediately goes into Blue >> >> Screen / >> >> >> BSOD with below error messages: >> >> >> >> >> >> === >> >> >> Your PC ran into a problem and needs a restart. We'll restart for >> you. >> >> >> >> >> >> For more information about this issue and possible fixes, visit >> >> >> http://windows.com/stopcode >> >> >> >> >> >> If you call a support person, give them this info: >> >> >> Stop Code: SYSTEM THREAD EXCEPTION NOT HANDLED >> >> >> === >> >> >> >> >> >> and then it will go into restart, hit with the same error and keep >> on >> >> >> restarting on an infinite loop. >> >> >> >> >> >> I browse around and it seems the error is related to outdated or >> wrong >> >> >> driver (most probably display driver) or due to resources issues. >> Have >> >> >> tried to increase the resources to 8 GB RAM, 4 CPU cores and 60 GB >> of >> >> disk >> >> >> space, and the problem still persists. Have tried different OS >> types: >> >> >> "Other PV (64-bit)", "Other (64-bit)" and "Windows Server 2012 R2 >> >> >> (64-bit"), and problem still persists. >> >> >> >> >> >> I understand that Windows Server 2016 should work and some people >> have >> >> >> managed to get Windows Server 2016 VM and template up and running >> (see >> >> >> below email thread for example) -- anyone encountered similar >> issues and >> >> >> can provide advise? >> >> >> >> >> >> Any advice is greatly appreciated. >> >> >> >> >> >> Thanks in advance. >> >> >> >> >> >> Cheers. >> >> >> >> >> >> >> >> >> >> >> >> ---------- Forwarded message ---------- >> >> >> From: Andrija Panic <andrija.pa...@gmail.com> >> >> >> Date: Thu, May 4, 2017 at 4:49 AM >> >> >> Subject: Re: OS Type: Windows Server 2016 - CS 4.9.2 >> >> >> To: "us...@cloudstack.apache.org" <us...@cloudstack.apache.org> >> >> >> >> >> >> >> >> >> 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 <pd...@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.amo...@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ć >> > >
