-
Apparently it only happens if the vdi is not attached to the IDE primary master. If the only vdi is attached to SATA 0 these lines after line 271 should fix it (sorry for the line breaks)
if [ $vdifile=="" ]
then
vdifile=$($vbox_command showvminfo "$name" | grep "SATA 0" | cut -d ":" -f2 | cut -d "(" -f1 | sed -e 's/^[ \t]*//' | sed 's/[ \t]*$//')
fi.
2009-11-26 00:44:38 UTC by boehmi2202
-
When executing "vboxtool backup" the content of the current folder is copied to $backup_folder/VDI/.
The reason is that in line 271 of the script it assigns an empty string to $vdifile and then rsync copies the current directory into $backup_folder/VDI/ instead of the VDI file.
Here's the line of the script. I'm not able to fix it by myself as I'm not a programmer ;-...
2009-11-25 14:49:08 UTC by boehmi2202
-
Without chencking if there is a vrdp-port defined in machines.conf, the configuration command '$vboxcommand modifyvm $uuid -vrdpport $vrdpport_config' is still executed.
As it turns out, VirtualBox translates the empty value into the default 3389; this can also be defined as unwanted behaviour.
2009-11-06 14:57:25 UTC by markbaa
-
"autostart" command now uses VRDP port from machines.conf file, while "start" command uses the port from the vm settings file (or the default 3389). I find this somewhat confusing.
I would like a feature where i can apply the VRDP port from machines.conf when using "start" command. Either as default, or as a switch to the command.
Regards.
2009-11-03 12:21:29 UTC by takilara
-
Ill add a feature request, as i fairly often stop and start vm's after boot.
thanks for a brilliant product btw:)
2009-11-03 12:18:19 UTC by takilara
-
This could be a bug in VBoxTool: without chencking if there is a vrdp-port defined in machines.conf, the configuration command '$vbox_command modifyvm $uuid -vrdpport $vrdp_port_config' is still executed.
As it turns out, VirtualBox translates the empty value into the default 3389; this can also be defined as unwanted behaviour.
But to make this easy: just enter a bug report for VBoxTool...
2009-11-03 11:59:04 UTC by markbaa
-
I would like to auto-start my VM's without a RDP session being created. Not including the port mo. in the machines.conf simply defaults the port to 3389.
2009-11-03 11:33:33 UTC by Nad
-
Yes , this is desired behaviour. I agree, it's a little confusing, so maybe it's better to apply the vrdp-setting also in the start command. If you would like this, you can enter a feature request for this, than I'll sort/work this out.
2009-11-03 09:42:01 UTC by markbaa
-
Not sure if this is a bug or intended behaviour.
"autostart" properly applies VRDP ports from machines.conf file, however the "start" command does not do this, but uses the default 3389 instead.
This is confusing to me, but as mentioned; this might be the desired behaviour to use port from VM config instead of from machines.conf.
2009-11-03 09:34:25 UTC by takilara
-
This is the content of my /etc/vboxtool/mavhines.conf
ns1,VRDP-7771
Proxy,VRDP-7772
this is te contento of my /etc/vboztool/vboxtool.conf
vbox_user='Administrador'
and this is the result of "vboxtool show" command
Proxy: state=powered-off vrdp=3389
ns1: state=powered-off vrdp=
and, my mistake, no machine are started on boot,
and I omitted the > and...
2009-10-07 12:39:14 UTC by madtrek