[GH-ISSUE #203] Resize RAM when VM runing #138

Closed
opened 2026-02-27 15:57:28 +03:00 by kerem · 10 comments
Owner

Originally created by @letran3691 on GitHub (Nov 7, 2018).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/203

I want Resize RAM a VM when it running. Must change where?
I did fix a paragraph code, can Resize. but it's not apply when running, must shutdown it applies
version old I fix success. after update version I can't fix it's :(

image

Originally created by @letran3691 on GitHub (Nov 7, 2018). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/203 I want Resize RAM a VM when it running. Must change where? I did fix a paragraph code, can Resize. but it's not apply when running, must shutdown it applies version old I fix success. after update version I can't fix it's :( ![image](https://user-images.githubusercontent.com/19284401/48124537-27d19180-e2af-11e8-978b-3d62a64a320e.png)
kerem closed this issue 2026-02-27 15:57:28 +03:00
Author
Owner

@catborise commented on GitHub (Nov 7, 2018):

you cannot change maximum allocation of memory while running.
but you should change current allocation of memory while instance is running.

which one you cannot change?

<!-- gh-comment-id:436599524 --> @catborise commented on GitHub (Nov 7, 2018): you cannot change maximum allocation of memory while running. but you should change current allocation of memory while instance is running. which one you cannot change?
Author
Owner

@letran3691 commented on GitHub (Nov 8, 2018):

I can't change any option at tab #RESIZE while VM running. when just shutdown VM, changes apply to VM

<!-- gh-comment-id:436874117 --> @letran3691 commented on GitHub (Nov 8, 2018): I can't change any option at tab #RESIZE while VM running. when just shutdown VM, changes apply to VM
Author
Owner

@catborise commented on GitHub (Nov 8, 2018):

i can work it on. but i need time..

<!-- gh-comment-id:436950321 --> @catborise commented on GitHub (Nov 8, 2018): i can work it on. but i need time..
Author
Owner

@letran3691 commented on GitHub (Nov 8, 2018):

Yes. Please help me!!!

<!-- gh-comment-id:436969364 --> @letran3691 commented on GitHub (Nov 8, 2018): Yes. Please help me!!!
Author
Owner

@letran3691 commented on GitHub (Nov 9, 2018):

When VM shutdown. I set "Current allocation (MB) 2G" and "Maximum allocation (MB) 8G "
image

But when I run VM then part "Current allocation " auto received "Maximum allocation 8G"
image

I don't know bug where

<!-- gh-comment-id:437234942 --> @letran3691 commented on GitHub (Nov 9, 2018): When VM shutdown. I set "Current allocation (MB) 2G" and "Maximum allocation (MB) 8G " ![image](https://user-images.githubusercontent.com/19284401/48240706-5910a580-e406-11e8-8479-3f5f659312f1.png) But when I run VM then part "Current allocation " auto received "Maximum allocation 8G" ![image](https://user-images.githubusercontent.com/19284401/48240749-8a897100-e406-11e8-954d-c78d8f56afaf.png) I don't know bug where
Author
Owner

@catborise commented on GitHub (Nov 9, 2018):

there is nothing change on resize code by me. but as you said it happens as described.
may be it was broken before.. i will check it.

<!-- gh-comment-id:437262929 --> @catborise commented on GitHub (Nov 9, 2018): there is nothing change on resize code by me. but as you said it happens as described. may be it was broken before.. i will check it.
Author
Owner

@catborise commented on GitHub (Nov 9, 2018):

i think it is default behaviour of KVM guests. While vm is starting it set maxiumu allocation. After boot up of instance, memory ballooning mechanism activates. Then if it is possible, it shrinks to current allocation.

to sum up, there is not any bug. but it is a feature :)

<!-- gh-comment-id:437265419 --> @catborise commented on GitHub (Nov 9, 2018): i think it is default behaviour of KVM guests. While vm is starting it set maxiumu allocation. After boot up of instance, memory ballooning mechanism activates. Then if it is possible, it shrinks to current allocation. to sum up, there is not any bug. but it is a feature :)
Author
Owner

@letran3691 commented on GitHub (Nov 9, 2018):

Yes. I check again and accurate as you say. But i can't #resize current memory while VM running. I did test Increase RAM while VM running with command "virsh setmem php-fpm_test 2049M --live", it's works normally.
Please help me can #resize while VM running. Please!!!

<!-- gh-comment-id:437274359 --> @letran3691 commented on GitHub (Nov 9, 2018): Yes. I check again and accurate as you say. But i can't #resize current memory while VM running. I did test Increase RAM while VM running with command "virsh setmem php-fpm_test 2049M --live", it's works normally. Please help me can #resize while VM running. Please!!!
Author
Owner

@catborise commented on GitHub (Nov 20, 2018):

hi @letran3691 i add online resize for memory, it appears to work. it is now on branch. but after some test i will merge it to master. link

<!-- gh-comment-id:440285930 --> @catborise commented on GitHub (Nov 20, 2018): hi @letran3691 i add online resize for memory, it appears to work. it is now on branch. but after some test i will merge it to master. [link](https://github.com/catborise/webvirtcloud/commit/44d73cc780bc1e5a5fef213c0b54536fab6c05a7)
Author
Owner

@letran3691 commented on GitHub (Nov 21, 2018):

thank you very much. but i have change a paragraph code file instance.html
github.com/catborise/webvirtcloud@44d73cc780 (r31376128)

<!-- gh-comment-id:440511992 --> @letran3691 commented on GitHub (Nov 21, 2018): thank you very much. but i have change a paragraph code file instance.html https://github.com/catborise/webvirtcloud/commit/44d73cc780bc1e5a5fef213c0b54536fab6c05a7#r31376128
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/webvirtcloud#138
No description provided.