From: Kyle Sexson <ksexson@cobaltcattle.com>
To: Eneko Lacunza <elacunza@binovo.es>,
"pve-user@lists.proxmox.com" <pve-user@lists.proxmox.com>
Subject: RE: Big VMWare disk import experience/recommendation
Date: Wed, 4 Mar 2026 16:18:29 +0000 [thread overview]
Message-ID: <SN6PR17MB25913F7D5136ECF8C5A28179DE7CA@SN6PR17MB2591.namprd17.prod.outlook.com> (raw)
In-Reply-To: <42d1010a-c578-45da-9d26-8de21288ab41@binovo.es>
Have you looked into he 'Minimal Downtime' move option? https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Attach_Disk_&_Move_Disk_(minimal_downtime)
The short description is you have VMWare move the vmdk files to shared storage with PVE and then import the disks from the shared storage. This can avoid the speed limitations with the VMWare API used by the automated process
-----Original Message-----
From: Eneko Lacunza <elacunza@binovo.es>
Sent: Wednesday, March 4, 2026 9:58 AM
To: pve-user@lists.proxmox.com
Subject: Big VMWare disk import experience/recommendation
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hello all,
We are planning a migration of about 65 VMs from a VMWare v8 cluster to PVE. There is a mixture of Debian, Ubuntu and Windows machines there.
We have done that before, but during the last migration a month ago (unrelated customer) we had performance issues importing/converting the disks (WUI wizard). Some of the issues we could fix removing VM snapshots from VMWare, but others (with the biggest disks, about 3,5T) prevailed, even after checking for snapshots (no snapshots present) and trying to flatten the disk image. Those were file servers and we had to fail back to copying disk contents with robocopy, and fippling VMs to minimize downtime; a procedure that has its issues....
In the new migration, we have a pair of VMs with 12TB disks, and one with 35TB. We're afraid to suffer again the disk copy/convert performance issues.
Any recommendation would be much appreciated.
Regards
Eneko Lacunza
Zuzendari teknikoa | Director técnico
Binovo IT Human Project
Tel. +34 943 569 206 | https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fwww.binovo.es&c=E,1,iKIS-qIMU5XaqfA8IIHrkueNLILrXA13jFJNFanqLdRXwGDcg_N1TbhjC8aBjleG6skI4b4qFKxkTdsIobmFu31yftkfHMBvTGFmtYZEJekURXNZ9WH-RpnQlVo,&typo=1
Astigarragako Bidea, 2 - 2º izda. Oficina 10-11, 20180 Oiartzun
https://www.youtube.com/user/CANALBINOVO
https://www.linkedin.com/company/37269706/
next prev parent reply other threads:[~2026-03-04 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 15:57 Eneko Lacunza
2026-03-04 16:18 ` Kyle Sexson [this message]
2026-03-04 16:59 ` Eneko Lacunza
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=SN6PR17MB25913F7D5136ECF8C5A28179DE7CA@SN6PR17MB2591.namprd17.prod.outlook.com \
--to=ksexson@cobaltcattle.com \
--cc=elacunza@binovo.es \
--cc=pve-user@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