Difference between revisions of "VirtualBox"
(notes about getting it) |
(updates for 2018) |
||
| Line 1: | Line 1: | ||
| + | {{highlight|text=This page needs an update. The introduction is all new.}} | ||
| + | |||
| + | First of all, if you're going to use VirtualBox with Ubuntu, and either dual-boot, or even if Ubuntu is the only thing on your machine, you will probably need to deal with EUFI Secure Boot. For example, if you have a Hewlett Packard system, you'll find instructions [https://support.hp.com/in-en/document/c04784866 here] for enabling and disabling Secure Boot. (hint; hit <kbd>F10</kbd> at POST). While you're in your system setup (aka "BIOS" although it's not BIOS anymore) make sure you enable [[wp:X86_virtualization#Intel_virtualization_(VT-x)|VT-x]] / VT-d | ||
| + | |||
| + | * https://era86.github.io/2018/01/24/vagrant-virtualbox-secureboot-in-ubuntu-1604.html | ||
| + | * https://askubuntu.com/questions/914997/install-virtualbox-while-keeping-secure-boot | ||
| + | * https://stegard.net/2016/10/virtualbox-secure-boot-ubuntu-fail/ | ||
| + | * Assuming you disable secure boot due to a package installation, even when you re-enable secure boot in your system configuration, you may still see [https://askubuntu.com/questions/726052/ubuntu-booting-in-insecure-mode-with-secureboot-enabled “Booting in insecure mode” with SecureBoot enabled] | ||
| + | |||
| + | |||
| + | The packaged version of VirtualBox on Ubuntu 17.10 is older than the upstream (like normal) so you should just add the ppa for Oracle. | ||
| + | |||
== VirtualBox == | == VirtualBox == | ||
| Line 56: | Line 68: | ||
== Other Projects using VirtualBox == | == Other Projects using VirtualBox == | ||
See [[Drupal/virtualization]] | See [[Drupal/virtualization]] | ||
| − | |||
[[Category:Virtualization]] | [[Category:Virtualization]] | ||
[[Category:Development]] | [[Category:Development]] | ||
[[Category:DevOps]] | [[Category:DevOps]] | ||
Revision as of 21:12, 3 May 2018
First of all, if you're going to use VirtualBox with Ubuntu, and either dual-boot, or even if Ubuntu is the only thing on your machine, you will probably need to deal with EUFI Secure Boot. For example, if you have a Hewlett Packard system, you'll find instructions here for enabling and disabling Secure Boot. (hint; hit F10 at POST). While you're in your system setup (aka "BIOS" although it's not BIOS anymore) make sure you enable VT-x / VT-d
- https://era86.github.io/2018/01/24/vagrant-virtualbox-secureboot-in-ubuntu-1604.html
- https://askubuntu.com/questions/914997/install-virtualbox-while-keeping-secure-boot
- https://stegard.net/2016/10/virtualbox-secure-boot-ubuntu-fail/
- Assuming you disable secure boot due to a package installation, even when you re-enable secure boot in your system configuration, you may still see “Booting in insecure mode” with SecureBoot enabled
The packaged version of VirtualBox on Ubuntu 17.10 is older than the upstream (like normal) so you should just add the ppa for Oracle.
Contents
VirtualBox[edit | edit source]
"VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL)."
Getting it[edit | edit source]
# prep
# Stop any virtual machines
vagrant halt qualitybox
cd ~/Downloads
wget http://download.virtualbox.org/virtualbox/5.0.26/virtualbox-5.0_5.0.26-108824-Ubuntu-trusty_i386.deb
sudo dpkg -i ~/Downloads/virtualbox-5.0_5.0.26-108824-Ubuntu-trusty_i386.deb
If you get a 'conflict with virtualbox' error, remove the existing package and re-try the previous install command
sudo dpkg --remove virtualbox-4.3
You may also need to upgrade vagrant E.g. VirtualBox GUI runs fine, but 'vagrant up' does not. This happened to me when my installed version of vagrant 1.7.1 only supported VirtualBox <= 4.3. Upgrading to vagrant 1.8.5 added support for VirtualBox 5.x
sudo dpkg -i /home/greg/Downloads/vagrant_1.8.5_i686.deb
VBoxManage[edit | edit source]
Besides the GUI interface for VirtualBox, you can manage your VirtualBox machines with the VBoxManage command line tool
Important Settings[edit | edit source]
Be sure to enable PAE/NX in the System -> Processor tab for your Ubuntu guests
Vagrant[edit | edit source]
"Vagrant is a tool for building and distributing virtualized development environments. By providing automated creation and provisioning of virtual machines using Oracle's VirtualBox (ed.: as well as other virtualization engines), Vagrant provides the tools to create and configure lightweight, reproducible, and portable virtual environments."
The MediaWiki project uses vagrant and provides instructions as well as the configuration itself so that you can setup a development instance in a snap. See MediaWiki-Vagrant
[edit | edit source]
Configuring shared folders in virtualbox for Quickstart development
- Power down the Quickstart virtual machine.
- On the host computer, start the Virtualbox management UI.
- right-click Quickstart -> settings -> shared folders -> click the folder with the green plus on the right
- Set the "Folder Path" to a path on the host computer. Give full read/write access.
- Set the "Folder Name" to "shared". no caps. no vbox-
- Ok -> Ok -> start Quickstart vm and this file should disappear.
- Test by moving a file in the host computer into the host shared folder.
Learn more about VDI - Virtual Disk Images http://forums.virtualbox.org/viewtopic.php?t=8046
