Discuss: Mount any VBox-compatible disk image on the host
Re: Discuss: Mount any VBox-compatible disk image on the host
The "" => "vdi" patch should be part of the file in the main howto page; can you fix that, Terry?
-
- Posts: 13
- Joined: 27. Apr 2009, 11:45
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
Unfortunately I still have no success with this vdfuse program.
Situtation as of today:
Linux Kernel 2.6.30
glibc 2.7
gcc 4.4.1
fuse 2.8.0
Vbox 3.04
The original vdfuse-v50.c from May 2009 kept producing the error message:
fuse: mount failed: Invalid argument
With the patch mentioned a few times here in the forum
- fuse_opt_add_arg (&fuseArgs, "");
+ fuse_opt_add_arg (&fuseArgs, "vdi");
this message disappeared.
Now, when I do
vdfuse -v -g -f /virtwin/Windows2000.vdi /mnt/vdi
I get (only?):
Partition Size Offset
========= ==== ======
Partition1 32256 22002591744
and any process which tries to access the mountpoint /mnt/vdi hangs forever.
Not interruptible, not killable, not even with kill -9
The numbers above look also very strange, the vdi-file has 14GB and contains a single primary NTFS partition with a Windows 2000.
JRO
Situtation as of today:
Linux Kernel 2.6.30
glibc 2.7
gcc 4.4.1
fuse 2.8.0
Vbox 3.04
The original vdfuse-v50.c from May 2009 kept producing the error message:
fuse: mount failed: Invalid argument
With the patch mentioned a few times here in the forum
- fuse_opt_add_arg (&fuseArgs, "");
+ fuse_opt_add_arg (&fuseArgs, "vdi");
this message disappeared.
Now, when I do
vdfuse -v -g -f /virtwin/Windows2000.vdi /mnt/vdi
I get (only?):
Partition Size Offset
========= ==== ======
Partition1 32256 22002591744
and any process which tries to access the mountpoint /mnt/vdi hangs forever.
Not interruptible, not killable, not even with kill -9
The numbers above look also very strange, the vdi-file has 14GB and contains a single primary NTFS partition with a Windows 2000.
JRO
Re: Discuss: Mount any VBox-compatible disk image on the host
Can you provide a backtrace of the program?
-
- Posts: 13
- Joined: 27. Apr 2009, 11:45
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
Hi h2o,
You are the program author of the vdfuse program, right?
An strace of the "other" programs show these usually hang in a "fstat".
Meanwhile I have also figured out how to use some of the example programs in the fuse distribution and they show the same behaviour, so it looks like I have a more general problem on the fuse side of things.
I have found another thread for it in the fuse mailing list, but no solution yet. I have just sent a followup there, let's see if the people there have an idea.
JRO
You are the program author of the vdfuse program, right?
You mean a backtrace of vdfuse after startup?h2o wrote:Can you provide a backtrace of the program?
An strace of the "other" programs show these usually hang in a "fstat".
Meanwhile I have also figured out how to use some of the example programs in the fuse distribution and they show the same behaviour, so it looks like I have a more general problem on the fuse side of things.
I have found another thread for it in the fuse mailing list, but no solution yet. I have just sent a followup there, let's see if the people there have an idea.
JRO
Re: Discuss: Mount any VBox-compatible disk image on the host
Try either:
building a debug version of vdfuse and running it with gdb, or
run strace -f vdfuse
Hopefully that should find the source of the problem.
building a debug version of vdfuse and running it with gdb, or
run strace -f vdfuse
Hopefully that should find the source of the problem.
-
- Posts: 13
- Joined: 27. Apr 2009, 11:45
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
OK, will try both.h2o wrote:Try either:
building a debug version of vdfuse and running it with gdb, or
run strace -f vdfuse
But I have not much time during the week for more experiments, so I think, there will be no interesting results before next weekend.
JRO
-
- Posts: 13
- Joined: 27. Apr 2009, 11:45
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
So now I have a debug and a strace output from vdfuse. But I fear that it will not help much.burghj wrote:OK, will try both.h2o wrote:Try either:
building a debug version of vdfuse and running it with gdb, or
run strace -f vdfuse
But I have not much time during the week for more experiments, so I think, there will be no interesting results before next weekend.
JRO
I think there are still two different issues:
The partition list looks strange as if the vdi file isn't read correctly.
Some deeper confusion happens in the fuse system.
I also got no response to my fuse questions in the fuse maling list.
JRO
- Attachments
-
- strace-out.txt
- (46.53 KiB) Downloaded 34 times
-
- gdb-out.txt
- (1.38 KiB) Downloaded 27 times
-
- Posts: 1
- Joined: 12. Sep 2009, 14:07
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: windows haiku
Re: Discuss: Mount any VBox-compatible disk image on the host
Hi,
I successfully built and user the fusedriver, homewhere, I see no way to deactivate the driver for a specific vdi file ?
If i use vdfuse -f XXX.vdi /mnt/vdi, then i can not cancel this process and need reboot to remove the EntireDisk / Partition1.
Please give me informations on how i could do it thanks.
I successfully built and user the fusedriver, homewhere, I see no way to deactivate the driver for a specific vdi file ?
If i use vdfuse -f XXX.vdi /mnt/vdi, then i can not cancel this process and need reboot to remove the EntireDisk / Partition1.
Please give me informations on how i could do it thanks.
-
- Posts: 1
- Joined: 12. Sep 2009, 16:24
- Primary OS: Ubuntu 8.04
- VBox Version: OSE Fedora
- Guest OSses: Windows 7
Re: Discuss: Mount any VBox-compatible disk image on the host
yes,I can't mount the vdi image.
Re: Discuss: Mount any VBox-compatible disk image on the host
Try "killall vdfuse" or "fusermount -u <mountpoint>" as root.pasnox wrote:Hi,
I successfully built and user the fusedriver, homewhere, I see no way to deactivate the driver for a specific vdi file ?
If i use vdfuse -f XXX.vdi /mnt/vdi, then i can not cancel this process and need reboot to remove the EntireDisk / Partition1.
Please give me informations on how i could do it thanks.
-
- Posts: 13
- Joined: 27. Apr 2009, 11:45
- Primary OS: Linux other
- VBox Version: PUEL
- Guest OSses: Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
Meanwhile my questions on the fuse mailing-list got some attention, albeit no real solution yet.burghj wrote:
I think there are still two different issues:
The partition list looks strange as if the vdi file isn't read correctly.
Some deeper confusion happens in the fuse system.
I also got no response to my fuse questions in the fuse maling list.
JRO
But as a side effect of the tests recommended there, I found out that it has something to do with threading. The fuse hangs happen only in the default multi-threading mode. When I run the fuse code single-threaded everything works ok.
So as a workaround I have added the appropriate parameter (-s) to the internal fuse-mount parameters in vdfuse.c and can now fuse-mount my vdi as expected and everything looks as described. I can loop-mount my partition and see all my files in the virtual disk.
I don't know the real importance of the multi-threaded mode, but for the sole purpose of accessing some files in the virtual disk the single-threaded mode seems sufficient.
JRO
Re: Discuss: Mount any VBox-compatible disk image on the host
I think that the virtualbox disk library might not be thread-safe. We seem to have quite a few inportant patches posted on this forum so far, but none of them are put onto the main vdfuse page.
- use "vdi" instead of an empty string for the mount parameter
- use single threading, there's really no advantage in multi-threading
-
- Posts: 3
- Joined: 6. Apr 2009, 22:01
- Primary OS: Linux other
- VBox Version: OSE other
- Guest OSses: Windows, Linux, BSD
Re: Discuss: Mount any VBox-compatible disk image on the host
This mounts with the patch suggested by jagdpanther on an up-to-date Arch Linux system (kernel 2.6.31), but it seems to be only read-only. The reason I needed this was so I could transfer data faster between the host and guest than one can do wth \\vboxsvr. At this rate, it's going to take more than 2 hours to transfer the extracted whole of several gigabyte 7z archive from a mounted network drive or about the same to extract it within the virtualized OS Itself. I'm hoping that the FUSE'd implementation would be faster than this, but it doesn't seem to mount correctly. I didn't run ./vdfuse with -r and /etc/mtab shows that the thing is mounted rw.
The actual error I get when I try to touch, cp, or rm a file is Operation Not Permitted or Permission Denied, though I am root. Perhaps it's a different problem? chmod doesn't help.
The actual error I get when I try to touch, cp, or rm a file is Operation Not Permitted or Permission Denied, though I am root. Perhaps it's a different problem? chmod doesn't help.
-
- Posts: 4
- Joined: 2. Oct 2009, 23:23
- Primary OS: Ubuntu other
- VBox Version: OSE other
- Guest OSses: Linux, Windows
Re: Discuss: Mount any VBox-compatible disk image on the host
I wasn't able to use this mountig tool:
root@most:/tmp/vdimount# ./vdfuse-v50 -f hdd.vdi /tmp/vdimount/mnt
fuse: mount failed: Invalid argument
root@most:/tmp/vdimount# file hdd.vdi
hdd.vdi: data
root@most:/tmp/vdimount# file /tmp/vdimount/mnt
/tmp/vdimount/mnt: directory
root@most:/tmp/vdimount# ls -a mnt
. ..
root@most:/tmp/vdimount# ./vdfuse-v50 -f hdd.vdi /tmp/vdimount/mnt
fuse: mount failed: Invalid argument
root@most:/tmp/vdimount# file hdd.vdi
hdd.vdi: data
root@most:/tmp/vdimount# file /tmp/vdimount/mnt
/tmp/vdimount/mnt: directory
root@most:/tmp/vdimount# ls -a mnt
. ..
Re: Discuss: Mount any VBox-compatible disk image on the host
We should seriously consider applying the patches to the vdfuse on the main howto page. It hasn't been updated for months, and people who could be successfully accessing their disks cannot unless they look at the discussion topic. If vdfuse is going to be stickied, then it better work.