Hi
During some testing of Proxmox VE (Currently still running with PVE 4.4), we have noticed some strange behaviour with some systems when memory hotplug is enabled.
First thing is Ubuntu 16.04. When we enable memory hotplug, the guest OS only sees 1GB of RAM even if a higher value was initially assigned. It does not matter whether the memory hotplug was enabled before or after the initial KVM VM guest install.
Since we run ERP applications on Ubuntu Linux, it is very important that we can hot add memory during peek usage at times like black friday, as these ERP applications are also running some webshops.
We have tested this with Debian 8 (Jessie) and observed the same behaviour.
But when using CentOS 6 and CentOS 7, we could enable after installation with no issues and the correct memory was reported by the OS and also registered when changed.
In all cases we did install the qemu-guest-agent from the OS repositories.
How would I overcome this issue Debian/Ubuntu?
The other issue is regarding Windows Server 2016. We currently have one VM running windows server 2016 standard edition with desktop. This was initially installed exactly like demonstrated here: https://forum.proxmox.com/threads/install-windows-2016-server-on-proxmox-ve-video-tutorial.31344/
Afterwards we enabled memory hotplug and observed, that although the system was assigned 6144MB of RAM, windows can only see 3584MB of RAM. We are using the stable VirtIO drivers (0.1.126).
If we disable memory hotplug, then all 6144MB are seen by windows.
Is this is an issue with the stable VirtIO drivers or something general with VirtIO?
During some testing of Proxmox VE (Currently still running with PVE 4.4), we have noticed some strange behaviour with some systems when memory hotplug is enabled.
First thing is Ubuntu 16.04. When we enable memory hotplug, the guest OS only sees 1GB of RAM even if a higher value was initially assigned. It does not matter whether the memory hotplug was enabled before or after the initial KVM VM guest install.
Since we run ERP applications on Ubuntu Linux, it is very important that we can hot add memory during peek usage at times like black friday, as these ERP applications are also running some webshops.
We have tested this with Debian 8 (Jessie) and observed the same behaviour.
But when using CentOS 6 and CentOS 7, we could enable after installation with no issues and the correct memory was reported by the OS and also registered when changed.
In all cases we did install the qemu-guest-agent from the OS repositories.
How would I overcome this issue Debian/Ubuntu?
The other issue is regarding Windows Server 2016. We currently have one VM running windows server 2016 standard edition with desktop. This was initially installed exactly like demonstrated here: https://forum.proxmox.com/threads/install-windows-2016-server-on-proxmox-ve-video-tutorial.31344/
Afterwards we enabled memory hotplug and observed, that although the system was assigned 6144MB of RAM, windows can only see 3584MB of RAM. We are using the stable VirtIO drivers (0.1.126).
If we disable memory hotplug, then all 6144MB are seen by windows.
Is this is an issue with the stable VirtIO drivers or something general with VirtIO?