[
https://issues.apache.org/jira/browse/CLOUDSTACK-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nux closed CLOUDSTACK-5945.
---------------------------
Resolution: Won't Fix
> Expand Upscaling feature to KVM
> -------------------------------
>
> Key: CLOUDSTACK-5945
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5945
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Hypervisor Controller, KVM
> Affects Versions: 4.3.0
> Environment: CentOS 6.5 KVM
> Reporter: Nux
> Labels: kvm, upscale
>
> Hello,
> Scaling up memory and cpu works well on KVM/libvirt, too. Here's what needs
> to happen to make it so:
> - the domain's libvirt xml file needs to contain the maximum number of CPUs -
> aka the number of cpu from the template with most CPUs:
> <vcpu placement='static' current='3'>6</vcpu>
> that means currently the VM uses 3 CPUs, but it can scale up to 6.
> To scale it up live to 6 you'd just do:
> virsh setvcpus 1-2-3-VM --live --count 6
> - the domain's libvirt xml file needs to contain the following about memory:
> <memory unit='KiB'>3072000</memory>
> <currentMemory unit='KiB'>1048576</currentMemory>
> that means the VM can scale up to 3000 MB, but currently only uses 1024 MB.
> To scale it up live to 3000MB you'd have to do:
> virsh setmem 1-2-3-VM --size 3072000
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
