Mailing-List: contact cloudstack-users-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-users@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
MIME-Version: 1.0
In-Reply-To: <2018874769.7125416.1354034414097.JavaMail.root@inria.fr>
References: <1705008077.7111993.1354033846835.JavaMail.root@inria.fr>
 <2018874769.7125416.1354034414097.JavaMail.root@inria.fr>
From: David Nalley <david@gnsa.us>
Date: Tue, 27 Nov 2012 11:50:11 -0500
Message-ID: 
 <CAKprHVYxyBbPRgqHkHn8AQuHnmTrnJnwE4ty_LCML-Rk=-C8Gw@mail.gmail.com>
Subject: Re: Cloudstack + kvm : set arch = i686
To: "cloudstack-users@incubator.apache.org"
 <cloudstack-users@incubator.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 27, 2012 at 11:40 AM, Julien Garet <julien.garet@inria.fr> wrot=
e:
> Hello,
>
>
> We have discovered something today we didn't expect... We are using CS 3.=
0.2 with KVM hypervisors. Our users want to be able to use 32 or 64 bits VM=
s, so, we have set up templates using 32 or 64 bits OSes (setting OS type 3=
2 or 64 bits accordingly), but that does not have any impact on the VM depl=
oyed... arch option in the domain xml file is x86_64, whatever we choose as=
 OS Type.
>
>
> Is there a way to deploy 32bits VMs on 64bits hypervisors ?
>
>

The arch of the operating system is different than the arch of the
virtualized CPU (which is what I think you are referring to).
What benefit do you expect to extract from having a virtualized 32bit
CPU compared to a virtualized 64bit cpu? Do users that have physical
machines in your environment note that you deployed a 32bit OS on a
64bit CPU?

--David