Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D0A25200CE7 for ; Thu, 3 Aug 2017 06:04:43 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id CF2B216AC40; Thu, 3 Aug 2017 04:04:43 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E9D1116AC41 for ; Thu, 3 Aug 2017 06:04:42 +0200 (CEST) Received: (qmail 31252 invoked by uid 500); 3 Aug 2017 04:04:41 -0000 Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list dev@cloudstack.apache.org Received: (qmail 31238 invoked by uid 99); 3 Aug 2017 04:04:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Aug 2017 04:04:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 1CD07C39A2 for ; Thu, 3 Aug 2017 04:04:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.002 X-Spam-Level: ** X-Spam-Status: No, score=2.002 tagged_above=-999 required=6.31 tests=[AC_DIV_BONANZA=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=sg-or-id.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 4OsZZ0sg2gUf for ; Thu, 3 Aug 2017 04:04:28 +0000 (UTC) Received: from mail-qt0-f177.google.com (mail-qt0-f177.google.com [209.85.216.177]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 663475FCE2 for ; Thu, 3 Aug 2017 04:04:26 +0000 (UTC) Received: by mail-qt0-f177.google.com with SMTP id t37so1253221qtg.5 for ; Wed, 02 Aug 2017 21:04:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sg-or-id.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RF/KRwjEna7iczdrPxBX0jZLeNMBE+Gg9vE61RrNlOM=; b=eYXCbJi6n9j2grael6iQfRYj0bxNQeFhf0n6hQoxtEBkcPuxKzH/Nm7Lc8S50+uDlU HjK6jvEbmJnmJxsfKRc+zxV2MQi7aQ3ElUeEONSwDe80q+iz1Ez17f+kqjI8ovoU2ee9 w6P5NtCsy30C0CkfZaibJmJqHOPcIRODMR4xu92715ebJpmVvOZXxIe6nIsXepX6oaAl UJB2GsvfyoZ9UOMvVMdxIsewMfXJD9W1zv0SuHvke32MkstKu3WhSmTEVn8bkHZ37xBR w3HABljo1B4BpbmpQk4LDttJ8kE9OC8B/VFAtGBAisnUyVLbhtUezh354n71UypULYj2 6LjQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RF/KRwjEna7iczdrPxBX0jZLeNMBE+Gg9vE61RrNlOM=; b=qUk6c5TohYNpXlo7UlpauO0STKhSNGTBl1N0psy+Tcv+MzUdzWiln95EQzMI/F2cdP E6GE/QuzaikDfcM47jVUG0/PW1PkhgCNxNKwj3yZuA2Y7qrhmkaFhrle53DQs4RY2a+0 5ggHlxgzfBNwSNsEFS8vhQxmKspMtRQP5m3bGVZxblsEO94rNVJlp4WCGpTcaQn/0Kxb 5ygbcSNq0K1gdx89QHQUn68NVrYgwkudyZ3rBJ2qtxOdI0IziaqeC7fVZj4XgxQgdkrz XZH/5N+i/2K9k1fGregZAPZqq3WJ+DgbKeze8RmnWfc2HY+juDUJNPvYCZOT4HQ7aloM BQqw== X-Gm-Message-State: AIVw1110Os7ZgbgMdSlQYc40KkymPM8TTI4XzKOCSX2lAhXTlXxYH5i/ PUf7mJTakv0skPH6oYytp9nckYAcYJXRI3Q= X-Received: by 10.237.37.140 with SMTP id x12mr345290qtc.133.1501733065651; Wed, 02 Aug 2017 21:04:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.179.134 with HTTP; Wed, 2 Aug 2017 21:04:25 -0700 (PDT) In-Reply-To: <1749816808.899.1501601216438.JavaMail.zimbra@li.nux.ro> References: <1558762004.5137.1501516491471.JavaMail.zimbra@li.nux.ro> <504901664.77.1501519533658.JavaMail.zimbra@li.nux.ro> <1749816808.899.1501601216438.JavaMail.zimbra@li.nux.ro> From: Cloud List Date: Thu, 3 Aug 2017 12:04:25 +0800 Message-ID: Subject: Re: Windows Server 2016 - unable to boot ISO for installation To: dev Cc: users@cloudstack.apache.org Content-Type: multipart/alternative; boundary="001a114211e2ed08e70555d17917" archived-at: Thu, 03 Aug 2017 04:04:44 -0000 --001a114211e2ed08e70555d17917 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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-f= 26a40dc703a/failed-install-of-build-10041-in-the-kvm-virtual-machine-system= -thread-exception-not-handled?forum=3DWinPreview2014Setup 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/h= ypervisor/kvm.html Based on the above instruction, I would need to add some lines on agent.properties file as follows: =3D=3D=3D guest.cpu.mode=3Dcustom guest.cpu.model=3Dcore2duo =3D=3D=3D 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! 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 > > Let us know how it went :) > > -- > Sent from the Delta quadrant using Borg technology! > > Nux! > www.nux.ro > > ----- Original Message ----- > > From: "Cloud List" > > To: "users" > > Cc: "dev" > > 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 thi= s > > 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! wrote: > > > >> 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!" > >> > To: "users" > >> > Cc: "dev" > >> > Sent: Monday, 31 July, 2017 16:54:51 > >> > Subject: Re: Windows Server 2016 - unable to boot ISO for installati= on > >> > >> > What version of KVM? > >> > > >> > -- > >> > Sent from the Delta quadrant using Borg technology! > >> > > >> > Nux! > >> > www.nux.ro > >> > > >> > ----- Original Message ----- > >> >> From: "Cloud List" > >> >> To: "users" > >> >> Cc: "dev" > >> >> 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 downloade= d > >> >> 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: > >> >> > >> >> =3D=3D=3D > >> >> 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 > >> >> =3D=3D=3D > >> >> > >> >> 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 type= s: > >> >> "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 issue= s > and > >> >> can provide advise? > >> >> > >> >> Any advice is greatly appreciated. > >> >> > >> >> Thanks in advance. > >> >> > >> >> Cheers. > >> >> > >> >> > >> >> > >> >> ---------- Forwarded message ---------- > >> >> From: Andrija Panic > >> >> 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" > >> >> > >> >> > >> >> 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 > 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 defau= lt > >> HVM > >> >>> when using the new xenserver template for Windows 2016. > >> >>> My understanding is that if you run a VM in XenServer as HVM and y= ou > >> 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=C3=ADn < > >> >>> 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))=3DHVM for Windows Server 2016 VMs? > >> >>> > > >> >>> > > >> >>> > Do you know when will be available Windows Server 2016 as OS Typ= e? > >> >>> > > >> >>> > > >> >>> > Thanks > >> >>> > > >> >>> > > >> >>> > David > >> >>> > > >> >>> > > >> >>> > >> >> > >> >> > >> >> > >> >> -- > >> >> > >> > > Andrija Pani=C4=87 > --001a114211e2ed08e70555d17917--