Hide Forgot
Description of problem: When in virt-manager menu, click Run, then Shutdown->Reboot, final the virt-manager guest vnc console can not display correctly, but with the error: TCP/IP error:VNC connection to hypersivor host got refused or disconnected! Version-Release number of selected component (if applicable): # uname -a Linux localhost.localdomain 2.6.18-256.el5xen #1 SMP Thu Apr 7 20:09:34 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux xen-3.0.3-127.el5 libvirt-0.8.2-19.el5 virt-manager-0.6.1-14.el5 How reproducible: Always Steps to Reproduce: 1. Launch virt-manager(xen connection) 2. For a well PV guest, click Run,waiting for the guest start successfully. 3. Click Shutdown->Reboot, check the guest console Actual results: Guest console can not display well, with the error:TCP/IP error:VNC connection to hypersivor host got refused or disconnected! Expected results: Console can display correctly Additional info: # tail -f /root/.virt-manager/virt-manager.log ... [Thu, 12 May 2011 16:43:07 virt-manager 19188] DEBUG (engine:529) Rebooting vm 'pv'. [Thu, 12 May 2011 16:43:32 virt-manager 19188] DEBUG (details:1111) VNC disconnected [Thu, 12 May 2011 16:43:32 virt-manager 19188] WARNING (details:1137) Retrying connection in 125 ms [Thu, 12 May 2011 16:43:32 virt-manager 19188] DEBUG (details:1147) Got timed retry [Thu, 12 May 2011 16:43:32 virt-manager 19188] DEBUG (details:1205) Trying console login [Thu, 12 May 2011 16:43:32 virt-manager 19188] DEBUG (details:1212) Getting graphics console failed: failed Xen syscall xenDaemonDomainFetch failed to find this domain [Thu, 12 May 2011 16:43:38 virt-manager 19188] DEBUG (manager:469) VM pv started # virt-viewer <guest> The console can display correctly with virt-viewer
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
I'm pretty sure this error goes away if you just close and reopen the details console, so the impact isn't very high, and isn't worth fixing at this point in RHEL5. Closing as WONTFIX