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: xend issues

To: "Neugebauer, Rolf" <rolf.neugebauer@xxxxxxxxx>
Subject: [Xen-devel] Re: xend issues
From: Leendert van Doorn <leendert@xxxxxxxxxxxxxx>
Date: Wed, 15 Jun 2005 20:18:15 -0400
Cc: "Sharma, Arun" <arun.sharma@xxxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 16 Jun 2005 00:19:12 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Organization: IBM T.J. Watson Research Center
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Neugebauer, Rolf wrote:

# On a related note, currently the VNC viewer for the VMX domain is
# started by xend but in my opinion should be started by 'xm' (as with
# native xen VMs) as you are more likely to have your DISPLAY/XAUTH set
# when executing xm rather than when xend is started.


This is why I added VMX support to vmtools. It allowed me to create the
device model from the controlling terminal so that it would have access
to the user's environment and it even allowed me to pass options to qemu
such as "-monitor stdio" so I could issue "change cdrom ..."  commands.

Alas, the developers of vmtools have (temporarily?) dropped vmx support
from vmtools and the old version is incompatible with the latest version
of Xen.  I'm now forced to use xm/xend as well :-( :-(


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>