Bug 903889

Summary: The value of steal time in "top" command always is "0.0% st" after guest migration
Product: Red Hat Enterprise Linux 7 Reporter: huiqingding <huding>
Component: qemu-kvmAssignee: Marcelo Tosatti <mtosatti>
Status: CLOSED CURRENTRELEASE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: 7.0CC: acathrow, areis, bsarathy, hhuang, juli, juzhang, mkenneth, mtosatti, qzhang, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qemu-kvm-1.5.3-7.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 903123 Environment:
Last Closed: 2014-06-13 10:11:03 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: 903123    
Bug Blocks:    
Attachments:
Description Flags
The result of top command of the source first guest.
none
The result of top command in the second source guest.
none
After migration, the result of top command in the first guest.
none
After migration, the result of top command in the second guest. none

Comment 1 huiqingding 2013-01-25 01:41:14 UTC
Created attachment 687121 [details]
The result of top command of the source first guest.

Comment 2 huiqingding 2013-01-25 01:43:02 UTC
Created attachment 687122 [details]
The result of top command in the second source guest.

Comment 3 huiqingding 2013-01-25 01:43:38 UTC
Created attachment 687123 [details]
After migration, the result of top command in the first guest.

Comment 5 huiqingding 2013-01-25 01:44:10 UTC
Created attachment 687124 [details]
After migration, the result of top command in the second guest.

Comment 6 Jaromír Cápík 2013-08-27 16:02:40 UTC
Hello Huiqing & Orion.

Why is this reported against procps-ng? It's very likely a matter of the kernel or qemu-kvm. 'top' only translates values reported by the kernel in a well readable form.
As I'm reading the parent bug, the root cause seems to be in the qemu-kvm component. Switching ...

Regards,
Jaromir.

Comment 7 Miroslav Rezanina 2013-09-26 09:35:31 UTC
Fix included in qemu-kvm-1.5.3-7.el7

Comment 9 Jun Li 2013-11-04 10:09:49 UTC
Reproduce:
Version:
3.10.0-41.el7.x86_64
qemu-kvm-1.4.0-4.el7.x86_64

Reproduce this bug with the same command line as the comments 0 descript. After migration, the value of steal time in both destination guests are "0.0% st".
-----------

The steps as the comments 0 descript.
Version:
qemu-kvm-1.5.3-11.el7.x86_64
3.10.0-41.el7.x86_64

Before migration:
%Cpu(s):  1.7 us,  0.0 sy,  0.0 ni,  0.0 id,  0.0 wa, 48.3 hi,  0.0 si, 50.0 st
%Cpu(s):  1.7 us,  0.0 sy,  0.0 ni,  0.0 id,  0.0 wa, 48.2 hi,  0.0 si, 50.2 st

After migration:
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,  0.0 id,  0.0 wa, 49.8 hi,  0.0 si, 50.2 st
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni,  0.0 id,  0.0 wa, 50.2 hi,  0.0 si, 49.8 st

After migration, the value of steal time in both destination guests almost do not changed. 

Based on above test results, I think this bug has been verified.

Comment 11 Ludek Smid 2014-06-13 10:11:03 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.