HIGH MEMORY CONSUMPTION IN KMV WITH WINDOWS

[Victor Mendoza]

Hello community, I am writing to you presenting the following problems and I would like to receive some help:

I am using PROXMOX 4.4 on Debian Jessie.
I'm noticing that having a virtual machine with Windows in the Proxmox panel indicates a high consumption of RAM and when I enter the machine's desktop I can see that the consumption is normal. And this I think that causes Proxmox to restart the machine after an indefinite time on.

Unlike Virtual Machines with Linux work perfectly.

I will leave a sample image attached.

 

[killmasta93]

Enable ballooning and install the service on the windows machine

 

[Victor Mendoza]

Hello, enable the option ballooning and install the driver, the consumption of memory that shows the proxmox tends to be normal and the same in both parts but now the VM every so often I get BlueScreen. This happens only with Windows VM.

 

[Rhinox]

So you created Windows-VM with 4GB RAM, and now you are surprised Windows is trying to use those 4GB RAM, right?

 

[Victor Mendoza]

So you created Windows-VM with 4GB RAM, and now you are surprised Windows is trying to use those 4GB RAM, right?

In the main theme you can see the image of what I mean.

In the VM the consumption of ram memory is normal 200MB - 450MB
But in the statistics shown by the Proxmox panel is almost 4GB RAM and this makes after a while the machine is restarted.

When installing the driver and the ballooning service the ram consumption in proxmox goes down and shows what the VM is actually using but from time to time the machine crashes "BlueScreen".

 

[Victor Mendoza]

Revivo theme, I still can not solve.

 

[denos]

Which virtio version did you use to install the Balloon driver and service? I haven't had any problem with virtio-0.1.126 across several hundred Windows KVMs so you may want to try that version if you continue to have blue screens.

 

[Victor Mendoza]

Which virtio version did you use to install the Balloon driver and service? I haven't had any problem with virtio-0.1.126 across several hundred Windows KVMs so you may want to try that version if you continue to have blue screens.

I'm going to try your version of Virtio.
I am using the version of virtio-win-0.1.141
and I'm having blue screens.

 

[Victor Mendoza]

The problem persists to have installed the drivers with virtio disk 0.1.126

 

[Rhinox]

In the main theme you can see the image of what I mean.

In the VM the consumption of ram memory is normal 200MB - 450MB
But in the statistics shown by the Proxmox panel is almost 4GB RAM and this makes after a while the machine is restarted.

And where on the image you see that? I do not speak spanish/portuguese (or whatever language it is), yet I see your Windows-VM reports ~1.8GB free memory out of 4GB, so it is using ~2.2GB. That's much more than your 200-450MB...

 

[Vasu Sreekumar]

I am using Balloon driver for windows 2012 successfully.

For an 8GB KVM it as using almost 8GB earlier, after installing Balloon driver, it is reduced to less than 2GB.

 

[Victor Mendoza]

I am using Balloon driver for windows 2012 successfully.

For an 8GB KVM it as using almost 8GB earlier, after installing Balloon driver, it is reduced to less than 2GB.

When installing the Balloon driver from virtio version 0.1.141, the machine starts to have blue screens at every moment.

 

[mbaldini]

Can you post the output of

qm config 101

What Windows version are you using?

I have a lot of VM with various Windows version, all with balooning enabled, virtio drivers installed, balloon service installer inside Windows, and I get no blue screen.

You should try to update from proxmox 4.4 to latest 5.1

 

[Saroop P V]

When installing the Balloon driver from virtio version 0.1.141, the machine starts to have blue screens at every moment.

Bluescreen was an occasional guest on windows 2003 with old virtio.
But windows 2012 or 2016 with Virtio 0.1.141 is a charm.
Didn't see any Blue screen error on Windows 2012 and 2016 with vrtio 0.1.141
By the way, I didn't use proxmox 4.x , jumped from 3.4 to 5.1

 

[Vasu Sreekumar]

Yes 5.1 is the version I also use.

And balloonung works perfect.