Fedora xen - Nov 2006 - RE: virt-manager gives "The console is currently unavailable" in FC6

Yes there is qemu-dm process running.

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'')

In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.

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: Monday, November 13, 2006 8:04 PM
To: Ranganathan, Shobha
Cc: fedora-xen@redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
unavailable" in FC6

On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha
wrote:
> I had a typo in my previous message.
> 
> I see no errors in xend.log and xend-debug.log.
Ok, that''s good - can you see if there is a qemu-dm process running,
eg

  ps -auxfww | grep qemu-dm
> But I do have qemu*log messages. For my last problem, I only see the
> following
> Domid: 2
> Shared page at pfn:ffff, mfn:34cd5
> Buffered io page at pfn:fffd, mfn:34cd7
Looks reasonable. Can you see if there is a ''<graphics>''
block
in the XML  when you run

  ''virsh dumpxml  <domain name>''  

For the domain that you failed to get a console on. Also make sure that
in the /etc/xen/<domain name> there is a ''vnc=1'' config
option. Finally,
take a look at /root/.virt-manager/virt-manager.log to see if there''s
any errors reported.
> -----Original Message-----
> From: Daniel P. Berrange [mailto:berrange@redhat.com] 
> Sent: Monday, November 13, 2006 5:24 PM
> To: Ranganathan, Shobha
> Cc: fedora-xen@redhat.com
> Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
> unavailable" in FC6
> 
> On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote:
> > I am trying to install unmodified guest FC5 in host Os FC6.
> > 
> > I am using virt-manager and upon gathering all information, when I
> click
> > finish, the GUI shows me "The console is currently
unavailable".
> 
> This basically means that virt-manager was unable to successfully
> connect
> to the VNC server which exports the guest framebuffer / console. Since
> you say this is with fully virt, it probably means that the qemu-dm
> process
> failed to startup correctly - since VNC itself rarely fails I imagine
> some
> other bit of the guest config broke - network / disk setup being most
> likely
> 
> > 
> > What is wrong ? xm list shows the guest as blocked. I see error
> messages
> > in xend-debug.log and xend.log
> 
> What are the errors you see - they may well help diagnose the problem
> you are encountering ? Also check for /var/log/xen/qemu-dm*.log for
> info about the fully-virt device model startup
Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392
2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/
-=|
|=-               Projects: http://freshmeat.net/~danielpb/
-=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
-=|

Hi,

After a new check, it looks like I have exactly the same problem than your
with the same logs.
I found no solution for the moment as making a new FC6 installation.

Best Regards

2006/11/14, Ranganathan, Shobha
<shobha.ranganathan@intel.com>:
>
> Yes there is qemu-dm process running.
>
> 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'')
>
> In the /etc/xen/xen_FC5G1, I do have vnc=1 and vncunused=1.
>
> 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: Monday, November 13, 2006 8:04 PM
> To: Ranganathan, Shobha
> Cc: fedora-xen@redhat.com
> Subject: Re: [Fedora-xen] virt-manager gives "The console is currently
> unavailable" in FC6
>
> On Mon, Nov 13, 2006 at 06:03:17PM -0800, Ranganathan, Shobha wrote:
> > I had a typo in my previous message.
> >
> > I see no errors in xend.log and xend-debug.log.
>
> Ok, that''s good - can you see if there is a qemu-dm process
running,
> eg
>
>   ps -auxfww | grep qemu-dm
>
> > But I do have qemu*log messages. For my last problem, I only see the
> > following
> > Domid: 2
> > Shared page at pfn:ffff, mfn:34cd5
> > Buffered io page at pfn:fffd, mfn:34cd7
>
> Looks reasonable. Can you see if there is a
''<graphics>'' block
> in the XML  when you run
>
>   ''virsh dumpxml  <domain name>''
>
> For the domain that you failed to get a console on. Also make sure that
> in the /etc/xen/<domain name> there is a ''vnc=1''
config option. Finally,
> take a look at /root/.virt-manager/virt-manager.log to see if
there''s
> any errors reported.
>
> > -----Original Message-----
> > From: Daniel P. Berrange [mailto:berrange@redhat.com]
> > Sent: Monday, November 13, 2006 5:24 PM
> > To: Ranganathan, Shobha
> > Cc: fedora-xen@redhat.com
> > Subject: Re: [Fedora-xen] virt-manager gives "The console is
currently
> > unavailable" in FC6
> >
> > On Mon, Nov 13, 2006 at 05:08:48PM -0800, Ranganathan, Shobha wrote:
> > > I am trying to install unmodified guest FC5 in host Os FC6.
> > >
> > > I am using virt-manager and upon gathering all information, when
I
> > click
> > > finish, the GUI shows me "The console is currently
unavailable".
> >
> > This basically means that virt-manager was unable to successfully
> > connect
> > to the VNC server which exports the guest framebuffer / console. Since
> > you say this is with fully virt, it probably means that the qemu-dm
> > process
> > failed to startup correctly - since VNC itself rarely fails I imagine
> > some
> > other bit of the guest config broke - network / disk setup being most
> > likely
> >
> > >
> > > What is wrong ? xm list shows the guest as blocked. I see error
> > messages
> > > in xend-debug.log and xend.log
> >
> > What are the errors you see - they may well help diagnose the problem
> > you are encountering ? Also check for /var/log/xen/qemu-dm*.log for
> > info about the fully-virt device model startup
>
> Regards,
> Dan.
> --
> |=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392
> 2496 -=|
> |=-           Perl modules: http://search.cpan.org/~danberr/
> -=|
> |=-               Projects: http://freshmeat.net/~danielpb/
> -=|
> |=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505
> -=|
>
> --
> Fedora-xen mailing list
> Fedora-xen@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-xen
>

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.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|