Hi,
OK, it seems that I'm comming closer to my problem!
I start my first VM with vnc=1 and vncviewer=1 in the config but no VNC
is starting. I get the following message:
# xm create test
Using config file "test".
VNC= 1
vncviewer -listen: Listening on port 11001 (flash port 10901)
vncviewer -listen: Command line errors are not reported until a
connection comes in.
Started domain test
# xm list -l
...
(domain
(domid 1)
(uuid eb5b11e5-8176-3411-08e0-a01a15ef6c39)
(ssidref 0)
(vcpus 1)
(vcpu_avail 1)
(cpu_weight 1.0)
(memory 384)
(maxmem 384)
(name test)
(on_poweroff destroy)
(on_reboot restart)
(on_crash restart)
(image
(vmx
(kernel /usr/lib/xen/boot/vmxloader)
(args 'VNC_VIEWER=10.65.0.32:5501 ')
(device_model /usr/lib64/xen/bin/qemu-dm)
(vcpus 1)
(cdrom /dev/hda)
(boot c)
(vnc 1)
(vncviewer 1)
(display :0.0)
(xauthority /root/.Xauthority)
)
)
(state -b----)
(shutdown_reason poweroff)
(cpu_time 2.8362e-05)
(online_vcpus 1)
(up_time 68.7826452255)
(start_time 1138754868.61)
(store_mfn 426582)
)
If I try to connect on the local machine (xen0-host) to the xenU I only get:
# vncviewer 10.65.0.31:5501
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
# vncviewer 10.65.0.31:11001
vncviewer: ConnectToTcpAddr: connect: Connection refused
Unable to connect to VNC server
And if I do so from remote with OS/2 or Windows I get with
10.65.0.32:5501 only "unable to connect" and if I try to connect to
10.65.0.32:11001 the following error on the host:
vncviewer -listen: invalid command line argument: -log
TightVNC viewer version 1.2.9
Usage: vncviewer [<OPTIONS>] [<HOST>][:<DISPLAY#>]
...
..
For me that looks like using wrong commandline-parameters, but which one
are the right ones and where can I change it?
On which ports the XEN-vncserver is listening, normaly VNC uses 5900+,
in conjunction with XEN I read 5500+ and XEN tells me above that he is
"Listening on port 11001".
And if I start a second xenU-domain I also get an error:
# xm create test2
Using config file "test2".
VNC= 1
vncviewer: ListenAtTcpPort: bind: Address already in use
vncviewer: ListenAtTcpPort: bind: Address already in use
Started domain test2
So here seems to be s.th. quite wrong, but I don't know how to solve it :-(
Thanks a lot for any help!
BTW: I'm using SuSE Linux 10.1 Beta2 x86-64 on Xeon/VT with Kernel
2.6.16_rc1_git3-4 and XEN 3.0_8628-2. Using SLES 10 Beta or SuSE Linux
10.0 results in not working onboard ethernet-interfaces.
--
Chau y hasta luego,
Thorolf
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home