| 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 |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
