Thanks, this is an unexpected behavior, because you are starting with
small amount of total memory exposed to a balloon at the beginning and
there should be no issues except if the inflation races with plugging
in new DIMMs (just a wild guess), dmesg output will be helpful there
as I pointed earlier.
Try to start qemu with small amount of 'base' memory (like 1GB), and add
(even have static defined, not hotplugged after boot) 8GB in DIMMs but
do not online it.
My guest see 1GB RAM, balloon see 9GB. At this state, try to shrink
guest RAM to 8GB. My guest becomes unresposive and kernel messages loops
witch similar string.
So, perhaps balloon shoud consider only onlined DIMM RAM and report 1GB
in my example.
Best regards
Piotr Rybicki
