I built Xen the way the README specifies. So although FC6 is 2.6.18, I get it built against 2.6.16.29
So uname -a yields 2.6.16.29-xen. I have kernel-xen version as this
My xen version is xen-3.0.3-rc3 src rpm that comes with FC6.
I installed libvirt-0.1.7-2.i386.rpm (again this comes with FC6).
Virt-manager version is 0.2.3 from the About button of the GUI.
I always login as root in these machines.
When I tried it again this time , I still get same results.
Regards Shobha Ranganathan "The significant challenges we face cannot be resolved at the same level of thinking we were at when we created them." Albert Einstein
-----Original Message----- From: Daniel P. Berrange [mailto:berrange@redhat.com] Sent: Tuesday, November 14, 2006 3:57 PM To: Ranganathan, Shobha Cc: fedora-xen@redhat.com Subject: Re: [Fedora-xen] virt-manager gives "The console is currently unavailable" in FC6
On Tue, Nov 14, 2006 at 10:53:59AM -0800, Ranganathan, Shobha wrote:
Yes there is qemu-dm process running.
Great.
I see a line in "virsh dumpxml xen_FC5G1"
<graphics type='vnc' port='5900'/>
From the log file of virt-manager I have
DEBUG Graphics vnc://localhost:5902 ERROR Unable to activate console socket.error(111,'Connection
refused')
Ok, that's a very odd situation - virsh is saying port 5900 is where the VNC server is (which sounds plausible), but virt-manager is trying to connect to 5902 (which sounds like old, hardcoded port behaviour).
Could you tell me what version of kernel-xen, xen, libvirt & virt-manager RPMs you have installed in the host.
If you close the console window & re-open it, I assume it still fails to connect again, with same error message in the logs ?
In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.
Ok, that's good - so port 5900 is definitely the desired port.
Oh, are you running 'virsh' and 'virt-manager' as root, or a normal user ?
Regards, Dan.