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 for a reliable, high-performance, and cost-effective shared storage solution for your production cluster?
Dmytro Malynka
Dmytro MalynkaStarWind Virtual SAN Product Manager
We’ve got you covered! StarWind Virtual SAN (VSAN) is specifically designed to provide highly-available shared storage for Hyper-V, vSphere, and KVM clusters. With StarWind VSAN, simplicity is key: utilize the local disks of your hypervisor hosts and create shared HA storage for your VMs. Interested in learning more? Book a short StarWind VSAN demo now and see it in action!