Hi Ahmad, CS doesn't support export CPU topology to guest VM even though some hypervisor supports it. Like you described, this feature might be critical to some Guest OSes , like windows 2008 server. Please file a feature request for this.
Anthony > -----Original Message----- > From: Ahmad Saif [mailto:ahmad.abos...@gmail.com] > Sent: Tuesday, January 08, 2013 2:24 AM > To: cloudstack-users@incubator.apache.org > Subject: How to export CPUs as Cores not Sockets > > Dear CloudStackers, > > I've hit a very weird situation last night, I've a VM that's running > (Windows 2008 Standard R2 64bit) which was working on a 4 cores offer. > when I upgraded the service offer to 8 cores and checked the VM I > notecied that it still have only 4 cores !! > > I dig a little bit on the windows machine itself, and found that it see > the CPUs as sockets not cores and this version of windows support only > up to 4 cores. > > I'm running CloudStack on KVM hosts, so when I checked the VM XML file > on the host I saw that the CPU is exported as following : > > <vcpu>4</vcpu> > > and it should be exported as following: > > <vcpu>4</vcpu> <cpu> > <topology sockets='1' cores='4' threads='1'/> > </cpu> > > So it export the CPU as cores not socket. how can I change this > behavior ? > > Any suggestions ? > > Thanks > >
