Bug 996058 - CPU and Host CPU usage still display status after my Virtual Machine Shutoff
CPU and Host CPU usage still display status after my Virtual Machine Shutoff
Product: Virtualization Tools
Classification: Community
Component: virt-manager (Show other bugs)
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Cole Robinson
Depends On:
  Show dependency treegraph
Reported: 2013-08-12 06:43 EDT by yi.a.zhang
Modified: 2013-09-27 11:03 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-09-27 11:03:17 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
The screen shot (1021.09 KB, image/png)
2013-08-12 06:43 EDT, yi.a.zhang
no flags Details

  None (edit)
Description yi.a.zhang 2013-08-12 06:43:55 EDT
Created attachment 785639 [details]
The screen shot

Description of problem:
CPU and Host CPU usage still display after my Virtual Machine Shutoff

Version-Release number of selected component (if applicable):
Virtual Machine Manager 0.10.0 on Fedora 19

How reproducible:
Steps to Reproduce:
1. Install Ubuntu 12.10 and power on it.
2. Login my Ubuntu OS and 
3. Click Virtual Machine->Shut Down->Shut Down
4. Wait for the Ubuntu OS shut down finished.
5. After the Ubuntu shut down and it display "Shutoff" 
6. Check the CPU usage and Host CPU usage status.

Actual results:
The CPU usage and Host CPU usage still display the status and the machine has been shutdown

Expected results:
The status should not display the status after it display "Shutoff"

Additional info:
Comment 1 Cole Robinson 2013-09-27 11:03:17 EDT
Thanks for the report, but I don't really see this as a bug. The graph is showing the historical CPU usage of the VM, independent of its on off state. It could be useful to see the resource usage for a few seconds after the VM is shutoff. So NOTABUG

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