The ESX driver doesn't account for resources that have been allocated without nova-compute. When nova-compute first launches, it polls the esx hypervisor for available resources and initializes the disk/memory/vcpu usage metrics with incorrect values (assumes all resources are available). Which can result in over allocation errors when provisioning new virtual machines.
How to reproduce:
1. Create a virtual machine on the ESX machine
2. Launch nova-compute
3. Check the "Hypervisor Summary" page on the dashboard
4. Notice that the disk/memory/vcpu usage doesn't reflect the virtual machine's(from step 1) allocated resources
The ESX driver doesn't account for resources that have been allocated without nova-compute. When nova-compute first launches, it polls the esx hypervisor for available resources and initializes the disk/memory/vcpu usage metrics with incorrect values (assumes all resources are available). Which can result in over allocation errors when provisioning new virtual machines.
How to reproduce:
1. Create a virtual machine on the ESX machine
2. Launch nova-compute
3. Check the "Hypervisor Summary" page on the dashboard
4. Notice that the disk/memory/vcpu usage doesn't reflect the virtual machine's(from step 1) allocated resources