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

[Robert Thiem]

When first setting up FC6 I had an issue where I could start an FC6 Xen
guest install but couldn't connect with VNC.

I don't know if it's the same (I can't remember the exact messages I was
getting), but it ended up being that "localhost" wouldn't resolve to an
IPv4 address. This was due to a nasty combination of anaconda putting IPv4
and v6 entries in /etc/hosts and system-config-network trimming the
"extra" v4 entry when run.

Anyway I'd suggest:
- Check that you can ping localhost
- Check there's a localhost entry in /etc/hosts associated with 127.0.0.1
(and not with ::1)
- Run "netstat -antp" to see what ports programs are listening on

Regards,
Robert Thiem

virt-manager gives "The console is currently unavailable" in FC6

[Daniel P. Berrange]

On Wed, Nov 15, 2006 at 11:23:20AM +1000, Robert Thiem wrote:
>  When first setting up FC6 I had an issue where I could start an FC6
> Xen
>  guest install but couldn't connect with VNC.
>  
>  I don't know if it's the same (I can't remember the exact messages I was
>  getting), but it ended up being that "localhost" wouldn't resolve to an
>  IPv4 address. This was due to a nasty combination of anaconda putting IPv4
>  and v6 entries in /etc/hosts and system-config-network trimming the
>  "extra" v4 entry when run.
>  
>  Anyway I'd suggest:
>  - Check that you can ping localhost
>  - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1
>  (and not with ::1)
>  - Run "netstat -antp" to see what ports programs are listening on 
Ahhh, that would certainly make sense - virt-manager explicitly connects
to 'localhost' when opening the VNC connection. Since the VNC server
doesn't support IPv6, I think it'd be fairly safe for me to switch
virt-manager to explicitly use '127.0.0.1'  which would eliminate this
particularly /etc/hosts issue.

Thanks for the info about the issue.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  [phone] -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=|

virt-manager gives "The console is currently unavailable" in FC6

[Laurent Flesch]

YES.
You are right.
Each time I had the intuition it was a problem with VNC connection.
Effectively, after initialising localhost in /etc/hosts everrything works
right again.
The good question is now why it comes in this situation ? I never modified
this localhost.
Is this an issue with system-config-network or another installation I made ?

In any case, really THANKS for your help !

2006/11/15, Robert Thiem <junk(a)remcc.org&gt;:
>  When first setting up FC6 I had an issue where I could start an FC6 Xen
>  guest install but couldn't connect with VNC.
>
>  I don't know if it's the same (I can't remember the exact messages I was
>  getting), but it ended up being that "localhost" wouldn't resolve to an
>  IPv4 address. This was due to a nasty combination of anaconda putting IPv4
>  and v6 entries in /etc/hosts and system-config-network trimming the
>  "extra" v4 entry when run.
>
>  Anyway I'd suggest:
>  - Check that you can ping localhost
>  - Check there's a localhost entry in /etc/hosts associated with 127.0.0.1
>  (and not with ::1)
>  - Run "netstat -antp" to see what ports programs are listening on
>
>  Regards,
>  Robert Thiem
>
>  --
>  Fedora-xen mailing list
>  Fedora-xen(a)redhat.com
>  https://www.redhat.com/mailman/listinfo/fedora-xen
>