From: Jeff Layton <jlayton@kernel.org>
To: Luis Chamberlain <mcgrof@kernel.org>, kdevops@lists.linux.dev
Cc: dave@stgolabs.net, a.manzanares@samsung.com, fan.ni@samsung.com,
jim.harris@samsung.com
Subject: Re: [PATCH] bringup: make guestfs default
Date: Fri, 08 Mar 2024 17:08:26 -0500 [thread overview]
Message-ID: <89f94da3e8cfa012577a01674e614e0bfd05be15.camel@kernel.org> (raw)
In-Reply-To: <20240308220046.2722712-1-mcgrof@kernel.org>
On Fri, 2024-03-08 at 14:00 -0800, Luis Chamberlain wrote:
> guestfs has been tested in quite a bit of workflows already and other
> than CXL and ZNS support, it's all there. ZNS support should be easy
> to add, and we need to revisit how we scale CXL support for more
> random dynamic topologies anyway, so that work can be done with
> guestfs. So just make guestfs default now.
>
> Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
> ---
>
> Speak now or hold your peace.
>
> kconfigs/Kconfig.bringup | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kconfigs/Kconfig.bringup b/kconfigs/Kconfig.bringup
> index 2d913ea625ba..d20d427057f2 100644
> --- a/kconfigs/Kconfig.bringup
> +++ b/kconfigs/Kconfig.bringup
> @@ -3,7 +3,7 @@ config BRINGUP_SUPPORTS_CXL
>
> choice
> prompt "Node bring up method"
> - default VAGRANT
> + default GUESTFS
>
> config VAGRANT
> bool "Vagrant for local virtualization (KVM / VirtualBox)"
> @@ -22,7 +22,7 @@ config VAGRANT
> make deps
>
> config GUESTFS
> - bool "Use guestfs-tools for local virtualization via KVM and libvirt (EXPERIMENTAL)"
> + bool "Use guestfs-tools for local virtualization via KVM and libvirt"
> select EXTRA_STORAGE_SUPPORTS_LARGEIO
> help
> This option will use libguestfs utilities instead of Vagrant to build
Acked-by: Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2024-03-08 22:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 22:00 [PATCH] bringup: make guestfs default Luis Chamberlain
2024-03-08 22:08 ` Jeff Layton [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=89f94da3e8cfa012577a01674e614e0bfd05be15.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=a.manzanares@samsung.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=jim.harris@samsung.com \
--cc=kdevops@lists.linux.dev \
--cc=mcgrof@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox