From: 山﨑結友 <miagetegorann@gmail.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH pve-kernel v4 0/2] fix #8027: restore built-in Hyper-V VMBus
Date: Mon, 9 Nov 2026 10:39:46 -0800 [thread overview]
Message-ID: <CAEP6gkYrtf=0dgK4yY9Wcbs1Zr1mTgprZYFL-oBT1QQY-g=a0w@mail.gmail.com> (raw)
In-Reply-To: <20261024052438.1274-1-miagetegorann@gmail.com>
Gentle ping, can anyone please take a look?
The series still applies cleanly on current master.
Thanks,
結友
On Sat, Oct 24, 2026 02:24 PM, 結友 <miagetegorann@gmail.com> wrote:
> v4 is a transport-only resend of the same two commits.
> Please disregard v1-v3: the Gmail API delivery path rewrote inline
> patch lines or lost attachment data. This version is sent directly
> with git send-email over SMTP. No code or commit-message changes.
> Sorry for the repeated submissions.
>
> This series restores built-in VMBus support for the Proxmox VE installer
> in Hyper-V Generation 2 guests. Linux 6.18 split HYPERV_VMBUS out of
> HYPERV;
> the existing HYPERV=y override therefore no longer makes hv_vmbus built in.
> The installer takes one snapshot of sysfs modalias paths, so the VMBus
> storage children must be enumerated before that snapshot.
>
> Patch 1 fixes the ABI parser first: three namespaced VMBus exports would
> otherwise be reported as missing when moved from hv_vmbus into vmlinux.
> Patch 2 enables HYPERV_VMBUS=y. Config-override cleanup and general build
> validation changes are kept in a separate follow-up series.
>
> Validation of this exact two-commit submission:
> - Generated patches apply with git am --whitespace=error-all, with the
> same resulting tree. Perl syntax and all 12 ABI regression tests pass.
> - Clean complete amd64 make deb succeeds for the fixed and modular
> control builds in Debian trixie with rustc 1.94.1 and pahole 1.30.
> CONFIG_RUST and BTF are enabled. Both have the same existing lintian
> perf-bench man-page warning; no build or lintian errors.
> - Strict fresh-build ABI checks (SKIPABI=0, empty blacklist) preserve all
> 32,726 symbols, CRCs, export types and namespaces. The fixed build has
> only the expected 47 VMBus provider moves into vmlinux.
> - Gen2 A/B test: the fresh modular control reproduces ISO-not-found;
> the fixed ISO auto-discovers storage on three cold boots, completes
> installation, and passes three installed disk-only cold boots.
> /init is unchanged and hv_storvsc is not manually preloaded.
> - The installed image hash matches the build artifact. Storage I/O,
> persistent data across cold boots, SSH/network, ZFS module loading
> and PVE services pass on Gen2 and non-Hyper-V QEMU/KVM.
> - QEMU/KVM also passes complete installation, two installed cold boots
> and installation of the newly built headers and perf packages.
> - Hyper-V Gen1 passes complete BIOS installation, two installed cold
> boots, persistent disk I/O, networking and ZFS module loading.
> - arm64: full native-emulated Debian package build and minimal QEMU
> initramfs boot, virtio ext4 I/O and networking pass.
>
> Validation limits:
> - No arm64 Hyper-V host was available. arm64 QEMU tests do not cover
> Hyper-V on arm64 or a complete Proxmox VE arm64 installation.
> - arm64 QEMU directly boots the verified packaged EFI zboot payload;
> the EFI firmware entry path is not tested. There is no previous arm64
> ABI or firmware baseline in this repository, so those comparisons
> were skipped by the standard build rules.
> - Hyper-V tests used unsigned test kernels with Secure Boot disabled.
>
> Base: current pve-kernel master at 78f3d3e2f3ce28c51b80919bc3fc35
> a399ddb3c7.
> Bug: https://bugzilla.proxmox.com/show_bug.cgi?id=8027
>
> 結友 (2):
> d/scripts: correctly compare namespaced ABI exports
> fix #8027: config: enable CONFIG_HYPERV_VMBUS
>
> .gitignore | 1 +
> README | 13 +++
> debian/rules.d/config-common.opts | 1 +
> debian/scripts/abi-check | 56 +++++++++---
> debian/tests/test_abi_check.py | 140 ++++++++++++++++++++++++++++++
> 5 files changed, 198 insertions(+), 13 deletions(-)
> create mode 100644 debian/tests/test_abi_check.py
>
>
> base-commit: 78f3d3e2f3ce28c51b80919bc3fc35a399ddb3c7
> --
> 2.56.0.windows.1
>
>
prev parent reply other threads:[~2026-11-09 18:40 UTC|newest]
Thread overview: 4+ 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 ` [PATCH pve-kernel v4 2/2] fix #8027: config: enable CONFIG_HYPERV_VMBUS 結友
2026-11-09 18:39 ` 山﨑結友 [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='CAEP6gkYrtf=0dgK4yY9Wcbs1Zr1mTgprZYFL-oBT1QQY-g=a0w@mail.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