Bug 533342 - Guest can not work well after resume from suspend to mem (virtio block)
Summary: Guest can not work well after resume from suspend to mem (virtio block)
Keywords:
Status: CLOSED DUPLICATE of bug 542378
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kvm
Version: 5.5
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Eduardo Habkost
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-11-06 08:37 UTC by Suqin Huang
Modified: 2013-01-09 22:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 12:46:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
strace result (43.87 KB, text/plain)
2009-11-06 08:37 UTC, Suqin Huang
no flags Details

Description Suqin Huang 2009-11-06 08:37:43 UTC
Created attachment 367793 [details]
strace result

Description of problem:
after resume from suspend to mem, guest can not work well. no respond for every operation, such as issue command ls, ifconfig, clear, or open firefox. mouse can be moved, but no response for operation.

Version-Release number of selected component (if applicable):
kvm-83-105.el5_4.10

How reproducible:
always

Steps to Reproduce:
1.CLI:
/usr/libexec/qemu-kvm -drive file=~/images/rhel5.4-32.raw,if=virtio,boot=on -no-hpet -rtc-td-hack -smp 2 -m 4G -uuid `uuidgen` -net  nic,model=e1000,macaddr=00:96:00:FA:88:95,vlan=0 -net tap,vlan=0,script=/etc/qemu-ifup -cpu qemu64,+sse2 -boot c -vnc :3 -monitor stdio -name 5.4-32-virtio -balloon none 
2.echo mem > /sys/power/state
3.issue command: ls, clear, ping baidu.com, ifconfig,dmesg after resume
  
Actual results:
no response

Expected results:


Additional info:

1. guest: rhel5.4-32/64, kerne-2.6.18-164.6.1.el5l
2. host: 
processor	: 7
vendor_id	: GenuineIntel
cpu family	: 6
model		: 26
model name	: Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz

3. top: 7309 root      15   0 4343m 585m  68m S  0.3  4.9   0:31.18 qemu-kvm                                                                         
 7298 root      16   0 4343m 585m  68m S  0.0  4.9   0:04.77 qemu-kvm                                                                         
 7308 root      15   0 4343m 585m  68m S  0.0  4.9   0:00.14 qemu-kvm                                                                         
 7310 root      15   0 4343m 585m  68m S  0.0  4.9   0:19.79 qemu-kvm                                                                         
 7311 root      15   0 4343m 585m  68m S  0.0  4.9   0:00.00 qemu-kvm

4. kvm_stat
 efer_reload                  0       0
 exits                  9641887    8588
 fpu_reload             1005976       3
 halt_exits              938455    2009
 halt_wakeup              65926      65
 host_state_reload	3002406    2635
 hypercalls                   0       0
 insn_emulation         5055770    3164
 insn_emulation_fail          0       0
 invlpg                       0       0
 io_exits               2207474    2315
 irq_exits               205637      85
 irq_injections         1474991    3032
 irq_window              487928    1008
 kvm_request_irq              0       0
 largepages                   0       0
 mmio_exits              736945      74
 mmu_cache_miss            5050       0
 mmu_flooded                  0       0
 mmu_pde_zapped               0       0
 mmu_pte_updated              0       0
 mmu_pte_write            16000       0
 mmu_recycled                 0       0
 mmu_shadow_zapped         5200       0
 mmu_unsync                   0       0
 mmu_unsync_global            0       0
 nmi_injections               0       0
 nmi_window                   0       0
 pf_fixed                520549      26
 pf_guest                     0       0
 remote_tlb_flush         44573       5
 request_nmi                  0       0
 signal_exits                 1       0
 tlb_flush               352717       3

5. strace (attached)
6. kvmtrace
http://focus.bne.redhat.com/~shuang/kvmtrace/

Comment 1 Suqin Huang 2009-11-06 08:39:19 UTC
guest which is installed with if=ide can suspend well.

Comment 2 Yaniv Kaul 2009-11-06 09:06:16 UTC
Irrelevant to the bug, you can't just -uuid `uuidgen` in every run - it means it'll get a different UUID every time, which is plain wrong.

Comment 3 Suqin Huang 2009-11-09 02:54:59 UTC
the same result when I use certain uuid.

/usr/libexec/qemu-kvm -drive file=~/images/rhel5.4-32.raw,if=virtio,boot=on -no-hpet -rtc-td-hack -smp 2 -m 4G -uuid 5e96d19c-66a4-4030-845f-0ad0ed03cfb7 -net  nic,model=e1000,macaddr=00:A6:78:FA:6D:85,vlan=0 -net tap,vlan=0,script=/etc/qemu-ifup -cpu qemu64,+sse2 -boot c -vnc :3 -monitor stdio -name 5.4-32 -balloon none

Comment 5 Dor Laor 2010-01-04 12:46:59 UTC

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


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