On 10/19/07, Kjel Delaey <[EMAIL PROTECTED]> wrote: > > If I do this I got a VFS problem > > Not syncing: VFS: Unable to mount root fs on unknown-block(3,1.)
then maybe it's a kernel config issue. it may not be only fs dependent. do you have the .config file ? > > I also tried to enable reiserfs support. I read on a forum that this may be > a solution to the init problem. In my case it wasn't a working solution. > > ________________________________ > > From: [EMAIL PROTECTED] > > To: qemu-devel@nongnu.org; [EMAIL PROTECTED] > > Subject: Re:[Qemu-devel] Kernel panic - not syncing: No init found. > Trypassing init= option to kernel. > > Date: Fri, 19 Oct 2007 09:19:59 +0200 > > CC: > > > > > On Friday 19 October 2007 09:13:40 [EMAIL PROTECTED] wrote: > > > Then I try this command: > > > qemu -m 32 hda rootfs.img kernel linux-2.6.18.1/arch/i386/boot/bzImage > > > -append "root=/dev/hda \clock=pit" > > > > > > and I get the error... > > > > > > I tried to pass init=/sbin/init or init=/bin/init but it doesn't help... > > > > Hi! > > Although allmost every documentation tells you to use exactly what you > did, I > > always use > > > > qemu [....] -append "root=/dev/hda1" > > > > (note HDA1 instead HDA) > > > > and direct booting works fine for me :-) > > > > Clemens > > > > > > ________________________________ > Start vandaag nog je eigen Windows Live Space en deel je leven met je > vrienden Windows Live Spaces -- Christian -- http://detaolb.sourceforge.net/, a linux distribution for Qemu with Git inside !
