generic/ubuntu1804 kernel panic on boot with virtualbox

[lavabit]

generic/ubuntu1804 kernel panic on boot with virtualbox

[ladar]

I believe the only custom kernel options in use for that image are net.ifnames=0 biosdevname=0 ... but the robox install config does include the linux-tools-$(uname -r) linux-cloud-tools-$(uname -r) linux-cloud-tools-common linux-cloud-tools-generic linux-cloud-tools-virtual packages, which could be causing the robox version to load additional kernel modules, or use a different kernel version. Those packages are required by the Hyper-V version, but could be removed from the default package set on other hypervisors (I think).

I suppose there is also a slim chance the other boxes use a different swap configuration, which allows them to swap out data during boot and avoid the error you're seeing, which doesn't happen with the robox (for some unknown reason).

If you find the culprit, let me know.

[ladar]

@furlongm were you able to identify the problem? Or should I close this issue? I assume the image worked just fine with more memory, say 512mb or greater?

[furlongm]

Yes it happens in other images too, once the kernel is updated. So this is an Ubuntu issue. Increasing the memory works.