From: George Dunlap <dunlapg@gmail.com>
To: taskstructfromhell@googlemail.com
Cc: xen-devel@lists.xensource.com, Etienne Martineau <etmartin@cisco.com>
Subject: Re: Hypervisor architecture?
Date: Fri, 7 May 2010 10:05:18 -0500 [thread overview]
Message-ID: <r2kde76405a1005070805y36b114e8j2070488e08dfcc9d@mail.gmail.com> (raw)
In-Reply-To: <1273015225.7760.21.camel@stellar.promisc.org>
On Tue, May 4, 2010 at 6:20 PM, TSFH <taskstructfromhell@googlemail.com> wrote:
> It would also be useful if someone on this list who have read the book
> could enlighten the community WRT possible caveats on the book or parts
> that no longer resemble the current implementation, as it appears Xen
> has changed considerably since the book was released.
I haven't read the book, but we have had several people come to the
list to try to get help getting the "pluggable scheduler" example from
the book working. The two caveats are:
* The example code, as it's written in the book, doesn't actually work
* The scheduler is actually a lot harder than it looks. It's at one
of the very lowest layers. If there's a bug, the whole system hangs
(as opposed to just returning an error message). Debugging it takes a
lot of skill. So it's not a good place to start playing around with
Xen. :-)
-George
prev parent reply other threads:[~2010-05-07 15:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 19:25 Hypervisor architecture? Etienne Martineau
2010-05-04 20:33 ` Jeremy Fitzhardinge
2010-05-04 23:36 ` Etienne Martineau
2010-05-04 23:58 ` Jeremy Fitzhardinge
2010-05-04 23:20 ` TSFH
2010-05-07 15:05 ` George Dunlap [this message]
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=r2kde76405a1005070805y36b114e8j2070488e08dfcc9d@mail.gmail.com \
--to=dunlapg@gmail.com \
--cc=etmartin@cisco.com \
--cc=taskstructfromhell@googlemail.com \
--cc=xen-devel@lists.xensource.com \
/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).