Why isn't my memory information being updated all the time?

T

Tinwen

New Member
Aug 19, 2024
29
0
1
1739788204404.png
1739788257691.png1739788307143.png

Moreover, the external and internal memory displays are inconsistent.

VM Operating system：ubuntu 22.04.05
1739788420428.png
The ballooning feature and QGA (QEMU Guest Agent) have been enabled.
1739788490558.png
 
Yes, it doesn’t return instantly as soon as the memory pressure is gone. Various things to consider: is the host truly no longer memory starved (<80%) this could have various reasons such as disk buffers or application/memory caches? Does your VM need more memory (I see 0 major page faults, so, no!).
 
guruevi said:
Yes, it doesn’t return instantly as soon as the memory pressure is gone. Various things to consider: is the host truly no longer memory starved (<80%) this could have various reasons such as disk buffers or application/memory caches? Does your VM need more memory (I see 0 major page faults, so, no!).
Click to expand...
However, all virtual machines on this host have undergone this stress test, and the display is normal. Also, by sending "info balloon" through the monitor, the memory data can be updated in a timely manner. The memory pressure on the host is not high. Only for VM 113, the memory data remains unupdated, regardless of whether the memory usage is decreased or increased.
The memory utilization of the host machine is approximately 22.3%. However, the memory utilization of other virtual machines undergoing stress tests is around 95%. Will this have an impact?
 
The `free -h` command shows the memory information of the virtual machine. The memory occupancy of the host machine is 23%.
 
yes, the VM will be a lot slower.
 
either you/something disabled the polling (does it work again if you cold-reboot the VM?), or the guest driver is broken (which you'd have to take up with the vendor/project of your guest OS ;)).
 
fabian said:
either you/something disabled the polling (does it work again if you cold-reboot the VM?), or the guest driver is broken (which you'd have to take up with the vendor/project of your guest OS ;)).
Click to expand...
There is a probability that it will return to normal after a cold start. How can I check if I have disabled it? However, if I enable KVM hardware virtualization, this problem will not occur again.
 
You must log in or register to reply here.
Top Bottom