Hide Forgot
Description of problem: In Edit -> Preference, setting Open console "only for all new domains". But run virt-manager all running guest will open their consoles. Version-Release number of selected component (if applicable): # 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 kernel-2.6.32-99.el6.x86_64 qemu-kvm-0.12.1.2-2.129.el6.x86_64 libvirt-0.8.7-1.el6.x86_64 virt-manager-0.8.6-1.el6 How reproducible: Always Steps to Reproduce: 1.Open virt-manager, Click Edit->Preference, set Open console only for all new domains, then close virt-manager 2.Re-open virt-manager again Actual results: 3.Found virt-manager is open with all existing running guest consoles opened automatically Expected results: 3. Only virt-manager is open. And when create a new guest, that guest console will be open. Additional info:
Urgh, a dumb regression. I noticed this but forgot to fix it before the release. Upstream now: http://hg.fedorahosted.org/hg/virt-manager/rev/f2b2601affd1 We need to get this in for 6.1
Created attachment 480807 [details] Don't always launch consoles for when starting app
Fix build in virt-manager-0.8.6-2
checked with virt-manager-0.8.6-2.el6.noarch Steps: 1.Open virt-manager,start some domains. Click Edit->Preference, set Open console only for all new domains, then close virt-manager 2.Re-open virt-manager again 3.create a new guest via virt-manager Only virt-manager is open.The existing old domains' consoles didn't prompt up. And when create a new guest, that guest console will be opened. So set bug status to VERIFIED
*** Bug 688525 has been marked as a duplicate of this bug. ***
Created attachment 486031 [details] virt-manager.log
------- Comment From santwana.samantray.com 2011-03-22 06:20 EDT------- Hi, I verified this issue on RHEL6.1 Beta(k.v-2.6.32-122.el6.x86_64) and the issue is solved. We can close this bug now. Thanks, Santwana
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-2011-0637.html