Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
dracut currently can't deal with mounting virtiofs as root filesystem. Add support for virtiofs in dracut. People are trying to use virtiofs as rootfs
and complaining.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
I assume you have the set up to test this easily, so: does it work if you add qemu module into initrd? If not, does it work if you add qemu module and virtiofs driver?
(In reply to David Tardon from comment #1)
> I assume you have the set up to test this easily, so: does it work if you
> add qemu module into initrd? If not, does it work if you add qemu module and
> virtiofs driver?
I don't have a working setup yet. Frankly speaking, my initrd will not mount it and drop me to emergency shell. There I will mount it manually "mount -t virtiofs myfs /sysroot" and then continue booting.
I think one problem is that how rootfs device should be specified for virtiofs filessytem. There does not seem to be a good way and different kind of hacks are being used. I have proposed one patch upstream
just now.
https://lore.kernel.org/linux-fsdevel/20210608153524.GB504497@redhat.com/
If this gets accepted then we can specify "root=fstag:myfs rootfstype=virtiofs" on kernel command line. I am assuming that some dracut module can parse this and mount virtiofs. Not sure if we will need a separate
virtiofs module for this or some existing module can take care this.
I have not played with "qemu" module. Can give it a try. What is it supposed to do? I mean what kind of filesystems it can mount.
I see that we have a module 95virtfs/ which seems to have support for 9p/virtfs. I think we will need something similar for virtiofs.
What I am not sure is that does dracut relies on same syntax for "root=" option for kernel and dracut. Or dracut has moved on and has its own
way to parse root= option irrespective of kernel.
If dracut parses "root=virtiofs:myfs", then problem becomes little easier. Or may be we can modify it to parse "root=fstag:myfs rootfstype=virtiofs" combo so that it is inline with kernel parsing. Assuming kernel,
will accept my proposal.