Re: [libvirt] Bug in DOMINFO command when balloon driver is used on a vm with more then 8 GB of MaxMemory ?
On 03/22/2013 04:11 PM, fc lists wrote:
Hi ,
I have been banging my head on this for the last 8 hours ... and i really
need to know if is really a bug or i am doing something wrong.
Cleaning out my inbox, and I don't think I ever saw a reply to this one.
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.
It turned out to be a bug in qemu and not libvirt; it has since been
fixed for the upcoming qemu 1.5, and will probably be backported to
other stable builds (pester your distro to include the fix, if they
haven't already).
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.
Platform is Centos 6.4 (problem was present in 6.3 as well starting
with libvirt-0.9.10-21.el6.3.7 )
Then it looks like this bug is relevant to your setup:
https://bugzilla.redhat.com/show_bug.cgi?id=927336
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
Attachments:
- signature.asc (application/pgp-signature — 621 bytes)