[PATCH v2 02/33] kconfigs: fix Kconfig references after vagrant removal

[Luis Chamberlain <mcgrof@kernel.org>]

Remove Vagrant references from Kconfig files that were causing build
failures after the vagrant directory was removed:
- Remove vagrant/Kconfig source line from Kconfig.bringup
- Remove VAGRANT_LIBVIRT_SELECT dependency from LIBVIRT config
- Remove PCIe passthrough Vagrant references from Kconfig.libvirt
- Remove VAGRANT-dependent machine type options
- Update help text to remove Vagrant mentions

Generated-by: Claude AI
Suggested-by: Chuck Lever <cel@kernel.org>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
 kconfigs/Kconfig.bringup | 11 +++++------
 kconfigs/Kconfig.libvirt | 20 --------------------
 2 files changed, 5 insertions(+), 26 deletions(-)

diff --git a/kconfigs/Kconfig.bringup b/kconfigs/Kconfig.bringup
index a9aefc56..887d3851 100644
--- a/kconfigs/Kconfig.bringup
+++ b/kconfigs/Kconfig.bringup
@@ -14,8 +14,8 @@ config GUESTFS
 	select KDEVOPS_ENABLE_GUESTFS
 	select EXTRA_STORAGE_SUPPORTS_LARGEIO
 	help
-	  This option will use libguestfs utilities instead of Vagrant to build
-	  guest images and spin them up using libvirt with KVM.
+	  This option will use libguestfs utilities to build guest images and
+	  spin them up using libvirt with KVM.
 
 config TERRAFORM
 	bool "Terraform for cloud environments"
@@ -24,8 +24,8 @@ config TERRAFORM
 	select EXTRA_STORAGE_SUPPORTS_2K
 	select EXTRA_STORAGE_SUPPORTS_4K
 	help
-	  This option will enable use of Vagrant. Enable this if you want to
-	  use terraform to create nodes on a cloud environment such as:
+	  Enable this if you want to use terraform to create nodes on a cloud
+	  environment such as:
 
 	    * Azure
 	    * AWS
@@ -55,11 +55,10 @@ endchoice
 
 config LIBVIRT
 	bool
-	depends on VAGRANT_LIBVIRT_SELECT || GUESTFS
+	depends on GUESTFS
 	default y
 
 source "kconfigs/Kconfig.guestfs"
-source "vagrant/Kconfig"
 source "terraform/Kconfig"
 if LIBVIRT
 source "kconfigs/Kconfig.libvirt"
diff --git a/kconfigs/Kconfig.libvirt b/kconfigs/Kconfig.libvirt
index 1b8f4b95..743a76c6 100644
--- a/kconfigs/Kconfig.libvirt
+++ b/kconfigs/Kconfig.libvirt
@@ -463,32 +463,12 @@ config HAVE_LIBVIRT_PCIE_PASSTHROUGH
 	bool
 	default $(shell, scripts/check_pciepassthrough_kconfig.sh passthrough_libvirt.generated)
 
-if HAVE_LIBVIRT_PCIE_PASSTHROUGH
-source "vagrant/Kconfig.pcie_passthrough_libvirt"
-endif # HAVE_LIBVIRT_PCIE_PASSTHROUGH
 
 choice
 	prompt "Machine type to use"
 	default LIBVIRT_MACHINE_TYPE_Q35 if TARGET_ARCH_X86_64
 	default LIBVIRT_MACHINE_TYPE_VIRT if TARGET_ARCH_ARM64
 
-config LIBVIRT_MACHINE_TYPE_DEFAULT
-	bool "Use the default machine type"
-	depends on VAGRANT
-	help
-	  Use whatever default the guest was intended to use. This will either
-	  be the machine type used at virt-install time or some other default
-	  by QEMU / libvirt. This is important for backward compatibility with
-	  older kernels. For example if you enable q35 on an old kernel the old
-	  kernel may not boot. For details refer to kdevops commit 83952e2e532e
-	  ("vagrant/kdevops_nodes.yaml.in: remove machine_type)".
-
-	  It would seem today's default for libvirt is to still use "pc" which
-	  is the old i440x, so you will not get PCIe support.
-
-	  We only want to support PCI-E capable guests with libguest so the
-	  default is not allowed on libguest.
-
 config LIBVIRT_MACHINE_TYPE_Q35
 	bool "q35"
 	depends on TARGET_ARCH_X86_64
-- 
2.47.2