From: "Harry G. Coin" <hgcoin@gmail.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: virtio-fs-list <virtio-fs@redhat.com>
Subject: Re: [Virtio-fs] Virtiofs Kernel Boot howto
Date: Fri, 4 Jun 2021 16:53:50 -0500 [thread overview]
Message-ID: <040a0a58-10f1-b959-5294-404d113a212e@gmail.com> (raw)
In-Reply-To: <20210604205817.GA323260@redhat.com>
On 6/4/21 3:58 PM, Vivek Goyal wrote:
> On Fri, Jun 04, 2021 at 11:28:42AM -0500, Harry G. Coin wrote:
>> Mentioned up-list, here's a further little helper to allow virtio-fs root.
> Hi Harry,
>
> Thanks for posting instructions on how to boot with virtiofs as rootfs.
>
> [..]
>> and as 'kernel args' (presuming you've built dracut with the added conf
>> files I published on this list previously):
>>
>> root=virtiofs:myfs rd.shell rd.fstab
> Ok, this is interesting bit that how virtiofs root should be specified
> so that it can be parsed both by kernel as well as initramfs module.
>
> I don't think "root=virtiofs:myfs" is recognized by kernel. So you must
> have coded dracut module to parse it appropriately.
Actually, until recent kernels the addition of 'virtiofs:...' was not
required, only rootfstype=virtiofs and 'the tag was just that, any
tag'. However recent kernels failed to boot, so I had to specify that.
My suggestion, if you like standards, is to notice how 9p does it, and
follow that. The reason I suggest that is I suspect nearly everyone
that presently uses 9p will move to this if their systems support it,
once it doesn't take a Ph.D. in five or six things to 'seem as good as
installing from ISO to a block device'.
prev parent reply other threads:[~2021-06-04 21:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-04 16:28 [Virtio-fs] Virtiofs Kernel Boot howto Harry G. Coin
2021-06-04 20:58 ` Vivek Goyal
2021-06-04 21:53 ` Harry G. Coin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=040a0a58-10f1-b959-5294-404d113a212e@gmail.com \
--to=hgcoin@gmail.com \
--cc=vgoyal@redhat.com \
--cc=virtio-fs@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.