Increase the memory with reboot / shutdown the VM

[jegan]

hello,

I create the VM with 2 GB memory and 2 core CPU, Now I want increase the memory 4GB but without reboot / shutdown the VM.

Increase the memory with reboot / shutdown the VM.

root@proxmox1:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"

root@proxmox1:~# pveversion -v
proxmox-ve: 6.2-2 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-12 (running version: 6.2-12/b287dd27)
pve-kernel-5.4: 6.2-7
pve-kernel-helper: 6.2-7
pve-kernel-5.4.65-1-pve: 5.4.65-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.5
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
proxmox-backup-client: 0.8.19-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-12
pve-cluster: 6.1-8
pve-container: 3.2-2
pve-docs: 6.2-6
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-1
pve-qemu-kvm: 5.1.0-2
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

 

[Moayad]

I create the VM with 2 GB memory and 2 core CPU, Now I want increase the memory 4GB but without reboot / shutdown the VM.

if you change the RAM, you need to power off your VM.
Also a reboot of the windows guest is not enough.

 

[jegan]

hello,

thanks for your reply.

Actually I am doing vertical scaling for this VMs. If we continuous reboot the server. it's may get corrupted.

So There is any alternative way for the "vertical scaling" in proxmox VMs.

 

[Moayad]

Actually I am doing vertical scaling for this VMs. If we continuous reboot the server. it's may get corrupted.

No need reboot the server only VM stop and start like qm stop VMID && qm start VMID

 

[rcd]

No need reboot the server only VM stop and start like qm stop VMID && qm start VMID

Wait - doesn't qm stop implicitly reboot the server? Or does it like suspend/hibernate/freeze it first, so that it can continue unbooted after qm start? Otherwise I don't get the point?

I always assumed qm stop is like a qm shutdown without being nice about it.

 

[Moayad]

I always assumed qm stop is like a qm shutdown without being nice about it.

no not the same.
The qm shutdown VMID is like a clean shutdown, and the qm stop VMID is like a pulling power plug of a device.

check man page of qm cli [0]

[0] https://pve.proxmox.com/pve-docs/qm.1.html

 

[rcd]

no not the same.
The qm shutdown VMID is like a clean shutdown, and the qm stop VMID is like a pulling power plug of a device.

check man page of qm cli [0]

[0] https://pve.proxmox.com/pve-docs/qm.1.html

Right, that was also how I expected it to be. The previous post can be a bit misleading then.