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/02/17 09:19] – 172.26.0.166 | virtualbox [2011/06/03 12:51] – [Optimal settings for a guest] aorth | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== VirtualBox ===== | + | ====== VirtualBox |
| - | VirtualBox is a free/opensource Hypervisor | + | VirtualBox is a free, open-source hypervisor |
| * [[http:// | * [[http:// | ||
| - | ===== Create a VM ===== | + | * [[http:// |
| + | ====== Create a VM ====== | ||
| Copy an ISO to your home directory: | Copy an ISO to your home directory: | ||
| - | < | + | < |
| * SSH to VM server: 172.26.0.200 | * SSH to VM server: 172.26.0.200 | ||
| < | < | ||
| Line 15: | Line 16: | ||
| - Hard disk size: less than 30Gb | - Hard disk size: less than 30Gb | ||
| - | ===== Networking ===== | + | ====== Networking |
| - | ==== Bridged 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 23: | Line 24: | ||
| 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 31: | Line 32: | ||
| Then you can log in to the VM from your own computer using the port you've forwarded above: | Then you can log in to the VM from your own computer using the port you've forwarded above: | ||
| < | < | ||
| - | ===== Updating VirtualBox ===== | ||
| - | 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 ('' | ||
| - | < | ||
| - | VirtualBox Command Line Management Interface Version 3.0.8 | ||
| - | (C) 2005-2009 Sun Microsystems, | ||
| - | All rights reserved. | ||
| - | 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100% | + | ====== Commonly-used commands |
| - | [jmagochi@biovbox ~]$ sudo / | + | ===== List your VMs ===== |
| - | + | ||
| - | $ yum install virtualbox-3.1 | + | |
| - | </ | + | |
| - | ===== Commonly-used commands ===== | + | |
| - | ==== List your VMs ==== | + | |
| < | < | ||
| - | ==== List your running VMs ==== | + | ===== List your running VMs ===== |
| < | < | ||
| - | ==== Autostart VMs at host boot ==== | ||
| - | ---- | ||
| - | |||
| - | Two Methods: | ||
| - | |||
| - | 1 VBoxTool http:// | ||
| - | |||
| - | 2 Script from http:// | ||
| - | |||
| - | VBoxTool currently consist only of a set of scripts. With this scripts, virtual | ||
| - | machines of VirtualBox in a Linux headless server can be controlled. Start, stop, | ||
| - | save, backup and show status of sessions in batch mode from the command line. | ||
| - | |||
| - | Usage and installation is tested only on Ubuntu. Please report if a specific | ||
| - | function is not working in another environment, | ||
| - | |||
| - | INSTALLATION | ||
| - | |||
| - | Note. Precede commands with ' | ||
| - | |||
| - | * Place the main script script/ | ||
| - | |||
| - | * Make vboxtool executable: | ||
| - | chmod +x / | ||
| - | |||
| - | * Place the init script script/ | ||
| - | |||
| - | * Make vboxtoolinit executable: | ||
| - | chmod +x / | ||
| - | | ||
| - | * Activate the init script vboxtoolinit: | ||
| - | update-rc.d vboxtoolinit defaults 99 10 | ||
| - | | ||
| - | * Create a folder / | ||
| - | configuration section below, type ' | ||
| - | | ||
| - | Note. To remove vboxtoolinit from autostart: update-rc.d -f vboxtoolinit remove | ||
| - | |||
| - | CONFIGURATION | ||
| - | |||
| - | Note. Configuration from vboxtool does *not* taking place on *running* sessions, | ||
| - | so save or stop all sessions before issueing the autostart command. | ||
| - | |||
| - | * Create / | ||
| - | <session name>,< | ||
| - | |||
| - | The VRDP-port enables RDP-clients like rdesktop to connect. It may be left blank. | ||
| - | |||
| - | * Create / | ||
| - | vbox_user='< | ||
| - | |||
| - | * Issue the following command: | ||
| - | vboxtool autostart | ||
| - | |||
| - | VBoxTool will configure sessions (VRDP-port). By now, session(s) should be up and | ||
| - | running and configured. | ||
| - | |||
| - | * Check if sessions or running, with the assumed vrdp-port: | ||
| - | vboxtool show | ||
| - | |||
| - | Show only the running sessions: | ||
| - | vboxtool showrun | ||
| - | |||
| - | * Check if sessions configured in / | ||
| - | started at reboot. Reboot your system, check with: vboxtool showrun | ||
| - | |||
| - | UPGRADING FROM 0.2 | ||
| - | |||
| - | Sorry for breaking things here, but it's all in the name of naming consistency... | ||
| - | |||
| - | - Config folder is moved from /etc/vbox to / | ||
| - | - Main script ' | ||
| - | |||
| - | USAGE | ||
| - | After installation, | + | ====== Updating VirtualBox ====== |
| + | ===== Stop any running VMs ===== | ||
| + | Either shut down or "save state" | ||
| + | < | ||
| + | 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: | ||
| - | KNOWN ISSUES | + | < |
| + | $ VBoxManage controlvm nobu savestate | ||
| + | $ VBoxManage controlvm lims savestate | ||
| + | $ exit | ||
| + | # su - aorth | ||
| + | $ VBoxManage controlvm b0237553-9653-4461-bd0e-d4d316c16d4f savestate | ||
| + | $ exit</ | ||
| + | ===== Update VirtualBox ===== | ||
| + | ==== CentOS ==== | ||
| + | < | ||
| + | ===== Resume VMs ===== | ||
| + | < | ||
| + | $ VBoxHeadless -s nobu & | ||
| + | $ VBoxHeadless -s lims & | ||
| + | $ exit | ||
| + | # su - aorth | ||
| + | $ VBoxHeadless -s b0237553-9653-4461-bd0e-d4d316c16d4f -v off &</ | ||
| - | - Backup is not working as expected when using snapshots. When a snapshot is | + | ===== Mount a CD to a running VM ===== |
| - | | + | Attach an ISO to a running VM. The CD/DVD device is on the Secondary IDE controller (--port 1), and it is the slave device |
| - | previous backups. Problem | + | < |
| - | | + | |
| - | vdi instead of the expected, chained main vdi in the vdi folder. | + | |
| - | (Tracker #2132265) | + | |
| - | MORE HELP | + | ====== Optimal settings for a guest ====== |
| - | - Type: 'vboxtool help' | + | * Notes about '' |
| - | - See http://vboxtool.sourceforge.net for more details. | + | * Set the IO scheduler to '' |
| + | * Edit the grub command line to set the default IO scheduler, usually in /// | ||
| + | * Install guest additions (VirtualBox or VMware) | ||
| + | * Run a virtual machine-specific kernel: | ||
| + | * Ubuntu: linux-image-virtual | ||
| + | * Mount filesystems with '' | ||