© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
What I believe is happening: The hypervisor treats available VCPUs as sockets*cores. But when threads are assigned for VCPUs (via mechanisms in new blueprint).. that's what throws off the accounting, as it simply substracts guest VCPUs from the overall total VCPUs available. Suggestion would be to only count guest cores against the accounting (since that's what the hypervisor is calling an available VCPU.