[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] xen 3.3.1, HVM, vncunused=0 problem?


  • To: Xen List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
  • Date: Sat, 31 Jan 2009 23:08:35 +0700
  • Delivery-date: Sat, 31 Jan 2009 08:09:23 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I've been using vncunused=0 on HVM domU config file, and it works fine
on RH's Xen-3.1
However, on Xen 3.3.1 it seems to be broken. The domU won't start properly.

xm list shows this (note strange State)

Name                                        ID   Mem VCPUs      State   Time(s)
testvnc                                     19   500     1     ------      0.0

/var/log/xen/xend.log shows normal output
[2009-01-31 22:59:22 6717] INFO (XendDomain:1174) Domain testvnc (19) unpaused.

/var/log/xen/qemu-dm-testvnc.log shows something's wrong
domid: 19
qemu: the number of cpus is 1
config qemu network with xen bridge for  tap19.0 br6
Watching /local/domain/0/device-model/19/logdirty/next-active
Watching /local/domain/0/device-model/19/command
xs_read(): vncpasswd get error.
/vm/5ec82aad-523f-453e-279f-35c4d185d8e3/vncpasswd.
bind() failed

The questions are :
(1) Is this a known problem?
(2) commenting vncunused=0 line made the domain startup normally,
However, this means domU's vnc console will use the next available
port starting from 5900. Is there a way to make the correlation which
domain uses which port?

Regards,

Fajar

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.