| OpenVZ on CentOS 4.2 [message #2055] |
Fri, 17 March 2006 12:53  |
czaveri
Messages: 7
Registered: March 2006
|
Junior Member |
|
|
On a fresh install of CentOS 4.2, I tried to install OpenVZ using three different methods and encountered failure in some way:
Method 1. Source RPM. This is the source rpm that I used:
http://download.openvz.org/kernel/022stab070.1/ovzkernel-2.6 .8-022stab070.1.src.rpm
Result: Some error regarding Intel Microcode on boot and that MAC address is not as expected, finally, on checking /sbin/ifconfig I noticed that the interface for which I receive the MAC address error was missing .... please see result of dmesg below.
What I did exactly: Downloaded the above srpm and said "rpmbuild --rebuild --target=i686 ovzkernel-2.6.8-022stab070.1.src.rpm". Then I went to RPMS directory and installed the rpm using -ivh flags. (I received a warning here about module ata_piix).
Method 2. RPM. This is the rpm that I used:
http://download.openvz.org/kernel/022stab070.1/ovzkernel-2.6 .8-022stab070.1.i686.rpm
Result: Same error as above.
What I did exactly: Downloaded the above rpm and simply said "rpm -ivh ovzkernel-2.6.8-022stab070.1.i686.rpm".
(I received a warning here about module ata_piix).
Method 3: Patch. Patching the kernel:
Kernel:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.8.tar. bz2
Patch:
http://download.openvz.org/kernel/022stab070.1/patches/patch -022stab070-combined.gz
Result: The vanilla kernel is bootable and fine. After patching, I get error in make step.
Compiled and installed the vanilla kernel first, using the following commands:
make mrproper
make xconfig
make
make modules_install
cp arch/i386/boot/bzImage /boot/vmlinux-2.6.8
cp System.map /boot/System.map /boot/System.map-2.6.8
/sbin/mkinitrd /boot/initrd-2.6.8.img 2.6.8
gunzip patch-022stab070-combined.gz
patch -p1 <patch-022stab070-combined
make oldconfig
make
(I received error here)
the output of dmesg is in attached file.
Please let me know if further information is required.
It is a P4 CPU @ 3.0 GHz, 2 GB RAM and 2 SATA HDD each one 80 GB. The second hdd is under partition /vz.
Thank-you,
Sincerely,
Chintan Zaveri.
[Updated on: Fri, 17 March 2006 13:12] Report message to a moderator |
|
|
|
|
|
| Re: OpenVZ on CentOS 4.2 [message #2057 is a reply to message #2056] |
Fri, 17 March 2006 13:36  |
czaveri
Messages: 7
Registered: March 2006
|
Junior Member |
|
|
Thank-you for replying kir.
I have edited the previous message and shifted the dmesg output to a file.
I have again, overwritten the previous installation wherein I lost the errors that I received after patching the kernel.
However, here are the errors that are visible on booting the OpenVZ kernel. Yes, these are not shown in the dmesg output.
The first error is:
Applying Intel Microcode update: FATAL: Module microcode not found
Error: module microcode does not exist in /proc/modules
The second error is:
dev eth1 has different MAC address than expected, so ignoring.
And, here is how I installed OpenVZ:
[root@server kernel]# rpm -ivh ovzkernel-2.6.8-022stab070.1.i686.rpm
warning: ovzkernel-2.6.8-022stab070.1.i686.rpm: V3 DSA signature: NOKEY, key ID a7a1d4b6
Preparing... ########################################### [100%]
1:ovzkernel ########################################### [100%]
WARNING: No module ata_piix found for kernel 2.6.8-022stab070.1, continuing anyway
[root@server kernel]#
I have received the same error when I tried installing using the RPM created by SRPMs.
Do you suggest, I try recompiling the kernel and installing the patch?
Please let me know if some other information is required.
Thanks and regards,
Chintan Zaveri.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: OpenVZ on CentOS 4.2 [message #2069 is a reply to message #2068] |
Fri, 17 March 2006 18:50 |
|
|
The file in question is probably /etc/init.d/microcode_ctl.
I took a look at this script and found out those errors are harmless -- first error is printed by '/sbin/modprobe microcode' which tries to load module (but there is no need to do that as it's compiled into the kernel), and second error is caused by '/sbin/rmmod microcode' which tells there is no such module loaded.
Other than those two error messages, script is just fine, i.e. it actually applies microcode update, so you can certainly ignore those messages. If you do not like them you can comment out two lines in /etc/init.d/microcode_ctl -- the one with modprobe and the one with rmmod -- but that way microcode update will not be applied in the case you boot into non-openvz kernel.
Hope I made it clear enough. Still, the bug exists and we will see what to do.
Kir Kolyshkin
[Updated on: Fri, 17 March 2006 18:51] Report message to a moderator |
|
|
|
|
|
|
|
| Re: OpenVZ on CentOS 4.2 [message #2075 is a reply to message #2074] |
Fri, 17 March 2006 22:47 |
|
|
No it does not -- with OpenVZ kernel there is no need to load the module as this script does. So it is still better to keep the script. To avoid those messages you can redirect modprobe and rmmod output to /dev/null, like this
/sbin/modprobe microcode 2>/dev/null
....
/sbin/rmmod microcode 2>/dev/null
Kir Kolyshkin
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
