[Dropped] vdautomount fails to find the machine

TheSaint · 2015-01-17 06:10:42

Hello,

I'm using virtualbox-bin 4.3.20r96996, so I'd like some time to inspect some file into the VDI. Then I installed vdfuse but, the mounting still awful.
The python2 script vdautomount is not able to find the machine name nor the UUID.
All of these functions are based on the VboxAPI, found in the python2 libraries, but while VBoxManage gets the info, the script is some kind of trouble and even I tried to use some of the classes, then they fail.
Anyways, vdfuse mounts my VDI, but still some missing step to have the access to the file system. I hope that vdautomount will do it for me. Unfortunately I'm scarcely able to get vdautomount work.

Here's the report.
Any point ?

Last edited by TheSaint (2015-01-19 04:52:11)

tomk · 2015-01-17 10:27:34

You should probably contact whoever wrote it.

TheSaint · 2015-01-17 11:54:20

I think it's here. Still since 4 years back.

Muflone · 2015-01-17 11:54:59

@TheSaint
please try to switch to the official community/virtualbox package instead of the aur/virtualbox-bin
(I'm awaiting a response from the maintainer before to proceed to the virtualbox-bin package removal)

Here works fine by using:
mkdir ~/myvmdisk
vdautomount -v "My VM Name" ~/myvmdisk

Last edited by Muflone (2015-01-17 11:56:57)

TheSaint · 2015-01-17 12:05:54

What did you used to get that ? OSE or PUEL ?
I'm using PUEL because I need to use USB devices with particular win program, like Eprom programmer.

Will this means the end of PUEL in AUR ?

Muflone · 2015-01-17 12:14:16

I'm using the official community/virtualbox package and the AUR vdfuse package itself is released to use the official package from the community repository, not the virtualbox-bin (see my last comment on the AUR page).

As far I know there's no more a PUEL version of VirtualBox [1].

VirtualBox source is released under GPL2, while the extension pack is released under the PUEL license.

[1] https://www.virtualbox.org/wiki/Downloads

TheSaint · 2015-01-17 15:08:32

So, as far as I could understand I gave up the AUR package, I just installed from community. I suppose USB will work.
Back to vdautomount, still the same issue. I should say that the VDI are in another partition, but I don't have problems to run them.

Muflone · 2015-01-17 15:13:04

what the issue is?

TheSaint · 2015-01-18 03:29:30

I did:

$ mkdir /tmp/XPvdi

$ sudo vdautomount "xp" /tmp/XPvdi/
Usage: vdautomount [options] machine-name-or-uuid mountpoint

vdautomount: error: couldn't find machine "xp"

$ VBoxManage showvminfo xp |grep -i uuid
UUID:            67ed29f5-7d85-4322-aa6c-2a49110884d4
Hardware UUID:   67ed29f5-7d85-4322-aa6c-2a49110884d4
SATA (0, 0): /mnt/Store/Vboximg/Electron-14-08-11.vdi (UUID: 1f996f93-9f59-4c3c-a9f9-dab62b9c3df0)

$ sudo vdautomount "1f996f93-9f59-4c3c-a9f9-dab62b9c3df0" /tmp/XPvdi/
Usage: vdautomount [options] machine-name-or-uuid mountpoint

vdautomount: error: couldn't find machine "1f996f93-9f59-4c3c-a9f9-dab62b9c3df0"

$ vdfuse -f /mnt/Store/Vboximg/Electron-14-08-11.vdi /tmp/XPvdi/
$ ls -l /tmp/XPvdi/
total 20968141
-rw------- 1 user users 10737418240 17 gen 15.46 EntireDisk
-rw------- 1 user users 10733958144 17 gen 15.46 Partition1

Even I switched to community/virtualbox, deleted all /home related files and reinstall vdfuse, the problem hasn't change anything. The problem isn't the vdautomount script, but is rather the python2 vboxapi toolkit.
Can you show me

 VBoxManage showvminfo "My VM Name"  |grep -i '(uuid'

I don't think is a issue related to the path, the VBoxManage hasn't it.

EDIT
I inspected vdautomount and I found that is just a mere helper to find a named VM and pass the path to vdfuse execution.
My mistake was to expect that the script could find the name VM and mount it in loop, so it is possible to access the files in the partitions.
Beside that, vdautomount doesn't work, I'm giving it up, it fill not my expectations.

Last edited by TheSaint (2015-01-18 06:42:18)

Muflone · 2015-01-18 17:08:27

I'm unsure why your vdautomount is unable to find your VM (it works fine here, with multiple VM, using both names or UUID), but it's not really needed if you know where the disk images are stored.

Like you said, vdautomount is just a mere helper to find the disk images from a VM name.
If your need is to mount a vdi file you can use vdfuse and the partitions in loop to access your files.

Arch Linux

#1 2015-01-17 06:10:42

[Dropped] vdautomount fails to find the machine

#2 2015-01-17 10:27:34

Re: [Dropped] vdautomount fails to find the machine

#3 2015-01-17 11:54:20

Re: [Dropped] vdautomount fails to find the machine

#4 2015-01-17 11:54:59

Re: [Dropped] vdautomount fails to find the machine

#5 2015-01-17 12:05:54

Re: [Dropped] vdautomount fails to find the machine

#6 2015-01-17 12:14:16

Re: [Dropped] vdautomount fails to find the machine

#7 2015-01-17 15:08:32

Re: [Dropped] vdautomount fails to find the machine

#8 2015-01-17 15:13:04

Re: [Dropped] vdautomount fails to find the machine

#9 2015-01-18 03:29:30

Re: [Dropped] vdautomount fails to find the machine

#10 2015-01-18 17:08:27

Re: [Dropped] vdautomount fails to find the machine

Board footer