Enforcing import of .vmdk (on zfs) without converting to zvol

fcorbelli

New Member
Feb 6, 2023
24
1
3
Italy
github.com
I am trying to import a .vmdk file (ESXi-derived) on a proxmox server which is 'all' zfs.
Basically, I want to keep the file in .vmdk format, and not turn it into a zvol (this is because it's much easier to "bring it back" to ESXi when needed)

Just to be sure, an empty VM
Code:
qm create 503 --name ripristinato

First try:
Code:
root@pve:/rpool/data# qm importdisk 503 /rpool/data/pippo.vmdk local --format vmdk
storage local does not support vm images

Second:
Code:
qm importdisk 503 /rpool/data/pippo.vmdk local-zfs --format vmdk
getting a zvol (on /rpool/data)

Not the best choice (for performance), but just a small mail server, convenience is definitely more important than speed

Perhaps there is some switch to be added, to retain the .vmdk file format?
 
Storages of type "ZFSPool" like "local-zfs" can only store virtual disks as zvols. If you want to store files like vmdk, you need to use a storage of type "Directory" like "local".
 
  • Like
Reactions: leesteken
Storages of type "ZFSPool" like "local-zfs" can only store virtual disks as zvols. If you want to store files like vmdk, you need to use a storage of type "Directory" like "local".
True, but (or at least I think so) need to enable
"disk image" (in content) dropdown, if not already present
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!