From: Travis Newman <panickedthumb@gmail.com>
To: xen-devel@lists.sourceforge.net
Subject: Xen kernel issue
Date: Sun, 30 Jan 2005 15:43:02 -0500 [thread overview]
Message-ID: <41FD46D6.50203@gmail.com> (raw)
I've gotten Xen working for dom0, but I haven't gone past that because
when using the Xen kernel, there's no support for fat filesystems (which
contain a lot of what I need, though I don't use Windows anymore, I
don't have the space to backup everything to format to ext3) and no
support for sound. I'm using Alsa by the way. I've tried to recompile
the kernel in different ways. First off, I tried "make ARCH=xen xconfig"
and enabling what I needed, "make ARCH=xen oldconfig" after restoring my
.config from my current kernel, and finally, using mkbuildtree to
xen-ify my kernel source (2.6.10) and then loading the .config from
xconfig. None of these worked, they would keep failing for different
reasons. I can be more specific if I need to, I'm just wondering what
the "right way" to get the exact same options that are in my kernel now,
along with the xen options.
I'm using Ubuntu Linux (a Debian variant), and though I'm using a stock
kernel, I have had experience with compiling my own kernel before.
Thanks in advance!
Travis
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next reply other threads:[~2005-01-30 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-30 20:43 Travis Newman [this message]
2005-01-31 1:38 ` Xen kernel issue Travis Newman
2005-01-31 2:05 ` Travis Newman
2005-01-31 2:58 ` Robin Green
[not found] ` <f6244b740502011740392349b8@mail.gmail.com>
2005-02-02 2:18 ` Robin Green
2005-01-31 3:03 ` Mark Williamson
2005-01-31 4:57 ` Travis Newman
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=41FD46D6.50203@gmail.com \
--to=panickedthumb@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.