RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 566261 - doesn't cooperate with libvirt ... kilobytes/bytes misunderstanding
Summary: doesn't cooperate with libvirt ... kilobytes/bytes misunderstanding
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.0
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 580594 581852 586909 590188 591784 591979 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-17 18:08 UTC by Matěj Cepl
Modified: 2018-10-27 12:09 UTC (History)
9 users (show)

Fixed In Version: libvirt-0.7.6-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-02 19:29:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Comment 3 RHEL Program Management 2010-02-17 18:39:08 UTC 
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.
Comment 4 Daniel Berrangé 2010-02-18 10:59:56 UTC 
http://www.redhat.com/archives/libvir-list/2010-February/msg00537.html
Comment 5 Daniel Berrangé 2010-02-26 17:14:23 UTC 
Built fix into libvirt-0.7.6-3.el5
Comment 6 Daniel Berrangé 2010-02-26 17:14:51 UTC 
That version should of course have said libvirt-0.7.6-3.el6
Comment 8 Matěj Cepl 2010-02-27 10:33:43 UTC 
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"}}}')
Comment 9 Daniel Berrangé 2010-04-22 13:43:54 UTC 
*** Bug 581852 has been marked as a duplicate of this bug. ***
Comment 11 Jiri Denemark 2010-04-29 12:55:51 UTC 
*** Bug 580594 has been marked as a duplicate of this bug. ***
Comment 12 Daniel Berrangé 2010-04-30 08:33:32 UTC 
*** Bug 586909 has been marked as a duplicate of this bug. ***
Comment 13 Issue Tracker 2010-05-04 20:46:03 UTC 
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
Comment 14 Cole Robinson 2010-05-10 12:38:26 UTC 
*** Bug 590188 has been marked as a duplicate of this bug. ***
Comment 15 Daniel Berrangé 2010-05-13 17:11:19 UTC 
*** Bug 591979 has been marked as a duplicate of this bug. ***
Comment 16 Kirby Zhou 2010-05-17 04:15:56 UTC 
How can we get libvirt-0.8.0-3.el6.x86_64 ?
Comment 17 Daniel Berrangé 2010-06-07 15:21:30 UTC 
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.
Comment 18 Daniel Berrangé 2010-06-07 15:34:09 UTC 
*** Bug 591784 has been marked as a duplicate of this bug. ***
Comment 19 dyuan 2010-06-13 08:23:27 UTC 
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.
Comment 20 Mikolaj Kucharski 2010-06-17 23:58:07 UTC 
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
Comment 21 dyuan 2010-06-18 04:03:14 UTC 
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)
Comment 22 releng-rhel@redhat.com 2010-07-02 19:29:16 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.