[PVE-User] Migrating a vmdk from NAS to LVM

Dhaussy Alexandre ADhaussy at voyages-sncf.com
Tue Sep 13 10:35:47 CEST 2016


Le 13/09/2016 à 05:30, Alexandre DERUMIER a écrit :
> ok, this could be a fast workaround to implement
> # qemu-img info -f vmdk /nas/proxmox/testmox2/testmox2.vmdk
>
Yes, i have made a quick workaround that seems to work.
Not sure if it's the way to go..

--- /tmp/Plugin.pm    2016-09-13 10:24:11.665002256 +0200
+++ /usr/share/perl5/PVE/Storage/Plugin.pm    2016-09-13 
10:32:45.384107517 +0200
@@ -625,7 +625,9 @@
      return wantarray ? (0, 'subvol', 0, undef) : 1;
      }

-    my $cmd = ['/usr/bin/qemu-img', 'info', '$filename'];
+    my $cmd = ['/usr/bin/qemu-img', 'info'];
+    push @$cmd, '-f', 'vmdk' if $filename =~ /.vmdk$/;
+    push @$cmd, $filename;

      my $format;
      my $parent;


> Why is the filename in extend : testmox2-flat.vmdk ?
I'm not very skilled on Wmware, but it seems to be the standard.
It may be related to thin/thick provisioning format ?

I found some info here about the format : 
http://www.pocs.nl/pocs/fr/technique/63-linux-pocs/139-vmdk-disk-decscriptors-how-are-they-defined.html?eprivacy=1



More information about the pve-user mailing list