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 1253163 - [Virtio 1.0] Memory balloon device does not work after migration unless a reboot
Summary: [Virtio 1.0] Memory balloon device does not work after migration unless a reboot
Keywords:
Status: CLOSED DUPLICATE of bug 1243750
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.2
Hardware: All
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: jason wang
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-13 07:16 UTC by Qunfang Zhang
Modified: 2015-08-14 06:15 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-14 06:15:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Qunfang Zhang 2015-08-13 07:16:09 UTC
Description of problem:
Boot up a RHEL7.2 guest with virtio-ballloon-pci with virtio 1.0 parameter, migrate guest to the destination host, and then balloon the guest memory. The value does not change. If I reboot the guest, the memory balloon with enlarge or shrink to the target value.  Test without virtio 1.0, the issue does not exist. 

Version-Release number of selected component (if applicable):
ppc64le:
Host:
kernel-3.10.0-302.el7.ppc64le
qemu-kvm-rhev-2.3.0-16.el7.ppc64le
Guest: 
kernel-3.10.0-300.el7.ppc64le

x86:
Host: 
kernel-3.10.0-300.el7.x86_64
qemu-kvm-rhev-2.3.0-16.el7.x86_64

Guest:
kernel-3.10.0-304.el7.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Boot up a guest with virtio-balloon (virtio 1.0)

 /usr/libexec/qemu-kvm -name qzhang_test -machine pc -m 8G -smp 4,sockets=2,cores=1,threads=2 -uuid 8aeab7e2-f341-4f8c-80e8-59e2968d85c2 -realtime mlock=off -nodefaults -monitor stdio -rtc base=utc -device virtio-scsi-pci,bus=pci.0,addr=0x5,id=scsi0 -drive file=RHEL-Server-7.2-64-virtio.qcow2,if=none,id=drive-scsi0-0-0-0,format=qcow2,cache=none -device scsi-hd,bus=scsi0.0,drive=drive-scsi0-0-0-0,bootindex=1,id=scsi0-0-0-0  -drive if=none,id=drive-scsi0-0-1-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,drive=drive-scsi0-0-1-0,bootindex=2,id=scsi0-0-1-0 -vnc :15 -msg timestamp=on -usb -device usb-tablet,id=tablet1  -vga std -qmp tcp:0:4666,server,nowait -netdev tap,id=hostnet1,script=/etc/qemu-ifup,vhost=on -device virtio-net-pci,netdev=hostnet1,id=net1,mac=00:54:5a:5f:5b:5c -device virtio-balloon-pci,bus=pci.0,addr=0x9,id=balloon0,disable-legacy=on,disable-modern=off


2. Boot the guest on destination host with "-incoming tcp:0:5800"

3. Balloon the guest memory:
(qemu) info balloon
balloon: actual=8192
(qemu) balloon 4096
(qemu) info balloon (after 3~5s)
balloon: actual=4096 

4.Migrate guest to destination host:
(qemu) migrate -d tcp:0:5800

6. On destination host:
(qemu)  info balloon
balloon: actual=4096 

7. On destination host:
(qemu)balloon 8000
(qemu)info balloon
balloon: actual=4096 

8. Reboot guest

9.  On destination host:
(qemu)info balloon
balloon: actual=8000

Actual results:
Memory balloon device does not work after migration unless a reboot

Expected results:
Memory balloon device should work after migration

Additional info:

Comment 4 jason wang 2015-08-14 06:15:29 UTC

*** This bug has been marked as a duplicate of bug 1243750 ***


Note You need to log in before you can comment on or make changes to this bug.