From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DA3kX-0005FS-6g for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:21:37 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DA3kS-0005ED-Mx for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:21:35 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DA3kQ-00058N-PK for qemu-devel@nongnu.org; Sat, 12 Mar 2005 05:21:31 -0500 Received: from [193.252.22.21] (helo=smtp10.wanadoo.fr) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DA3LX-0005hs-Fg for qemu-devel@nongnu.org; Sat, 12 Mar 2005 04:55:47 -0500 Subject: Re: [Qemu-devel] gentoo disk image for QEmu From: =?ISO-8859-1?Q?J=E9r=F4me?= Bouat In-Reply-To: References: <1110228937.3297.18.camel@penguin> Content-Type: text/plain; charset=ISO-8859-15 Date: Sat, 12 Mar 2005 10:55:49 +0100 Message-Id: <1110621349.28647.6.camel@penguin> Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Magnus Damm , qemu-devel@nongnu.org Here is what did my scripts in order to install the bootloader : --- /sbin/losetup $(loop_device_2) $(disk_image).tmp && \ mount -t proc none $(tree)/proc && \ $(chroot) $(tree) /bin/bash install_grub.sh && \ /sbin/losetup -d $(loop_device_2) && \ --- with 'install_grub.sh': --- /usr/sbin/env-update && source /etc/profile && echo using this device map for GRUB: && echo --- && cat dev.map && echo --- && grub --device-map=3Ddev.map < Hello, >=20 > On Mon, 07 Mar 2005 21:55:36 +0100, J=E9r=F4me Bouat > wrote: > > I would generate a Gentoo Linux disk image for QEmu. > >=20 > > This source based Linux distro can be configurated to generate hardwa= re > > specific binaries through its package management system. > >=20 > > I previously tried with Bochs. Therefore, I wrote some scripts. The m= ain > > part of the generation was made in a Linux chrooted environment on a > > real host which was compatible with the emulated host. The disk image > > generation was blocked by the boot loader installation step. >=20 > I'm not sure I understand your question. Is the problem that the > chrooted environment was unable to install a bootloader for the target > system? >=20 > I've hacked up a filesystem manipulation tool that is available for dow= nload at: >=20 > http://www.smallworks.com/~jim/fsimage/ >=20 > The tool is actually a shell script and a small x86 distribution that > together are used to access filesystems independent of root access or > host kernel configuration. Needless to say, the tool depends on QEMU. > 0.6.1 or newer. >=20 > I am not sure if the tool is of interest for you, but maybe it helps. >=20 > / magnus >=20 >=20 > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel >=20