docs(pvm-deploy): add OpenCloudOS 9 yum one-click install shortcut

[caoqianyun]

What

Adds a "Quick path for OpenCloudOS 9 users" callout to the PVM deployment guide,
linking to the OpenCloudOS WeChat article that walks through the 5-command
deployment flow.

Why

The OpenCloudOS extras repo now ships kernel-6.6.69-1.1.cubesandbox.oc9 and
related kernel packages. OpenCloudOS 9 users can dnf install directly and
skip the legacy flow of "download release → rpm -ivh → grubby --info=ALL to
find the index". Surfacing this shortcut at the top of the PVM doc noticeably
improves the first-run experience for the (officially recommended)
OpenCloudOS 9 audience.

Verified

• End-to-end run of the 5-command flow on a clean OpenCloudOS 9.4 CVM
• dnf install resolves dependencies automatically (kernel-core /
  kernel-modules pulled in together)
• Cube one-click installer completes with CUBE_PVM_ENABLE=1,
  /dev/kvm available, and the kvm_pvm module loaded successfullyid deployment on OpenCloudOS 9

[github-actions]

Claude finished @caoqianyun's task in 2m 27s —— View job

---

PR Review: docs(pvm-deploy): add OpenCloudOS 9 yum one-click install shortcut

• Read repo guidelines (CLAUDE.md)
• Read the changed file and diff
• Check DCO (Signed-off-by) on commits
• Provide detailed review feedback

---

DCO Check: Missing Signed-off-by

The commit da7b4e8 ("Update pvm-deploy.md") does not contain a Signed-off-by: trailer, which is required by the Developer Certificate of Origin. Please amend with:

git commit --amend -s
git push --force

---

Review Feedback

The change is clean and well-placed — the callout sits right after the OpenCloudOS 9 recommendation, which is the most natural entry point for readers who would benefit from the shortcut. A few items to consider:

1. English doc not updated (consistency)

The English version at docs/guide/pvm-deploy.md:43 has the same OpenCloudOS 9 recommendation paragraph but lacks the corresponding callout. This creates a divergence between the two language versions. Consider adding an equivalent callout there as well, or noting in the PR that a follow-up is planned.

2. Minor spacing inconsistency

In the callout at docs/zh/guide/pvm-deploy.md:46:

无需手动下载 rpm， dnf install

There's a space after the Chinese comma ， before dnf install. The rest of the document doesn't use this pattern (e.g., line 43: "可获得最佳兼容性，且无需"). Either remove the extra space for consistency, or apply it uniformly — but pick one.

3. External link durability

The callout links to a WeChat article (mp.weixin.qq.com). WeChat article URLs can be fragile (they may break if the article is edited, unlisted, or the platform changes URL schemes). Not a blocker for a docs-only PR, but worth being aware of — if this link rots, users will hit a dead end at the top of the deployment guide.

4. "yum 仓库" vs "dnf install"

The callout says "已上架 OpenCloudOS 官方 yum 仓库" but then says "dnf install 一行命令可实现直装". On OpenCloudOS 9, dnf is the package manager and yum is just a compatibility symlink. This is a minor terminology mismatch — the repo is commonly called a "yum repo" colloquially, so it's acceptable as-is, but you could use "dnf/yum 仓库" or just "软件仓库" for precision.

---

Summary

The change itself is low-risk and improves the first-run experience for OpenCloudOS 9 users. The blocking issue is the missing Signed-off-by trailer. The English doc consistency is the most impactful non-blocking item to address.

[github-actions]

Minor spacing inconsistency: there's a space after the Chinese comma ， before dnf install, but the rest of the document doesn't use this pattern (e.g., line 43: "可获得最佳兼容性，且无需"). Consider removing the extra space for consistency.

Also note: "yum 仓库" vs "dnf install" — on OpenCloudOS 9, dnf is the package manager. The repo is commonly called a "yum repo" colloquially so this is acceptable, but you could use "dnf/yum 仓库" or just "软件仓库" for precision.