cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nux! <...@li.nux.ro>
Subject Re: Windows Server 2016 - unable to boot ISO for installation
Date Mon, 31 Jul 2017 16:45:33 GMT
It could be this
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.8_Release_Notes/known_issues_virtualization.html

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro

----- Original Message -----
> From: "Nux!" <nux@li.nux.ro>
> To: "users" <users@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-list@sg.or.id>
>> To: "users" <users@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.panic@gmail.com>
>> Date: Thu, May 4, 2017 at 4:49 AM
>> Subject: Re: OS Type: Windows Server 2016 - CS 4.9.2
>> To: "users@cloudstack.apache.org" <users@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 <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ć

Mime
View raw message