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: 136
Popularity: 0.32
First Submitted: 2009-10-15 04:51 (UTC)
Last Updated: 2020-02-08 21:54 (UTC)

Latest Comments

scorici commented on 2019-12-30 19:56 (UTC)

The file from following link worked for me: I only needed to change the first source link with: and the hash is the same.

rustatian commented on 2019-07-02 05:29 (UTC)

Please, replace the broken link with this for example:

Tyomix commented on 2019-04-16 09:51 (UTC) (edited on 2019-04-16 09:53 (UTC) by Tyomix)

curl: (22) The requested URL returned error: 404 Not Found ==> ОШИБКА: Ошибка при загрузке '' Anybody knows correct link?

MagiCarbon commented on 2016-08-24 03:48 (UTC)

i got a .vmdk file created by VMware on windows. i could manage it by adding to VMBOX. but when trying to access it by vdfuse, i got an Error, 'error: -38 (Function not implemented)', triggered by `mount vmdk/Partition1 mnt/`. * output of `mount vmdk/Partition1 mnt/`: ------------------------------------------------------------------ mount: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. * output of `vdfuse -t VMDK -d -v -f /opt/VMs/Disk1.vmdk vmdk/`: ------------------------------------------------------------------ unique: 68, opcode: READ (15), nodeid: 3, insize: 80, pid: 22511 read[0] 8192 bytes from 53686947840 flags: 0x8002 read: /Partition1, offset=53686947840, length=8192 read[0] 8192 bytes from 53686947840 unique: 68, success, outsize: 8208 unique: 69, opcode: READ (15), nodeid: 3, insize: 80, pid: 22511 read[0] 94208 bytes from 53686964224 flags: 0x8002 read: /Partition1, offset=53686964224, length=94208 read[0] 94208 bytes from 53686964224 unique: 69, success, outsize: 94224 unique: 70, opcode: READ (15), nodeid: 3, insize: 80, pid: 22511 read[0] 16384 bytes from 53687062528 flags: 0x8002 read: /Partition1, offset=53687062528, length=16384 read[0] 16384 bytes from 53687062528 unique: 70, success, outsize: 16400 unique: 71, opcode: READ (15), nodeid: 3, insize: 80, pid: 22511 read[0] 4096 bytes from 2097152 flags: 0x8002 read: /Partition1, offset=2097152, length=4096 read[0] 4096 bytes from 2097152 unique: 71, success, outsize: 4112 unique: 72, opcode: FSYNC (20), nodeid: 3, insize: 56, pid: 22511 unique: 72, error: -38 (Function not implemented), outsize: 16 unique: 73, opcode: RELEASE (18), nodeid: 3, insize: 64, pid: 0 release[0] flags: 0x8002 release: /Partition1 Partition Size Offset ========= ==== ====== Partition1 512 53687090688 unique: 73, success, outsize: 16

Grandma commented on 2016-04-21 16:06 (UTC)

And checksum for virtualbox_4.1.42-dfsg-1+deb7u1.debian.tar.xz is: 54af4a721b6534de5f23f86e6d644d3e5b03383f2d1d90f4dbfeff84bbed47e9

wzyboy commented on 2016-04-14 04:27 (UTC)

Source file returns HTTP 404. Updated to and build passed.

Muflone commented on 2015-09-20 13:33 (UTC)

Package updated

lilydjwg commented on 2015-09-14 08:24 (UTC)

The debian URL returns 404.

Muflone commented on 2015-01-17 10:52 (UTC)

@TheSaint that's an issue with the virtualbox-bin package that installs into /opt instead of /usr.

TheSaint commented on 2015-01-17 03:28 (UTC)

Error in compiling gcc: error: /usr/lib/virtualbox/ No such file or directory Wrong path for virtualbox-bin 4.3.20r96996 I changed to /opt/VirtualBox/ instead of /usr/lib/virtualbox/ (case sensitive), in the build() function.

Muflone commented on 2015-01-02 18:26 (UTC)

@intelfx package updated, thank you for your fixes

intelfx commented on 2014-12-31 17:05 (UTC)

Disregard the previous link, it has tabs and spaces mixed. Properly modified one:

intelfx commented on 2014-12-31 17:00 (UTC)

Hi! The package currently doesn't build due to bad arguments to gcc. I've fixed the issue and cleaned PKGBUILD (source modification goes to prepare(), cd "$srcdir" may be omitted, and so on). Here it is:

jose1711 commented on 2014-12-29 11:27 (UTC)

for some reason i had to create symlinks in /usr/lib/virtualbox: sudo ln -s sudo ln -s and modify build(): -L/usr/lib/virtualbox \ -lVBoxDD \ -lVBoxDDU \ maybe it's just my setup, who knows

Muflone commented on 2014-05-10 15:17 (UTC)

@jamesan looking at the debian changelog no changes were made to the interesting files for vdfuse. However I've updated the package to reflect the latest available debian package.

jamesan commented on 2014-05-07 12:44 (UTC)

The revision number for the VirtualBox Debian source package has moved up from deb7u1 to deb7u3, with a corresponding MD5 checksum of: 1615e64dc1802a8fe3807da238f0d247. Both vdfuse and vdautomount seem to be working fine with the update.

thebodzio commented on 2013-10-15 11:50 (UTC)

There's a problem with SSL certificate during download (given HTTP address redirects to the HTTPS version).

Muflone commented on 2013-07-09 11:39 (UTC)

Finally dropped the Gordon Miller source code. My Github repository virtualbox-includes contains only snapshots from VirtualBox SVN trunk source repository, not any single line of code was changed. Patching is done only in AUR using the attached patches.

Muflone commented on 2013-07-09 10:57 (UTC)

Package adopted! Not using anymore the Gordon Miller source code as stated in Temporarily I'm using the VirtualBox include headers from Gordon Miller while patching the original code. Very soon the Gordon Miller source code will be dropped. Actually I'm using the virtualbox-fuse source code from Debian repository, which recently has been dropped from official repositories. I'll try my best at let include it again because I think I can fix it.

someoneelse123 commented on 2013-03-23 12:23 (UTC)

virtualbox-sdk package is needed by vdautomount script.

teekay commented on 2012-09-24 10:14 (UTC)

@laloch: See - don't use his xspect3d/gordstuff/vdfuse-v82a.tgz, use the debian one instead.

teekay commented on 2012-09-14 21:28 (UTC)

I needed this, so here's the update. * Use debian maintained version - it's the sane one * Compile using upstream headers matching debian's version I didn't test vdautomount.

commented on 2012-03-19 03:28 (UTC)

makepkg breaks with the following errors: ==> Starting build()... vdfuse-v82a.c: In function ‘detectDiskType’: vdfuse-v82a.c:518:7: warning: ignoring return value of ‘read’, declared with attribute warn_unused_result [-Wunused-result] /usr/bin/ld: /tmp/cc0pWkfJ.o: undefined reference to symbol 'VDWrite' /usr/bin/ld: note: 'VDWrite' is defined in DSO /usr/lib/virtualbox/ so try adding it to the linker command line /usr/lib/virtualbox/ could not read symbols: Invalid operation collect2: ld returned 1 exit status strip: 'vdfuse-v82a': No such file Compile Failed! ==> Starting package()... install: cannot stat `vdfuse-v82a': No such file or directory ==> ERROR: A failure occurred in package().

Shanto commented on 2011-12-07 09:45 (UTC)

vdautomount no longer works with current VirtualBox.

Shanto commented on 2011-11-07 15:14 (UTC)

@tdy: I think virtualbox-sdk should be added to depends, for the vbox Python modules utilized by this program.

jackoneill commented on 2011-07-17 13:06 (UTC)

Uhh, sorry, the previous message is not targeted specifically at the maintainer of this package, but at everyone (ambiguous "you" ftl).

jackoneill commented on 2011-07-17 12:58 (UTC)

Ohai there. The owner of would appreciate it if you stopped sending him bugreports and expecting fixes — apparently he just fixed someone else's code at one time. Anyway, you're more than welcome to fork this (hint hint). The tarball may or may not remain available. (He doesn't have an account here, so I'm relaying the message instead.)

tdy commented on 2011-04-01 16:40 (UTC)

thanks, 'force' was deprecated for 'epoch' in pacman 3.5

dhaines commented on 2011-03-31 11:35 (UTC)

The PKGBUILD is causing makepkg to throw an error: "options array contains unknown option 'force'". Also, I see that the md5 that I mentioned was added, but that pkgrel was not incremented. Shouldn't that be the case?

dhaines commented on 2011-03-22 11:22 (UTC)

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 (UTC)

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 (UTC)

Running 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 (UTC)

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

dax commented on 2011-03-18 13:28 (UTC)

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

chungy commented on 2011-03-10 02:08 (UTC)

project owner took away everything off of sourceforge

commented on 2011-03-01 18:57 (UTC)

v82a out

commented on 2011-02-18 21:58 (UTC)

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?

commented on 2011-02-02 22:51 (UTC)

Patched, working PKGBUILD.

schivmeister commented on 2010-12-28 02:30 (UTC)

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.

x33a commented on 2010-11-26 07:16 (UTC)

Hello guys, a fellow arch user is having problem with vdautomount complaining about not finding VBoxPython module. Here's the thread:

Dieter_be commented on 2010-10-19 12:02 (UTC)

the current pkgbuild is broken (checksum failures on source files), the one given by kolebas works. i had a brief look at the source files and none of them seems to install rootkits or delete home directories ;) so +1 on kolebas' pkgbuild.

commented on 2010-09-30 08:43 (UTC)

change please PKGBUILD

commented on 2010-08-02 14:21 (UTC)

update the package url to this: on that page you can see the correct download urls for the script and the source code...

tdy commented on 2010-07-05 03:42 (UTC)