Closed flavorjones closed 14 years ago
Hi,
This is because VirtualBox gem only supports VirtualBox 3.1 and higher. I'll add a check soon to detect if you're using a VirtualBox version which isn't supported.
Mitchell
Ah! Thanks for the update. I don't think you need to auto-detect this, just document it. I couldn't find any mention of a minimum-version-requirement in the docs or the repo.
Right, well I think I'm going to throw an UnsupportedVirtualBoxVersion Exception or something along those lines. An additional note is that the OSE version is not supported either.
It needs to be >= 3.1 and not OSE.
Hmmm... I get this same error on Ubuntu and I'm using version 3.2.
$ lsb_release -d
Description: Ubuntu 10.04 LTS
$ gem list | fgrep virtualbox
virtualbox (0.6.1)
$ VBoxManage --version
3.2.0r61806
Bryan
Bryan,
VirtualBox 0.6.1 only supports 3.1 =] The latest git version supports 3.2.
Sorry for the confusion.
Mitchell
I've added VirtualBox.supported?
in the latest version of the gem so hopefully this will help people out. This method will tell you whether or not the installed (or not installed) version of VirtualBox is supported. I plan on integrating this into more parts of the gem as well.
http://github.com/mitchellh/virtualbox/commit/56606f2d6c328cd76010af2217b8ca4150a2e9d9
Hi,
This is probably a question better-suited to a mailing list, but I couldn't find a reference to one, so here I am. :)
Dove in to the codes a bit and I can see that after the call to pfnComInitialize (in FFIInterface#initialize_com) the pointer value of virtualbox_ptr is NULL, which indicates to me that things aren't being initialized properly.
Any ideas?