Hello.
Actually it was my mistake.
After some time using memory in guest (find /, cp bigfine, etc), res
size of qemu process shrinks to expected value.
Sorry for disturbing.
Now i don't see any memory waste in guest and host when using 'base'
memory + 'dimm' memory.
Although i have one issue.
When i start qemu via libvirt with 16GB mem and 1G current mem:
(...)
<memory unit='KiB'>16777216</memory>
<currentMemory unit='KiB'>1048576</currentMemory>
(...)
Qemu starts, and balloon can't free memmory, so guest doesn't boot (It
hangs or is looped in ' virtio_balloon virtio2: Out of puff! Can't get 1
pages').
I think this is because dimm memmory is not yet onlined, and balloon
already tries to shring memory in guest.
Best regards
Piotr Rybicki
W dniu 2015-06-18 o 23:23, Andrey Korolyov pisze:
Do You see similar results at Your side?
Best regards
Would you mind to share you argument set to an emulator? As far as I
understood you are using plain ballooning with most results from above
for which those numbers are expected. The case with 5+gig memory
consumption for deflated 1G guest looks like a bug with mixed
dimm/balloon configuration if you are tried against latest qemu, so
please describe a setup a bit more verbosely too.
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list