Description of problem:
Dracut identifies kernel modules for block devices in
90kernel-modules/installkernel by a list of symbols.
One of the symbols is "blk_init_queue", which in the past lead to the inclusion of virtio_blk.ko for vm guests.
In kernel 3.13 virtio_blk calls the new function blk_mq_init_queue rather than blk_init_queue and thus the symbol match fails and virtio_blk is not included any more.
That way vm guests configured vor virtio_blk fail to boot kernel 3.13 unless virtio_blk is included for other reasons.
Please add symbol "blk_mq_init_queue" to the list of symbols next to "blk_init_queue" in 90kernel-modules/installkernel.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fix suggested within above description.
I was having a boot problem on my KVM guest that uses virtio (host=RHEL 6.5 and guest=CentOS 6.5, kernel 3.13). This bug report explains the cause quite well. I created initramfs with a '--add-drivers virtio_blk' option and the kernel booted just fine.
dracut-037-10.git20140402.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dracut-037-10.git20140402.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dracut-037-10.git20140402.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.