From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steven Smith <sos22-xen@srcf.ucam.org>
Subject: Re: [PATCH] Paravirt framebuffer frontend kernel support
	[1/5]
Date: Fri, 3 Nov 2006 17:01:35 +0000
Message-ID: <20061103170135.GA5457@cam.ac.uk>
References: <20060904090045.GA4812@cam.ac.uk>
	<87hczgrx07.fsf@pike.pond.sub.org>
	<20060910093801.GA1874@cam.ac.uk>
	<87wt7l68jm.fsf@pike.pond.sub.org>
	<871womyxa3.fsf@pike.pond.sub.org>
	<20061102103643.GB3879@leeni.uk.xensource.com>
	<87slh2xc0m.fsf@pike.pond.sub.org>
	<20061102161955.GA7065@cam.ac.uk>
	<20061102163111.GA5265@leeni.uk.xensource.com>
	<87mz78wr4v.fsf@pike.pond.sub.org>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0032267712=="
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <87mz78wr4v.fsf@pike.pond.sub.org>
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>
Mime-version: 1.0
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Markus Armbruster <armbru@redhat.com>
Cc: aliguori <aliguori@mail.utexas.edu>, Ewan Mellor <ewan@xensource.com>, xen-devel <xen-devel@lists.xensource.com>, Jeremy Katz <katzj@redhat.com>
List-Id: xen-devel@lists.xenproject.org


--===============0032267712==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="IS0zKkzwUGydFO0o"
Content-Disposition: inline


--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

> I created a trivial xend/server/vfbif.py:
Looks plausible.  You probably want to have a createDevice method
which calls DevController.createDevice and then spawns the backend,
but that can come later.

> I added it to xend/XendDomainInfo.py, as follows:
I think this bit is correct.

I think this should work if your SXP includes an entry for the
backend.  Adding something like ``(device (vfb ()))'' to the end of
the (vm) section should work.

``xm create -n'' will convert an ordinary xm configuration file to SXP
format, and ``xm create -C'' can create a domain directly from the
SXP.  Eventually, you'll want to add something to the xm parser which
makes it possible to do this without directly editting the SXP, but
that can wait for a bit.

Steven.

--IS0zKkzwUGydFO0o
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFS3XvO4S8/gLNrjcRAnwhAJ4+fXLSuwtwfgdTGHcWCcj+Y0YXYACgvPPS
0Y33sjSJOg0/pNvW6+mMF8A=
=FyUu
-----END PGP SIGNATURE-----

--IS0zKkzwUGydFO0o--


--===============0032267712==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

--===============0032267712==--