The same problem occurs in different scenarios: the unabletoloadselinuxpolicy occurs during startup.

Scenario 1: unabletoloadselinuxpolicymachineisinenforcingmodehaltingnowkernelpanic-notsyncing: attemptedtoki appears after you change etcselinuxconfigSELINUX = disable.

Scenario 1:

It appears after/etc/selinux/config SELINUX = disable is modified

Unable to load selinux policy. Machine is in enforcing mode. halting now.

Kernel panic-not syncing: attemptedToKill init!

Solution:

Press e on the Grub startup menu to enter the editing mode.

Kernel/vmlinuz-2.6.23.1-42.fc8 ro root =/dev/vogroup00/logvol00 rhgb quiet"

Add enforcing = 0, press enter, and then press B to start.

Scenario 2:

When a physical machine with a KVM virtual machine is forcibly disabled, the following figure is not displayed after the instance is started:

Then go to the grub command line and execute:/etc/inittab. some initialization failure information appears:

... Unable to load selinux policy ..........

Solution:

On the Grub startup menu, press e to enter the editing mode and enter the startup item

"Kernel/vmlinuz-2.6.23.1-42.fc8 ro root =/dev/vogroup00/logvol00 rhgb quiet", add selinux = 0;

And then reboot.