Subject: Re: How to use a file system image for Linux DomU ?
To: Thierry Herbelot <thierry@herbelot.com>
From: Manuel Bouyer <bouyer@antioche.eu.org>
List: port-xen
Date: 08/03/2005 12:54:38
On Mon, Jul 25, 2005 at 07:22:26PM +0200, Thierry Herbelot wrote:
> [...]
> has someone been able to run an image-based Linux DomU under NetBSD/Dom0 ?
>
> Cheers
>
> TfH
>
> (as this was crucial for partition-based Linux/DomUs, the /dev/vnd0d has been
> formatted from NetBSD using e2fsprogs-1.32)
>
> -------------------------------------
>
> When I start the image-based Linux DomU and a vmlinuz-2.4.30-XenU kernel :
> xm create -c dom5.debian.image
> Using config file "dom5.debian.image".
> Started domain Debian-dom5, console on port 9614
> ************ REMOTE CONSOLE: CTRL-] TO QUIT ********
> Linux version 2.4.30-xenU (xenod@freefall.cl.cam.ac.uk) (gcc version 3.3.3
I admit I never tried to start a linux-2.4.x kernel from NetBSD dom0.
linux-2.6.x works fine for me.
> [...]
>
> When I start the image-based Linux DomU and a vmlinuz-2.6.11.10-xenU :
> Linux version 2.6.11.10-xenU (xenod@freefall.cl.cam.ac.uk) (gcc version 3.3.3
> 20040412 (Red Hat Linux 3.3.3-7)) #1 Sun May 22 11:42:16 BST 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 0000000002000000 (usable)
> 32MB LOWMEM available.
> ....
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 112k freed
> attempt to access beyond end of device
> sda1: rw=0, want=2576980378, limit=819200
> Buffer I/O error on device sda1, logical block 3435973836
> [multiply repeated identical error message]
OK, this is known problem with the NetBSD xbd backend, which should be fixed
now. Try to update to a more recent NetBSD kernel (newer than 07/19 on
current).
--
Manuel Bouyer <bouyer@antioche.eu.org>
NetBSD: 26 ans d'experience feront toujours la difference
--