From: Will Andrews <andrewsw@crypt.rcac.purdue.edu>
To: xen-devel@lists.sourceforge.net
Subject: Re: Xen unprivileged domain not booting
Date: Tue, 24 Aug 2004 12:02:28 -0500 [thread overview]
Message-ID: <20040824170228.GN606@crypt.rcac.purdue.edu> (raw)
In-Reply-To: <E1BzedR-0005yV-00@mta1.cl.cam.ac.uk>
On Tue, Aug 24, 2004 at 05:59:00PM +0100, Ian Pratt wrote:
> The file from the 2.6 tree is linked into the 2.4 build tree as
> its common between both. (It makes it easier for us to maintain
> than having two files).
Ah, ok. I didn't realize there were files shared between the
sparse trees. I am rebuilding the kernel now, just replying to
answer your question:
> Are you sure you're exporting the partition read-write rather
> than read-only? I guess that might result in 'short write' messages.
"Exporting" it? It's just a filesystem I set aside for Xen
domain 1, it's not NFS mounted.
Thanks,
--
wca
Purdue University Rosen Center for Advanced Computing
Office: MATH G135 @ Purdue - http://www.itap.purdue.edu/rcs/
NB: crypt.rcs.purdue.edu has retired recently, please use
andrewsw@crypt.rcac.purdue.edu for all future contact.
-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
next prev parent reply other threads:[~2004-08-24 17:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 22:21 Xen unprivileged domain not booting Will Andrews
2004-08-21 7:24 ` Ian Pratt
2004-08-24 16:42 ` Will Andrews
2004-08-24 16:59 ` Ian Pratt
2004-08-24 17:02 ` Will Andrews [this message]
2004-08-24 17:13 ` Ian Pratt
2004-08-24 17:20 ` Mark Williamson
2004-08-24 17:15 ` Mark Williamson
2004-08-24 17:03 ` Mark Williamson
2004-08-24 16:52 ` Will Andrews
2004-08-24 17:02 ` Niraj Tolia
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=20040824170228.GN606@crypt.rcac.purdue.edu \
--to=andrewsw@crypt.rcac.purdue.edu \
--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.