virtualbox.org

Dear all,

I was trying to enlarge my virtual machine for which I found some easy tutorials (e.g. this one [url=http://www.gubatron.com/blog/2011/08/29 ... ive-on-mac]here[/url]). The command I should use is

$ VboxManage clonehd <path to your original drive> <path of the copy>

However, the bash cannot find the command. I am new to Mac and guess I need to be Within the directory or otherwise have to specify the path in front of the command VboxManage. The funny thing now is that I cannot find the command or the directory. I checked with spotlight which should be able to crawl all folders on my computer. I had a look in ~/library/virtual box, but only lots of VBoxSVC.log-files.

I read suggestions on the web that my installation is broken, but all my VMs are running and I always install the latest updates so it should be all complete.

Any ideas? Thanks so much!

John

ps: I read that only dynamic VMs can be enlarged with that easy command above. Is that correct and how can I find out whether my installation was dynamic?
pps: and why are my URLs never working??

The command is case sensitive, it's VBoxManage. Upper case V, B and M. And to increase the VDI size, it's not clonehd, which creates a file that's exactly the same size, just a different UUID to use in a different VM. The command to use is modifyhd --resize.

The reason that your URLs don't work is because you probably have disabled bbCode support.

Hi. Enjoying virtual box but have some issues with VBoxManage "command not found" error on OSX, not even a simple "VBoxManage showvminfo" command works.
Have drafted a post with more info and no urls but can't post it?? I get a new members can't post urls error.
So here's my 1st post, just gotta wait 24 hours before I can post my full one.
Matt

Why do you feel that you need to post URLs?

Post your question/s and be specific. If you need to provide a file then do so here as an attachment. Compress if it is too large.

Perryg,
Reason being to show you the steps I was taking from a tutorial online. I've just found a solution on a blog comment. Below are my successful terminal commands.

MBP:~ m$ cd /Applications/VirtualBox.app/Contents/MacOS
MBP:MacOS m$ ./VBoxManage modifyhd /Volumes/750/VirtualBox\ VMs/Win7_50/Win7_50-disk1.vdi --resize 50000
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

Note the 2nd line with ./ at the beginning.
Could someone please explain the need for this? Do I need use ./ whenever I use VBoxManage?

Because trying to run the command from the command line in the absolute location can not be done on Mac or Linux. So you need to back up a level and that is where the "./" comes in.
This is not a restriction of VirtualBox though. It is just how the host works.

If you do not want to use the "./" then don't change to the directory to run the command.

Perryg wrote:If you do not want to use the "./" then don't change to the directory to run the command.

Thanks for your help perryg, one last thing please. Why does the following happen then according to what you've outlined in above quote?

MBP:~ m$ VBoxManage showvminfo
-bash: VBoxManage: command not found
and this:
MBP:~ m$ cd /Applications/VirtualBox.app/Contents/MacOS
MBP:MacOS m$ VBoxManage showvminfo
-bash: VBoxManage: command not found

But if I do this I get the result as desired:

MBP:MacOS m$ ./VBoxManage showvminfo
Usage:

VBoxManage showvminfo <uuid|vmname> [--details]
[--machinereadable]
VBoxManage showvminfo <uuid|vmname> --log <idx>

For the exact same reason.

If you want to execute the command while in the directory you need to use "./" or you can just run the command with the absolute location and properties.


/Applications/VirtualBox.app/Contents/MacOS/VBoxManage showvminfo

or ./VBoxManage showvminfo while you are in the directory.

Again this has nothing to do with VirtualBox but is how your host operates. You can add the location to the hosts environmental variables and then you just run the command from anywhere but for this you would need to ask your Mac gurus. Outside the scope of this forum.

Ah yes. I see now. Thankyou very much.