Description of the problem:

When the virsh setmem command is used to inflate the balloon on a VM to which 8GB of MaxMemory or more are allocated then the information reported with virsh dominfo , virsh dumpxml after the balloon change has been performed are wrong. 

The actual balloon is inflated correctly though and that is verifiable both in the vm itself and through the "virsh dommemstat" commands.

I *think* that is because the dommestat command will perform a proper query to find out the amount of ram currently used (and i can see that in the logs when issuing a dommestat command) 

2013-03-22 21:22:41.820+0000: 23181: debug : virJSONValueToString:1133 : result={"execute":"query-balloon","id":"libvirt-9"}

2013-03-22 21:22:41.820+0000: 23181: debug : qemuMonitorJSONCommandWithFd:265 : Send command '{"execute":"query-balloon","id":"libvirt-9"}' for write with FD -1

2013-03-22 21:22:41.820+0000: 23181: debug : qemuMonitorSend:903 : QEMU_MONITOR_SEND_MSG: mon=0x7f3d643eb5a0 msg={"execute":"query-balloon","id":"libvirt-9"}

2013-03-22 21:22:41.820+0000: 23179: debug : qemuMonitorIOWrite:461 : QEMU_MONITOR_IO_WRITE: mon=0x7f3d643eb5a0 buf={"execute":"query-balloon","id":"libvirt-9"}

but no entries are shown in the log for qemu-monitor when virsh dominfo is run, how does dominfo gather those informations?

I am going to raise a ticket on RED HAT bugzilla for this but was hoping to get some feedback here first to avoid raising a ticket for something that maybe i just misunderstood.