From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Rick <judicator3@gmail.com>, xen-devel@lists.sourceforge.net
Subject: Re: Re: mini-os for Xen2
Date: Sat, 12 Feb 2005 18:39:07 -0800 [thread overview]
Message-ID: <420EBDCB.3030709@diku.dk> (raw)
In-Reply-To: <E1CzwpI-0008Cd-00@mta1.cl.cam.ac.uk>
Keir Fraser wrote:
> xm gives the world's most unhelpful error messages. You may well find
> a more useful message hidden away in /var/log/xend[-debug].log as
> comes straight from the domain builder in libxc.
>
> My guess woul dbe that you do not have a '__xen_guest' section in your
> Elf image. Look at the top of
> linux-2.6.10-xen-sparse/arch/xen/i386/kernel/head.S for an example of
> how to specify one.
>
The new vm-tools that were just announced will probably be easier to use
for this kind of debugging than xn/xend. Also, I used to re-create the
HYPERVISOR_console_write syscall, and configure Xen to allow unpriv
domains to write to the serial console. I think the new
HYPERVISOR_console_io syscall can be convinced to do the same thing.
In my xen tarball at http://www.diku.dk/~jacobg/self-migration/ you can
find the source of 'mstrap' which is very much like mini-os, but perhaps
a little more up to date. The network driver is not working in Xen2, but
the elf-image should at least load using the recent tools.
Jacob
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-13 2:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 23:56 mini-os for Xen2 Rick
2005-02-12 11:01 ` Rick
2005-02-12 12:56 ` Keir Fraser
2005-02-13 2:39 ` Jacob Gorm Hansen [this message]
2005-02-14 1:37 ` Rick
-- strict thread matches above, loose matches on Subject: below --
2005-02-14 1:50 Ian Pratt
2005-02-14 2:52 ` Rick
2005-02-15 1:32 ` Rick
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=420EBDCB.3030709@diku.dk \
--to=jacobg@diku.dk \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=judicator3@gmail.com \
--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.