yahoo-eng-team team mailing list archive

[Leslie Wang <wqyuwss@xxxxxxxxxxx>]

Public bug reported:

I'm using default m1.xlarge to create one VM whose OS is windows server
2008 R2 service Pack 1. The flavor has 8 CPU. When VM is started, it
shows the number of CPU is only 4.

I did some trouble shooting. I found when invoking KVM, the argument is
"kvm -smp 1,sockets=8,cores=1,threads=1 ". Sounds like in this case,
windows VM only recognises 4 socket, then show 4 CPU.

The only way I've discovered is to modify libvirt domain file, and add
below topology element.

  <cpu>
    <topology sockets='4' cores='2' threads='1'/>
  </cpu>

Then via virsh command, I manually modify the profile to this value, and
start the VM using virsh, then windows server VM can recognise 8 CPUs
now.

I suggest to divide CPU number to both socket and cores, thus it can be
applicable for many cases.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1265426

Title:
  wrong CPU number in windows VM

Status in OpenStack Compute (Nova):
  New

Bug description:
  I'm using default m1.xlarge to create one VM whose OS is windows
  server 2008 R2 service Pack 1. The flavor has 8 CPU. When VM is
  started, it shows the number of CPU is only 4.

  I did some trouble shooting. I found when invoking KVM, the argument
  is "kvm -smp 1,sockets=8,cores=1,threads=1 ". Sounds like in this
  case, windows VM only recognises 4 socket, then show 4 CPU.

  The only way I've discovered is to modify libvirt domain file, and add
  below topology element.

    <cpu>
      <topology sockets='4' cores='2' threads='1'/>
    </cpu>

  Then via virsh command, I manually modify the profile to this value,
  and start the VM using virsh, then windows server VM can recognise 8
  CPUs now.

  I suggest to divide CPU number to both socket and cores, thus it can
  be applicable for many cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1265426/+subscriptions