LxCenter Forum: Windows under Xen » cannot start VNC client

HyperVM & Kloxo Support

Forum

Members

Help

Home

Home » HyperVM Community Support » Windows under Xen » cannot start VNC client

Show: Today's Messages :: Show Polls :: Message Navigator

cannot start VNC client [message #47861]

Thu, 27 November 2008 09:40

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

From HyperVM it shows: Network error: could not connect to server xxxxxxx:5932

From /var/log/xen/

domid: 7
qemu: the number of cpus is 1
Watching /local/domain/7/logdirty/next-active
qemu_map_cache_init nr_buckets = 10000
shared page at pfn ffff
buffered io page at pfn fffd
xs_read(/vm/ed091dd0-0080-b883-ec58-450ed3b4457b/rtc/timeoffset): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch

How to fix it please?
Thanks.

Report message to a moderator

Re: cannot start VNC client [message #47939 is a reply to message #47861]

Fri, 28 November 2008 01:50

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

tried to enable VT-d on Bios too, without any change. The same error. And VM is blocked

# xm list
Name                                      ID Mem(MiB) VCPUs State   Time(s)
Domain-0                                   0      512     4 r-----     43.3
windows.vm                                 6      519     1 -b----     20.1

Report message to a moderator

Re: cannot start VNC client [message #47945 is a reply to message #47939]

Fri, 28 November 2008 03:26

Lxhelp
Messages: 23691
Registered: July 2006

The Champion

That's normal. All VMs are always in the blocked state. That's how they should be. If they are constantly running, then there is something wrong inside the vps. Check the time, it has run successfully for 20 seconds of CPU.

On Fri, Nov 28, 2008 at 06:50:57AM -0000, hpm77 wrote:
>
>
> tried to enable VT-d on Bios too, without any change. The same error. And VM is blocked
>
> # xm list
> Name ID Mem(MiB) VCPUs State Time(s)
> Domain-0 0 512 4 r----- 43.3
> windows.vm 6 519 1 -b---- 20.1
>
>

Report message to a moderator

Re: cannot start VNC client [message #47996 is a reply to message #47861]

Fri, 28 November 2008 11:17

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

Here are what I did
- download trial Windows ISO file from this page
- ln -sf /home/w2k3sp2_3959_usa_x86fre_spcd.iso /home/wincd.img
- create new VPS with windows-lxblank.img template = successful.

But cannot connect to VNC client. Error is "Network error: could not connect to server xxxxxxx:5932"

Can you let me know if I did anything wrong, and somewhere I can find out the reason?

Thanks.

Report message to a moderator

Re: cannot start VNC client [message #48435 is a reply to message #47861]

Mon, 01 December 2008 10:47

dkhosting

Messages: 268
Registered: April 2007

Senior Member

That is not a trial that you have downloaded. That is the service pack 2 update.

Report message to a moderator

Re: cannot start VNC client [message #48455 is a reply to message #47861]

Mon, 01 December 2008 11:49

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

Well... I tried several copies, even Windows 2008, without any success.

Report message to a moderator

Re: cannot start VNC client [message #48996 is a reply to message #48455]

Thu, 04 December 2008 19:06

aidanlx

Messages: 92
Registered: June 2007

Valuable Member

I'm having a similar issue. Create a VPS on XEN, open a VNC session, choose a few steps in Windows 2008 installation procedure, the installation starts copying and expanding files as normal, then the VNC connection goes dead and cannot be reconnected.

[Updated on: Thu, 04 December 2008 19:07]

Report message to a moderator

Re: cannot start VNC client [message #55609 is a reply to message #47861]

Tue, 10 February 2009 10:00

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

I tried again, but I still could not connect VNC. Any detail steps please?

Report message to a moderator

Re: cannot start VNC client [message #59352 is a reply to message #47861]

Thu, 12 March 2009 11:12

hpham

Messages: 390
Registered: November 2007
Location: the net

Master

Just tried again on a new Q9550 server without any luck. Anyone has idea for helping please?

Thanks.

Report message to a moderator

Re: cannot start VNC client [message #61772 is a reply to message #47861]

Thu, 09 April 2009 22:43

winlinfix

Messages: 4
Registered: April 2009

Member

xm list
Name ID Mem(MiB) VCPUs State Time(s)
192.168.1.12.vm 3 191 1 ------ 0.0
Domain-0 0 3624 2 r----- 45.7

i am getting following error while click on vnc client.
network error: could not connect server ip:5905

i did install yum install vnc-server at vps node and i am able to connect main node by vnc using ip :5901 but it shows blank screen. i can see 5905 port is not open.
i am still unable to connect windows vnc
[root@wolf2 ~]# ll /home
total 32
drwx------ 2 192168112vm 192168112vm 4096 Apr 9 09:41 19216811vm
drwxr-xr-x 2 root root 4096 Apr 4 07:24 httpd
drwxr-xr-x 7 root root 4096 Apr 7 03:57 hypervm
drwx------ 2 lxlabs lxlabs 4096 Apr 4 07:23 lxlabs
lrwxrwxrwx 1 root root 51 Apr 9 09:40 wincd.img -> /vz/template/cache/w2k3sp2_3959_usa_x64fre_spcd.iso

[Updated on: Mon, 13 April 2009 00:00]

Report message to a moderator

Re: cannot start VNC client [message #62081 is a reply to message #47861]

Mon, 13 April 2009 02:42

s1llyforyou

Messages: 16
Registered: April 2009
Location: india

Member

hello

please update on last reply asap

Report message to a moderator

Re: cannot start VNC client [message #62091 is a reply to message #47861]

Mon, 13 April 2009 09:40

winlinfix

Messages: 4
Registered: April 2009

Member

i can see linux vps node while access vnc it must show windows install screeen.

Report message to a moderator

Re: cannot start VNC client [message #72464 is a reply to message #62091]

Mon, 11 January 2010 05:16

darkn3 king

Messages: 1
Registered: January 2010

Member

please help me i have this problem aslo i installed xen and i cant connect to vnc console

Report message to a moderator

Re: cannot start VNC client [message #99223 is a reply to message #72464]

Sun, 08 July 2012 12:39

dewadragoon

Messages: 6
Registered: July 2012

Member

Same here. VNC console failed to connect.

Report message to a moderator

Re: cannot start VNC client [message #99314 is a reply to message #99223]

Tue, 10 July 2012 10:14

Rioter

Messages: 25
Registered: April 2012

Member

please show your config file and iptables.

Regards,

Rioter

Report message to a moderator

Re: cannot start VNC client [message #99319 is a reply to message #99314]

Tue, 10 July 2012 13:15

dewadragoon

Messages: 6
Registered: July 2012

Member

Rioter wrote on Tue, 10 July 2012 21:14

please show your config file and iptables.

IP Tables :
/sbin/iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination
ACCEPT all -- xxx.xxx.xxx.xxx anywhere PHYSDEV match --physdev-in viftest1
ACCEPT udp -- anywhere anywhere PHYSDEV match --physdev-in viftest1 udp spt:bootpc dpt:bootps
ACCEPT all -- anywhere anywhere PHYSDEV match --physdev-in vif11.0

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

------------------------------------------------------------ --

:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A FORWARD -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
COMMIT
------------------------------------------------------------ ---

Hypervm auto generated VM Config:
import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
name = 'winxp.vm'
kernel = '/usr/lib/xen/boot/hvmloader'
builder='hvm'
boot='d'
memory = 512
vif = [ ]
device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
vnc=1
sdl=0
vcpus = 1
vnclisten='0.0.0.0'
vncpasswd='123qweasdzxc'
disk = [ 'file:/home/wincd.img,hdc:cdrom,r', 'phy:/dev/VPS/winxp_rootimg,ioemu:hda,w']
acpi=1
vncunused=0
vncdisplay=

------------------------------------------------------------ --

Error Message :

qemu-dm.log :

xs_read(/vm/fb460777-27a8-4543-dd49-b1565a20dd29/rtc/timeoff set): read error

------------------------------------------------------------ ---

Report message to a moderator

Re: cannot start VNC client [message #99345 is a reply to message #99319]

Wed, 11 July 2012 10:49

Rioter

Messages: 25
Registered: April 2012

Member

your vif is empty.

my window config:

import os, re
arch = os.uname()[4]
if re.search('64', arch):
arch_libdir = 'lib64'
else:
arch_libdir = 'lib'
name = 'window.vm'
kernel = '/usr/lib/xen/boot/hvmloader'
builder='hvm'
boot='c'
memory = 2048

vif = [ 'type=ioemu, bridge=virbr0, mac=aa:00:bf:ab:5a:01 ' ]

device_model = '/usr/' + arch_libdir + '/xen/bin/qemu-dm'
vnc=1
sdl=0
vcpus = 4
vnclisten='0.0.0.0'
vncpasswd='passwordqwer'
disk = [ 'phy:/dev/vg/window_rootimg,ioemu:hda,w']
acpi=1
vncunused=0
vncdisplay=2
usbdevice='tablet'
on_reboot = 'restart'
on_crash = 'restart'

i use libvirtd for windows network.

iptables:

# Generated by iptables-save v1.3.5 on Sat May 26 08:56:32 2012
*filter
:INPUT ACCEPT [31:4723]
:FORWARD ACCEPT [2604:40379546]
:OUTPUT ACCEPT [29:5300]
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 94.xx.xx.xx -p tcp -m tcp --dport 21:65535 -j ACCEPT
-A OUTPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
COMMIT
# Completed on Sat May 26 08:56:32 2012
# Generated by iptables-save v1.3.5 on Sat May 26 08:56:32 2012
*nat
:PREROUTING ACCEPT [614:71096]
:POSTROUTING ACCEPT [527:64785]
:OUTPUT ACCEPT [29:5300]
-A PREROUTING -d 94.xx.xx.xx -p tcp -m tcp --dport 21:65535 -j DNAT --to-destination 192.168.122.5
-A POSTROUTING -s 192.168.122.5 -j SNAT --to-source 94.xx.xx.xx
-A POSTROUTING -o eth0 -j MASQUERADE
-A POSTROUTING -s 192.168.122.0/255.255.255.0 -d ! 192.168.122.0/255.255.255.0 -p tcp -j MASQUERADE --to-ports 1024-65535
-A POSTROUTING -s 192.168.122.0/255.255.255.0 -d ! 192.168.122.0/255.255.255.0 -p udp -j MASQUERADE --to-ports 1024-65535
-A POSTROUTING -s 192.168.122.0/255.255.255.0 -d ! 192.168.122.0/255.255.255.0 -j MASQUERADE
COMMIT
# Completed on Sat May 26 08:56:32 2012

94.xx.xx.xx is my public ip, this is NAT 1:1, it will transfer all network on 94.xx.xx.xx to 192.168.122.5 vice versa.
192.168.122.5 is windows static ip addr.

hope that will help you.

Regards,

Rioter

Report message to a moderator

Re: cannot start VNC client [message #99346 is a reply to message #99345]

Wed, 11 July 2012 10:50

Rioter

Messages: 25
Registered: April 2012

Member

just look at my vif function, that the network for windows and iptables NAT

Regards,

Rioter

Report message to a moderator

Re: cannot start VNC client [message #99354 is a reply to message #99346]

Wed, 11 July 2012 13:05

dewadragoon

Messages: 6
Registered: July 2012

Member

Hello Rioter,

thanks for your advice.

unfortunately still can't gain access to VNC Console, so i can't install the windows (in my case i use windows xp iso ).

this my libvirt :
[root@GATOTKACA bayu]# yum list installed | grep libvirt
libvirt.i386 0.8.2-25.el5 installed
libvirt.x86_64 0.8.2-25.el5 installed
libvirt-python.x86_64 0.8.2-25.el5 installed

i am using xen 3.0.3 ( Centos Default )
[root@GATOTKACA bayu]# yum list installed | grep xen
kernel-xen.x86_64 2.6.18-308.el5 installed
kernel-xen.x86_64 2.6.18-308.11.1.el5 installed
xen.x86_64 3.0.3-135.el5_8.2 installed
xen-libs.i386 3.0.3-135.el5_8.2 installed
xen-libs.x86_64 3.0.3-135.el5_8.2 installed

i am looking at xend.log :
DEBUG (blkif:27) exception looking up device number for ioemu: [Errno 2] No such file or directory: '/dev/ioemu'

and from qemu-dm.log :
xs_read(/vm/ef776721-7310-7643-04fc-6ec03bfca9b0/rtc/timeoff set): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
gpe_sts_write: addr=0x1f68, val=0x0.
gpe_sts_write: addr=0x1f69, val=0x0.
ACPI PCI hotplug: read addr=0x10c1, val=0x0.
ACPI PCI hotplug: read addr=0x10c2, val=0x0.

from xend-debug.log:
TypeError: int argument required
Traceback (most recent call last):
File "/usr/lib64/python2.4/logging/handlers.py", line 71, in emit
if self.shouldRollover(record):
File "/usr/lib64/python2.4/logging/handlers.py", line 149, in shouldRollover
msg = "%s\n" % self.format(record)
File "/usr/lib64/python2.4/logging/__init__.py", line 617, in format
return fmt.format(record)
File "/usr/lib64/python2.4/logging/__init__.py", line 405, in format
record.message = record.getMessage()
File "/usr/lib64/python2.4/logging/__init__.py", line 276, in getMessage
msg = msg % self.args
TypeError: int argument required

Report message to a moderator