Hello All,

Today I seen a strange issue in my production environment .

Issue : The Vm (OS : Linux –Centos X) is showing an error and shutdown itself after flashing the message.


Cause : This is the issue both in vmware/Linux itself. Reason VMware doesn’t actually provide that level interface for CPU access, but Ubuntu try to load the kernel module anyway.

Resolution. For fixing this you need to go in to the Single user mode of the Impacted VM and blacklist the component which is causing error to boot up the OS.

Hope all knows how to goes in to Single User Mode of Linux but I am explaining with Centos Version 7 which is lil bit different. please follow the steps.

1. First, reboot your server and when you enter the Kernel Selection menu, press e to modify the parameters to boot the kernel.


2. Scroll down until you find the actual kernel line. It starts with linux16 /vmlinuz-... and will span a couple of lines. You’re now looking for the ro keyword in the kernel linux, which would start the OS with a read only (ro) file system.Use your arrow keys to go to the ro line and replace it with rw init=/sysroot/bin/bash. The result should look like this. If that’s the case, press ctrl+x to boot the kernel with those options.


3. If everything went fine, you’re now in a limited shell with access to the entire filesystem. To make things easier, you can chroot the filesystem so you can access all your known files/directories with the same paths.

vi /etc/modprobe.d/blacklist.conf


Modify the file with the below comment on the bottom of the file and save it.

blacklist i2c-piix4

Reboot the System. Now your problem is solved .Enjoy.

Leave a reply