[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] FreeBSD domU kernel
- To: "Retzki, Sascha [Xplain]" <sascha.retzki@xxxxxxxxx>
- From: Kip Macy <kip.macy@xxxxxxxxx>
- Date: Mon, 12 Sep 2005 12:52:41 -0700
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Mon, 12 Sep 2005 19:50:33 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:references; b=M49VWhdvrA6iN55roo+Pv+q3a/Hfu3Qd8X0nz6ACFWglkZaItmsooqc6pR/4A88Kt63fK1+vgAxy8Tk+kU55D8QOdR+Pa+ITguW1ZXJzKc0Gi+Hxc172Rj6qafhP+C1eCuGNwOujkNJpe8gy7XgsEFeTO4cLpipRGD26byAZVm0=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
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@xxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
