From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev
Cc: dave@stgolabs.net, a.manzanares@samsung.com, fan.ni@samsung.com,
jim.harris@samsung.com, Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH] bringup: make guestfs default
Date: Fri, 8 Mar 2024 14:00:45 -0800 [thread overview]
Message-ID: <20240308220046.2722712-1-mcgrof@kernel.org> (raw)
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
--
2.43.0
next reply other threads:[~2024-03-08 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 22:00 Luis Chamberlain [this message]
2024-03-08 22:08 ` [PATCH] bringup: make guestfs default Jeff Layton
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=20240308220046.2722712-1-mcgrof@kernel.org \
--to=mcgrof@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 \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).