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] PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] PATCH: 0/10: Merge xenfb & xenconsoled into qemu-dm
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Wed, 15 Aug 2007 21:00:56 +0100
Delivery-date: Wed, 15 Aug 2007 13:01:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
The following series of 10 patches is a merge of the xenfb and xenconsoled
functionality into the qemu-dm code. The general approach taken is to have
qemu-dm provide two machine types - one for xen paravirt, the other for
fullyvirt. For compatability the later is the default. The goals overall
are to kill LibVNCServer, remove alot of code duplication and/or parallel
impls of the same concepts, and increase the functionality for PV. In
particular this will let paravirt guests take advantage of TLS encryption
for the VNC server, and let us configure the text console in all the variety
of ways QEMU supports (PTY, File, TCP, TCP_Telnet,UDP, etc).

One interesting possiblity that merging the text & graphics consoles into
same daemon allows for, is to expose the pygrub screens over both a PTY 
and VNC server at the same time. If I can figure out how to actually code
this idea it would solve a major headache when using bootloaders with PV
guests remotely.

The only feature this re-factoring looses is the ability to have the paravirt
text console persistently logged to a file. QEMU allows us to specify that
a character device is either sent to a PTY, or a file, but not both at the
same time. I'm thinking about ways in which QEMU's character device config
syntax & drivers may be extended to allow use of a PTY & File concurrently.

The patches should be applied in order - after each individual patch you
should still have a fully operational system for both FV & PV.

|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

Xen-devel mailing list