Hi,
    I am getting a new error message with UML. First a few lines of
Using a channel type which is configured out of UML
parse_chan_pair failed for device 15 : Configuration failed

and then the vfs can't mount the root partition specified with ubd0.
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)

This error is quite confusing because I did not change too much on my
setup. Earlier today UML was working with the same image I always use,
then I fooled around with a iptables on my host( nothing to do with UML
) and after a reboot I started getting this error. I tried various other
images to no avail. Here is the complete log

./linux ubd0=images/x
Core dump limits :
        soft - 0
        hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
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.22.4 ([EMAIL PROTECTED]) (gcc version 4.1.2 (Gentoo
4.1.2 p1.0.2)) #7 Mon Dec 17 13:07:24 MST 2007
Built 1 zonelists.  Total pages: 8128
Kernel command line: ubd0=images/x root=98:0
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 30460k available
Mount-cache hash table entries: 512
Checking for host processor cmov support...Yes
Checking for host processor xmm support...No
Checking that host ptys support output SIGIO...Yes
Checking that host ptys support SIGIO on close...No, enabling workaround
Using 2.6 host AIO
NET: Registered protocol family 16
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
Checking host MADV_REMOVE support...OK
mconsole (version 2) initialized on /home/kazzmir/.uml/OkXtmv/mconsole
Host TLS support detected
Detected host type: i386
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
loop: module loaded
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
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)

EIP: 0073:[<ffffe410>] CPU: 0 Not tainted ESP: 007b:b7e55fb4 EFLAGS:
00000246
    Not tainted
EAX: 00000000 EBX: 000016dd ECX: 00000013 EDX: 000016dd
ESI: 000016d9 EDI: 00000011 EBP: b7e55fd8 DS: 007b ES: 007b
08201e64:  [<0806339c>] show_regs+0xb4/0xb9
08201e90:  [<08057fdc>] panic_exit+0x25/0x3f
08201ea4:  [<08072c74>] notifier_call_chain+0x21/0x4d
08201ec4:  [<08072d16>] __atomic_notifier_call_chain+0x17/0x19
08201ee0:  [<08072d2d>] atomic_notifier_call_chain+0x15/0x17
08201efc:  [<08067bd6>] panic+0x52/0xdd
08201f1c:  [<08049b21>] mount_block_root+0x100/0x116
08201f70:  [<08049b83>] mount_root+0x4c/0x54
08201f94:  [<08049c58>] prepare_namespace+0xcd/0xf9
08201fa4:  [<0804984f>] kernel_init+0x79/0x85
08201fb4:  [<0805e289>] run_kernel_thread+0x37/0x42
08201fe0:  [<08058401>] new_thread_handler+0x57/0x7e
08201ffc:  [<a55a5a5a>] 0xa55a5a5a

Segmentation fault

-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user

Reply via email to