Bug 701836 - guest rhel5.7 network can not be resumed from s3
Summary: guest rhel5.7 network can not be resumed from s3
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.7
Hardware: Unspecified
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-04 02:33 UTC by FuXiangChun
Modified: 2011-05-04 02:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-04 02:50:23 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description FuXiangChun 2011-05-04 02:33:00 UTC
Description of problem:
Run a network process(ping) before do s3, after s3 shell will appear warning messages "ping : sendmsg: no buffer space available", network unavailable. 

Version-Release number of selected component (if applicable):
--host
kvm-83-232.el5
etherboot-zroms-kvm-5.4.4-15.el5
kmod-kvm-debug-83-232.el5
kvm-tools-83-232.el5
kmod-kvm-83-232.el5
kvm-qemu-img-83-232.el5
kvm-debuginfo-83-232.el5

uname -r
2.6.18-259.el5


How reproducible:


Steps to Reproduce:
1./usr/libexec/qemu-kvm -no-hpet -usbdevice tablet -rtc-td-hack -name 57 -smp 2 -m 4G -uuid 9e6f04cf-2ad7-45aa-9333-2d2ee26570c6 -boot c -drive file=/mnt/rhel57.qcow2,if=virtio,cache=none,boot=on,format=qcow2,werror=stop -net nic,vlan=1,macaddr=52:54:00:94:a3:8b,model=virtio -net tap,vlan=1,script=/etc/qemu-ifup -notify all -balloon none -monitor stdio  -vnc :1
2. use vnc connect to guest
3. start a process ping 10.66.11.212
4. echo mem>/sys/power/state
5. check ping process and network status
  
Actual results:
guest resume successfully but network unavailable

Expected results:
network work well after resume


Additional info:

Comment 2 FuXiangChun 2011-05-04 02:50:23 UTC
as s3 do not support virtio nic so it isn't a bug. when changed model to rtl8139,guest work well.


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