This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH][1/10] Device model cleanup.

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: [Xen-devel] Re: [PATCH][1/10] Device model cleanup.
From: Arun Sharma <arun.sharma@xxxxxxxxx>
Date: Thu, 30 Jun 2005 13:19:11 -0700
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Jun 2005 20:18:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D28246A@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28246A@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Ian Pratt wrote:

Rolf applied a patch sometime back that has two separate ways of connect a vncviewer to device models:

a) vncviewer -listen (port communicated to xend and then to qemu via -vncconnect). This is forked from xm.
b) libvncserver within qemu-dm (-vncport). This is forked from xend.

And then

c) the user may choose vnc=0 sdl=1.

Just to check I understand:

In (a), xm forks off vncviewer, qemu-dm runs libvncserver and then
connects back to the viewer.  I presume we can still fix the local port
with -vncport?

-vncport is for (b). For (a) the user doesn't get to specify the local port - an unused local port is auto picked.

In (b), what is actually forking the vncviewer, and when does it know
that the libvncserver is up and running?

For (b) the user manually starts the vncviewer, possibly from a different machine.

For (c), we just pop up an Xwindow on the Display.
* we still need some tests when building to ensure libvncserver and libsvg are installed. As the current behaviour when they're not is confusing -- I think its better to refuse to build ioemu if they're not installed.

Not all distributions are shipping libvncserver (for eg: FC4 didn't). Once we resolve that I think it's a reasonable thing to do.

Can we fail to support vnc gracefully at run time if the library isn't

I think so. This is how VMX on FC4 works. We'll verify and send patches if anything is broken..


Xen-devel mailing list