From: Kip Macy <kip.macy@gmail.com>
To: "Retzki, Sascha [Xplain]" <sascha.retzki@xplain.de>
Cc: xen-devel@lists.xensource.com
Subject: Re: FreeBSD domU kernel
Date: Mon, 12 Sep 2005 12:52:41 -0700 [thread overview]
Message-ID: <b1fa291705091212521a549fa1@mail.gmail.com> (raw)
In-Reply-To: <3AF26F5605627543BEC429636A5222900B7433@rohrpostix.xplain.local>
[-- Attachment #1.1: Type: text/plain, Size: 1194 bytes --]
The instructions are out of date. You can build a FreeBSD domU in the xen
tree using the scripts provided.
-Kip
On 9/12/05, Retzki, Sascha [Xplain] <sascha.retzki@xplain.de> wrote:
>
>
> it is hard to find, it is hard to build: A FreeBSD domU kernel.
>
> Of course I found http://www.fsmware.com/xenofreebsd/, but the problem
> is that all i386-xen*.tar.gz files I can find don't build, as
> headerfiles are linked to some place in /t (?), and so on.
>
>
> Files that start with "kernel" are a really good try, they are indeed
> domU kernels, and they boot - but they all stop at (in verbose kernel
> output):
> [dmesg]
> cpu0 on motherboard
> Device configuration finished.
> procfs registered
> Timecounters tick every 10.000 msec
> xc0: <Xen Console> on motherboard
> WARNING: driver "xc" used unreserved major device number 12
> GEOM: new disk xdb0
> [... GEOM stuff ommited]
> lo0: bpf
> [/dmesg]
>
> I tried without xennet-devices, but nothing changed.
>
> So, does anyone has an idea?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
[-- Attachment #1.2: Type: text/html, Size: 1688 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2005-09-12 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 15:48 FreeBSD domU kernel Retzki, Sascha [Xplain]
2005-09-12 19:52 ` Kip Macy [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=b1fa291705091212521a549fa1@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=sascha.retzki@xplain.de \
--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 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.