virtualbox ubuntu kernel panic not syncing

With that removed, the error message is: List of all partitions: I can reach this case by removing the kernel's ability to read an ext4 filesystem: CONFIG_EXT4_FS=y This is normally because you didn't configure the kernel to read that filesystem type. Linux can read bytes from the disk, but it doesn't understand the filesystem to read files out of it. In our case, the list is empty however, since the next line is completely unrelated. Then, at Please append a correct 'root=' boot option here are the available partitions: it gives a list of partitions it could read. So here Linux tells us that it can't read from vda at all at: VFS: Cannot open root device 'vda' or unknown-block(0,0): error -6.

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Please append a correct 'root=' boot option here are the available partitions: The resulting error message is looks like this VFS: Cannot open root device 'vda' or unknown-block(0,0): error -6 In my QEMU case I can reproduce this by removing the key options that allow the kernel to read that virtio disk: CONFIG_VIRTIO_BLK=y This could be either because the disk is broken, or because you didn't configure Linux with the ability to read from that hardware type. In normal operation, that device would appear under /dev/vda ( v is the indicator letter for virtio, if it were partitioned the partitions would be /dev/vda1, /dev/vda2, etc.) that virtio disk has a raw unpartitioned ext4 image in it.a single virtio disk which represents a hard disk or SDD of real hardware.In that simple setup, QEMU emulates a system with:

Full diagnosis procedure based on kernel messagesīut using this QEMU emulation setup I tried to produce minimal examples of every possible failure type to help you debug your problem.

Virtualbox ubuntu kernel panic not syncing