public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: 結友 <miagetegorann@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-kernel v4 2/2] fix #8027: config: enable CONFIG_HYPERV_VMBUS
Date: Sat, 24 Oct 2026 14:24:38 +0900	[thread overview]
Message-ID: <20261024052438.1274-3-miagetegorann@gmail.com> (raw)
In-Reply-To: <20261024052438.1274-1-miagetegorann@gmail.com>

Linux 6.18 split the Hyper-V guest support options: CONFIG_HYPERV became a
plain bool covering only the core hypervisor support, and the VMBus bus
driver moved to the new tristate CONFIG_HYPERV_VMBUS:

  -obj-$(CONFIG_HYPERV)       += hv_vmbus.o
  +obj-$(CONFIG_HYPERV_VMBUS) += hv_vmbus.o

(upstream 94b04355e639 ("Drivers: hv: Add CONFIG_HYPERV_VMBUS option") and
e3ec97c3abaf ("Drivers: hv: Make CONFIG_HYPERV bool"))

So the `-e CONFIG_HYPERV` added in ef257cb ("config: enable CONFIG_HYPERV")
does not build the VMBus driver into the kernel anymore. CONFIG_HYPERV_VMBUS
does default to HYPERV, but the Ubuntu config sets it to 'm' explicitly and
olddefconfig keeps that. proxmox-kernel-6.17.13-21-pve accordingly still
lists kernel/drivers/hv/hv_vmbus.ko in modules.builtin, while 7.0.2-6-pve
and 7.0.14-25-pve ship it as a module.

That breaks installing Proxmox VE in a Hyper-V Generation 2 VM, where the
storage controller is a VMBus device: VMBus devices only appear in sysfs
once hv_vmbus has been probed. The installer initrd collects the list of
/sys/devices/**/modalias once, before loading the modules discovered
through those aliases. It loads hv_vmbus through the ACPI VMBus node,
but never sees the vmbus: aliases of its children. hv_storvsc therefore
stays unloaded, no /dev/sr0 shows up and the installation aborts with
"no device with valid ISO found". Accordingly the 9.2 ISO fails, while
the 9.1 one with its 6.17 kernel works.

With hv_vmbus built in again, the VMBus children are already enumerated by
the time the initrd runs, so that single modalias scan picks up hv_storvsc
on its own.

Record in the README why it has to be built in rather than modular.

Signed-off-by: 結友 <miagetegorann@gmail.com>
---
 README                            | 5 +++++
 debian/rules.d/config-common.opts | 1 +
 2 files changed, 6 insertions(+)

diff --git a/README b/README
index 00564c8..1a16bbb 100644
--- a/README
+++ b/README
@@ -210,6 +210,11 @@ NOTE: For the exact and current list see debian/rules (PVE_CONFIG_OPTS)
 
 - enable INTEL_MEI_WDT=m (to allow disabling via patch)
 
+- enable CONFIG_HYPERV and CONFIG_HYPERV_VMBUS=y
+  hv_vmbus has to be built in, otherwise VMBus devices are not enumerated in
+  time for the installer initrd's single modalias scan and installing in a
+  Hyper-V Generation 2 VM fails to find its storage controller (#8027)
+
 - disable CONFIG_SND_PCM_OSS (enabled by default in Ubuntu, not needed)
 
 - switch CONFIG_TRANSPARENT_HUGEPAGE to MADVISE from ALWAYS
diff --git a/debian/rules.d/config-common.opts b/debian/rules.d/config-common.opts
index 64505b4..56907e5 100644
--- a/debian/rules.d/config-common.opts
+++ b/debian/rules.d/config-common.opts
@@ -35,6 +35,7 @@
 -e CONFIG_MEMCG_SWAP_ENABLED
 -e CONFIG_MEMCG_V1
 -e CONFIG_HYPERV
+-e CONFIG_HYPERV_VMBUS
 -m CONFIG_VFIO_IOMMU_TYPE1
 -e CONFIG_VFIO_VIRQFD
 -m CONFIG_VFIO
-- 
2.56.0.windows.1




      parent reply	other threads:[~2026-10-24  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-24  5:24 [PATCH pve-kernel v4 0/2] fix #8027: restore built-in Hyper-V VMBus 結友
2026-10-24  5:24 ` [PATCH pve-kernel v4 1/2] d/scripts: correctly compare namespaced ABI exports 結友
2026-10-24  5:24 ` 結友 [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=20261024052438.1274-3-miagetegorann@gmail.com \
    --to=miagetegorann@gmail.com \
    --cc=pve-devel@lists.proxmox.com \
    /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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal