It is possibly compatible with the VMware providers as well but I haven't tried yet.

Alas, this seems not to be the case. And the behavior is weird.

I was setting up a multi-vm environment so at first I thought these errors were coming from contention on the shared apt cache dir, but then I realized I can reproduce it with a fresh single machine.

Steps to reproduce

1. Use a simple Vagrantfile something like this
2. Spin up a fresh machine using the official precise64 vmware_fusion box
3. Attempt to install a package (I tried vim-nox)

Expected Behavior

Happiness, sunshine, flowers

Actual Behavior

Package corruption errors left and right!

dpkg-deb (subprocess): data: internal gzip read error: '<fd:4>: invalid block type'
dpkg-deb: error: subprocess <decompress> returned error exit status 2
dpkg: error processing /var/cache/apt/archives/perl_5.14.2-6ubuntu2.3_amd64.deb (--unpack):
 short read on buffer copy for backend dpkg-deb during `./usr/lib/perl/5.14.2/auto/Encode/JP/JP.so'
Preparing to replace perl-base 5.14.2-6ubuntu2.1 (using .../perl-base_5.14.2-6ubuntu2.3_amd64.deb) ...

I'm guessing it has something to do with the way shared folders are implemented in VMWare, but I haven't had a chance to look into it further. I'll follow up here if I figure anything else out.