public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 01/40] vagrant: remove entire vagrant configuration directory
Date: Sun, 27 Jul 2025 17:17:20 -0700	[thread overview]
Message-ID: <20250728001800.3188617-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20250728001800.3188617-1-mcgrof@kernel.org>

Remove the complete vagrant/ directory and all its configuration files
as Vagrant support has been removed from kdevops. This includes:
- Kconfig files for various distributions
- PCIe passthrough configurations
- Main Vagrant configuration

Generated-by: Claude AI
Suggested-by: Chuck Lever <cel@kernel.org>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 vagrant/.gitignore                       |   2 -
 vagrant/Kconfig                          | 295 -----------------------
 vagrant/Kconfig.debian                   |  46 ----
 vagrant/Kconfig.fedora                   |  29 ---
 vagrant/Kconfig.kdevops                  |  42 ----
 vagrant/Kconfig.opensuse                 | 144 -----------
 vagrant/Kconfig.pcie_passthrough_libvirt |  53 ----
 vagrant/Kconfig.suse                     |   0
 8 files changed, 611 deletions(-)
 delete mode 100644 vagrant/.gitignore
 delete mode 100644 vagrant/Kconfig
 delete mode 100644 vagrant/Kconfig.debian
 delete mode 100644 vagrant/Kconfig.fedora
 delete mode 100644 vagrant/Kconfig.kdevops
 delete mode 100644 vagrant/Kconfig.opensuse
 delete mode 100644 vagrant/Kconfig.pcie_passthrough_libvirt
 delete mode 100644 vagrant/Kconfig.suse

diff --git a/vagrant/.gitignore b/vagrant/.gitignore
deleted file mode 100644
index 2a00270b..00000000
--- a/vagrant/.gitignore
+++ /dev/null
@@ -1,2 +0,0 @@
-.vagrant
-*.img
diff --git a/vagrant/Kconfig b/vagrant/Kconfig
deleted file mode 100644
index ecf7bcaf..00000000
--- a/vagrant/Kconfig
+++ /dev/null
@@ -1,295 +0,0 @@
-if VAGRANT
-
-choice
-	prompt "Vagrant virtualization technology to use"
-	default VAGRANT_LIBVIRT_SELECT
-
-config VAGRANT_LIBVIRT_SELECT
-	bool "Libvirt"
-	help
-	  Select this option if you want to use KVM / libvirt for
-	  local virtualization.
-
-config VAGRANT_VIRTUALBOX
-	bool "Virtualbox"
-	select EXTRA_STORAGE_SUPPORTS_512
-	select EXTRA_STORAGE_SUPPORTS_1K
-	select EXTRA_STORAGE_SUPPORTS_2K
-	select EXTRA_STORAGE_SUPPORTS_4K
-	help
-	  Select this option if you want to use VirtualBox for
-	  local virtualization.
-
-endchoice
-
-if VAGRANT_VIRTUALBOX
-
-choice
-	prompt "VirtualBox storage pool path"
-	default VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_MANUAL if !DISTRO_SUSE
-	default VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_CWD if DISTRO_SUSE
-
-config VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_CWD
-	bool "Use the current vagrant working directory"
-	help
-	  Select this option if you want to use the vagrant directory inside
-	  where you git cloned kdevops as the Vagrant storage pool path where
-	  additional NVMe drives will be created. As it is today it
-	  would seem only fedora restricts the $HOME to g-rwx o-rwx and so
-	  by default this option won't work on Fedora by default. This used
-	  to be the old default on kdevops but because of this it should not
-	  be used by default. Distributions still relying on this should
-	  verify they can change this default.
-
-config VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_MANUAL
-	bool "Custom manual path"
-	help
-	  Select this option if you want to manually specify where to use as
-	  the directory where we'll have kdevops create additional NVMe drives
-	  for VirtualBox to use. This is today's default given otherwise
-	  we may have to muck with the $HOME directory permissions.
-
-endchoice
-
-config VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM
-	string "VirtualBox storage pool path"
-	default $(shell, scripts/cwd-append.sh vagrant) if VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_CWD
-	default "/opt/virtualbox/storage/" if VIRTUALBOX_STORAGE_POOL_PATH_CUSTOM_MANUAL
-	help
-	  The path to use for creating additional NVMe drives used by
-	  VirtualBox. kdevops adds a postfix "kdevops" to this directory as it
-	  wants to allow Vagrant full control over that directory. For instance
-	  if this is /opt/virtualbox/storage/ kdevops will have VirtualBox
-	  create the NVMe files under the directory
-	  /opt/virtualbox/storage/kdevops/.vagrant/nvme_disks/guest-hostname/.
-
-choice
-	prompt "VirtualBox extra drive format"
-	default VIRTUALBOX_EXTRA_DRIVE_VDI
-
-config VIRTUALBOX_EXTRA_DRIVE_VDI
-	bool "vdi"
-	help
-	  Select this option if you want to use the vdi format.
-
-config VIRTUALBOX_EXTRA_DRIVE_VMDK
-	bool "vmdk"
-	help
-	  Select this option if you want to use the vmdk format.
-
-config VIRTUALBOX_EXTRA_DRIVE_VHD
-	bool "vhd"
-	help
-	  Select this option if you want to use the vhd format.
-
-endchoice
-
-config VIRTUALBOX_EXTRA_DRIVE_FORMAT
-	string
-	default "vdi" if VIRTUALBOX_EXTRA_DRIVE_VDI
-	default "vmdk" if VIRTUALBOX_EXTRA_DRIVE_VMDK
-	default "vhd" if VIRTUALBOX_EXTRA_DRIVE_VHD
-
-endif # VAGRANT_VIRTUALBOX
-
-config HAVE_SUSE_VAGRANT
-	bool
-	default $(shell, scripts/check_distro_kconfig.sh suse)
-
-choice
-	prompt "Vagrant guest Linux distribution to use"
-	default VAGRANT_DEBIAN if DISTRO_DEBIAN || DISTRO_UBUNTU
-	default VAGRANT_FEDORA if DISTRO_FEDORA
-	default VAGRANT_OPENSUSE if DISTRO_OPENSUSE
-	default VAGRANT_SUSE if HAVE_SUSE_VAGRANT
-
-config VAGRANT_DEBIAN
-	bool "Debian"
-	select HAVE_CUSTOM_DISTRO_HOST_PREFIX
-	select HAVE_DISTRO_XFS_PREFERS_MANUAL if FSTESTS_XFS
-	select HAVE_DISTRO_BTRFS_PREFERS_MANUAL if FSTESTS_BTRFS
-	select HAVE_DISTRO_EXT4_PREFERS_MANUAL if FSTESTS_EXT4
-	select HAVE_DISTRO_PREFERS_CUSTOM_HOST_PREFIX
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	help
-	  This option will set the target guest to Debian.
-
-config VAGRANT_OPENSUSE
-	bool "OpenSUSE"
-	select HAVE_CUSTOM_DISTRO_HOST_PREFIX
-	select HAVE_DISTRO_XFS_PREFERS_MANUAL if FSTESTS_XFS
-	select HAVE_DISTRO_BTRFS_PREFERS_MANUAL if FSTESTS_BTRFS
-	select HAVE_DISTRO_EXT4_PREFERS_MANUAL if FSTESTS_EXT4
-	select HAVE_DISTRO_BLKTESTS_PREFERS_MANUAL if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_CUSTOM_HOST_PREFIX
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	help
-	  This option will set the target guest to OpenSUSE.
-
-config VAGRANT_SUSE
-	bool "SUSE"
-	depends on HAVE_SUSE_VAGRANT
-	select HAVE_KDEVOPS_CUSTOM_DEFAULTS
-	select HAVE_CUSTOM_DISTRO_HOST_PREFIX
-	select HAVE_DISTRO_PREFERS_CUSTOM_HOST_PREFIX
-	select HAVE_DISTRO_XFS_PREFERS_MANUAL if FSTESTS_XFS
-	select HAVE_DISTRO_BTRFS_PREFERS_MANUAL if FSTESTS_BTRFS
-	select HAVE_DISTRO_BLKTESTS_PREFERS_MANUAL if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_SUSE
-	select HAVE_DISTRO_PREFERS_REGISTRATION
-	select HAVE_DISTRO_REG_METHOD_TWOLINE
-	select VAGRANT_INSTALL_PRIVATE_BOXES
-	select HAVE_CUSTOM_KDEVOPS_GIT
-	select HAVE_CUSTOM_KDEVOPS_GIT_DATA
-	select HAVE_CUSTOM_KDEVOPS_DIR
-	help
-	  This option will set the target guest to SUSE. There is currently
-	  no scriptable way to download Vagrant images, however the images
-	  are available for download via:
-
-	    https://suse.com/download
-
-config VAGRANT_FEDORA
-	bool "Fedora (or derived distro)"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_PREFERS_MANUAL if FSTESTS_XFS
-	select HAVE_DISTRO_BTRFS_PREFERS_MANUAL if FSTESTS_BTRFS
-	select HAVE_DISTRO_EXT4_PREFERS_MANUAL if FSTESTS_EXT4
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	help
-	  This option will set the target guest to be a distro in the Fedora family.
-	  For example, Fedora, CentOS Stream, RHEL, etc.
-
-config VAGRANT_KDEVOPS
-	bool "kdevops kernel builds"
-	select HAVE_CUSTOM_DISTRO_HOST_PREFIX
-	select HAVE_DISTRO_XFS_PREFERS_MANUAL if FSTESTS_XFS
-	select HAVE_DISTRO_BTRFS_PREFERS_MANUAL if FSTESTS_BTRFS
-	select HAVE_DISTRO_EXT4_PREFERS_MANUAL if FSTESTS_EXT4
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_FSTESTS
-	help
-	  This option will let you select custom kernel builds by the
-	  kdevops project. The distributions may vary and are are specified.
-endchoice
-
-config HAVE_VAGRANT_BOX_VERSION
-	bool
-	default n
-
-source "vagrant/Kconfig.debian"
-source "vagrant/Kconfig.opensuse"
-source "vagrant/Kconfig.fedora"
-source "vagrant/Kconfig.kdevops"
-
-if HAVE_SUSE_VAGRANT
-source "vagrant/Kconfig.suse"
-endif # HAVE_SUSE_VAGRANT
-
-config VAGRANT_BOX
-	string
-	default "debian/testing64" if VAGRANT_DEBIAN_TESTING64 || !VAGRANT
-	default "debian/bullseye64" if VAGRANT_DEBIAN_BULLSEYE64
-	default "debian/buster64" if VAGRANT_DEBIAN_BUSTER64
-	default "opensuse/Tumbleweed.x86_64" if VAGRANT_OPENSUSE_X86_64_TW
-	default VAGRANT_FEDORA_BOX_STRING if VAGRANT_FEDORA
-	default "generic/rhel8" if VAGRANT_REDHAT_GENERIC_RHEL8_X86_64
-	default "generic/rhel9" if VAGRANT_REDHAT_GENERIC_RHEL9_X86_64
-	default "opensuse/Leap-15.3.x86_64" if VAGRANT_OPENSUSE_X86_64_LEAP_15_3
-	default "opensuse/Leap-15.4.x86_64" if VAGRANT_OPENSUSE_X86_64_LEAP_15_4
-	default "Leap-15.4.x86_64" if VAGRANT_OPENSUSE_X86_64_LEAP_15_4
-	default "linux-kdevops/debian-next-20220629" if VAGRANT_KDEVOPS_DEBIAN_TESTING64_NEXT_20220629 || !VAGRANT
-	default "linux-kdevops/debian-xfs-20230427" if VAGRANT_KDEVOPS_DEBIAN_TESTING64_XFS_20230427 || !VAGRANT
-	default VAGRANT_SUSE_BOX if VAGRANT_SUSE
-	help
-	  The Vagrant box to use.
-
-config VAGRANT_BOX_UPDATE_ON_BRINGUP
-	bool "Run Vagrant box update prior to bringup"
-	default y
-	help
-	  When you use Vagrant on a system the target box for the distribution
-	  will first be downloaded on its first use. It will not be updated
-	  until you manually run "vagrant box update" on the respective vagrant
-	  directory. This can mean that if your system first used kdevops in
-	  January 2022 and you are using Debian testing, the old version of
-	  Debian testing as of January 2022 will be used if you try to
-	  instantiate a guest in January 2023. This can means your userspace
-	  may be too old to deal with some new kernel features. An example
-	  is zstd module support for initframfs does not work well with old
-	  userspace on Debian testing. The boot will fail when trying to
-	  run "make linux" and it would not be clear why, the reason would be
-	  a failed ext4 module could not be loaded, in fact no modules could
-	  be loaded by the initramfs. To fix the user experience we ensure we
-	  always run "vagrant box update" as the first step to "make bringup".
-
-	  Folks testing stable kernels will use stable distributions, such as
-	  Debian bullseye that don't move userspace as often but in fact welcome
-	  their own stable updates to userspace, and this is why this is kept
-	  as enabled by default.
-
-	  You may want to disable this if you don't want to deal with these
-	  updates on bringup, and you want to do the updates on your own.
-	  Note that if you already ran bringup with an old box, you won't
-	  reap benefits of the new one until you "make destroy" and then
-	  "make bringup" again. If you are already on an old box and don't
-	  want to destroy your current box image you can just upgrade userspace
-	  manually by the typical distro means to update itself. For example
-	  on Debian testing that's "apt-get update && apt-get dist-upgrade".
-
-config VAGRANT_VALIDATE_BEFORE_BRINGUP
-	bool "Validate Vagrantfile prior to bringup"
-	default y
-	help
-	  Folks hacking on the Vagrantfile may want to ensure they validate
-	  the Vagrantfile first. This will allow developers to identify issues
-	  prior to running some real virtualization commands. Enable this by
-	  default as validation is fast and safe.
-
-config VAGRANT_PREFERRED_KERNEL_CI_SUBJECT_TOPIC
-	string
-	default VAGRANT_BOX if VAGRANT_DEBIAN_BUSTER64
-	default VAGRANT_BOX if VAGRANT_DEBIAN_BULLSEYE64
-
-config HAVE_VAGRANT_BOX_URL
-	bool
-
-if HAVE_VAGRANT_BOX_URL
-
-config VAGRANT_BOX_URL
-	string
-	depends on HAVE_VAGRANT_BOX_URL
-	default VAGRANT_SUSE_BOX_URL if HAVE_SUSE_VAGRANT
-	default "https://download.opensuse.org/repositories/Virtualization:/Appliances:/Images:/openSUSE-Leap-15.4/images/boxes/Leap-15.4.x86_64.json" if VAGRANT_OPENSUSE_X86_64_LEAP_15_4
-
-endif # HAVE_VAGRANT_BOX_URL
-
-if HAVE_VAGRANT_BOX_VERSION
-
-config VAGRANT_BOX_VERSION
-	string
-	default "1.0.20230425" if VAGRANT_OPENSUSE_X86_64_TW_1020230425
-	default "1.0.20220528" if VAGRANT_OPENSUSE_X86_64_TW_1020220528
-	default "1.0.20210915" if VAGRANT_OPENSUSE_X86_64_TW_1020210915
-	default "1.0.20210203" if VAGRANT_OPENSUSE_X86_64_TW_1020210203
-	default "1.0.20200714" if VAGRANT_OPENSUSE_X86_64_TW_1020200714
-	default "1.0.20210203" if VAGRANT_OPENSUSE_X86_64_TW_1020210203
-	default "0.1.0" if VAGRANT_KDEVOPS_DEBIAN_TESTING64_NEXT_20220629
-	help
-	  The Vagrant box version to use. This is set for you depending on the
-	  image you select. You can manually override the version we have last
-	  tested here.
-
-endif # HAVE_VAGRANT_BOX_VERSION
-
-if !HAVE_VAGRANT_BOX_VERSION
-
-config VAGRANT_BOX_VERSION
-	string
-	default ""
-
-endif # !HAVE_VAGRANT_BOX_VERSION
-endif # VAGRANT
diff --git a/vagrant/Kconfig.debian b/vagrant/Kconfig.debian
deleted file mode 100644
index c316e728..00000000
--- a/vagrant/Kconfig.debian
+++ /dev/null
@@ -1,46 +0,0 @@
-# SPDX-License-Identifier: copyleft-next-0.3.1
-if VAGRANT_DEBIAN
-
-choice
-	prompt "Debian release to use"
-	default VAGRANT_DEBIAN_TESTING64
-
-config VAGRANT_DEBIAN_BUSTER64
-	bool "debian/buster64"
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will set the target guest to debian/buster64.
-
-config VAGRANT_DEBIAN_BULLSEYE64
-	bool "debian/bullseye64"
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will set the target guest to debian/bullseye64.
-
-config VAGRANT_DEBIAN_TESTING64
-	bool "debian/testing64"
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will set the target guest to debian/testing64.
-
-endchoice
-
-config VAGRANT_DEBIAN_BOX_SHORT
-	string
-	default "buster64" if VAGRANT_DEBIAN_BUSTER64
-	default "bullseye64" if VAGRANT_DEBIAN_BULLSEYE64
-	default "testing64" if VAGRANT_DEBIAN_TESTING64
-
-endif # VAGRANT_DEBIAN
diff --git a/vagrant/Kconfig.fedora b/vagrant/Kconfig.fedora
deleted file mode 100644
index 420e6cc8..00000000
--- a/vagrant/Kconfig.fedora
+++ /dev/null
@@ -1,29 +0,0 @@
-# SPDX-License-Identifier: copyleft-next-0.3.1
-if VAGRANT_FEDORA
-
-config VAGRANT_FEDORA_BOX_STRING
-	string "Vagrant box string"
-	default "fedora/38-cloud-base"
-	help
-	  This is the box string that vagrant should use. This is typically
-	  something like fedora/??-cloud-base or generic/rhel?. We default
-	  to the latest Fedora cloud-base release.
-
-config VAGRANT_FEDORA_OLD_RELEASE
-	bool "Is this an old release (pre-Fedora 32)?"
-	default n
-	help
-	  XFS on older Fedora releases lacked support for certain
-	  features. Enabling this will disable testing certain
-	  configurations by default in the fstests workflow.
-
-config VAGRANT_FEDORA_NEW_RELEASE
-	bool
-	default y
-	depends on !VAGRANT_FEDORA_OLD_RELEASE
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-
-endif # VAGRANT_FEDORA
diff --git a/vagrant/Kconfig.kdevops b/vagrant/Kconfig.kdevops
deleted file mode 100644
index 25398034..00000000
--- a/vagrant/Kconfig.kdevops
+++ /dev/null
@@ -1,42 +0,0 @@
-# SPDX-License-Identifier: copyleft-next-0.3.1
-if VAGRANT_KDEVOPS
-
-choice
-	prompt "Kdevops release to use"
-	default VAGRANT_KDEVOPS_DEBIAN_TESTING64_XFS_20230427
-
-config VAGRANT_KDEVOPS_DEBIAN_TESTING64_XFS_20230427
-	bool "linux-kdevops/debian-xfs-20230427"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	select HAVE_SUPPORTS_PURE_IOMAP
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will set the target guest to
-	  linux-kdevops/debian-xfs-20230423 which is based on
-	  debian-testing and only uses XFS for the root fs.
-
-config VAGRANT_KDEVOPS_DEBIAN_TESTING64_NEXT_20220629
-	bool "linux-kdevops/debian-next-20220629"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	depends on TARGET_ARCH_X86_64
-	help
-	  This option will set the target guest to
-	  linux-kdevops/debian-next-20220629 which is based on
-	  debian-testing. It just has linux-next next-20220629.
-
-endchoice
-
-config VAGRANT_DEBIAN_BOX_SHORT
-	string
-	default "debian-next-20220629" if VAGRANT_KDEVOPS_DEBIAN_TESTING64_NEXT_20220629
-	default "debian-xfs-20230427" if VAGRANT_KDEVOPS_DEBIAN_TESTING64_XFS_20230427
-
-endif # VAGRANT_KDEVOPS
diff --git a/vagrant/Kconfig.opensuse b/vagrant/Kconfig.opensuse
deleted file mode 100644
index 6da40275..00000000
--- a/vagrant/Kconfig.opensuse
+++ /dev/null
@@ -1,144 +0,0 @@
-# SPDX-License-Identifier: copyleft-next-0.3.1
-if VAGRANT_OPENSUSE
-
-choice
-	prompt "OpenSUSE release to use"
-	default VAGRANT_OPENSUSE_X86_64_LEAP_15_3
-
-config VAGRANT_OPENSUSE_X86_64_TW
-	bool "opensuse/Tumbleweed.x86_64"
-	depends on TARGET_ARCH_X86_64
-	help
-	  Enable this to be able to select between the supported OpenSUSE
-	  Tumbleweed releases.
-
-config VAGRANT_OPENSUSE_X86_64_LEAP_15_4
-	bool "opensuse/Leap-15.4.x86_64"
-	depends on TARGET_ARCH_X86_64
-	select HAVE_DISTRO_BTRFS_DISABLES_RAID56  if FSTESTS_BTRFS
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL
-	select HAVE_DISTRO_BLKTESTS_TEST_BLOCK if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_BLKTESTS_TEST_LOOP if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_BLKTESTS_TEST_NBD if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_BLKTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_BLKTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_REFRESH
-	select HAVE_DISTRO_PREFERS_UPDATE
-	select HAVE_DISTRO_PREFERS_INSTALL_KDEVTOOLS
-	select HAVE_DISTRO_PREFERS_ANSIBLE_PYTHON2 if !HAVE_DISTRO_PREFERS_DISABLE_ANSIBLE && KDEVOPS_ANSIBLE_PROVISION_ENABLE
-	help
-	  This enables the OpenSUSE Leap 15.4 release.
-
-config VAGRANT_OPENSUSE_X86_64_LEAP_15_3
-	bool "opensuse/Leap-15.3.x86_64"
-	depends on TARGET_ARCH_X86_64
-	select HAVE_DISTRO_BTRFS_DISABLES_RAID56  if FSTESTS_BTRFS
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG
-	select HAVE_DISTRO_PREFERS_FSTESTS_WATCHDOG_KILL
-	select HAVE_DISTRO_BLKTESTS_TEST_BLOCK if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_BLKTESTS_TEST_LOOP if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_BLKTESTS_TEST_NBD if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_BLKTESTS_WATCHDOG if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_BLKTESTS_WATCHDOG_KILL if KDEVOPS_WORKFLOW_ENABLE_BLKTESTS
-	select HAVE_DISTRO_PREFERS_REFRESH
-	select HAVE_DISTRO_PREFERS_UPDATE
-	select HAVE_DISTRO_PREFERS_INSTALL_KDEVTOOLS
-	select HAVE_DISTRO_PREFERS_ANSIBLE_PYTHON2 if !HAVE_DISTRO_PREFERS_DISABLE_ANSIBLE && KDEVOPS_ANSIBLE_PROVISION_ENABLE
-	help
-	  This enables the OpenSUSE Leap 15.3 release.
-
-endchoice
-
-if VAGRANT_OPENSUSE_X86_64_TW
-
-choice
-	prompt "opensuse/Tumbleweed.x86_64 version to use"
-	default VAGRANT_OPENSUSE_X86_64_TW_1020230529
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020230529
-	bool "opensuse/Tumbleweed.x86_64 1.0.20230529"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20230529.
-
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020230425
-	bool "opensuse/Tumbleweed.x86_64 1.0.20230425"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20230425.
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020220528
-	bool "opensuse/Tumbleweed.x86_64 1.0.20220528"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20220528.
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020210915
-	bool "opensuse/Tumbleweed.x86_64 1.0.20210915 "
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20210915.
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020210203
-	bool "opensuse/Tumbleweed.x86_64 1.0.20210203 "
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20210203.
-
-config VAGRANT_OPENSUSE_X86_64_TW_1020200714
-	bool "opensuse/Tumbleweed.x86_64 1.0.20200714"
-	select HAVE_VAGRANT_BOX_VERSION
-	select HAVE_DISTRO_XFS_SUPPORTS_CRC if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_EXTERNAL_LOG if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_REFLINKS if FSTESTS_XFS
-	select HAVE_DISTRO_XFS_SUPPORTS_BIGBLOCKS if FSTESTS_XFS
-	help
-	  This option will set the target guest to opensuse/Tumbleweed.x86_64
-	  release 1.0.20200714.
-
-endchoice
-
-endif # VAGRANT_OPENSUSE_X86_64_TW
-
-config VAGRANT_OPENSUSE_BOX_SHORT
-	string
-	default "tw" if VAGRANT_OPENSUSE_X86_64_TW
-	default "leap15sp3" if VAGRANT_OPENSUSE_X86_64_LEAP_15_3
-	default "leap15sp4" if VAGRANT_OPENSUSE_X86_64_LEAP_15_4
-
-endif # VAGRANT_OPENSUSE
diff --git a/vagrant/Kconfig.pcie_passthrough_libvirt b/vagrant/Kconfig.pcie_passthrough_libvirt
deleted file mode 100644
index 62d3a86d..00000000
--- a/vagrant/Kconfig.pcie_passthrough_libvirt
+++ /dev/null
@@ -1,53 +0,0 @@
-# SPDX-License-Identifier: copyleft-next-0.3.1
-
-config KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH
-	bool "Enable libvirt PCIE passthrough support"
-	default n
-	help
-	  Enable this if you want to enable PCI-E passthrough onto target
-	  guests.
-
-if KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH
-
-choice
-	prompt "What guest target type to passthrough to"
-	default KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TYPE_FIRST
-
-config KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TYPE_FIRST
-	bool "Onto the first guest"
-	help
-	  Select this option if you want to passthrough PCI-E devices selected
-	  onto the first guest that kdevops generates on the nodes list.
-
-config KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TYPE_SPECIFIC
-	bool "Onto a specific host name you'll specify"
-	help
-	  Select this option if you want to passthrough PCI-E devices onto
-	  a guest hostname. This means you have foresight into the future
-	  generated kdevops nodes that will be available and you will manually
-	  specify a target hostname you want to use to pass on the selected
-	  PCI-E devices to.
-
-config KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TYPE_EACH
-	bool "Per device specific host"
-	help
-	  Select this option if you want to have the option passthrough PCI-E
-	  devices to different target guests. This will allow you to have the
-	  ability to specify for each found PCI-E device which, to which target
-	  guest you want to enable the device to passthrough onto.
-
-endchoice
-
-config KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TARGET_HOSTNAME
-	string "Guest target hostname to passthrough PCI-E devices to"
-	default "enter-valid-hostname"
-	depends on KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH_TYPE_SPECIFIC
-	help
-	  Set this to the hostname of the target guest you want to passthrough
-	  the enabled PCI-E devices to.
-
-menu "Select which PCI-E devices to passthrough"
-source "vagrant/Kconfig.passthrough_libvirt.generated"
-endmenu
-
-endif # KDEVOPS_LIBVIRT_PCIE_PASSTHROUGH
diff --git a/vagrant/Kconfig.suse b/vagrant/Kconfig.suse
deleted file mode 100644
index e69de29b..00000000
-- 
2.47.2


  reply	other threads:[~2025-07-28  0:18 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28  0:17 [PATCH 00/40] remove vagrant and bootlinux shape up Luis Chamberlain
2025-07-28  0:17 ` Luis Chamberlain [this message]
2025-07-28  0:17 ` [PATCH 02/40] kconfigs: fix Kconfig references after vagrant removal Luis Chamberlain
2025-07-28  0:17 ` [PATCH 03/40] scripts: remove Vagrant-specific scripts and Makefiles Luis Chamberlain
2025-07-28  0:17 ` [PATCH 04/40] playbooks: remove Vagrant-specific playbooks and roles Luis Chamberlain
2025-07-28  0:17 ` [PATCH 05/40] gitignore: remove Vagrant-specific ignore patterns Luis Chamberlain
2025-07-28  0:17 ` [PATCH 06/40] docs: remove Vagrant-specific documentation files Luis Chamberlain
2025-07-28  0:17 ` [PATCH 07/40] Remove all remaining Vagrant references from codebase Luis Chamberlain
2025-07-28  0:17 ` [PATCH 08/40] AuthorDate: Fri Jul 25 14:23:00 2025 -0400 Luis Chamberlain
2025-07-28  0:17 ` [PATCH 09/40] ansible.cfg: Explicitly set the ssh user Luis Chamberlain
2025-07-28  0:24   ` Chuck Lever
2025-07-28  0:27     ` Luis Chamberlain
2025-07-28  0:36       ` Chuck Lever
2025-07-28  0:17 ` [PATCH 10/40] fstests: local NFS list Luis Chamberlain
2025-07-28  0:17 ` [PATCH 11/40] terraform: Clean up the destroy tasks Luis Chamberlain
2025-07-28  0:17 ` [PATCH 12/40] Switch to the cloud.terraform.terraform module Luis Chamberlain
2025-07-28  0:17 ` [PATCH 13/40] terraform: Make use of the new "terraform_output" module Luis Chamberlain
2025-07-28  0:17 ` [PATCH 14/40] terraform: Move "wait_for_connection" out of the terraform playbook Luis Chamberlain
2025-07-28  0:17 ` [PATCH 15/40] terraform: Remove "delegate_to: localhost" Luis Chamberlain
2025-07-28  0:17 ` [PATCH 16/40] terraform: Replace scripts/status_terraform.sh Luis Chamberlain
2025-07-28  0:17 ` [PATCH 17/40] Kconfig: Convert the 9p option to a choice menu Luis Chamberlain
2025-07-28  0:17 ` [PATCH 18/40] bootlinux: fix making 9p default if using libvirt Luis Chamberlain
2025-07-28  0:17 ` [PATCH 19/40] bootlinux: Relocate tasks that select a kernel .config Luis Chamberlain
2025-07-28  0:17 ` [PATCH 20/40] bootlinux: Simplify tasks that select the kernel .config to build Luis Chamberlain
2025-07-28  0:17 ` [PATCH 21/40] bootlinux: Select the kernel .config earlier Luis Chamberlain
2025-07-28  0:17 ` [PATCH 22/40] bootlinux: Move 9p build tasks to a subrole Luis Chamberlain
2025-07-28  0:17 ` [PATCH 23/40] bootlinux: fix missing make command when using 9P builds Luis Chamberlain
2025-07-28  0:17 ` [PATCH 24/40] guestsfs: ensure linux directory exists Luis Chamberlain
2025-07-28  0:17 ` [PATCH 25/40] bootlinux: Move tasks for building on target nodes to a subrole Luis Chamberlain
2025-07-28  0:17 ` [PATCH 26/40] bootlinux: Clean up a grub set-up task Luis Chamberlain
2025-07-28  0:17 ` [PATCH 27/40] bootlinux: Harden update-grub/install.yml Luis Chamberlain
2025-07-28  0:17 ` [PATCH 28/40] bootlinux: fix grub_boot_number_cmd undefined error in update-grub Luis Chamberlain
2025-07-28  0:17 ` [PATCH 29/40] bootlinux: fix kernel_release_file.stat " Luis Chamberlain
2025-07-28  0:17 ` [PATCH 30/40] Add a guest/instance for building the test kernel Luis Chamberlain
2025-07-28  0:17 ` [PATCH 31/40] bootlinux: Add a new builder choice Luis Chamberlain
2025-07-28  0:17 ` [PATCH 32/40] workflows: Add a kconfig setting for installing kernels via package Luis Chamberlain
2025-07-28  0:17 ` [PATCH 33/40] bootlinux: Enclose tasks to find kernel release name in a block: Luis Chamberlain
2025-07-28  0:17 ` [PATCH 34/40] bootlinux: Pick up kernel release info for pre-built packages Luis Chamberlain
2025-07-28  0:17 ` [PATCH 35/40] bootlinux: Install pre-built kernels from packages Luis Chamberlain
2025-07-28  0:17 ` [PATCH 36/40] bootlinux: Add an option to build with clang instead of gcc Luis Chamberlain
2025-07-28  0:17 ` [PATCH 37/40] Makefile: add make style for style checking Luis Chamberlain
2025-07-28  0:17 ` [PATCH 38/40] CLAUDE.md: new workflow guide for hosts and nodes Luis Chamberlain
2025-07-28  0:17 ` [PATCH 39/40] CLAUDE.md: add don't BS rules Luis Chamberlain
2025-07-28  0:17 ` [PATCH 40/40] gen_nodes/gen_hosts: avoid usage of fs_config_path on task names 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=20250728001800.3188617-2-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kruces.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