Am 08.04.2013 15:05, schrieb Matthew Miller: > We're going to produce official Fedora Cloud images which should run on > Amazon EC2, and various open source cloud infrastructure -- OpenStack, > Eucalyptus, CloudStack, OpenNebula; with both KVM and Xen -- and probably > also under VMware and VirtualBox. > > These images will be generated in Koji, not in the target systems. What's > the best way to get the right stuff (and ideally only the right stuff) in > the initramfs? > Depends on what the dracut image should be able to boot. LVM, crypto, MD raids? Which filesystems? # dracut test.img \ --drivers 'ext4' \ --filesystems 'ext4' \ --fscks 'ext4' \ --add qemu \ --omit network \ --omit mdraid \ --omit dmraid \ --omit plymouth \ --omit drm \ --omit btrfs \ --omit biosdevname \ --omit caps \ --omit resume \ --omit crypt \ --omit i18n \ --omit terminfo \ --omit multipath \ --no-hostonly This will build the initramfs test.img without network, MD-raid, DM-raid, plymouth, gfx drivers, without general purpose HW block drivers, without resume, biosdevname, btrfs, caps, crypt, i18n, terminfo but with the "ext4" filesystem support, LVM, multipath and qemu block kernel drivers. $ ls -lh test.img -rw------- 1 harald harald 6,9M 8. Apr 16:05 test.img to see, which dracut modules have been used: $ lsinitrd test.img usr/lib/dracut/modules.txt dm kernel-modules lvm multipath qemu rootfs-block udev-rules systemd usrmount base fs-lib shutdown So, instead, you could also call dracut with: # dracut test.img \ --drivers 'ext4' \ --filesystems 'ext4' \ --fscks 'ext4' \ --modules "dm kernel-modules lvm multipath qemu rootfs-block udev-rules systemd usrmount base fs-lib shutdown" To see, which kernel drivers are in the initramfs: # lsinitrd test.img | grep /lib/modules To add a kernel driver, add it to the --drivers list. Let me know, if you need more info. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
