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 894967 - [virtio-win][balloon][win2012]Balloon cannot change to the expected value after resume from S4
Summary: [virtio-win][balloon][win2012]Balloon cannot change to the expected value aft...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: virtio-win
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: pre-dev-freeze
: 7.1
Assignee: Gal Hammer
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-14 07:21 UTC by Min Deng
Modified: 2014-11-26 18:33 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-11-26 18:33:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Min Deng 2013-01-14 07:21:40 UTC
Description of problem:
Hibernate guest while changing balloon size and after resume the guest the balloon size change to the original value claimed in CLI but not the expected one.

Version-Release number of selected component (if applicable):
kernel-2.6.32-353.el6.x86_64
qemu-kvm-rhev-0.12.1.2-2.351.el6.x86_64

How reproducible:
4 times 4 failed
Steps to Reproduce:
1.CLI
  /usr/libexec/qemu-kvm -m 6G -smp 4 -cpu Westmere,+sep,family=0xf -usb -device usb-tablet -drive file=win2012-active.raw,format=raw,serial=mike,if=none,id=drive-virtio0,cache=none,werror=stop,rerror=stop,boot=on -device ide-drive,drive=drive-virtio0,id=virtio-blk-pci0,bootindex=1 -uuid `uuidgen` -no-kvm-pit-reinjection -monitor stdio -vnc :1 -rtc base=localtime,clock=host,driftfix=slew -chardev socket,id=seabios_debug,path=/tmp/monitor-seabios,server,nowait -device isa-debugcon,iobase=0x402,chardev=seabios_debug -M rhel6.4.0 -vga cirrus -drive file=test.raw,format=raw,serial=mike,if=none,id=drive-virtio1,cache=none,werror=stop,rerror=stop -device virtio-blk-pci,addr=0x9,drive=drive-virtio1,id=virtio-blk-pci1 -device virtio-serial-pci,id=virtio-serial0,max_ports=16 -chardev socket,id=channel0,path=/tmp/helloworld,server,nowait -device virtserialport,chardev=channel0,name=com.redhat.rhevm.vdsm,bus=virtio-serial0.0,id=port0 -chardev socket,id=channel1,path=/tmp/helloworld1,server,nowait -device virtserialport,chardev=channel1,name=com.redhat.rhevm.vdsm1,bus=virtio-serial0.0,id=port1 -device virtio-balloon-pci,addr=0x6,bus=pci.0 -netdev tap,sndbuf=0,id=hostnet1,script=/etc/qemu-ifup,downscript=no -device e1000,netdev=hostnet1 -chardev socket,id=111a,path=/tmp/tt,server,nowait -mon chardev=111a,mode=readline -global PIIX4_PM.disable_s3=0 -global PIIX4_PM.disable_s4=0
2.install the balloon driver - virtio-win-prewhql-01-44 (whql version)
3.Go to monitor
(qemu) info balloon
balloon: actual=6144
(qemu) info balloon
balloon: actual=6144
(qemu) 
(qemu) 
(qemu) 
(qemu) balloon 1000
(qemu) info balloon
balloon: actual=5136
4.Do hibernate - shutdown /h
Actual results:
The guest resumed back successfully but the balloon size is 6144.
Expected results:
The expected size should be 1000 after a while.

Additional info:

Comment 2 Gal Hammer 2013-03-14 10:11:56 UTC
This bug says the opposite of the what is written in bz#804013.

What is the balloon's driver version?

Comment 3 Min Deng 2013-03-15 02:25:29 UTC
(In reply to comment #2)
> This bug says the opposite of the what is written in bz#804013.
> 
> What is the balloon's driver version?

Please have a look at step 2 that told you the exactly version(44).Any issues please let me know.

Best Regards,
Min

Comment 4 Vadim Rozenfeld 2013-03-24 12:24:26 UTC
Hi Min,
Could you please confirm that the same version still works on Win7?

Best regards,
Vadim.

Comment 5 Min Deng 2013-03-28 10:07:23 UTC
(In reply to comment #4)
> Hi Min,
> Could you please confirm that the same version still works on Win7?
> 
> Best regards,
> Vadim.

Hi Vadim,
   I tried the same version(44) on win7-32 OS and it is reproduced.
Best Regards,
Min

Comment 6 Vadim Rozenfeld 2013-03-28 11:52:06 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > Hi Min,
> > Could you please confirm that the same version still works on Win7?
> > 
> > Best regards,
> > Vadim.
> 
> Hi Vadim,
>    I tried the same version(44) on win7-32 OS and it is reproduced.
> Best Regards,
> Min

Thank you Min,
Does it mean that we have some sort of regression? Could you please trying
balloon driver from 6.3 on win7-32 to check if it works or not?

Best regards,
Vadim.

Comment 7 Amit Shah 2013-12-02 06:46:12 UTC
Balloon value is not stored across S4.  This is so that libvirt has exact control of the guest memory.  A balloon operation before s4 is not reflected after a resume.  The value from the cli will be taken in this case.

However, for S3, it should use the value set on the monitor.

So this looks like NOTABUG.

Comment 9 Ronen Hod 2014-09-16 12:32:41 UTC
Moving to RHEL7.
QE,
As Amit wrote in comment 7 this is not a bug. Can you try also with S3 please


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