From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] THX hell
Date: Tue, 1 May 2007 14:45:26 -0700 [thread overview]
Message-ID: <13426df10705011445h13cffe07x606dc71f8a365ca8@mail.gmail.com> (raw)
In-Reply-To: <20070501214043.86B6E5B2E@mail.bitblocks.com>
On 5/1/07, Bakul Shah <bakul+plan9@bitblocks.com> wrote:
> > 1. Stick with Xen, add vesafb to Xen, done.
> > 2. Stick with Xen, add X server to THX distro, run drawterm-x11, done.
> > 3. Move to KVM, so we can have vesafb, use drawterm-fb, done.
> >
> > any ideas here? What makes sense?
>
> Doesn't KVM requires hardware virtualization? Also Xen is
> supposedly faster on most benchmarks. Choice 2, while not
> ideal, makes the most sense to me.
>
That's what I decided too. yes, xen is 6x faster than kvm right now.
At the same time, I'm getting lots of input from folks in the business
that they expect kvm to win in the long run. But, for now, Xen is it.
I'm trying and failing to get X started in THX. X starts, but never
gets the keyboard. I think it's because the tty control is never
really started up. You can't do ctl-alt-f1, for example. Also, if I do
the magic sysrq sequence it works fine.
I hate to ask an X11 question here, but what would cause X not to be
able to grab keyboard?
ron
next prev parent reply other threads:[~2007-05-01 21:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 18:42 ron minnich
2007-05-01 18:46 ` Richard Miller
2007-05-01 18:52 ` ron minnich
2007-05-01 20:59 ` geoff
2007-05-01 21:40 ` Bakul Shah
2007-05-01 21:45 ` ron minnich [this message]
2007-05-01 22:14 ` Steve Simon
2007-05-02 0:24 ` ron minnich
2007-05-02 0:29 ` Eric Van Hensbergen
2007-05-02 9:14 ` csant
2007-05-02 17:00 ` ron minnich
2007-05-02 17:28 ` Anthony Sorace
2007-05-02 17:45 ` W B Hacker
2007-05-03 7:23 ` csant
2007-05-02 22:26 ` csant
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=13426df10705011445h13cffe07x606dc71f8a365ca8@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).