38 lines
1.3 KiB
Markdown
38 lines
1.3 KiB
Markdown
# Migrating a Windows Server 2025 VM from VMware ESXi to Proxmox VE
|
|
|
|
This guide describes the most reliable and direct way to migrate a Windows Server 2025 virtual machine
|
|
from **VMware ESXi** to **Proxmox VE**, using `virt-v2v`.
|
|
It also covers driver preparation and alternative manual import steps.
|
|
|
|
---
|
|
|
|
## 🧭 Overview
|
|
|
|
| Method | How it works | Pros | Cons |
|
|
|--------|---------------|------|------|
|
|
| **virt-v2v (recommended)** | Converts directly from ESXi to Proxmox | Keeps partitions, converts drivers | Requires CLI |
|
|
| **VMDK import** | Export disk → `qm importdisk` | Simple | Manual driver fix |
|
|
| **Veeam restore** | Restore backup | Handy for existing policy | Often fails to boot |
|
|
|
|
---
|
|
|
|
## ✅ Prerequisites
|
|
|
|
- Both **ESXi** and **Proxmox VE** hosts reachable on the same network.
|
|
- Proxmox host has sufficient storage and CPU.
|
|
- Administrative credentials for ESXi (usually `root`).
|
|
- `virtio-win.iso` downloaded and stored in `/var/lib/vz/template/iso/`.
|
|
|
|
---
|
|
|
|
## 🔧 1. Prepare Windows VM on ESXi
|
|
|
|
Before migrating, pre-install VirtIO drivers inside the Windows VM to ensure it boots in Proxmox.
|
|
|
|
Run this PowerShell script inside the VM (as Administrator):
|
|
|
|
```powershell
|
|
Set-ExecutionPolicy Bypass -Scope Process -Force
|
|
irm https://git.voskuil.cloud/marco/scripts/raw/branch/main/Prep-VirtIODrivers.ps1 | iex
|
|
|