Centos 5.5 on Hyper-V R2

Discussion in 'Installation/Configuration' started by Polk, Aug 10, 2010.

  1. Polk

    Polk HowtoForge Supporter

    Hi everyone,

    I have installed Centos 5.5 on Hyper-V R2 machine and all worked well.
    Then I installed integrated services and it did changes to kernel.
    This article needs to be updated, but at least it directed me into right path:
    http://www.howtoforge.com/installing-hyper-v-linux-integration-components-on-centos-5

    then I installed "Perfect server"
    following this:
    http://www.howtoforge.com/perfect-server-centos-5.5-x86_64-ispconfig-3

    yum update upgraded my kernel and it seems to change kernel.
    after that I was not able to load server and was getting error:

    Code:
    Mounting root filesystem.
    mount: could not find filesystem '/dev/root'
    Setting up other filesystems.
    Setting up new root fs
    setuproot: moving /dev failed: No such file or directory
    no fstab.sys, mounting internal defaults 
    setuproot: error mounting /proc: No such file or directory
    setuproot: error mounting /sys: No such file or directory
    Switching to new root and running init.
    unmounting old /dev
    unmounting old /proc
    unmounting old /sys 
    switchroot: mount failed: No such file or directory
    Booting has failed.
    I found this article:
    http://www.virtuatopia.com/index.ph...ile_or_directory_error_message"_error_message.

    The article above says how to fix this issue on Xen, but I'm running Hyper-V.

    Question:
    Can anyone help and give step by step guide like that but that fixes kernel on Hyper-V?

    Thank you.
     
    Last edited: Aug 10, 2010
  2. conan23

    conan23 New Member

    Hi,

    Try first uninstall integrated services, than from /boot/grub/menu.lst remove noprobe entries (ex. hda=noprobe, hdb=noprobe). This should be enough to start centos with new kernel.

    To uninstall integrated services go into directory from which you did make, make install and type: make uninstall.

    Good luck :)
     
  3. Polk

    Polk HowtoForge Supporter

    Actually, I was able to fix it by editing the hyper-v drivers and installing them to the kernel that is not running at the moment. This way, next time I load to new kernel, the drivers already applied.

    thanks for your message.
     

Share This Page