RHEL 7

Rohit_4739 · 10-06-2015, 09:39 AM

Hi,

I was attending a training for rhel7 and hence was trying some things to recover from a broken grub. So below i s what i did.

I am running a test rhel7 machine on VM Workstation 10

1. I moved my /boot/grub2/grub.cfg to /var in my test rhel7 machine and then rebooted.

2. So as expected system put me in

Quote:

grub>

command prompt; so i tried to boot the system manually using the below command set:

Code:

set root=(hd0,msdos1)
linux /vmlinuz-x.x.x. ... [followed by all different parameters]
initrd /initramfs-x.x.x ..
boot

System started to boot until it throws a weird error saying CPU has been disabled by guest OS, please reboot or reset the machine.

Now i have tried rebooting/resetting my VM multiple times and also tested this on multiple different systems; but without any luck. Now it seems to be some kind of kernel panic but i cannot seem to figure why it is panicking and how could i fix it.

However after restoring the grub.cfg from live cd things work(which they should).

So can anyone please guide me here if you have any insight on this.

berndbausch · 10-06-2015, 12:16 PM

The strange message is from Vmware, see http://kb.vmware.com/selfservice/mic...rnalId=2000542.

As to your problem, is it possible that you mistyped some kernel parameter? Also, my grub.cfg contains a number of other commands:

Code:

        load_video
        set gfxpayload=keep
        insmod gzio
        insmod part_msdos
        insmod xfs
        set root='hd1,msdos1'
        if [ x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  87005ff6-8a28-4a37-9a6a-14a6801899b5
        else
          search --no-floppy --fs-uuid --set=root 87005ff6-8a28-4a37-9a6a-14a6801899b5
        fi
        linux16 /vmlinuz-3.10.0-229.el7.x86_64 root=/dev/mapper/centos-root ro rd.lvm.lv=centos/root rd.lvm.lv=centos/swap crashkernel=auto console=ttyS1
        initrd16 /initramfs-3.10.0-229.el7.x86_64.img

Perhaps your problem is caused by a missing module.