OpenStack Compute (nova)

  1. Bug #1370390
  2. Comment #11

Comment 11 for bug 1370390

Revision history for this message
Tony Walker (tony-walker-h) wrote :

I'm seeing this on Kilo @ 2015.1.0. I have 2 NUMA flavors - one double the size of the other in terms of CPU and memory.
If I boot a new instance of the large type, all is well. If I boot the small, and resize to the large, the cputune section gets the correct shares for the large, but the <vcpupin> entries for the old. To compound the issue, the <numa> section contains the memory size of the smaller flavor resulting in:

qemu-system-x86_64: total memory for NUMA nodes (0x1c00000000) should equal RAM size (0x3800000000)

@sfinucan - what version did you find this fixed on?