Bug 1158408 - virt-manager GUI does not display CPU or update VM state correctly
Summary: virt-manager GUI does not display CPU or update VM state correctly
Keywords:
Status: CLOSED DUPLICATE of bug 1146277
Alias: None
Product: Fedora
Classification: Fedora
Component: virt-manager
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Cole Robinson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-29 10:24 UTC by Ian Lawson
Modified: 2014-10-29 17:57 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-10-29 17:57:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ian Lawson 2014-10-29 10:24:46 UTC
Description of problem:

Clean install of Fedora20, fully yum updated, 'yum install @virtualization', when virt-manager is run (windowing system is Cinnamon) VM state is displayed incorrectly and no CPU graph is provided. When closing a VM the state is still listed as 'Running' but when the VM is selected the window display 'Guest Not Running'.

I run virt-manager on F17 with Cinnamon and the GUI works fine. 

*Note* The VMs themselves are fine, I can run them up, shut them down, the VM state is not being propagated to the GUI correctly and the CPU information is absent. 

Version-Release number of selected component (if applicable):

Latest virt-manager

How reproducible:

I've re-installed F20 (from the LiveCD ISO) twice and get the same virt-manager behaviour, machine is a 16GB lenova X230


Steps to Reproduce:
1. Create LiveCD USB stick
2. Boot machine from USB stick
3. Install Fedora to the disk itself, reboot
4. yum update -y
5. yum install @virtualization
6. Create a VM (for example, RHEL6)
7. run virt-manager
8. Start VM, stop VM, state does not change, CPU not displayed

Actual results:


Expected results:


Additional info:

Comment 1 Cole Robinson 2014-10-29 17:57:12 UTC

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


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