You are not logged in.

#1 2013-12-17 20:17:19

smakovits
Member
Registered: 2013-12-15
Posts: 60

Xen VNC does not appear to be working/listening

Working through some issues, I am to a point where I think I should be able to install windows in a Xen VM, but when I try to connect to the session, the connection is refused.  I have tried various session numbers to make sure something was not conflicting, but no matter what I do, my connection gets refused.  Besides this, I have what appears to be a healthy system, but for some reason vnc is not listening or maybe it is simply not running.  If I type vncserver, the command it not found, but I am not sure that is needed to function with xen or not.  Any help is appreciated.

Last edited by smakovits (2013-12-18 21:49:33)

Offline

#2 2013-12-18 22:10:27

smakovits
Member
Registered: 2013-12-15
Posts: 60

Re: Xen VNC does not appear to be working/listening

I thought I should update this with slightly more information based on my testing and findings.  It would seem the most likely reason I am not able to connect to the host from my remote computer via vnc is because vnc is not listening for connections, so I am simply turned away at the door.

I have tried going into xend-config.spx and making sure the server is set to listen

(vnc-listen '192.168.0.0')

I have also tried

(vnc-listen '0.0.0.0')

The one thing I was not sure of is if something needs to be restarted between configuration changes.  For me, rebooting would seem to do the same, but I am not sure if I need to run a command to re-read the configuration or not.

The one thing that is certain is that when I run "netstat -tap" I see nothing using port 5900 and because of this, it is pretty obvious I will not be able to connect.

Here are the results of a few of the commands i have found and run:

testARCH ~ # ps -ef | grep vnc
root       734     1 19 12:04 ?        00:00:05 /usr/lib/xen/bin/qemu-dm -d 2 -domain-name windows -vnc 192.168.0.0:0 -vncunused -videoram 8 -boot dc -usb -usbdevice tablet -acpi -vcpu_avail 0x01 -net nic,vlan=0,macaddr=00:16:3e:51:20:4c,model=e1000 -net tap,vlan=0,ifname=vif2.0-emu,bridge=xenbr0,script=no,downscript=no -M xenfv
root       835   450  0 12:04 pts/0    00:00:00 grep --color=auto vnc
testARCH ~ # netstat -tap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 *:32469                 *:*                     LISTEN      467/Plex DLNA Serve
tcp        0      0 *:ssh                   *:*                     LISTEN      391/sshd
tcp        0      0 *:32443                 *:*                     LISTEN      398/Plex Media Serv
tcp        0      0 *:46850                 *:*                     LISTEN      395/rpc.statd
tcp        0      0 *:xinuexpansion4        *:*                     LISTEN      467/Plex DLNA Serve
tcp        0      0 *:58827                 *:*                     LISTEN      408/Plex Plug-in [c
tcp        0      0 192.168.0.0:rfb         *:*                     LISTEN      734/qemu-dm
tcp        0      0 *:sunrpc                *:*                     LISTEN      392/rpcbind
tcp        0      0 *:32400                 *:*                     LISTEN      398/Plex Media Serv
tcp        0      0 *:ndmp                  *:*                     LISTEN      318/perl
tcp        0      0 *:sunproxyadmin         *:*                     LISTEN      388/python2
tcp        0      0 *:52276                 *:*                     LISTEN      564/Plex Plug-in [c
tcp        1      0 testARCH:38815          192.168.:xinupageserver CLOSE_WAIT  467/Plex DLNA Serve
tcp        1      0 testARCH:53462          192.168.0.104:6357      CLOSE_WAIT  467/Plex DLNA Serve
tcp        1      0 localhost.localdo:56842 localhost.localdo:58827 CLOSE_WAIT  467/Plex DLNA Serve
tcp        1      0 testARCH:47976          192.168.:xinupageserver CLOSE_WAIT  467/Plex DLNA Serve
tcp        1      0 testARCH:48189          192.168.:xinupageserver CLOSE_WAIT  467/Plex DLNA Serve
tcp        0     64 testARCH:ssh            192.168.0.99:55725      ESTABLISHED 429/sshd: root@pts/
tcp        0      0 testARCH:53461          192.168.0.104:6357      TIME_WAIT   -
tcp        1      0 testARCH:53463          192.168.0.104:6357      CLOSE_WAIT  467/Plex DLNA Serve
tcp6       0      0 [::]:ssh                [::]:*                  LISTEN      391/sshd
tcp6       0      0 [::]:41638              [::]:*                  LISTEN      395/rpc.statd
tcp6       0      0 [::]:sunrpc             [::]:*                  LISTEN      392/rpcbind
testARCH ~ #

So it would seem that at this point I have sort of reached the end of the road with the stuff I know and can dig up so I am really hoping someone can help me out a bit.  I also hope I am in the right forum and if not, lets get it moved because this seems to be the last hurdle I need to cross before having a functional Arch/Xen test system.

Here is one last log that I saw helped someone else resolve things.
qemu-dm log

domid: 2
-videoram option does not work with cirrus vga device model. Videoram set to 4M.
Using file /dev/VMs/win7 in read-write mode
Strip off blktap sub-type prefix to /home/win7.iso (drv 'aio')
Using file /home/win7.iso in read-only mode
Watching /local/domain/0/device-model/2/logdirty/cmd
Watching /local/domain/0/device-model/2/command
Watching /local/domain/2/cpu
qemu_map_cache_init nr_buckets = 10000 size 4194304
shared page at pfn feffd
buffered io page at pfn feffb
Guest uuid = efe882ed-a79a-4573-8e23-1432529666ab
populating video RAM at ff000000
mapping video RAM from ff000000
Register xen platform.
Done register platform.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
xs_read(/local/domain/0/device-model/2/xen_extended_power_mgmt): read error
medium change watch on `hdb' (index: 1): aio:/home/win7.iso
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Log-dirty: no command yet.
vcpu-set: watch node error.
[xenstore_process_vcpu_set_event]: /local/domain/2/cpu has no CPU!
xs_read(/local/domain/2/log-throttling): read error
qemu: ignoring not-understood drive `/local/domain/2/log-throttling'
medium change watch on `/local/domain/2/log-throttling' - unknown device, ignored
cirrus vga map change while on lfb mode
mapping vram to f0000000 - f0400000
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state.

Last edited by smakovits (2013-12-18 22:24:56)

Offline

Board footer

Powered by FluxBB