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 11:42:17 -0700
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 30 Jun 2005 18:41:17 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D28244A@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: <A95E2296287EAD4EB592B5DEEFCE0E9D28244A@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Ian Pratt wrote:

This is useful progress, but I have a couple of comments/questions.

* should the empty config options be appearing in the sxp? I don't think
so. Further, perhaps they should be wrapped in a (ioemu ...) section?

* we should make it such that disks can be specified using the same
syntax as for normal paravirt drives e.g. file:, phy: etc.

Yes, will implement both of these.

* I presume that the vncviewer is being forked from xm, but that the
vncconect is being issued from xend, which is why it needs the $DISPLAY

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.

It's really case (c) that requires $DISPLAY. Also, I think the end user needs only one of (a) and (b), not both. If $DISPLAY is not set in xm's environment, (a) will fail. In that sense (b) is more reliable.

* 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

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

* we should move qemu-dm from /usr/bin to /usr/lib/xen/bin

* files like mem-map.sxp should probably live in /usr/lib/xen/boot

* presumably we no longer need bochsrc ?

Thanks for the comments. You should see some patches today.


Xen-devel mailing list