Create Package to install Virutalbox and create VM

[randd0]

What is the best way to create an install package (exe or msi) to install virutalbox and build a VM with specified iso and settings? I didn't know if virtualbox had this type ability built-in, or if there is a third party app that is recommended.

[loukingjr]

Why would anyone want to?

[randd0]

Because I want to automate the process, it makes me happy, it makes my life easier.

[loukingjr]

Okay. VirtualBox has no such feature and there is no third party app I'm aware of.

[scottgus1]

A quick search "Virtualbox silent install site:forums.virtualbox.org" shows posts saying there's a .msi inside the .exe installer, which may be able to be extracted and run silent.

If that still holds true and an "answer file" (I think that's what it's called that tells the installer which button to click in the wizard pages) can be made, then Virtualbox could get put on without user intervention. If that can be done, an install script could run the .msi, then using vboxmanage commands install the extension pack, import a .ova appliance or install a guest in its folder with the .vbox file, and even launch the guest.

[loukingjr]

Lots of ifs.

[randd0]

Thanks scottgus1.. that does sound like a potential solution to my issue. I'll dig into it further.

[scottgus1]

One other thing, Virtualbox has to be installed "Run as Administrator" for Windows hosts, so your script will have to know how to do that, too.

[loukingjr]

One other thing, Virtualbox has to be installed "Run as Administrator" for Windows hosts, so your script will have to know how to do that, too.

I think there are quite a few "things" besides that. For example, if it was for personal use, you would have to install VirtualBox to create this "package" to begin with so why would there be a need for auto-installing VirtualBox?

If it's not for personal use, then if the guest was Windows it would violate Microsoft's EULA. If the guest was OSX of course it would violate Apple's SLA, not to mention no guest additions. Linux could be okay but you would have to make sure any hardware that it was installed on was compatible.

Then you would have to update the package each time there is a new version of VirtualBox.
I'm sure I could think of some others.