Search
The Best Hyperconverged Infrastructure (HCI) for Enterprise ROBO, SMB & Edge

V2V Converter Kernel Panic

  • Troubleshooting
  • September 08, 2015


Symptoms

After converting your VM Virtual Disk File from CentOS to any non CentOS, booting might lead to the “kernel panic – not syncing: attempted to kill init!” error.

Solution

For this error to be fixed, your guest machine needs to be manually booted in maintenance mode. Maintenance mode boot will rebuild VM hardware so it is compatible with your current hypervisor, which will let your guest boot normally.

 

Request a Product Feature

To request a new product feature or to provide feedback on a StarWind product, please email to our support at support@starwind.com and put “Request a Product Feature” as the subject.

Hey! Looking to deploy a new, easy-to-manage, and cost-effective hyperconverged infrastructure?
Alex Bykovskyi
Alex BykovskyiStarWind Virtual HCI Appliance Product Manager
Well, we can help you with this one! Building a new hyperconverged environment is a breeze with StarWind Virtual HCI Appliance (VHCA). It’s a complete hyperconverged infrastructure solution that combines hypervisor (vSphere, Hyper-V, Proxmox, or our custom version of KVM), software-defined storage (StarWind VSAN), and streamlined management tools. Interested in diving deeper into VHCA’s capabilities and features? Book your StarWind Virtual HCI Appliance demo today!