From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed,  7 Sep 2005 10:07:29 +0200
Message-ID: <3AF26F5605627543BEC429636A5222900B723C@rohrpostix.xplain.local>
From: "Retzki, Sascha [Xplain]" <sascha.retzki@xplain.de>
To: <9fans@cse.psu.edu>
Subject: [9fans] Xen, Plan9, VNC
Topicbox-Message-UUID: 850fe44e-ead0-11e9-9d60-3106f5b1d025

Hi Fans,

Yamanashi Takeshi and Tim Newsham talked about Xen and Plan9 (boot
parameters), and "by the way", the string "vnc" poped up, and I got a
question regarding this (and similars) (and please correct me if I am
wrong ;-)):

By default, Xen creates a console, so if you boot Plan9 as a domU, you
cannot fire up Rio.
Now does VNC fit into this picture somehow?


Generally, the thing is that Plan9 without Rio is not really cool, and I
would really enjoy a Xen-driven host with NetBSD, Linux, $whatnot and
Plan9, all displaying GUIs and whatnot. So my plans were:

1.) Install a second graphic card, hide it from dom0, hand it to one
domU so this domU can display something.

2.) Write some API for VirtualGraphicsCards (in Xen), so each domU sees
a virtual card, starts up its graphical system, and the dom0 can
"connect" to these systems (using some own approach or VNC, I did not go
into details to know that yet).


How would you solve this problem? What about approach 2, good enough to
brainstorm about it, maybe post our results to the xen-devel@-list?