Bug #69
Virtual CPU support
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 1.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: |
Description
The CPU value in the template specifies the capacity requested by the VM. There is no way to specify the number of virtual CPUs for the VM, e.g. if you request a SMP.
Please check this mailing list thread, for more information
History
#1
Updated by Ruben S. Montero over 12 years ago
Added the proposed patch by Soren, thanks for this one :)
#2
Updated by Ruben S. Montero over 12 years ago
VCPU is now understand by the KVM and Xen drivers. By default this value is not set, and we rely on the hypervisor default behavior, usually 1 virtual CPU. However, a default value for VCPU can be set through the .conf files of the drivers for all the VMs.
I'll leave the ticket open till we update the documentation.
The change is r333, in the trunk. If any one is interested this can be safely backported to the 1.2 branch.
#3
Updated by Ruben S. Montero over 12 years ago
- Status changed from New to Closed
- Resolution set to fixed
The new attribute is now in the development documentation. Closing the ticket