CentOS 5 :: Hyper-v Cannot Start After Upgrading Kernel Via Yum Update
Dec 19, 2009
I have 2.6.18-164.2.1.e15 running on Hyper-v. I did yum update and noticed that kernel is upgraded to 2.6.18-164.9.1.e15. If I try to boot into the new kernel it hangs with message first "switchroot mount failed" and then "kernel panic". This is probably related to Hyper-v drivers installed in the old kernel. First question: Do you think this is correct? Is it possible to somehow disable Hyper-v drivers so I can boot into the new kernel and then reinstall drivers? There is nothing in Microsoft documentation about uninstalling Linux Integration Components.
I have a Centos 5.2 VM running under Windows 2008 Hyper-V. If I add two "legacy Nic's" and bridge them, everything appears to work fine. However, if I remove the legacy nics and replace them with two synthetic nics (linux integration components), the nics seems to function fine UNTIL I add them to a bridge.This VM will eventually be used as a DansGuardian/Squid transparent proxy for a local library. The logical layout is represented by the attached jpg image. I have also included the ifcfg- scripts for the adapters and bridge for both scenarios.It would also be useful if someone else has Hyper-V with the integration components and dual physical nics to see if they can reproduce my symptoms on their box.Legacy Adapters:
after update to kernel-2.6.18-164.el5 one of the 2 NIC's of my machine are only found at 1 of 4 reboots. Using the old one kernel-2.6.18-128.7.1.el5 all is fine. This are the to NIC's:
The server runs# uname -r2.6.18-128.4.1.el5However, today I executed yum update kernel*due to security advisory. I was just about to reboot the system when I realized that it runs VMWare Server Instance that will most likely fail to restart after kernel upgrade (I had a hard time fixing it after previous kernel update). Now I want to keep 2.6.18-128.4.1.el5 after reboot.I see that new kernel is scheduled for booting:
I'm running a CentOS 5.2 vm on a W2K8 hyper-v core server. The problem I have is that when I reboot, the system time always resets itself to 6:00 am in the morning. I tried the /sbin/hwclock --systohc command but it hasn't taken hold.
Yesterday I installed Fedora 15 instead of Ubuntu 11.04. I have nvidia card, so I've searched for nvidia driver installing howto and found it on this forum [URL]. But after updating kernel -
Code:
yum update kernel*
(now it's latest - 2.6.39) - and rebooting Fedora didn't start. I even don't know if it's something with GRUB because It automatically loads Fedora and I can't know whether it's its problem. When I try to start Fedora, I just see black screen with blinking underline cursor at the top left of the screen and it's the first and the last I see except laptop splash screen. I have Asus F50SV (Nvidia GT120M). By the way, I've tried to install nvidia drivers manually and xorg.conf became broken. I've edited it and now it like this:
I am an old days RH release user(from 6.x) and just switching back from Debian/Ubuntu to CentOS on some servers, but I can not understand the kernel update strategy currently enabled in CentOS.There are two boxes, with almost identical installation, but recently there was an auto update of kernel on one box. This auto update also seems to issue an auto reboot on the machine, which is unacceptable on server machines.
I've installed CentOS 5.x (64 bit) on a Hyper-V Server R2. When I trying to install integration serices I get an error: [root@localhost ~]# cd /opt/linux_ic_v21_rtm/ [root@localhost linux_ic_v21_rtm]# make Building all modules... make -C /lib/modules/2.6.18-164.el5/build SUBDIRS=/opt/linux_ic_v21_rtm/src modules make: *** /lib/modules/2.6.18-164.el5/build: No such file or directory. Stop. make: *** [all] Error 2
I am using: Linux localhost.localdomain 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux I did everything as it shows on [URL].
I'm running Fedora 13 x64 and updated the kernel to the latest version (2.6.34.7-56 to 2.6.34.7-61). I use the proprietary nvidia drivers (currently 260.19.12) so I had to compile the kernel module against the new kernel sources and reinstall the driver. The process was apparently successful, but when I try to start X nothing happens, it's as if the computer had been suspended, my monitor acts like it isn't receiving any input. I have full runlevel 3 access, and the system seems pretty much fine up to that point. Nvidia's own sanity tests which are built into the installer reported no problems with my driver.
I have centos 5.3 workin on mini itx atom 330. i have some problem with the network when i use Samba. when i move big files the network goes down. i wanna to install the new kernel on my centos to try to fix the network problem with the new drivers includes on the new kernel.
I applied the Kernel update that showed in the updater via the GUI.It now won't boot anymore.Memory for crash kernel (0x0 to 0x0) notwithin permissible range.WARNING calibrate_APIC_clock: the APIC timer calibration may be wrong.
i'm currently running centos 5 with kernel version 2.6.18-92.1.22.el5 is there any way to update to kernel version >= 2.6.27 via yum ? if not via yum is it advisable to compile from source?
I just upgraded to CentOS 5.6 (been on 5.2 for ages....) and am getting the following error in the apache error_log file:[Sat Jul 02 13:50:25 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)[Sat Jul 02 13:50:25 2011] [error] SSL Library Error: -8187 Security library: invalid argumentsThe notice entry, I can understand, however the SSL error is halting apache from starting. It has been suggested that this might be a package mismatch issue. I'll be more than happy sharing the package list for this box on request.
i have recently bought a system which has intel atom and my Lan card hasn't been installed on the system, i am using centos 5.2, i have read in some articles that Centos 5.4 directly support this LAN Card,so will upgrading the kernel for the Operating system help, or i have to download the whole iso for 5.4 and install it over the existing if upgrading the kernel will help which file i need to download to upgrade the kernel and where can i download that file.
I try to update my kernel to 2.6.18.128.4.1.el5 using # yum update
After # yum update # rpm -qa kernel*|sort gives the following: kernel-2.6.18-128.1.14.el5 kernel-2.6.18-128.1.16.el5.centos.plus kernel-2.6.18-128.4.1.el5.centos.plus kernel-2.6.18-92.1.18.el5 kernel-2.6.18-92.el5 kernel-devel-2.6.18-128.1.14.el5 .....
This my grub.conf: # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00 # initrd /initrd-version.img #boot=/dev/hda default=1 timeout=5.....
yum update installed: CentOS (2.6.18-128.4.1.el5.centos.plusxen) and CentOS (2.6.18-128.4.1.el5.centos.plus)
both are not working. I have to run the system using: 2.6.18-128.1.14.el5. Upon trying again #yum update it says that no packages are marked for update. Can I manually install the desired kernel? Do you know a reason why yum update is not automatically installing the proper kernel?
I had a Centos 5.5 system working great...and then due to crazy curiosity, installed the kernel update. Did this through the graphical interface, uncheck all update other than kernel. It downloaded, installed fine..After reboot now all I get is GRUB_ and then nothing else! I waited 3-4 minutes and had to shut down system. Have been googling around but thought I will post it here as well..When I boot with Win7 and use Ext2fsd to check, the boot folder is empty. Not sure if this is because ext2fsd does not read boot folder or it got wiped out by the yum upgrade process.
I have recently run an update and now we are unable to boot the newer kernel. We get stuck as below;
Memory for crash kernel (0x0 to 0x0) notwithin permissible range Red Hat nash version 5.1.19.6 starting Unable to access resume device (/dev/VolGroup00/LogVol06)
[Code]...
The kernel version we were at was 2.6.18-194.el5 and the update move us to 2.6.18-194.17.1.el5. I've done some googleing but I'm unable to work out exactly what I need to do. I'm guessing the new kernal is missing a module?
after I do all new installation and before i do PHP update my browser can show me apache default page but after update PHP to 5.2.0 I can't even see the default page and always give me Problem loading page and I have 3-4 times reinstall my server which i need to do this as mail serer locally. Here are the version for my php and apache on my server currently :Apache[root@localhost local]# httpd -vServer version: Apache/2.2.14 (Unix)Server built: Oct 14 2009 13:19:18
I'm trying to install CentOS 5.3 on a VMWare virtual machine running VMWareServe 1.0.4 build-56528. I have 8 virtual machines that are running some older kernel (RH FedoraCore 4) without any trouble. My system has an AMD Athlon XP 1800 processor and has 1G RAM. Every time during the installation after choosing skip media (I have already checked that the media is OK) I get a kernel OOPS and the capslock and scroll lock keys start blinking. My first guess was that this could be a ACPI issue, so I have disabled ACPI using the acpi=no boot option. The problem persists with the acpi=no option set. During the boot install process, I have seen some messages like this one
ACPI Exception (processor_core-xxxx): AE_NOT_FOUND, Processor Device is not present [xxxxxxxxx]
I have searched for this issue and found a RedHat Bug 435653 that reports this same issue, but this report is somewhat old, so i think that this issue as already been fixed and reflected to upstream. I have tried also to install using the text mode installation, but the same problem. To further isolate this problem, i have avoided the hardware detection and this was the first time that i have overcome the first screen (test media screen), as i have choosen with the success the language and the keybord layout. After choosing the beyboard layout, the kernel OOPS shows up again. On the screen 4 (debug screen) I don't see any relevant messages.
I am running CentOS 5.x and want to yum update, but I do not want to touch the kernel. How can I exclude the kernel update and prevent yum from removing my current kernel?
I'm using Cpanel on my server, before upgrade to new kernel, i could see 8 cores on my i7 server, now i only see 4 cores, is there anything that i need to do to have another time the 8 cores?
I installed the Centos 5.5 with XEN and put 03 virtual machines (Centos 5.5 too). I did this correctly, but I have a problem. In the virtual machine, I need update the kernel. I used "yum update kernel" and this is downloaded correctly and the menu.lst file is updated too, but the kernel not ran. I ran "grub-install /dev/sda" or "grub-install /dev/xvda" and received a error return. I read the device.map file and i ran "grub-install /dev/sde" and received a error return too.
The errors: [root@vm01 ~]# grub-install /dev/sda /dev/sda: Not found or not a block device. [root@vm01 ~]# grub-install /dev/sde /dev/sda1 does not have any corresponding BIOS drive. [root@vm01 ~]# grub-install /dev/xvda /dev/xvda: Not found or not a block device.
I am currently working to get to a stable dual boot Win7/CentOS 5.5 configuration on a Dell Latitude E6510 with the Intel 82577LM chipset. I haven't gotten the Centrino N WiFI chipset working yet, but the Eth0 device was working just fine.However, yesterday I did a system update. I did not pay close attention, but I believe the update did mention networking, because I thought it might help me get my wireless going. Now, Eth0 fails with the message, "Determining IP information for eth0... failed; no link present. Check cable?" It does this at boot up and if we try reactivating it once the system is up. We have tried unstalling and re-installing the driver.The Window 7 boot sees the adapter and runs just fine. I was at a different site location yesterday when everything was working, but my co-workers and I can't help but think it might be related to the update yesterday, since everything worked prior to the update and Windoze 7 works fine with the adapter.
I have not been able to mount my NTFS harddrive on the CentOS side, despite installing fuse, and I don't have wireless, which makes it difficult to get access to new drivers. I also have a FAT32 partition that would be great to share between the boots for passing info, but I haven't found a way to mount a FAT32 partition in CentOS.
Last I upgraded one of our cent 5 boxes which is running kvm with a mix of centos and windows VMs.After the update performance just tanked on the XP guest, but the others (including other windows VMs) are just fine.I checked with our good friend google and didn't really get any help there.We're hoping to NOT have to rebuild the XP guest, so I thought I'd check in here first.
After update to 5.3 and reboot I got this error. googling for it I found that it is a known bug in kernel REHL 5.3 and there is also a patch for it [URL]. I am very new to linux, so how to apply, or just wait for a new kernel?
I'm fairly new to linux Red Hat. We are running Rhel 3 on our VM's. We ran into a issue, (Bug 121801 - athlon-smp kernel does not support >4GB of RAM. what the stepos are to upgrade the existing kernel to the new i686? .
I have one machine where I have several versions installed on different partitions. The base partition (/dev/hda1) is Slack 12.1. On a spare partition (/dev/hdc4) I had installed Slackware64-current. Last week I slackpkg upgraded and installed the 2.6.32.2 kernel, and now that partition will not boot. I know that with the new kernels the hd* designation has been removed, and have already redone that fstab (accessing it from a different boot) to reflect the sd*. Here is the slack64 section of my lilo.conf:
Code: # Linux bootable partition config begins image = /other/spare4/boot/vmlinuz
I'm trying to create new RAM image file to get my server load raid1 module upon start, I was following redhat documentation & it suggested to use the following command mkinited --with=raid1 inited-raid1-$(uname -r).img $(uname -r) However after running this command I'm getting this message No Kernel available for 'inited-2.6.18-128.el5"
