Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
System: Red Hat Enterprise Linux (v. 5 for 64-bit x86_64)
with 1 virtual machine server and this one has 4 virtual machines
Updated: through Red Hat network.
(Bare with me, im not the administrator of the server, but we are so screwed right now, so need help )
After an update through the rhn interface, the 4 vm stopped responding to the vmserver. Basicly it just says the network is not responding. The WMserver responds without any problem.
Yeah, the kernel modules any of the VMs use is specific to that kernel, as it needs to be able to talk to the hardware too. Change the kernel, and you change the module's interface, making it impossible for the VM to communicate with the kernel, therefore the hardware.
As for how to do a rollback with GRUB, I would have to advise against it, but if you really need to, check to see if /boot has any of the old kernel binaries (normally something like vmlinuz-2.6.x.x, system.map-2.6.x.x, etc). Then, change the boot option in /boot/grub/menu.lst from whatever the kernel it's using to the desired on. Althogh, as I said, not recommended, especially if you don't know exactly what you're doing.
Hi
Thanks for you help so far.
We have tried the kernel rollback, that didn't solve the problem.
Regarding the re-compilation of the kernel modules:
It isn't VMware we are running, but Xen. Do any of you know, how to re-compile the modules into the kernel, is there a script? Like the one #2 refered to in VMware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.