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 612801 - balloon: win7 x86 guest quit with"virtio: trying to map MMIO memory" when checking balloon info using qmp
Summary: balloon: win7 x86 guest quit with"virtio: trying to map MMIO memory" when che...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-09 04:59 UTC by Shirley Zhou
Modified: 2015-03-05 00:51 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A virtual machine must be restarted after the installation of the kernel windows driver framework. If the virtual machine is not restarted it may crash when a memory balloon is operation is performed.
Clone Of:
Environment:
Last Closed: 2010-11-11 16:30:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Shirley Zhou 2010-07-09 04:59:22 UTC 
Description of problem:
win7 x86 guest quit with"virtio: trying to map MMIO memory" when checking balloon info using qmp 

Version-Release number of selected component (if applicable):
virtio-win-1.1.7-2
qemu-kvm-0.12.1.2-2.91.el6.x86_64
kernel-2.6.32-44.el6.x86_64

How reproducible:
about 20%

Steps to Reproduce:
1.Run windows 7 x86 guest with CLI
 /usr/libexec/qemu-kvm  -M pc -m 2G -smp 2 -cpu qemu64,+x2apic  -usbdevice tablet -drive file=/mnt/win7-32-virtio.qcow2,if=none,id=drive-ide0-0-0,format=qcow2,cache=none -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0  -netdev tap,id=hostnet0,vhost=on,script=/etc/qemu-ifup -device virtio-net-pci,netdev=hostnet0,mac=00:00:14:3F:20:1A,bus=pci.0 -uuid 1234127c-e6e3-4e67-95da-8dd0a8891cc4  -name win7-32  -qmp tcp:0:4444,server,nowait -vnc :1 -boot c -monitor stdio -device virtio-balloon-pci,bus=pci.0
2.Install virtio balloon driver
3.Install balloon service :blnsrv.exe -i
4.Check balloon info using qmp
 {"execute":"query-balloon"}
  
Actual results:
Guest quit with"virtio: trying to map MMIO memory" 

Expected results:
The balloon info should show correctly

Additional info:
This issue also happens when using monitor "info balloon" to check balloon info
Comment 2 Vadim Rozenfeld 2010-07-17 07:48:46 UTC 
Did you restart VM after step 2 or 3?
Comment 3 Shirley Zhou 2010-07-19 02:19:30 UTC 
(In reply to comment #2)
> Did you restart VM after step 2 or 3?    

No restart after step 2 and step 3.
Comment 4 Vadim Rozenfeld 2010-07-19 03:32:31 UTC 
VM must be restarted after first-time KWDF framework installation. Usually KMDF
co-installer notices the fact that framework was installed first time and asks for rebooting.
Comment 5 Shirley Zhou 2010-07-19 04:33:56 UTC 
(In reply to comment #4)
> VM must be restarted after first-time KWDF framework installation. Usually KMDF
> co-installer notices the fact that framework was installed first time and asks
> for rebooting.    
Hi, Vadim
There is no pop-up info to remind restart after install virtio balloon driver.
Comment 6 Dor Laor 2010-07-19 08:46:47 UTC 
(In reply to comment #5)
> (In reply to comment #4)
> > VM must be restarted after first-time KWDF framework installation. Usually KMDF
> > co-installer notices the fact that framework was installed first time and asks
> > for rebooting.    
> Hi, Vadim
> There is no pop-up info to remind restart after install virtio balloon driver.    

If you reboot it, will it work?
Comment 7 Shirley Zhou 2010-07-19 09:12:45 UTC 
(In reply to comment #6)
> (In reply to comment #5)
> > (In reply to comment #4)
> > > VM must be restarted after first-time KWDF framework installation. Usually KMDF
> > > co-installer notices the fact that framework was installed first time and asks
> > > for rebooting.    
> > Hi, Vadim
> > There is no pop-up info to remind restart after install virtio balloon driver.    
> 
> If you reboot it, will it work?    

After I reboot this guest, and using qmp checking balloon info for ten times,can not reproduce this issue.
Comment 8 Dor Laor 2010-07-19 09:16:13 UTC 
ok, I think we can close this issue and note the reboot in release notes.
Comment 9 Dor Laor 2010-07-19 09:16:13 UTC 
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.

New Contents:
The VM must be restarted after first-time KWDF framework installation. Without restart, the VM might access unprivileged memory when the balloon is used. This will lead to VM crash.
Comment 10 Shirley Zhou 2010-08-17 06:17:21 UTC 
Verify this bug with virtio-win-1.1.11 on qemu-kvm-0.12.1.2-2.109.el6.x86_64 as following:
1. start win7 x86 guest using virt manager
2. install virtio balloon driver
3. reboot guest
4. install balloon service
5. reboot guest
6. after about 15 mins, check libvirt log, we can see query balloon many times, and guest still runs ok
[root@t78 libvirt]# cat libvirtd.log |grep query-balloon|wc -l
1005

This bug has been fixed. change status to verified.
Comment 15 Ryan Lerch 2010-10-05 05:13:17 UTC 
    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1 +1 @@
-The VM must be restarted after first-time KWDF framework installation. Without restart, the VM might access unprivileged memory when the balloon is used. This will lead to VM crash.+A virtual machine must be restarted after the installation of the kernel windows driver framework. If the virtual machine is not restarted it may crash when a memory balloon is operation is performed.
Comment 16 releng-rhel@redhat.com 2010-11-11 16:30:50 UTC 
Red Hat Enterprise Linux 6.0 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.