If I used root=/dev/ubd0 or root=/dev/ubda I get basically the same error VFS: Cannot open root device "ubd0" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Adding con0=... did not get rid of the parse_chan_pair errors. Antoine Martin wrote: > have you tried adding root=/dev/ubda ? > > using ubda/b/c instead of ubd0/1/2? > > And for the parse_chan_pair warnings, you may also want: > con0=fd:0,fd:1 con=null > > > Antoine > > Jon Rafkind wrote: >> I just tried UML with the new 2.6.25 kernel but it would not boot up >> properly. I was using the same rootfs with 2.6.21.3 and it worked fine. >> >> $ file rootfs/Gentoo-2006.1-AMD64-root_fs >> rootfs/Gentoo-2006.1-AMD64-root_fs: Linux rev 1.0 ext3 filesystem >> data (large files) >> $ ./linux ubd0=rootfs/Gentoo-2006.1-AMD64-root_fs ubd1=rootfs/swap_fs >> ubd2=rootfs/usr eth0=tuntap,,,192.168.0.254 mem=256MB >> >> Core dump limits : >> soft - 0 >> hard - NONE >> Checking that ptrace can change system call numbers...OK >> Checking syscall emulation patch for ptrace...missing >> Checking for tmpfs mount on /dev/shm...OK >> Checking PROT_EXEC mmap in /dev/shm/...OK >> Checking for the skas3 patch in the host: >> - /proc/mm...not found: No such file or directory >> - PTRACE_FAULTINFO...not found >> - PTRACE_LDT...not found >> UML running in SKAS0 mode >> Linux version 2.6.25 ([EMAIL PROTECTED]) (gcc version 4.1.2 >> (Gentoo 4.1.2 p1.0.1)) #1 Thu Apr 17 09:52:08 MDT 2008 >> Built 1 zonelists in Zone order, mobility grouping on. Total pages: >> 64640 >> Kernel command line: ubd0=rootfs/Gentoo-2006.1-AMD64-root_fs >> ubd1=rootfs/swap_fs ubd2=rootfs/usr eth0=tuntap,,,192.168.0.254 >> mem=256MB root=98:0 >> PID hash table entries: 1024 (order: 10, 8192 bytes) >> Dentry cache hash table entries: 32768 (order: 6, 262144 bytes) >> Inode-cache hash table entries: 16384 (order: 5, 131072 bytes) >> Memory: 251648k available >> Mount-cache hash table entries: 256 >> Checking that host ptys support output SIGIO...Yes >> Checking that host ptys support SIGIO on close...No, enabling workaround >> net_namespace: 280 bytes >> Using 2.6 host AIO >> NET: Registered protocol family 16 >> NET: Registered protocol family 2 >> IP route cache hash table entries: 2048 (order: 2, 16384 bytes) >> TCP established hash table entries: 8192 (order: 5, 131072 bytes) >> TCP bind hash table entries: 8192 (order: 4, 65536 bytes) >> TCP: Hash tables configured (established 8192 bind 8192) >> TCP reno registered >> Checking host MADV_REMOVE support...OK >> mconsole (version 2) initialized on /home/kazzmir/.uml/zA6EWE/mconsole >> VFS: Disk quotas dquot_6.5.1 >> Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> io scheduler noop registered >> io scheduler anticipatory registered (default) >> io scheduler deadline registered >> io scheduler cfq registered >> TCP cubic registered >> NET: Registered protocol family 1 >> NET: Registered protocol family 17 >> Initialized stdio console driver >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 1 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 2 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 3 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 4 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 5 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 6 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 7 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 8 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 9 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 10 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 11 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 12 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 13 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 14 : Configuration failed >> Using a channel type which is configured out of UML >> parse_chan_pair failed for device 15 : Configuration failed >> Console initialized on /dev/tty0 >> console [tty0] enabled >> console [mc-1] enabled >> VFS: Cannot open root device "98:0" or unknown-block(98,0) >> Please append a correct "root=" boot option; here are the available >> partitions: >> Kernel panic - not syncing: VFS: Unable to mount root fs on >> unknown-block(98,0) >> >> Modules linked in: >> Pid: 1, comm: swapper Not tainted 2.6.25 >> RIP: 0033:[<00002b375f178fe7>] >> RSP: 00007fff4bb7ebd8 EFLAGS: 00000206 >> RAX: 0000000000000000 RBX: 0000000000006ac6 RCX: ffffffffffffffff >> RDX: 0000000000000000 RSI: 0000000000000013 RDI: 0000000000006ac6 >> RBP: 00007fff4bb7ebf0 R08: 0000000000000000 R09: 00007fff4bb7ebf0 >> R10: 0000000000000000 R11: 0000000000000206 R12: 0000000000006ac3 >> R13: 00007fff4bb7eda8 R14: 0000000000000006 R15: 00007fff4bb7eda8 >> Call Trace: >> 6fc27d38: [<60012be8>] panic_exit+0x2f/0x45 >> 6fc27d58: [<6003b389>] notifier_call_chain+0x33/0x65 >> 6fc27d98: [<6003b44b>] __atomic_notifier_call_chain+0x9/0xb >> 6fc27da8: [<6003b45c>] atomic_notifier_call_chain+0xf/0x11 >> 6fc27db8: [<600254f2>] panic+0xe6/0x17d >> 6fc27e20: [<60001a4b>] mount_block_root+0x26/0x13e >> 6fc27e48: [<600080e9>] printk_all_partitions+0x14f/0x15e >> 6fc27ea8: [<60001b47>] mount_block_root+0x122/0x13e >> 6fc27ef8: [<60001bb3>] mount_root+0x50/0x54 >> 6fc27f18: [<60001cc6>] prepare_namespace+0x10f/0x134 >> 6fc27f28: [<60001830>] kernel_init+0x75/0x7e >> 6fc27f48: [<60018f8a>] run_kernel_thread+0x41/0x4b >> 6fc27f58: [<600017bb>] kernel_init+0x0/0x7e >> 6fc27f98: [<60018f71>] run_kernel_thread+0x28/0x4b >> 6fc27fc8: [<60010327>] new_thread_handler+0x67/0x91 >> >> I used my old .config from 2.6.21.3 and did 'make oldconfig ARCH=um' >> and accepted the defaults for any new option. I have CONFIG_EXT2_FS=y >> and CONFIG_EXT3_FS=y so thats not the issue. Usually that error means >> some other process locked the filesystem but fuser reports no other >> processes using them. I probably forgot to set something up, but I >> don't know what. >> >> ------------------------------------------------------------------------- >> >> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference >> Don't miss this year's exciting event. There's still time to save >> $100. Use priority code J8TL2D2. >> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone >> >> >> _______________________________________________ >> User-mode-linux-user mailing list >> User-mode-linux-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user >> >> ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
