> On Thu March 11 2010, Glomet wrote:
>> >> Just a problem remains:
>> >>
>> >> On both of the systems, new guest vservers now run fine. [...]
>> >> But on the Debian host (it is a AMD Athlon based machine), I wasn't
>> >> able to run the same old FC1 guest vservers images that are now
>> >> running on the FC host Xeon based machine.
>> >>
>> >> The error message follows, while starting the guest vserver:
>> >>
>> >> An error occured while executing the vserver startup sequence; when
>> >> there are no other messages, it is very likely that the init-script
>> >> (/etc/rc.d/rc 3) failed. [...]
>>
>> >> [...] am I missing something [...] ?
>> >
>> > I'd double check that [...] you do not start a 32bit
>> > guest without the proper 32 bit personality
>>
>> Here is an extract from vserver-info:
>> host:/vservers# vserver-info
>> Versions:
>> Kernel: 2.6.31.12-vs2.3.0.36.28
>> VS-API: 0x00020305
>> util-vserver: 0.30.216-pre2882; Mar 9 2010, 20:35:13
>> [...]
>> build/host:
>> x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu
>> [...]
>>
>> Unfortunately I don't know what a "32 bit personality" is, and how can I
>> set it, but, for sure, I can say you that the old Fedora Core 1 guest
>> images I'm using were built years ago using a 32 bit system.
>> As you observed, they now run on the 32bit Xeon System, and, at the
>> moment, I wasn't still able to let them run on the AMD Athlon 64.
>>
>
> Do you have "emulate 32 bit" set in your kernel configuration?
I'm not familiar with such this "option", however,
if you are meaning the "option" that is identified by the
CONFIG_IA32_EMULATION row in the kernel .config file, I see that:
host:~# zcat /proc/config.gz |grep IA32
CONFIG_IA32_EMULATION=y
CONFIG_IA32_AOUT=y
So, I suppose: yes, I did
(but I'm not sure this was you were speaking about).
Regards
-- Umberto
Received on Thu Mar 11 22:24:44 2010