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 1167595 - qemu-kvm: virtio: trying to map MMIO memory when do reboot win8.1.32 guest
Summary: qemu-kvm: virtio: trying to map MMIO memory when do reboot win8.1.32 guest
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 1069309
TreeView+ depends on / blocked
 
Reported: 2014-11-25 06:31 UTC by ShupingCui
Modified: 2015-03-24 07:21 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-24 07:21:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description ShupingCui 2014-11-25 06:31:09 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
# rpm -q qemu-kvm
qemu-kvm-1.5.3-79.el7.x86_64
# rpm -q seabios
seabios-1.7.5-6.el7.x86_64

virtio-win-prewhql-0.1-94

How reproducible:
only once

Steps to Reproduce:
1. boot win8.1.32 guest with virtio-scsi
/bin/qemu-kvm \
    -S  \
    -name 'virt-tests-vm1'  \
    -sandbox off  \
    -M pc  \
    -nodefaults  \
    -vga qxl  \
    -global qxl-vga.vram_size=33554432  \
    -chardev socket,id=qmp_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20141124-232553-GaXpwxcU,server,nowait \
    -mon chardev=qmp_id_qmpmonitor1,mode=control  \
    -chardev socket,id=serial_id_serial0,path=/tmp/serial-serial0-20141124-232553-GaXpwxcU,server,nowait \
    -device isa-serial,chardev=serial_id_serial0  \
    -chardev socket,id=seabioslog_id_20141124-232553-GaXpwxcU,path=/tmp/seabios-20141124-232553-GaXpwxcU,server,nowait \
    -device isa-debugcon,chardev=seabioslog_id_20141124-232553-GaXpwxcU,iobase=0x402 \
    -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=03 \
    -device virtio-scsi-pci,id=virtio_scsi_pci0,bus=pci.0,addr=04 \
    -drive id=drive_image1,if=none,cache=none,snapshot=off,aio=native,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/images/win8-32.1-virtio.qcow2 \
    -device scsi-hd,id=image1,drive=drive_image1 \
    -device virtio-net-pci,mac=9a:20:21:22:23:24,id=idqb8M69,vectors=4,netdev=idXd74TK,bus=pci.0,addr=05  \
    -netdev tap,id=idXd74TK,vhost=on,vhostfd=23,fd=22  \
    -m 32768  \
    -smp 16,maxcpus=16,cores=4,threads=2,sockets=2  \
    -cpu 'Opteron_G4',+sep,+kvm_pv_unhalt,hv_relaxed,hv_spinlocks=0x1fff,hv_vapic,hv_time \
    -drive id=drive_cd1,if=none,snapshot=off,aio=native,media=cdrom,file=/root/staf-kvm-devel/autotest-devel/client/tests/virt/shared/data/isos/windows/winutils.iso \
    -device scsi-cd,id=cd1,drive=drive_cd1 \
    -device usb-tablet,id=usb-tablet1,bus=usb1.0,port=1  \
    -spice port=3000,password=123456,addr=0,image-compression=auto_glz,zlib-glz-wan-compression=auto,streaming-video=all,agent-mouse=on,playback-compression=on,ipv4  \
    -rtc base=localtime,clock=host,driftfix=slew  \
    -boot order=cdn,once=c,menu=off \
    -enable-kvm

2. do reboot guest 20 times
3.

Actual results:
[qemu output] qemu-kvm: virtio: trying to map MMIO memory
[qemu output] (Process terminated with status 1)

Expected results:
reboot guest successfully, and guest works well

Additional info:
Host cpu info:

processor	: 31
vendor_id	: AuthenticAMD
cpu family	: 21
model		: 1
model name	: AMD Opteron(TM) Processor 6274                 
stepping	: 2
microcode	: 0x6000626
cpu MHz		: 2199.996
cache size	: 2048 KB
physical id	: 1
siblings	: 16
core id		: 7
cpu cores	: 8
apicid		: 79
initial apicid	: 47
fpu		: yes
fpu_exception	: yes
cpuid level	: 13
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 cx16 sse4_1 sse4_2 popcnt aes xsave avx lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 nodeid_msr topoext perfctr_core perfctr_nb arat cpb hw_pstate npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold
bogomips	: 4399.77
TLB size	: 1536 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm 100mhzsteps hwpstate cpb

# free -m
              total        used        free      shared  buff/cache   available
Mem:          64379        1244       59173           8        3960       62500
Swap:         32191           0       32191
Comment 3 Ronen Hod 2014-11-30 09:10:37 UTC 
Vadim,
Is there any Windows side analysis that you can provide, or is it a pure QEMU side problem?
Comment 4 Vadim Rozenfeld 2014-11-30 09:37:06 UTC 
(In reply to Ronen Hod from comment #3)
> Vadim,
> Is there any Windows side analysis that you can provide, or is it a pure
> QEMU side problem?

It's not a QEMU problem. It happens because vioscsi or netkvm submits an invalid
element in SG list. Can we try reproducing the problem with only one virtio
device - vioscsi or netkvm installed?

Vadim.
Comment 6 ShupingCui 2014-12-22 03:10:33 UTC 
(In reply to Vadim Rozenfeld from comment #4)
> (In reply to Ronen Hod from comment #3)
> > Vadim,
> > Is there any Windows side analysis that you can provide, or is it a pure
> > QEMU side problem?
> 
> It's not a QEMU problem. It happens because vioscsi or netkvm submits an
> invalid
> element in SG list. Can we try reproducing the problem with only one virtio
> device - vioscsi or netkvm installed?
> 
> Vadim.

Hi Vadim,

I cannot reproduce this bug with virtio-scsi+e1000 and ide+virtio-net.
Comment 7 Vadim Rozenfeld 2014-12-22 04:08:57 UTC 
(In reply to ShupingCui from comment #6)
> (In reply to Vadim Rozenfeld from comment #4)
> > (In reply to Ronen Hod from comment #3)
> > > Vadim,
> > > Is there any Windows side analysis that you can provide, or is it a pure
> > > QEMU side problem?
> > 
> > It's not a QEMU problem. It happens because vioscsi or netkvm submits an
> > invalid
> > element in SG list. Can we try reproducing the problem with only one virtio
> > device - vioscsi or netkvm installed?
> > 
> > Vadim.
> 
> Hi Vadim,
> 
> I cannot reproduce this bug with virtio-scsi+e1000 and ide+virtio-net.

Did you run all the tests on the same or identical AMD Host?

Thanks,
Vadim.
Comment 8 ShupingCui 2014-12-22 04:39:29 UTC 
(In reply to Vadim Rozenfeld from comment #7)
> (In reply to ShupingCui from comment #6)
> > (In reply to Vadim Rozenfeld from comment #4)
> > > (In reply to Ronen Hod from comment #3)
> > > > Vadim,
> > > > Is there any Windows side analysis that you can provide, or is it a pure
> > > > QEMU side problem?
> > > 
> > > It's not a QEMU problem. It happens because vioscsi or netkvm submits an
> > > invalid
> > > element in SG list. Can we try reproducing the problem with only one virtio
> > > device - vioscsi or netkvm installed?
> > > 
> > > Vadim.
> > 
> > Hi Vadim,
> > 
> > I cannot reproduce this bug with virtio-scsi+e1000 and ide+virtio-net.
> 
> Did you run all the tests on the same or identical AMD Host?
> 
> Thanks,
> Vadim.

No, on the intel host this time, will try it on the same or identical AMD Host.
Comment 9 Vadim Rozenfeld 2014-12-22 08:42:33 UTC 
(In reply to ShupingCui from comment #8)
> (In reply to Vadim Rozenfeld from comment #7)
> > (In reply to ShupingCui from comment #6)
> > > (In reply to Vadim Rozenfeld from comment #4)
> > > > (In reply to Ronen Hod from comment #3)
> > > > > Vadim,
> > > > > Is there any Windows side analysis that you can provide, or is it a pure
> > > > > QEMU side problem?
> > > > 
> > > > It's not a QEMU problem. It happens because vioscsi or netkvm submits an
> > > > invalid
> > > > element in SG list. Can we try reproducing the problem with only one virtio
> > > > device - vioscsi or netkvm installed?
> > > > 
> > > > Vadim.
> > > 
> > > Hi Vadim,
> > > 
> > > I cannot reproduce this bug with virtio-scsi+e1000 and ide+virtio-net.
> > 
> > Did you run all the tests on the same or identical AMD Host?
> > 
> > Thanks,
> > Vadim.
> 
> No, on the intel host this time, will try it on the same or identical AMD
> Host.

Yes, please. We used to have some memory related problems seen on AMD platforms only.

Vadim.
Comment 10 ShupingCui 2014-12-23 01:35:30 UTC 
Hi Vadim,

This bug is very difficult to reproduce, I cannot reproduce this bug with virtio-scsi+e1000 and ide+virtio-net on identical AMD Host.
Comment 11 Vadim Rozenfeld 2014-12-23 02:16:09 UTC 
(In reply to ShupingCui from comment #10)
> Hi Vadim,
> 
> This bug is very difficult to reproduce, I cannot reproduce this bug with
> virtio-scsi+e1000 and ide+virtio-net on identical AMD Host.

It's true. Do you still have access to the VM where the problem happen?  Can you check if verifier was active that time?

In any case, let's spend some time trying to reproduce it under various guest/host memory and CPU loads. However, if it is not reproducible, I suggest to close it as WORKSFORME or WONTFIX.

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