LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Virtualization and Cloud (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/)
-   -   Mounting a VirtualBox drive image (vdi) without specifying a loop device (https://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/mounting-a-virtualbox-drive-image-vdi-without-specifying-a-loop-device-4175447404/)

frikdt 01-27-2013 06:14 AM

Mounting a VirtualBox drive image (vdi) without specifying a loop device
 
Hi

I'm running VirtualBox on Debian. I use vdfuse to mount my VDI files, running the following commands (showing the sequence for mounting a Windows Server 2008 guest image):

sudo vdfuse -w -g -f <my_image> /mnt/virtualbox/vdfuse

sudo mount -o uid=frikdt,gid=frikdt /mnt/virtualbox/vdfuse/Partition1 /mnt/virtualbox/vdi

I've been using these for a long time now without any problems. However, every discussion/tutorial I've seen so far includes the loop option; so the second command would become:

sudo mount -o loop,uid=frikdt,gid=frikdt /mnt/virtualbox/vdfuse/Partition1 /mnt/virtualbox/vdi

The output of the mount command is the same in both cases (and does not mention any loop device):

/mnt/virtualbox/vdfuse/Partition1 on /mnt/virtualbox/vdi type fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_permissions)

Is there any risk in not specifying the loop option?

jefro 01-28-2013 03:23 PM

I think it is just an issue between a fuse filesystem and a discrete loop mount point.

Fuse has been proven to be pretty good. If you use it and are happy then don't change.

In a way they are both loops but it is how the image is added to the system is my guess.

frikdt 02-03-2013 11:34 AM

Thanks for your reply, jefro.


All times are GMT -5. The time now is 08:12 PM.