Re: [uml-devel] WARNING: CPU: 0 PID: 1 at init/main.c:711 do_one_initcall()

[Boaz H. <bha...@pa...>]

On 11/25/2013 04:43 PM, Richard Weinberger wrote:
<snip>
>> [It stopped to be very important for me since I stopped using
>>  UM very much. Ever since FC17 I'm unable to produce a running
>>  image. It just will not boot, an image that a kvm would. So
>>  very sad me, but no UML for me anymore.]
> 
> Sad to hear.
> Did you try one from http://fs.devloop.org.uk/?
> Just booted a FC18 on UML. Works fine.
> 

I just tried this exact one last week. (It gets stuck half way through boot)
Could you post me the .config file you used, and command line, and/or any
other info?

I would love to try again. I used a pretty defconfig based config
and my invocation blow: (Note that I use make KBUILD_OUTPUT=.build_um)

#!/bin/bash
#

UMDIR=/home/bharrosh/dev/um
ROOT_FS=$UMDIR/Fedora18-AMD64-root_fs-1
UBD_SWAP=ubd1=$UMDIR/swap_file-1
FS_LOCAL_MOUNT=$UMDIR/target_rootfs-1
LOCALHOST_TUN_IP=192.168.1.117

MEM=384M

# run this to install new um drivers into an image
um_mkkernel()
{
	mount -o loop$ROOT_FS_OFFSET $ROOT_FS $FS_LOCAL_MOUNT \
		&& make ARCH=um KBUILD_OUTPUT=.build_um INSTALL_MOD_PATH=$FS_LOCAL_MOUNT modules_install
	umount $FS_LOCAL_MOUNT
}

# run this to load a UML system
um_load()
{
	./.build_um/vmlinux ubd0=$ROOT_FS $UBD_SWAP eth0=tuntap,,,$LOCALHOST_TUN_IP mem=$MEM
}


> In the past we've had some issues with systemd-enabled distros.
> systemd uncovered problem in the UML tty driver.
> 
>> If you want to investigate. try doing a modprobe xor.ko on
>> a uml and see. since xor.ko is only built on demand for example
>> enabling exofs or object-layout-driver will select it. ,or MD-raid5.
> 
> Ok.
> 

Thanks
Boaz

> Thanks,
> //richard
>