From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Mark Williamson <maw48@hermes.cam.ac.uk>
Cc: Jan Kundr?t <jan.kundrat@fzu.cz>,
Ian Pratt <Ian.Pratt@cl.cam.ac.uk>,
xen-devel@lists.sourceforge.net
Subject: Re: protecting xen startup
Date: Wed, 24 Nov 2004 10:39:30 +0000 [thread overview]
Message-ID: <20041124103930.GM5146@lkcl.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0411240813430.6001@hermes-1.csi.cam.ac.uk>
On Wed, Nov 24, 2004 at 08:17:27AM +0000, Mark Williamson wrote:
> >can i run an xserver in a separate guest OS and still allow the guest
> >OS direct access to the screen?
> >
> >how is that done - via a framebuffer drive?
> >
> >tellmetellme!!!!
>
> There was a very brave chap who had a second PCI graphics card and a
> second PCI USB controller, which he had given a domain (!=dom0) privileges
> to access and was trying to persuade X to run. I'm not sure how far he's
> got now but it's not straightforward.
that's what i kinda figured: that the solution would open up a larger
can of worms than the alternative.
not that i'm happy with it but it appears to be the simplest solution.
_another_ alternative which i don't believe offers _that_
much benefit is to run nomachine:
/etc/apt/sources.list -> deb http://debian.tu-bs.de/knoppix/nx/slh-debian/ ./
then it'd be possible to turn the xen master domain into a thin client
and have kde / gnome / fvwm / whatever running in a guest domain.
... but nomachine is quirky to set up, even with the packages being
available at the above location.
l.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-11-24 10:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 17:05 protecting xen startup Luke Kenneth Casson Leighton
2004-11-23 18:07 ` Mike Wray
2004-11-23 21:03 ` Luke Kenneth Casson Leighton
2004-11-23 18:07 ` Mark Williamson
2004-11-23 20:51 ` Luke Kenneth Casson Leighton
2004-11-23 21:03 ` Ian Pratt
2004-11-23 21:52 ` Luke Kenneth Casson Leighton
2004-11-23 22:00 ` Jan Kundrát
2004-11-24 0:21 ` Luke Kenneth Casson Leighton
2004-11-24 8:17 ` Mark Williamson
2004-11-24 10:39 ` Luke Kenneth Casson Leighton [this message]
2004-11-23 22:49 ` Mark Williamson
2004-11-24 0:18 ` [Xen-devel] " Luke Kenneth Casson Leighton
2004-11-24 0:18 ` Luke Kenneth Casson Leighton
2004-11-24 8:27 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2004-11-23 17:33 Charles Coffing
2004-11-23 17:58 ` Mike Wray
2004-11-23 23:58 Neugebauer, Rolf
2004-11-24 10:53 ` Luke Kenneth Casson Leighton
2004-11-24 11:55 ` Mark Williamson
2004-11-24 11:48 Neugebauer, Rolf
2004-11-24 15:24 ` Luke Kenneth Casson Leighton
2004-11-24 20:24 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041124103930.GM5146@lkcl.net \
--to=lkcl@lkcl.net \
--cc=Ian.Pratt@cl.cam.ac.uk \
--cc=jan.kundrat@fzu.cz \
--cc=maw48@hermes.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.