Bug 566261

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

http://www.redhat.com/archives/libvir-list/2010-February/msg00537.html

Built fix into libvirt-0.7.6-3.el5

That version should of course have said libvirt-0.7.6-3.el6

Well, I cannot even test whether this was fixed because with

[root@johanka ~]# rpm -qa libvirt\* qemu\*
libvirt-0.7.6-3.el6.x86_64
qemu-kvm-0.12.1.2-2.17.el6.x86_64
libvirt-client-0.7.6-3.el6.x86_64
qemu-img-0.12.1.2-2.17.el6.x86_64
libvirt-python-0.7.6-3.el6.x86_64
[root@johanka ~]# 

I get this when starting a virtual machine from virt-manager:

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/engine.py", line 588, in run_domain
    vm.startup()
  File "/usr/share/virt-manager/virtManager/domain.py", line 150, in startup
    self._backend.create()
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 300, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error error running QEMU command '{"execute":"qmp_capabilities","timestamp":{"seconds":1267266649,"microseconds":673361}}': CommandNotFound ('{"error":{"class":"CommandNotFound","desc":"The command qmp_capabilities has not been found","data":{"name":"qmp_capabilities"}}}')

*** Bug 581852 has been marked as a duplicate of this bug. ***

*** Bug 580594 has been marked as a duplicate of this bug. ***

*** Bug 586909 has been marked as a duplicate of this bug. ***

Event posted on 05-04-2010 12:28pm EDT by Glen Johnson

------- Comment From agl.com 2010-05-04 12:14 EDT-------
Snap1 contains an update of the libvirt package to
libvirt-0.8.0-3.el6.x86_64.  This update contains the upstream fix for the
issue and I can no longer reproduce the problem.


This event sent from IssueTracker by jkachuck 
 issue 819173

*** Bug 590188 has been marked as a duplicate of this bug. ***

*** Bug 591979 has been marked as a duplicate of this bug. ***

How can we get libvirt-0.8.0-3.el6.x86_64 ?

FYI this bug is a result of QEMU changing to use  bytes instead of kilobytes in the balloon monitor command. The corresponding change to libvirt was missed, so all guests got ballooned to unusably small memory sizes.

*** Bug 591784 has been marked as a duplicate of this bug. ***

Verified PASSED with libvirt-0.8.1-8.el6.x86_64.
- kernel-2.6.32-33.el6.x86_64
- qemu-img-0.12.1.2-2.73.el6.x86_64
- qemu-kvm-0.12.1.2-2.73.el6.x86_64

Change this bug status to VERIFIED.

Could you also verify virt-top:

# rpm -qf `which virt-top `
virt-top-1.0.4-3.1.el6.x86_64



virt-top 00:55:20 - x86_64 4/4CPU 2600MHz 8002MB
6 domains, 6 active, 6 running, 0 sleeping, 0 paused, 0 inactive D:0 O:0 X:0
CPU: 8.0%  Mem: 1572864 MB (1572864 MB by guests)

   ID S RDRQ WRRQ RXBY TXBY %CPU %MEM    TIME   NAME
    5 R             52    0  1.6 100    0:57.64 bulk1
    4 R            142   90  1.3 100    1:06.69 backups1
    6 R            142   90  1.3 100    0:45.92 current1
    3 R             52    0  1.3 100    1:41.83 cvs1
    2 R             52    0  1.2 100  597:09.34 mirror1
    1 R              0    0  1.2 100  590:04.28 openbsd47

the result just be expected for virt-top.

# virsh dumpxml demo
......
  <memory>1048576</memory>
  <currentMemory>1048576</currentMemory>
......

virt-top 11:52:54 - x86_64 4/4CPU 2000MHz 7398MB
3 domains, 1 active, 1 running, 0 sleeping, 0 paused, 2 inactive D:0 O:0 X:0
CPU: 0.2%  Mem: 1024 MB (1024 MB by guests)

   ID S RDRQ WRRQ RXBY TXBY %CPU %MEM    TIME   NAME                            
    1 R    0    0    0    0  0.2 13.0   0:53.41 demo
    -                                           (rhel68)
    -                                           (win2003)

# virsh dumpxml win2003
......
  <memory>524288</memory>
  <currentMemory>524288</currentMemory>
......

virt-top 11:59:19 - x86_64 4/4CPU 2000MHz 7398MB
3 domains, 2 active, 2 running, 0 sleeping, 0 paused, 1 inactive D:0 O:0 X:0
CPU: 5.4%  Mem: 1536 MB (1536 MB by guests)

   ID S RDRQ WRRQ RXBY TXBY %CPU %MEM    TIME   NAME                            
    5 R  974   69   98    0  5.2  6.0   0:12.62 win2003
    1 R    0    0    0    0  0.2 13.0   0:55.57 demo
    -                                           (rhel68)


edit win2003's mem from 512M to 1024M

virt-top 11:54:10 - x86_64 4/4CPU 2000MHz 7398MB
3 domains, 2 active, 2 running, 0 sleeping, 0 paused, 1 inactive D:0 O:0 X:0
CPU: 4.1%  Mem: 2048 MB (2048 MB by guests)

   ID S RDRQ WRRQ RXBY TXBY %CPU %MEM    TIME   NAME                            
    4 R  793   17  104    0  3.9 13.0   0:10.79 win2003
    1 R    0    0    0    0  0.2 13.0   0:53.86 demo
    -                                           (rhel68)

Red Hat Enterprise Linux Beta 2 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.