| |
|
 |
|
 |
|
|
|
| |
|
|
xen-ia64-devel
[Xen-ia64-devel] RE: Progress on RHEL4, but blocked at xlilo?
Hi Dan,
I think a initrd isn't made well.
Please try the following.
ftp://ftp.cistron.nl/pub/people/miquels/software/sysvinit-2.85.tar.gz
Best Regards,
Akio Takebe
>With the xen4elilo patch, I am able to get much further but
>am still running into a problem:
>
> NET: Registered protocol family 17
> Freeing unused kernel memory: 384kB freed
> Warning: unable to open an initial console.
> dm_mod: no version for "struct_module" found: kernel tainted.
> device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel@xxxxxxxxxx
> cdrom: open failed.
> Kernel panic - not syncing: Attempted to kill init!
>
>Is the kernel panic related to the other messages or is xenlinux
>panic'ing for some other reason? I tried using an /sbin/init
>from RHEL3 (but did not recompile the kernel with SELinux off).
>
>Thanks,
>Dan
>
>> -----Original Message-----
>> From: Kouya SHIMURA [mailto:kouya@xxxxxxxxxxxxxxxx]
>> Sent: Friday, November 11, 2005 4:11 AM
>> To: Yang, Fred
>> Cc: Magenheimer, Dan (HP Labs Fort Collins); Zhang, Xiantao;
>> takebe_akio@xxxxxxxxxxxxxx; Xu, Anthony;
>> xen-ia64-devel@xxxxxxxxxxxxxxxxxxx; Yoshi. Oguchi
>> Subject: RE: Progress on RHEL4, but blocked at xlilo?
>>
>> I'm also trying to boot RHEL4 on Xen3.0(IA64) and encountered
>> a execution
>> stuck problem in /sbin/init. It seems just the same as Akio's problem.
>>
>> I'm not sure but I suspects that the SELinux feature might be
>> concerned with this problem. Since there is no problem on RHEL3.
>> RHEL4's /sbin/init is special and performs some work for SELinux.
>> (mounting selinuxfs etc. Original SysVinit package doesn't support
>> SELinux)
>>
>> SELinux feature is not enabled in default Xen 3.0 setting
>> (xen0_defconfig_ia64).
>> So I made a SELinux enabled Xenolinux for RHEL4 and tried it.
>> As a result RHEL4 system is completely booted!
>>
>> Another solution is to exchange /sbin/init. Using orignal (not patched
>> for SELinux) /sbin/init I also succeeded to boot RHEL4 system.
>> It's so easy that Akio should try this solution.
>>
>> But Linux kernel whose SELinux feature is not enabled can boot RHEL4
>> sytem on actual machine. So non-SELinuxed Dom0 must be booted on
>> Xen. That is Xen3.0 has still potential bugs.
>> Akio will continue to investigate this problem.
>>
>> --
>> Kouya Shimura
>> ARCHTECTURE LABORATORY
>> FUJITSU LABORATORIES LTD.
>>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
|
|
| |
|
Home