Libguestfs - Jan 2018 - Re: Trying to mount vmdk - kernel panic not syncing: Attempted to kill init! exitcode=0x00000100

Here is Richard's W.M. Jones answer:
> This is caused by a bug in the way that supermin created symlinks
> which is not compatible with the new kernel:
>
>   291 l bzfgrep          120777 6 0:0 -> \x1c\v
>
> You need to upgrade to the new supermin which fixes this.
> https://www.redhat.com/archives/libguestfs/2017-July/msg00089.html
> https://github.com/libguestfs/supermin/commit/158854e3ba4be7
f6b8d81f662ddad98358ede1de
> https://bugzilla.redhat.com/show_bug.cgi?id=1470157
or alternatively you can rebuild appliance if you have older kernel version
around.
See https://bugzilla.redhat.com/show_bug.cgi?id=1470157#c11 on how to do
that.

Hi,

On Monday, 22 January 2018 13:07:02 CET James Cook
wrote:
> [...]
> supermin: mounting new root on /root
> [    0.387436] EXT4-fs (sdb): mounting ext2 file system using the ext4 
> subsystem
> [    0.389320] EXT4-fs (sdb): mounted filesystem without journal. Opts:
> supermin: chroot
> execl: /init: No such file or directory
> supermin: debug: listing directory /
This is a known bug in supermin, which caused issues with
kernels >= 4.13 -- see also the recent emails:
https://www.redhat.com/archives/libguestfs/2018-January/msg00056.html
https://www.redhat.com/archives/libguestfs/2018-January/msg00088.html

Thanks,
-- 
Pino Toscano

The bug you're hitting is in Ubuntu, it's nothing to do with VMDK.
Please see:

https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1743300
https://github.com/libguestfs/supermin/commit/158854e3ba4be7f6b8d81f662ddad98358ede1de

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org