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@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-xen
