public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: kdevops@lists.linux.dev, ross@kallisti.us
Cc: mcgrof@kernel.org
Subject: [PATCH kdevops 1/4] guestfs: make trixie generic image the default
Date: Thu, 10 Oct 2024 18:01:08 -0700	[thread overview]
Message-ID: <20241011010111.3543993-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20241011010111.3543993-1-mcgrof@kernel.org>

The cloud image lacks 9p fs support so can't be used for
kernel hacking on kdevops unless you don't want to use 9p fs..
So while at it codify all this by disabling bootlinux 9p support
if the user selects that image.

Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 kconfigs/Kconfig.guestfs | 14 ++++++++++++--
 workflows/linux/Kconfig  |  2 +-
 2 files changed, 13 insertions(+), 3 deletions(-)

diff --git a/kconfigs/Kconfig.guestfs b/kconfigs/Kconfig.guestfs
index 742781abcddc..da2f5e3961d7 100644
--- a/kconfigs/Kconfig.guestfs
+++ b/kconfigs/Kconfig.guestfs
@@ -10,6 +10,9 @@ config GUESTFS_REQUIRES_UEFI
 	bool
 	output yaml
 
+config GUESTFS_LACKS_9P
+	bool
+
 config GUESTFS_CUSTOM_RAW_IMAGE_URL
 	depends on GUESTFS_HAS_CUSTOM_RAW_IMAGE
 	depends on GUESTFS_HAS_CUSTOM_RAW_IMAGE_URL
@@ -111,19 +114,26 @@ if GUESTFS_DEBIAN_TRIXIE
 
 choice
 	prompt "Debian trixie flavor"
-	default GUESTFS_DEBIAN_TRIXIE_GENERIC_CLOUD_AMD64
+	default GUESTFS_DEBIAN_TRIXIE_GENERIC_AMD64
 
 config GUESTFS_DEBIAN_TRIXIE_GENERIC_AMD64
 	bool "debian-13-generic-amd64-daily"
 	help
 	  Should run in any environment using cloud-init, for e.g. OpenStack,
-	  DigitalOcean and also on bare metal.
+	  DigitalOcean and also on bare metal. This is the image you should
+	  try to use and stick to for kernel testing.
 
 config GUESTFS_DEBIAN_TRIXIE_GENERIC_CLOUD_AMD64
 	bool "debian-13-genericcloud-amd64-daily"
 	help
 	  Similar to generic. Should run in any virtualised environment. Is
 	  smaller than generic by excluding drivers for physical hardware.
+	  Note that the 9p client filesystem module will not be available to
+	  you with this image and so you cannot leverage 9p for building
+	  Linux on the host. This image also requires a EFI boot loader
+	  and secure boot is enabled by default which means your custom
+	  kernels will need to be signed and this plumbing is not supported
+	  yet so you are on your own.
 
 config GUESTFS_DEBIAN_TRIXIE_NOCLOUD_AMD64
 	bool "debian-13-nocloud-amd64-daily"
diff --git a/workflows/linux/Kconfig b/workflows/linux/Kconfig
index 8b1dfd3b25c7..b51d8ee3fb3d 100644
--- a/workflows/linux/Kconfig
+++ b/workflows/linux/Kconfig
@@ -38,7 +38,7 @@ endif # HAVE_SUPPORTS_PURE_IOMAP
 
 config BOOTLINUX_9P
 	bool "Use 9p to build Linux"
-	depends on LIBVIRT
+	depends on LIBVIRT && !GUESTFS_LACKS_9P
 	default LIBVIRT
 	help
 	  This will let you choose use 9p to build Linux. What this does is
-- 
2.43.0


  reply	other threads:[~2024-10-11  1:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-11  1:01 [PATCH kdevops 0/4] kdevops: make trixie default Luis Chamberlain
2024-10-11  1:01 ` Luis Chamberlain [this message]
2024-10-11  1:01 ` [PATCH kdevops 2/4] guestfs: fix uefi boot for debian trixie Luis Chamberlain
2024-10-11  1:01 ` [PATCH kdevops 3/4] guestfs: fix trixie bringup Luis Chamberlain
2024-10-11  1:01 ` [PATCH kdevops 4/4] guestfs: make debian trixie default Luis Chamberlain
2024-10-11 19:00 ` [PATCH kdevops 0/4] kdevops: make " Luis Chamberlain

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=20241011010111.3543993-2-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=kdevops@lists.linux.dev \
    --cc=ross@kallisti.us \
    /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