Re: Bootstrapping a Linux domU from scratch in a NetBSD dom0

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

On Fri, Apr 06, 2007 at 03:45:16PM -0400, Steven M. Bellovin wrote:
> On Thu, 5 Apr 2007 00:38:33 +0200
> Harold Gutch <logix%foobar.franken.de@localhost> wrote:
> 
> > Hi,
> > 
> > this actually isn't really NetBSD-related, but I could imagine that
> > some people on this list might find this interesting - also, I believe
> > that the goal is easier to achieve in a Linux dom0, so the main
> > audience probably actually are people running a NetBSD dom0.
> > 
> > Anyway, I wrote up a guide dealing with the problem of getting a Linux
> > domU up and running given a NetBSD dom0, without having to clone an
> > existing Linux-installation.  You rather create a Debian-installation
> > completely from scratch, without needing an existing Linux
> > installation or even (any) access to a Linux box at all.
> > 
> > Well, here's the URL.  Have fun with it, and I'm always open to
> > comments etc. on it:
> > 
> >   http://www.gutch.de/NetBSD/docs/xen.html
> > 
> 
> Minor comments: with xen3, the 'nics=' line should be deleted, and
> 'cpu=-1' doesn't work.
> 
> Major comment: it won't boot:
> 
>       VFS: Cannot open root device "hda1" or unknown-block(0,0)
>       Please append a correct "root=" boot option
>       Kernel panic - not syncing: VFS: Unable to mount root fs on
>       unknown-block(0,0)
> 
> I suspect the problem is that I need a /dev entry for hda1, but I have

No, you don't. Here's what I use for a linux domU on xen3:
disk = [ 'file:/domains/house0.vnd,hda,w']

root = "/dev/hda1 ro"

I'm not sure you can use 'hda1' instead of 'hda' in the disk entry with
Xen3.

-- 
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
     NetBSD: 26 ans d'experience feront toujours la difference
--