Ranganathan, Shobha
2006-Nov-15 02:13 UTC
RE: [Fedora-xen] virt-manager gives "The console iscurrentlyunavailable" in FC6
Also the qemu*log files do not any errors for my latest run.
One of the previous runs I had "False I/O request ... in-service
already: 0, pvalid: 0, port: 0, data: 0, count: 0, size: 0
Thanks Dan for all your help..
I pretty much have a valid configuration as you have down here though...
-----Original Message-----
From: fedora-xen-bounces@redhat.com
[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Ranganathan, Shobha
Sent: Tuesday, November 14, 2006 6:08 PM
To: Daniel P. Berrange
Cc: fedora-xen@redhat.com
Subject: RE: [Fedora-xen] virt-manager gives "The console
iscurrentlyunavailable" in FC6
# virsh dumpxml xenbox_G1FC5 | grep graphics
<graphics type=''vnc'' port=''5900''/>
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4517/qemu-dm
# ps -axuww | grep qemu
root 4517 0.3 0.4 32452 3324 ? Sl 17:53 0:01
/usr/lib64/xen/bin/qemu-dm -d 1 -m 256 -boot d -acpi -domain-name
xenbox_G1FC5 -net nic,vlan=1,macaddr=00:16:3e:4a:0d:50,model=rtl8139
-net tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
I did try commenting the ::1 entry in /etc/hosts file. I still see this
issue.
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 5:51 PM
To: Ranganathan, Shobha
Cc: Robert Thiem; fedora-xen@redhat.com
Subject: Re: [Fedora-xen] virt-manager gives "The console is
currentlyunavailable" in FC6
On Tue, Nov 14, 2006 at 05:45:17PM -0800, Ranganathan, Shobha
wrote:> Anyway I''d suggest:
> - Check that you can ping localhost
> I could ping the localhost
>
> - Check there''s a localhost entry in /etc/hosts associated with
> 127.0.0.1
> (and not with ::1)
> I have two entries one with 127.0.0.1 and ::1. I went ahead and
> commented out ::1 entry
> - Run "netstat -antp" to see what ports programs are listening on
> I see various services on IP address of the local host 172.xx.xx.xx
and> 127.0.0.1 and ::22 and ::1 and 0.0.0.0
>
> I see sshd, cupsd and hpiod running with local address as ::22, ::1
and> 0.0.0.0.
For fully-virt / HVM guests you should see a ''qemu-dm''
process
listening
on the port associated with VNC (something around 5900+). If you don''t
then this is the primary problem to address - the qemu-dm*log file may
be useful. Also grabbing the command line for qemu-dm active process
should indicate what port it tried to start on. In my case:
# virsh dumpxml rhel4i386 | grep graphics
<graphics type=''vnc'' port=''5900''/>
# ps -axuww | grep qemu
root 4005 0.0 0.1 64616 5132 ? Sl 20:05 0:00
/usr/lib64/xen/bin/qemu-dm -d 2 -m 500 -boot c -serial pty -vcpus 4
-acpi -domain-name rhel4i386 -net
nic,vlan=1,macaddr=00:16:3e:39:f9:76,model=rtl8139 -net
tap,vlan=1,bridge=xenbr0 -vncunused -k en-us -vnclisten 127.0.0.1
# netstat -t -a -n -p | grep qemu
tcp 0 0 127.0.0.1:5900 0.0.0.0:*
LISTEN 4005/qemu-dm
# virsh dumpxml rhel4i386 | grep graphics
<graphics type=''vnc'' port=''5900''/>
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