Package Details: vdfuse 82a-12

Git Clone URL: (read-only, click to copy)
Package Base: vdfuse
Description: A FUSE module for mounting VirtualBox disk images (VDI/VMDK/VHD) on the host
Upstream URL:
Licenses: GPL3
Submitter: tdy
Maintainer: Muflone
Last Packager: Muflone
Votes: 135
Popularity: 0.000633
First Submitted: 2009-10-15 04:51
Last Updated: 2020-02-08 21:54

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

dhaines commented on 2011-03-22 11:22

This isn't building, as the vdautomount download isn't checksumming correctly. The one that is downloaded has an md5 of f7044bcbc724983eb7d8ff60bff4d6e9, while the PKGBUILD thinks it should be 749fb26f511cc759818dc347878f24b0. Time for 82a-2?

tdy commented on 2011-03-19 17:36

well that has to do with the script itself, not a package() issue. i don't write/develop the script.

it looks like the gordstuff files are back, so i've updated to the unofficially fixed/updated version 82a again.

Mektub commented on 2011-03-19 12:17


virtualbox 4.0.4-2
virtualbox-additions 4.0.4-1
virtualbox-ext-oracle 4.0.4-1
vdfuse 82-1

vdfuse -vdf /mbackup/VM/VirtualBox/VDI/ArchVB.vdi /media/vb

Gives: disktype is VDI

ERROR: opening vbox image failed

And this happens with every VDI file I try.

tdy commented on 2011-03-18 17:23

"not working" how? works on all of my machines.

dax commented on 2011-03-18 13:28

there are issue at package(), it's not working

chungy commented on 2011-03-10 02:08

project owner took away everything off of sourceforge

Anonymous comment on 2011-03-01 18:57

v82a out

Anonymous comment on 2011-02-18 21:58

With, for instance, "vdfuse -vdf archvm64.vdi image/"

I'm getting:

disktype is VDI
ERROR: opening vbox image failed

And this happens with every VDI file I try.
Running with -vd gives no clues also.
Any hints?

Anonymous comment on 2011-02-02 22:51

Patched, working PKGBUILD.

schivmeister commented on 2010-12-28 02:30

Error from both both PKGBUILDs:

"Invalid include directory. Make sure that it has the VBox directory inside."

That is because there is no VBox/VBoxHDD.h in the checked out includes. Perhaps the build system changed with vbox 4 and the tool has not been updated upstream.