Description of problem:
Can't show a host summary after execute "virt-manager --show-host-summary -c qemu:///system" in terminal
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. First make sure no running virt-manager process
2. execute "virt-manager --show-host-summary -c qemu:///system" in terminal
No "Host details" window pop up and show overview tab
"Host details" window pop up and show overview tab
if there is a running virt-manager, Host details" window will pop up after executing "virt-manager --show-host-summary -c qemu:///system" in terminal
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
I don't think use of these CLI options is very common, deferring to 6.1
Fixed upstream: http://hg.fedorahosted.org/hg/virt-manager/rev/34e629e45630
Fixed in virt-manager-0.8.6-1.el6
Whenever the virt-manager is running or not, execute it in the terminal
# virt-manager --show-host-summary -c qemu:///system
Not only Host details with Overview page will display,but also the virtual machine detail page displays when the guest is in running status. And the setting for VM automatically open console is only for all new domains.
So please confirm if it is OK or not. Thanks.
# uname -a
Linux dhcp-65-85.nay.redhat.com 2.6.32-99.el6.x86_64 #1 SMP Fri Jan 14 10:46:00
EST 2011 x86_64 x86_64 x86_64 GNU/Linux
Sounds like you are hitting bug 670735, but I think this bug is VERIFIED
According to Comment 8, Verified as passed with virt-manager-0.8.6-1.el6.
Also I make all guests in shutdown status to walk around bug 670735. And only Overview page display.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.