cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kirk Jantzer <kirk.jant...@gmail.com>
Subject Re: CloudStack exports vCPU as socket, not core
Date Thu, 16 May 2013 11:15:26 GMT
Yes.

Regards,

Kirk Jantzer
http://about.me/kirkjantzer
On May 16, 2013 7:12 AM, "Stanley Kaytovich" <StanleyK@qwertyc.com> wrote:

>  I suppose the same goes for esx?
>
> Kirk Jantzer <kirk.jantzer@gmail.com> wrote:
>
>
> At present, I believe what you suggested is the only solution. We're
> looking to use XCP instead of XenServer as our hypervisor - XCP allows for
> this option, whereas you need at least the advanced license of XenServer to
> be able to utilize this feature.
>
>
> On Wed, May 15, 2013 at 5:50 PM, Stanley Kaytovich <StanleyK@qwertyc.com
> >wrote:
>
> > CloudStack: 4.0.2
> > -----------------------------------------------------
> >
> > Hi All,
> >
> > Similar to this bug report:
> > https://issues.apache.org/jira/browse/CLOUDSTACK-904, we're having the
> > same issue. All VMs are created with sockets instead of cores. This is a
> > huge issue since some OSes are limited to the number of sockets they can
> > have.
> >
> > Anyone found a solution/workaround for this? Seems like editing the
> > machine after it was created is the only option so far.
> >
> > Thanks in advance,
> > Stan
> >
>
>
>
> --
> Regards,
>
> Kirk Jantzer
> c: (678) 561-5475
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message