Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of Edison.su@citrix.com designates
 66.165.176.63 as permitted sender)
From: Edison Su <Edison.su@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: RE: Windows support for KVM
Thread-Topic: Windows support for KVM
Thread-Index: AQHO5G6DuIE+JrlpqEmXte7PkKzTS5orn1RA
Date: Mon, 18 Nov 2013 23:26:22 +0000
Message-ID: 
 <77B337AF224FD84CBF8401947098DD8715C23B2F@SJCPEX01CL01.citrite.net>
References: 
 <CADq5e0zP+O8-u7VsDb-QmHCo10=sN9fL4iDQAE7Jh=dSD=ok5Q@mail.gmail.com>
In-Reply-To: 
 <CADq5e0zP+O8-u7VsDb-QmHCo10=sN9fL4iDQAE7Jh=dSD=ok5Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


> -----Original Message-----
> From: Arnaud Gaillard [mailto:arnaud.gaillard@xtendsys.net]
> Sent: Monday, November 18, 2013 6:56 AM
> To: dev@cloudstack.apache.org
> Subject: Windows support for KVM
>=20
> Hello,
>=20
> A few days ago I created a new Jira ticket for the support of topology in
> network offering for KVM. This is needed in order to support Windows VM i=
n
> KVM (currently the limitation are such that it is not really possible to =
deploy
> real Windows VM with this configuration).
>=20
> The JIRA is CLOUDSTACK-
> 5071<https://issues.apache.org/jira/browse/CLOUDSTACK-5071>
> and
> is refering to a bug opened before:
> CLOUDSTACK-904<https://issues.apache.org/jira/browse/CLOUDSTACK-904>
> .
>=20
> As I have received no comment on it, I would like to know if the support =
of
> topology in service offering was considered as a priority, and if the imp=
act on
> the GUI was studied?

Using whatever Vmware supported is good enough?, e.g. Add coresPerSocket on=
 the service offering and UI: http://kb.vmware.com/selfservice/microsites/s=
earch.do?language=3Den_US&cmd=3DdisplayKC&externalId=3D1010184

>=20
> Cheers!