Linux cannot bootup after perform P2V "Kernel Panic: No init found"
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Usually this means that the system doesn't know which disk-drive is supposed to be the root volume. This is often specified as a kernel-parameter. Generally the configuration of the boot-loader (e.g. grub) specifies that value.
It can be handy to boot up a live-CD in your virtual-machine because they are especially designed to figure out how to get themselves started. You can then more-easily "have a look around" to see what the kernel is actually seeing when it tries to start.
They're not conflicting .. that's just a warning. Try booting on a live cd of the same distro and version as you P2V'ed .. then chroot into the local disk and recreate initrd. Actually I don't think chroot is required...
Like I said, I don't think chroot is required .. take a look at the man page for mkinitrd. All you want to do is create a new one that includes the relevant controller drivers, by booting on the live cd the correct controller drivers will probably be loaded and mkinitrd will automatically include them.