Skip to content

Fix virtio-win install steps for EL hosts - #657

Merged
andrijapanicsb merged 9 commits into
4.22from
andrijapanicsb/fix-virtio-win-el-install
Aug 6, 2026
Merged

Fix virtio-win install steps for EL hosts#657
andrijapanicsb merged 9 commits into
4.22from
andrijapanicsb/fix-virtio-win-el-install

Conversation

@andrijapanicsb

@andrijapanicsb andrijapanicsb commented May 26, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace the EL repo-based yum install virtio-win guidance with direct installation of the Fedora-provided virtio-win.noarch.rpm.
  • Add verification commands tested on Oracle Linux 8 and 9 KVM hosts.
  • Clarify that /usr/share/virtio-win is the virt-v2v driver search path and simplify the Debian RPM conversion workaround.
  • Added hints from where to download VDDK libraries and recommended versions
  • Instructions to create a missing link /usr/share/virt-tools/rhsrvany.exe
  • Warn that distribution virtio-win packages can be too old to contain drivers for recent Windows releases (e.g. EL9's 1.9.40 has none for Windows Server 2025, so virt-v2v converts the guest without a virtio storage driver and the imported VM cannot boot); document overwriting the ISO with the latest upstream build.
  • Document the Windows Server 2025 first-boot reboot loop caused by the rejected smbus driver signature (virtio-win 0.1.285) and its workaround (remove the non-essential smbus.inf/smbus.cat from the driver set before conversion).

Related to #640.


📚 Documentation preview 📚: https://cloudstack-documentation--657.org.readthedocs.build/en/657/

@andrijapanicsb

Copy link
Copy Markdown
Contributor Author

Pls make sure this is reviewed and merged for 4.22.x - since "yum install virtio-win" will not work at all.

@andrijapanicsb
andrijapanicsb force-pushed the andrijapanicsb/fix-virtio-win-el-install branch 3 times, most recently from ea5d826 to 41be3ba Compare May 26, 2026 09:45
andrijapanicsb and others added 4 commits May 26, 2026 11:45
Clarify installation instructions for virt-v2v and virtio drivers, including logging and error handling for Windows VMs.
Updated the instructions for importing VMware VMs into KVM, including recommendations for virt-v2v versions and installation steps for required tools.
@andrijapanicsb

Copy link
Copy Markdown
Contributor Author

@sureshanaparti please make sure this is merged as part of the official release docs, since some instructions were wrong (virtio-win installation on EL hosts). And there is also a clarification on the needed VDDK library versions, for stability etc (everything tested last few days by me)

… 2025 smbus driver issue

The Enterprise Linux distribution virtio-win packages can be old enough
to contain no drivers for recent Windows releases, in which case
virt-v2v converts the guest without a virtio storage driver and the
imported VM cannot boot. Document overwriting the ISO with the latest
upstream build, and document the Windows Server 2025 first-boot reboot
loop caused by the rejected smbus driver signature, with its
workaround.
… ISO

The previous note said to remove the driver from the driver set without
explaining that virt-v2v reads it from the ISO itself, which cannot be
edited in place. Document the full extract, delete and rebuild sequence
with xorriso; verified on an EL9 conversion host against virtio-win
0.1.285.
… on auto-detection

Auto-detection of the VDDK directory can pick up the wrong libraries on
real hosts - leftovers from container images, a second VDDK
installation, or a partially extracted tree - and the resulting
conversion failures are hard to trace to the wrong library path. The
text presented the property as an option for non-standard locations;
it is now the recommended default, with auto-detection described as a
fallback only. This also completes a sentence that was previously cut
off mid-reference.
…and newer only

Older Windows releases accept the driver's signature and work with the
unmodified upstream ISO; make that explicit so operators do not rebuild
the ISO unnecessarily.
@andrijapanicsb
andrijapanicsb merged commit 0f36f5f into 4.22 Aug 6, 2026
1 check passed
@andrijapanicsb

Copy link
Copy Markdown
Contributor Author

@codex please review, because it seems nobody gives a...damn about actually help users with proper docs.... this is all filed-tested/sourced data (most of it)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants