|2009-08-27||All day||#fedora-test-day (webirc)|
What to test?
Today's installment of Fedora Test Day will focus on the nash/mkinitrd replacement; Dracut. This page will outline several methods for enabling dracut on your system, and describe different root device storage scenarios where feedback is needed. Whether you run fedora on a laptop, or on a stateless nfs-mounted remote filesystem ... dracut will be used.
If you come to this page after the test day is completed, your testing is still valuable, and you can use the information on this page to test with your system and provide feedback.
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
What's needed to test
- A system with some kind of network connection
- Your hardware profile uploaded to Smolt according to these instructions
- An installed Fedora distribution, either:
How to test?
Update To Rawhide
See the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. Alternatively, see below ...
Optionally, you may download a non-destructive rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD.
To test dracut, you will first need to know how to enable dracut support for the distribution you are testing:
- When testing on Fedora 12 Alpha (or rawhide) - QA:Testcase Dracut switch to host-built ramdisk
- When testing on Fedora 11 - QA:Testcase Dracut switch to locally built ramdisk
- Alternatively, if using the rawhide live image - QA:Testcase_Dracut_live_image
To do a simple test, all you need to do is enable Dracut according to the appropriate test case above, then try and boot your system. Report your result in the results table. To find the root= parameter that was used in your test, run
cat /proc/cmdline: it will be shown in the result, usually as the second parameter.
The focus for the dracut test day is to exercise as many different root device partitioning schemas as possible, so if you are confident in your abilities to change the system's partitioning scheme, please try as many variations as possible and report each separately. The following section lists some sample scenarios and provides guidance on creating the partitioning scheme. These tests can be performed on rawhide, Fedora 12 Alpha, Fedora 11 or using the provided live image. In all cases, be sure to confirm you are testing with a dracut generated initial ramdisk image.
|Root=...||Suggested test case|
|root=/dev/dm-0 (encrypted LVM on RAID)||QA:Testcase_anaconda_encrypted_lvm_on_raid|
|Root=...||Suggested test case|
|iSCSI without iBFT||root on iSCSI without iBFT|
|iSCSI with iBFT||QA:Testcase_Anaconda_rootfs_on_iSCSI_with_iBFT|
|root on NFS||QA:Testcase_Dracut_root=nfs|
|root on NBD||QA:Testcase_Dracut_root=nbd|
Report your results
If you have problems with any of the tests, report a bug to Bugzilla usually for the component dracut. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template.
The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). The next two columns should reflect the test you performed and the result. For example, if you tested dracut support for booting a root device using the file system label, you would enter root=LABEL=foo. If any bugs are encountered, be sure to consult How_to_debug_Dracut_problems for guidance and add a link to the bug report in the References column (as in the example line).
In all cases, the following should be mentioned and attached to your bug report:
- The exact kernel command-line used. Typically from the bootloader configuration file (e.g.
/etc/grub.conf) or from
- A copy of your disk partition information from
- A device listing from device-mapper. This can be obtained by running the command
dmsetup ls --tree
- A list of block device attributes including vol_id compatible mode. This can be obtained by running the commands
blkid -o udev
- If you use a dracut configuration file, please include
Use the following table to detail problems discovered or results that don't match expectations.
|User||Smolt Profile||Test scenario||References|
|jlaska||HW||root=/dev/md0 (RAID) |
|Rhe||HW (VMWARE F11)||root=/dev/mapper/VolGroup-lv_root|
|oldfart||HW (F11)||root=/dev/mapper/vg_p5ewspro-fedora11 (LV over raid)|
Things that just work
Hopefully your testing reveals a list of things that work as expected. Please let us know what test scenarios behaved flawlessly.
|User||Smolt Profile||Test scenario||References|
|jlaska||HW (KVM Rawhide guest)||root=/dev/vda2||Worked, no problems|
|jlaska||HW (KVM Rawhide guest)||root=LABEL=rootfs||Worked, no problems|
|jlaska||HW (KVM Rawhide guest)||root=UUID=ffd49db4-0f17-4379-9d1f-ec6a8056d5c8||Worked, no problems|
|Rhe||HW (VMWARE Rawhide guest)||root=UUID=e428a9f4-9713-47a6-9e29-8572le672629||Worked, no problems|
|Rhe||HW (VMWARE Rawhide guest)||root=LABEL=dracut||Worked, no problems|
|Rhe||HW (VMWARE Rawhide guest)||root=/dev/mapper/VolGroup-lv_root||Worked, no problems|
|atodorov||(xen PV guest)||NBD with root=nbd:ip:port:fstype||Worked, no problems|
|atodorov||(xen PV guest)||NBD with root=UUID=UU-ID-BY-BLKID netroot=nbd:ip:port:fstype||Worked, no problems|
|Michal Nowak||(KVM guest)||root=/dev/mapper/VolGroup-lv_root||Worked, no problems|
|Michal Nowak||F-11||local img via dracut generation||W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko spotted. Was told is OK.|
|Jan Stodola||(f11, KVM guest, x86_64)||NFS with root=ip:/path||Worked, no problems|
|jlaska||HW - F11 x86_64 with dracut-0.9-2.fc11||root=/dev/mapper/VolGroup00-f11_root (LVM)
|mebourne||HW - F11 x86_64 with dracut-0.9-2.fc11||root=UUID=63aad468-b185-4404-b4e9-c00b4f2a5dbe luks encrypted PV, root on LVM||now working great|
|mebourne||HW - F11 x86_64 with dracut-0.9-2.fc11 and PXE boot||root=dhcp (dhcp root-path "nbd:192.168.65.2:2000:ext3:ro,noatime")
|Worked. root=<uuid> (as suggested by dracut-gencmdline) didn't work
root=/dev/nbd0 which worked with mkinitrd didn't work
|atodorov||(xen PV guest)||iSCSI without iBFT - root=UUID=... netroot=iscsi:...||Worked, no problems|
|emcnabb||HW - F11 x86_64 with dracut-0.9-2.fc11||root=/dev/mapper/volgrp-root (btrfs)||Worked, but did see RHBZ #519720 (should be fixed in rawhide version of udev) and RHBZ #519733.|
|Jan Stodola||HW (F11 ppc64 dracut-0.9-1.fc11)||root=/dev/sdb1||Worked, no problems|
|jkoten||HW - Rawhide x86_64 with dracut-0.9-2.fc12||root=/dev/sda3
|Worked, no problems|
|Jan Stodola||F11, KVM, x86_64, dracut-0.9-2.fc11||root=/dev/mapper/VolGroup-lv_root (LVM is encrypted)||Worked, no problems|
|Jan Stodola||F11, KVM, x86_64, dracut-0.9-2.fc11||root=/dev/mapper/luks-59f3bc15-e4e2-4131-9b41-7d30a512732c (encrypted ext4 on /dev/sda2)||Worked, no problems|
|mgr||HW - VirtualBox 3.0.4 F11 x86_64 guest with dracut-0.9-2.fc11||root=UUID=e1f390dc-2cf4-4536-928c-af367ce9fa1d||Worked with dracut-0.9-2, did not work with dracut-0.9-1|
|jlaska||HW (KVM Rawhide guest)||root=/dev/mapper/luks-478e81c0-9738-47e2-8a84-74639528032e (RAID + LVM + LUKS)||Failed to boot once ... but has booted fine several times.|
|stan||HW - F11 x86_64 with dracut-0.9-2.fc11||root=UUID=c94b5547-e098-45ca-8776-cce0e0cd6bac||Worked with dracut-0.9-2, though there were some warning messages before udev started. Could not find program name in proc/stat, loop nodes in use, from memory.|
|stan||HW - F11 x86_64 with dracut-0.9-1.fc11||root=UUID=c94b5547-e098-45ca-8776-cce0e0cd6bac||Worked without issue using dracut-0.9-1 when the dracut generated initramfs was compiled into the kernel. Failed otherwise.|
|fluo||HW - vmware F11 i386 with dracut-0.9-2.fc11||root=/dev/mapper/VolGroup-lv_root||Worked without issue using dracut-0.9-2|