virtualbox
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
virtualbox [2010/01/20 08:18] – 172.26.0.166 | virtualbox [2011/06/03 12:52] – aorth | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== VirtualBox ===== | + | ====== VirtualBox |
- | VirtualBox is a free/opensource Hypervisor | + | VirtualBox is a free, open-source hypervisor |
* [[http:// | * [[http:// | ||
+ | * [[http:// | ||
- | ===== Create a VM ===== | + | ====== |
- | Copy an ISO to your home directory: | + | ===== Bridged Networking |
- | < | + | |
- | * SSH to VM server: 172.26.0.200 | + | |
- | < | + | |
- | * start the virtualbox application | + | |
- | < | + | |
- | * Follow the wizard to create a VM with the following properties: | + | |
- | - Base Memory: less than 512 MB | + | |
- | - Network : NAT | + | |
- | - Hard disk size: less than 30Gb | + | |
- | + | ||
- | ===== Networking ===== | + | |
- | ==== Bridged Networking ==== | + | |
If your guest is using bridged networking you MUST use this command to allow other users to use the host's physical network card. Make sure your virtual machine is shut down and then run this command: | If your guest is using bridged networking you MUST use this command to allow other users to use the host's physical network card. Make sure your virtual machine is shut down and then run this command: | ||
< | < | ||
Line 24: | Line 13: | ||
As of VirtualBox 3.1.2 this is still a [[http:// | As of VirtualBox 3.1.2 this is still a [[http:// | ||
- | ==== Port Forwarding ==== | + | ===== Port Forwarding |
If your guest OS is using NAT for networking and you want to access services like Apache or SSH, you will need to enable port forwarding. | If your guest OS is using NAT for networking and you want to access services like Apache or SSH, you will need to enable port forwarding. | ||
Line 33: | Line 22: | ||
< | < | ||
- | ==== Updating VirtualBox ==== | + | ====== Commonly-used commands ====== |
- | To update VirtualBox to a new version you must shutdown all the running VMs. You can do this by first looking to see which VMs are running ('' | + | ===== List your VMs ===== |
- | <file>[jmagochi@biovbox ~]$ VBoxManage controlvm CentOS savestate | + | < |
- | VirtualBox Command Line Management Interface Version | + | ===== List your running VMs ===== |
- | (C) 2005-2009 Sun Microsystems, | + | < |
- | All rights reserved. | + | |
+ | ====== Updating VirtualBox | ||
+ | === Stop any running VMs === | ||
+ | Either shut down or " | ||
+ | <code># ps aux | grep -i VBoxHeadless | ||
+ | jmagochi | ||
+ | jmagochi | ||
+ | aorth 18431 9.7 1.7 998940 36160 ? Sl Oct11 129:54 / | ||
+ | As the user who owns the VM, save the VM's state: | ||
- | 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% | + | < |
- | [jmagochi@biovbox ~]$ sudo /etc/init.d/vboxdrv stop | + | $ VBoxManage controlvm nobu savestate |
+ | $ VBoxManage controlvm lims savestate | ||
+ | $ exit | ||
+ | # su - aorth | ||
+ | $ VBoxManage controlvm b0237553-9653-4461-bd0e-d4d316c16d4f savestate | ||
+ | $ exit</ | ||
+ | === Update VirtualBox === | ||
+ | < | ||
+ | === Resume VMs === | ||
+ | < | ||
+ | $ VBoxHeadless -s nobu & | ||
+ | $ VBoxHeadless -s lims & | ||
+ | $ exit | ||
+ | # su - aorth | ||
+ | $ VBoxHeadless -s b0237553-9653-4461-bd0e-d4d316c16d4f -v off &</code> | ||
- | $ yum install virtualbox-3.1 | + | ====== Optimal settings for Linux guests ====== |
- | </ | + | |
- | ==== Commonly-used commands ==== | + | * Set the IO scheduler to '' |
- | List your VMs: | + | * Edit the grub command line to set the default IO scheduler, usually in /// |
- | < | + | * Install guest additions (VirtualBox or VMware) |
- | List all running VMs: | + | * Run a virtual machine-specific kernel: |
- | < | + | * Ubuntu: linux-image-virtual |
+ | * Mount filesystems with '' |