You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nux (JIRA)" <ji...@apache.org> on 2014/01/25 12:19:38 UTC

[jira] [Commented] (CLOUDSTACK-5945) Expand Upscaling feature to KVM

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-5945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13881817#comment-13881817 ] 

Nux commented on CLOUDSTACK-5945:
---------------------------------

I retract my request as per MArcus comments on the ml:

"There are some issues with it. Last I checked, you can hotplug CPUs, but
you can't take them away (at least not for Linux guest os). Also, you can
scale memory, but it relies on balloon driver, which can simply be unloaded
by the guest to have access to all memory as the driver inside the guest
handles the memory size. I believe there was work on real memory hotplug,
but it might be awhile before that makes it to standard guest kernels."

> 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)