From: 結友 <miagetegorann@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH pve-kernel v5 0/2] fix #8027: restore built-in Hyper-V VMBus
Date: Tue, 17 Nov 2026 08:49:51 +0900 [thread overview]
Message-ID: <20261116234953.1476-1-miagetegorann@gmail.com> (raw)
This series restores built-in VMBus support, which the Proxmox VE
installer needs to find its storage in Hyper-V Generation 2 guests.
Linux 6.18 split HYPERV_VMBUS out of HYPERV, so the existing HYPERV=y
override no longer makes hv_vmbus built in.
Patch 1 fixes the ABI check first, as it would otherwise report three
namespaced VMBus exports as missing once they move into vmlinux.
Patch 2 enables HYPERV_VMBUS=y.
Changes since v4 [0], thanks @Thomas for the review:
- 1/2: drop the Python tests, together with their README and
.gitignore bits. They were not run by the build, so they would not
have noticed the generated format changing.
- 1/2: no change to abi-check itself. It already aborts on entries
matching neither layout and on duplicate symbols, for the actual
generated file on every build; spell that out in the commit message
and README.
- 1/2: mention in the commit message that the old parsing also missed
EXPORT_SYMBOL -> EXPORT_SYMBOL_GPL changes of namespaced exports.
- 2/2: unchanged.
- rebased on current master (7.0.14-29), no conflicts.
The amd64 package builds and the Hyper-V Gen1/Gen2 and QEMU/KVM
installation tests listed in the v4 cover letter were done with v4 on
7.0.14-26 and not repeated, as config-common.opts and abi-check are
identical to v4. For v5 I re-ran abi-check against
abi-prev-7.0.14-29-pve-amd64, see patch 1.
[0]: https://lore.proxmox.com/pve-devel/aa154653-9aa2-4554-be6a-d14253e34237@proxmox.com/
結友 (2):
d/scripts: correctly compare namespaced ABI exports
fix #8027: config: enable CONFIG_HYPERV_VMBUS
README | 12 +++++++
debian/rules.d/config-common.opts | 1 +
debian/scripts/abi-check | 56 ++++++++++++++++++++++++-------
3 files changed, 56 insertions(+), 13 deletions(-)
base-commit: 6e8323667a9635eede4b84cb71d1c9d5de04946e
--
2.56.0.windows.4
next reply other threads:[~2026-11-16 23:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-16 23:49 結友 [this message]
2026-11-16 23:49 ` [PATCH pve-kernel v5 1/2] d/scripts: correctly compare namespaced ABI exports 結友
2026-11-16 23:49 ` [PATCH pve-kernel v5 2/2] fix #8027: config: enable CONFIG_HYPERV_VMBUS 結友
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=20261116234953.1476-1-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