Description of problem: While domU is running try opening the virtual console using the VM GNOME pannel applet. It fails. Version-Release number of selected component (if applicable): gnome-applet-vm-0.1.2-1.el5 How reproducible: always Steps to Reproduce: 1. have a domU running 2. have the VM applet added to some GNOME pannel 3. right click the applet icon 4. a list of running domains (and other options) appears. right click on some of the running domUs 5. a list of options appears 6. right click on Virtual Console Actual results: Virtual console is not started for the chosen domain (even after user is asked to provide root password) Expected results: Virtual console is started. Additional info: This has been working in previous releases.
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
I don't think this is a regression in the applet. The applet wasn't updated (since RHEL5.0). It seems like a bug 435264 in virt-manager. I guess we need to backport http://hg.et.redhat.com/virt/applications/virt-manager--devel?cs=fdacfd833874 upstream patch to RHEL5. The problem has been fixed in Fedora only... Alexander, you try to start virt-manager by virt-manager -c Xen --show-domain-console <domain-UUID> My test: # virsh -c test:///default dominfo test Id: 1 Name: test UUID: 004b96e1-2d78-c30f-5aa5-f03c87d21e69 OS Type: linux State: running CPU(s): 2 CPU time: 1220270608.4s Max memory: 8388608 kB Used memory: 2097152 kB # virt-manager -c test:///default --show-domain-console 004b96e1-2d78-c30f-5aa5-f03c87d21e69 ... nothing. # virt-manager --show-domain-creator ... nothing
Created attachment 317090 [details] Fix virt-manager --show* options. Code is virtually identical to fix upstream. Commands seem to work now.
QE ack for RHEL5.3.
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. http://rhn.redhat.com/errata/RHBA-2009-0137.html