Thanks for your response.

I tried running it with a simple: ./vmlinux ubd0=root_fs.2005062201
and now it says:

[42949373.420000] Console initialized on /dev/tty0
[42949373.420000] ubda: unknown partition table
[42949373.420000] kjournald starting. Commit interval 5 seconds
[42949373.420000] EXT3-fs: mounted filesystem with ordered data mode.
[42949373.420000] VFS: Mounted root (ext3 filesystem) readonly.
[42949373.420000] Warning: unable to open an initial console.
[42949373.420000] Kernel panic - not syncing: Attempted to kill init!

Looks like it mounted the root file system but has a problem opening
a console. Maybe I'm missing some console related option in the kernel
config?

Thanks,

-Etay

On 9/30/05, Blaisorblade <blaisorblade@yahoo.it> wrote:
>
> On Friday 30 September 2005 12:51, Etay Meiri wrote:
> > Hi,
> >
> > I downloaded a root file system from:
> > http://www.stearns.org/uml-root/root_fs.fc-4-base.pristine.20050622.bz2
> > and followed the instructions in
> > http://www.stearns.org/uml-root/root_fs.fc-4-base.pristine.20050622.note
> > in order to extract it. I am able to mount it as a loop device without
> > problems.
> > I applied the patch from
> >
> http://www.user-mode-linux.org/~blaisorblade/patches/guest/uml-2.6.13-bs2/u
> >ml-2.6.13-bs2.patch.bz2 to the 2.6.13 vanilla kernel and built a uml
> kernel
> > with ext3 support not as a module.
> > Now when I run it I get the following error:
>
> > [cl@amber uml]$ ./vmlinux mem=160M ubd0=root_fs.2005062201 ubd1=swap
> > root=/dev/ubd/0 con=pty con0=fd:0,fd:1
> root=/dev/ubd/0 is wrong for two reasons:
> *) you don't need to specify root=, UML automatically sets it to point to
> ubd0
>
> *) /dev/ubd/0 is the DevFS syntax, and since 2.6.13 DevFS is no more
> supported.
>
> *) I'm not even sure if root=/dev/ubd0 would work - Uml, to be sure, uses
> major and minor (root=98:0).
>
> Thanks for attaching the logs, but look below:
> > [42949373.560000] VFS: Cannot open root device "ubd/0" or
> > unknown-block(0,0) [42949373.560000] Please append a correct "root="
> boot
> > option
> > [42949373.560000] Kernel panic - not syncing: VFS: Unable to mount root
> fs
> > on unknown-block(0,0)
> > [42949373.560000]
>
> The trace below is always output in case of panic, but in this case it's
> not a
> kernel bug, so don't get confused by it.
> > [42949373.560000] EIP: 0073:[<a0382721>] CPU: 0 Not tainted ESP:
> > 007b:b7f7df9c EFLAGS: 00200246
> > [42949373.560000] Not tainted
> > [42949373.560000] EAX: 00000000 EBX: 00000a1f ECX: 00000013 EDX:
> 00000a1f
> > [42949373.560000] ESI: 00000a1e EDI: 00000011 EBP: b7f7dfb8 DS: 007b ES:
> > 007b
> > [42949373.560000] aae97ac0: [<a006304d>] show_regs+0x309/0x378
> > [42949373.560000] aae97af0: [<a002d1c3>] panic_exit+0x43/0x8c
> > [42949373.560000] aae97b20: [<a0097206>] notifier_call_chain+0x2e/0x88
> > [42949373.560000] aae97b50: [<a006d7df>] panic+0x9f/0x1f8
> > [42949373.560000] aae97b80: [<a000231a>] mount_block_root+0x116/0x1cc
> > [42949373.560000] aae97bd0: [<a00025ee>] mount_root+0x7e/0x94
> > [42949373.560000] aae97bf0: [<a000266d>] prepare_namespace+0x69/0x224
> > [42949373.560000] aae97c00: [<a001c3c7>] init+0x1d7/0x220
> > [42949373.560000] aae97c20: [<a00227c5>] run_kernel_thread+0x59/0x74
> > [42949373.560000] aae97ce0: [<a003538e>] new_thread_handler+0xd2/0x138
> > [42949373.560000] aae97d20: [<b7f7f420>] 0xb7f7f420
> > [42949373.560000]
> > [42949373.560000]
>
> --
> Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
> Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ
> 215621894)
> http://www.user-mode-linux.org/~blaisorblade
>
>
>
>
>
> ___________________________________
> Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
> http://mail.yahoo.it
>
>


--
------------------------------------------------------
Etay Meiri
etay.meiri@gmail.com