ffe825113e
Currently, calling the troubleshoot function in a ramdisk script doesn't work as expected on dracut ramdisks. This adds an alternate troubleshoot implementation that will behave as intended. I did not make it conditional on a kernel param as was done in the original because dracut can behave strangely if you allow it to continue after an error. Always dropping to a shell immediately should be less confusing. Change-Id: I98000f4ac6d7890b1f44fe4d10394ac0ea332fcb
dracut-ramdisk
Build Dracut-based ramdisks
This is an alternative to the ramdisk element that uses Dracut to provide the base system functionality instead of Busybox.
For elements that need additional drivers in the ramdisk image, a dracut-drivers.d feature is included that works in a similar fashion to the binary-deps.d feature. The element needing to add drivers should create a dracut-drivers.d directory and populate it with a single file listing all of the kernel modules it needs added to the ramdisk. Comments are not supported in this file. Note that these modules must be installed in the chroot first.
By default, the virtio, virtio_net, and virtio_blk modules are included so that ramdisks are able to function properly in a virtualized environment.