Bug 1008873

Summary: qemu-kvm quit when get data from rng device in guest after wakeup from S4
Product: Red Hat Enterprise Linux 7 Reporter: Xu Han <xuhan>
Component: qemu-kvmAssignee: Amos Kong <akong>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 7.0CC: acathrow, ailan, akong, amit.shah, juzhang, mazhang, michen, rhod, virt-maint, xfu
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-09-26 06:32:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 923626    

Description Xu Han 2013-09-17 09:26:50 UTC
Description of problem:
qemu-kvm quit when get data from rng device in guest(RHEL6.5) after wakeup from S4.

Version-Release number of selected component (if applicable):
qemu: qemu-kvm-rhev-1.5.3-3.el7.x86_64
guest kernel: 2.6.32-419.el6.i686

How reproducible:
100%

Steps to Reproduce:
1.boot guest with rng-edg
# cat /dev/random | nc -l localhost 1024

#/usr/libexec/qemu-kvm ...
-chardev socket,host=localhost,port=1024,id=chr0 \
-object rng-egd,chardev=chr0,id=rng0 \
-device virtio-rng-pci,rng=rng0


2.do S4 on guest
#echo disk > /sys/power/state

3.wakeup guest and get data from rng device
#cat /dev/hwrng

Actual results:
after 3
hmp report 'qemu-kvm: virtio: trying to map MMIO memory' and qemu-kvm quit.

Expected results:


Additional info:
RHEL7 guest not hit this issue.

Comment 2 Amos Kong 2013-09-26 06:32:09 UTC
It's a bug of guest kernel, not qemu-kvm.

(https://bugzilla.redhat.com/show_bug.cgi?id=1008273#c7)

Comment 3 Xu Han 2013-09-26 11:19:11 UTC
Should this bug be duplicated to 1008273?  you mean they are the same issue, right?

Comment 4 Amos Kong 2013-09-26 15:29:59 UTC

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