Menu
▾
▴
user-mode-linux-user
|
From: Balaco B. <bal...@im...> - 2015-06-21 02:21:58
|
I'm remotely accessing an Ubuntu 14.04.2 machine. And now I'm trying to run an UML in it, but it is always giving me some errors, and it finishes with segfaults or coredumps. For example, the end of output is: ========================= request_module: runaway loop modprobe binfmt-464c Starting init: /sbin/init exists but couldn't execute it (error -8) Starting init: /etc/init exists but couldn't execute it (error -13) request_module: runaway loop modprobe binfmt-464c Starting init: /bin/sh exists but couldn't execute it (error -8) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance. CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.11-ckt20 #1 Stack: 69037e90 602e26cd 60260fa9 00000000 69037e90 601b0c71 60260fa9 00000000 60260fa9 00000000 69037ea0 60263274 Call Trace: [<60260fa9>] ? printk+0x0/0xa0 [<601b0c71>] ? bust_spinlocks+0x0/0x4f [<60260fa9>] ? printk+0x0/0xa0 [<60260fa9>] ? printk+0x0/0xa0 [<60263274>] dump_stack+0x2a/0x2c [<6026071d>] panic+0x141/0x290 [<602605dc>] ? panic+0x0/0x290 [<600b7e82>] ? copy_strings+0x0/0x2b9 [<600b93ec>] ? do_execve+0x53c/0x5a7 [<600185ed>] ? try_to_run_init_process+0x0/0x66 [<600185ed>] ? try_to_run_init_process+0x0/0x66 [<6025ff3b>] kernel_init+0x17e/0x184 [<60019c86>] new_thread_handler+0x81/0xa3 Aborted (core dumped) ========================= I get the same error with the 32bit kernel, the 64 bit kernel and with a kernel I compiled from source. The "init=" option didn't help either. I don't know what else I should do. -- Balaco -- http://www.fastmail.com - Access your email from home and the web |
|
From: Richard W. <ric...@gm...> - 2015-06-21 08:36:04
|
On Sun, Jun 21, 2015 at 4:21 AM, Balaco Baco <bal...@im...> wrote: > I'm remotely accessing an Ubuntu 14.04.2 machine. And now I'm trying to > run an UML in it, but it is always giving me some errors, and it > finishes with segfaults or coredumps. > > For example, the end of output is: > > ========================= > request_module: runaway loop modprobe binfmt-464c > Starting init: /sbin/init exists but couldn't execute it (error -8) 8 is ENOEXEC. Are you trying to use a 64bit userspace with a 32bit kernel? > Starting init: /etc/init exists but couldn't execute it (error -13) > request_module: runaway loop modprobe binfmt-464c > Starting init: /bin/sh exists but couldn't execute it (error -8) > Kernel panic - not syncing: No working init found. Try passing init= > option to kernel. See Linux Documentation/init.txt for guidance. > CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.11-ckt20 #1 > Stack: > 69037e90 602e26cd 60260fa9 00000000 > 69037e90 601b0c71 60260fa9 00000000 > 60260fa9 00000000 69037ea0 60263274 > Call Trace: > [<60260fa9>] ? printk+0x0/0xa0 > [<601b0c71>] ? bust_spinlocks+0x0/0x4f > [<60260fa9>] ? printk+0x0/0xa0 > [<60260fa9>] ? printk+0x0/0xa0 > [<60263274>] dump_stack+0x2a/0x2c > [<6026071d>] panic+0x141/0x290 > [<602605dc>] ? panic+0x0/0x290 > [<600b7e82>] ? copy_strings+0x0/0x2b9 > [<600b93ec>] ? do_execve+0x53c/0x5a7 > [<600185ed>] ? try_to_run_init_process+0x0/0x66 > [<600185ed>] ? try_to_run_init_process+0x0/0x66 > [<6025ff3b>] kernel_init+0x17e/0x184 > [<60019c86>] new_thread_handler+0x81/0xa3 > > Aborted (core dumped) > ========================= > > I get the same error with the 32bit kernel, the 64 bit kernel and with a > kernel I compiled from source. The "init=" option didn't help either. I > don't know what else I should do. Is the error really *exactly* the same when you build a 64bit UML? -- Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-06-23 11:42:02
|
Before, I tried with 32b and 64b downloaded kernels. Both gave the same error. I have even compiled the kernel, imagining some weird problems of config or the lastest Ubuntu "tricks an and trouble" I have been seeing for some time! No solution. The problem was in the images itself, probably for same kind of reason. Couldn't we make this have a more meaninful error message? Like what you've said, that would make the problem clear to me. Coredump/segfaults and such are not really helpful. -- Balaco On Sun, Jun 21, 2015, at 05:35, Richard Weinberger wrote: > On Sun, Jun 21, 2015 at 4:21 AM, Balaco Baco <bal...@im...> wrote: > > I'm remotely accessing an Ubuntu 14.04.2 machine. And now I'm trying to > > run an UML in it, but it is always giving me some errors, and it > > finishes with segfaults or coredumps. > > > > For example, the end of output is: > > > > ========================= > > request_module: runaway loop modprobe binfmt-464c > > Starting init: /sbin/init exists but couldn't execute it (error -8) > > 8 is ENOEXEC. > Are you trying to use a 64bit userspace with a 32bit kernel? > > > Starting init: /etc/init exists but couldn't execute it (error -13) > > request_module: runaway loop modprobe binfmt-464c > > Starting init: /bin/sh exists but couldn't execute it (error -8) > > Kernel panic - not syncing: No working init found. Try passing init= > > option to kernel. See Linux Documentation/init.txt for guidance. > > CPU: 0 PID: 1 Comm: swapper Not tainted 3.13.11-ckt20 #1 > > Stack: > > 69037e90 602e26cd 60260fa9 00000000 > > 69037e90 601b0c71 60260fa9 00000000 > > 60260fa9 00000000 69037ea0 60263274 > > Call Trace: > > [<60260fa9>] ? printk+0x0/0xa0 > > [<601b0c71>] ? bust_spinlocks+0x0/0x4f > > [<60260fa9>] ? printk+0x0/0xa0 > > [<60260fa9>] ? printk+0x0/0xa0 > > [<60263274>] dump_stack+0x2a/0x2c > > [<6026071d>] panic+0x141/0x290 > > [<602605dc>] ? panic+0x0/0x290 > > [<600b7e82>] ? copy_strings+0x0/0x2b9 > > [<600b93ec>] ? do_execve+0x53c/0x5a7 > > [<600185ed>] ? try_to_run_init_process+0x0/0x66 > > [<600185ed>] ? try_to_run_init_process+0x0/0x66 > > [<6025ff3b>] kernel_init+0x17e/0x184 > > [<60019c86>] new_thread_handler+0x81/0xa3 > > > > Aborted (core dumped) > > ========================= > > > > I get the same error with the 32bit kernel, the 64 bit kernel and with a > > kernel I compiled from source. The "init=" option didn't help either. I > > don't know what else I should do. > > Is the error really *exactly* the same when you build a 64bit UML? > > -- > Thanks, > //richard -- http://www.fastmail.com - Or how I learned to stop worrying and love email again |
|
From: Richard W. <ric...@gm...> - 2015-06-24 08:33:39
|
On Tue, Jun 23, 2015 at 1:41 PM, Balaco Baco <bal...@im...> wrote: > Before, I tried with 32b and 64b downloaded kernels. Both gave the same > error. I have even compiled the kernel, imagining some weird problems of > config or the lastest Ubuntu "tricks an and trouble" I have been seeing > for some time! No solution. The problem was in the images itself, > probably for same kind of reason. > > Couldn't we make this have a more meaninful error message? Like what > you've said, that would make the problem clear to me. Coredump/segfaults > and such are not really helpful. At first please show me both outputs of the 64bit and 32bit kernel. -- Thanks, //richard |
|
From: Balaco B. <bal...@im...> - 2015-07-04 14:23:17
|
> At first please show me both outputs of the 64bit and 32bit kernel. > I'll send them - just with a severe lack of time these last few weeks. -- Balaco On Wed, Jun 24, 2015, at 05:33, Richard Weinberger wrote: > On Tue, Jun 23, 2015 at 1:41 PM, Balaco Baco <bal...@im...> wrote: > > Before, I tried with 32b and 64b downloaded kernels. Both gave the same > > error. I have even compiled the kernel, imagining some weird problems of > > config or the lastest Ubuntu "tricks an and trouble" I have been seeing > > for some time! No solution. The problem was in the images itself, > > probably for same kind of reason. > > > > Couldn't we make this have a more meaninful error message? Like what > > you've said, that would make the problem clear to me. Coredump/segfaults > > and such are not really helpful. > > At first please show me both outputs of the 64bit and 32bit kernel. > > -- > Thanks, > //richard -- http://www.fastmail.com - Faster than the air-speed velocity of an unladen european swallow |
Thanks for helping keep SourceForge clean.
X