virtualbox
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| virtualbox [2010/02/18 09:36] – 172.26.0.166 | virtualbox [2017/07/03 11:22] (current) – removed aorth | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== VirtualBox ===== | ||
| - | VirtualBox is a free/ | ||
| - | |||
| - | * [[http:// | ||
| - | ===== Create a VM ===== | ||
| - | Copy an ISO to your home directory: | ||
| - | < | ||
| - | * 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: | ||
| - | < | ||
| - | Each and every VM using bridged networking must use this command. | ||
| - | |||
| - | As of VirtualBox 3.1.2 this is still a [[http:// | ||
| - | |||
| - | ==== 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. | ||
| - | < | ||
| - | $ VBoxManage setextradata Ubuntu " | ||
| - | $ VBoxManage setextradata Ubuntu " | ||
| - | 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% | ||
| - | [jmagochi@biovbox ~]$ sudo / | ||
| - | |||
| - | $ yum install virtualbox-3.1 | ||
| - | </ | ||
| - | ===== Commonly-used commands ===== | ||
| - | ==== List your VMs ==== | ||
| - | < | ||
| - | ==== List your running VMs ==== | ||
| - | < | ||
| - | ==== Autostart VMs at host boot ==== | ||
| - | ---- | ||
| - | |||
| - | Two Methods: | ||
| - | |||
| - | 1 VBoxTool http:// | ||
| - | |||
| - | 2 Script from http:// | ||
| - | |||
| - | ===Ubuntu: | ||
| - | 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, | ||
| - | |||
| - | KNOWN ISSUES | ||
| - | |||
| - | - Backup is not working as expected when using snapshots. When a snapshot is | ||
| - | present, the main vdi file is not copied, even if it's different from | ||
| - | previous backups. Problem is that once a snapshot is made, the main vdi | ||
| - | (according to info from ' | ||
| - | vdi instead of the expected, chained main vdi in the vdi folder. | ||
| - | (Tracker #2132265) | ||
| - | |||
| - | MORE HELP | ||
| - | |||
| - | - Type: ' | ||
| - | - See http:// | ||
| - | |||
| - | === Fedora :Redhat : CentOS === | ||
| - | ---- | ||
| - | How do I get my VirtualBox Guest VM’s to start and stop when the host system reboots, shutdown, or starts. | ||
| - | |||
| - | Solution / Answer: | ||
| - | |||
| - | Create an init.d script so that VirtualBox Guest VM are controlled as a system service. | ||
| - | http:// | ||