From mboxrd@z Thu Jan  1 00:00:00 1970
From: Arun Sharma <arun.sharma@intel.com>
Subject: Re: [PATCH][1/10] Device model cleanup.
Date: Thu, 30 Jun 2005 13:19:11 -0700
Message-ID: <42C453BF.1030906@intel.com>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D28246A@liverpoolst.ad.cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D28246A@liverpoolst.ad.cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: Ian Pratt <Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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
> present?

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

	-Arun