user-mode-linux on Debian sid AMD64
Hi,
Okay, I've tried running user-mode-linux on AMD64.
I've been away from using user-mode-linux for a year,
and trying to catch up with what's been happening.
I might be doing something totally off (as I've not yet
caught up with skas0 and stuff).
Anyway, this is what I've done so far.
Host kernel is Linus's git tree as of yesterday:
Linux dancer64 2.6.14-rc3dancer-gdd0fc66f #1 Mon Oct 10 12:25:11 JST 2005 x86_64 GNU/Linux
I've built the guest kernel in the following manner, and
selected TT-mode only, with SKAS disabled.
$ make-kpkg clean
$ make mrproper ARCH=um
$ make menuconfig ARCH=um
$ make-kpkg --rootcmd=fakeroot --arch=um --revision Custom.1.5.um kernel_image
$ sudo dpkg -i ../kernel-um*.deb
The following patch is applied, to make the thing compile.
diff --git a/arch/um/kernel/um_arch.c b/arch/um/kernel/um_arch.c
--- a/arch/um/kernel/um_arch.c
+++ b/arch/um/kernel/um_arch.c
@@ -334,8 +334,10 @@ int linux_main(int argc, char **argv)
add_arg(DEFAULT_COMMAND_LINE);
os_early_checks();
+#ifdef CONFIG_MODE_SKAS
if (force_tt)
clear_can_do_skas();
+#endif
mode_tt = force_tt ? 1 : !can_do_skas();
#ifndef CONFIG_MODE_TT
if (mode_tt) {
Then running the result seems to give me an instant oops.
$ linux-2.6.14-rc4 root=/dev/root rootflags=/ rootfstype=hostfs init=/bin/sh con=pty con0=fd:0,fd:1
Checking PROT_EXEC mmap in /tmp...OK
UML running in TT mode
tracing thread pid = 22025
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...missing
Linux version 2.6.14-rc4-g907a4261 (dancer@dancer64) (gcc version 4.0.2 (Debian 4.0.2-2)) #1 Tue Oct 11 17:27:50 JST 2005
Built 1 zonelists
Kernel command line: root=/dev/root rootflags=/ rootfstype=hostfs init=/bin/sh con=pty con0=fd:0,fd:1
PID hash table entries: 256 (order: 8, 8192 bytes)
Dentry cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Memory: 27300k 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
Checking for /dev/anon on the host...Not available (open failed with errno 2)
softlockup thread 0 started up.
Disabling 2.6 AIO in tt mode
2.6 host AIO support not used - falling back to I/O thread
NET: Registered protocol family 16
mconsole (version 2) initialized on /home/dancer/.uml/MVMAge/mconsole
UML Audio Relay (host dsp = /dev/sound/dsp, host mixer = /dev/sound/mixer)
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
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)
nbd: registered device at major 43
PPP generic driver version 2.4.2
SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
NET: Registered protocol family 2
IP route cache hash table entries: 512 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Initialized stdio console driver
Console initialized on /dev/tty0
Initializing software serial port version 1
Failed to open 'root_fs', errno = 2
VFS: Mounted root (hostfs filesystem) readonly.
Kernel panic - not syncing: Kernel mode fault at addr 0x0, ip 0x0
Pid: 1, comm: sh Not tainted 2.6.14-rc4-g907a4261
RIP: c000:[<0000000000000000>]
RSP: 000000006044fc30 EFLAGS: 00010202
RAX: 0000000000000001 RBX: 0000000000000000 RCX: 00000000601a0e0a
RDX: 00000000600326ae RSI: 0000000000000001 RDI: 000000006044fb00
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000008 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 000000000000000a R15: 0000000000000009
Call Trace:
6044f6f8: [<60015cdf>] panic_exit+0x2f/0x50
6044f718: [<6004801b>] notifier_call_chain+0x2b/0x50
6044f748: [<60038354>] panic+0xe4/0x180
6044f788: [<601a0e0a>] __sigprocmask+0x4a/0xb0
6044f7b8: [<601186d7>] __up_read+0x77/0xa0
6044f7d8: [<60014e22>] handle_page_fault+0xb2/0x2c0
6044f838: [<600151fa>] segv+0x1ca/0x2d0
6044f8b8: [<60012f31>] change_signals+0x51/0x80
6044f928: [<6001559e>] segv_handler+0x9e/0xb0
6044f968: [<60018aaa>] sig_handler_common_tt+0xfa/0x1a0
6044f9d8: [<60032810>] sig_handler+0x10/0x20
6044f9e8: [<601a0b90>] __restore_rt+0x0/0x10
6044fa78: [<600326ae>] run_kernel_thread+0x2e/0x50
6044fa88: [<601a0e0a>] __sigprocmask+0x4a/0xb0
6044fae8: [<600326c1>] run_kernel_thread+0x41/0x50
6044faf8: [<6000e1a0>] init+0x0/0x140
6044fb38: [<600326ae>] run_kernel_thread+0x2e/0x50
6044fbe8: [<60017033>] new_thread_handler+0x113/0x130
6044fcd8: [<601a0e0a>] __sigprocmask+0x4a/0xb0
regards,
junichi
Reply to: