User Tools

Site Tools


virtualbox

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
virtualbox [2010/01/14 09:29] 172.26.0.166virtualbox [2010/02/17 08:54] 172.26.0.166
Line 1: Line 1:
-===== VirtualBox tips/tricks ===== +===== VirtualBox ===== 
-==== Commonly-used commands ==== +VirtualBox is free/opensource Hypervisor from Sun Microsystems.  It has performance on par with VMware and is very mature.  We have two virtualization servers, [[biovbox]] and biovboxtesting.
-To change between "not attached", NAT,Bridged,internal network and host olny adapter:  +
-<code>VBoxManage modifyvm <uuid|name> [--nic<1-N> none|null|nat|bridged|intnet|hostonly]</code> +
-Set the boot order: +
-<code>VBoxManage modifyvm <uuid|name> [--boot<1-4> none|floppy|dvd|disk|net>]</code> +
-Add shared folder: +
-<code>VBoxManage sharedfolder add <vmname>|<uuid> --name <name> --hostpath <hostpath> [--transient] [--readonly] </code> +
-Acpi Vm: +
-<code>VBoxManage controlvm  <uuid>|<name>pause|resume|reset|poweroff|savestate|acpipowerbutton|acpisleepbutton| </code> +
-Change rdp address: +
-<code>VBoxManage modifyvm <uuid|name> [--vrdpaddress <host>]</code> +
-Change the Authentication type:  +
-<code>VBoxManage modifyvm <uuid|name> [--vrdpauthtype null|external|guest]</code> +
-**Note**: option "external" will limit access to individual users, The user will be required to use rdesktop-vrdp with username and password: +
-<code>rdesktop-vrdp -u <username> -p - <host ip address>:<vrdp port></code> +
-Change rdp port: +
-<code>VBoxManage modifyvm <uuid|name> [--vrdpport <port>]</code> +
-List all VMs in the server: +
-<code>VBoxManage list vms</code> +
-List all running VMs: +
-<code>VBoxManage list runningvms </code> +
-List guest properties: +
-<code> VBoxManage list -l  vms </code> +
-Note: All the guest parameters(configuration) are in <guestname>.xml+
  
 +  * [[http://www.virtualbox.org|VirtualBox homepage]]
 ===== Create a VM ===== ===== Create a VM =====
 Copy an ISO to your home directory: Copy an ISO to your home directory:
-<code>$scp <dist>.iso <username>@172.26.0.205:~/</code> +<code>$scp ubuntu-9.04-desktop-i386.iso alan@172.26.0.200:~/</code> 
-  * SSH to VM server: 172.26.0.205 +  * SSH to VM server: 172.26.0.200 
-<code>$ ssh <username>@172.26.0.205</code>+<code>$ ssh alan@172.26.0.200</code>
   * start the virtualbox application   * start the virtualbox application
 <code>$ VirtualBox</code> <code>$ VirtualBox</code>
-  * Follow the wizzard to create a VM with the following properties:+  * Follow the wizard to create a VM with the following properties:
       - Base Memory: less than 512 MB       - Base Memory: less than 512 MB
       - Network : NAT       - Network : NAT
-      - Harddisk size: less than 30Gb+      - 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: 
 +<code>VBoxManage setextradata MyMachine VBoxInternal/Devices/pcnet/0/LUN#0/Config/RestrictAccess 0</code> 
 +Each and every VM using bridged networking must use this command.  If you are seeing errors like ''VERR_PERMISSION_DENIED'' regarding the network interface, this is the cause! 
 + 
 +As of VirtualBox 3.1.2 this is still a [[http://www.virtualbox.org/ticket/2852|known issue]]. 
 ==== Port Forwarding ==== ==== Port Forwarding ====
  
-If your guest OS is using NAT for networking you will need to enable port forwarding.  There is no GUI for this in VirtualBox, but you can use ''VBoxManage setextradata'' to make the required changes.  If you want to SSH to your VM, for example:+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.  There is no GUI for this in VirtualBox, but you can use ''VBoxManage setextradata'' to make the required changes.  If you want to SSH to your VM, for example:
 <code>$ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/HostPort" 2223 <code>$ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/HostPort" 2223
 $ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/GuestPort" 22 $ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/GuestPort" 22
-$ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/Protocol" TCP+$ VBoxManage setextradata Ubuntu "VBoxInternal/Devices/pcnet/0/LUN#0/Config/ssh/Protocol" TCP</code>
 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:
-<code>$ ssh -p 2223 username@172.26.0.205</code> +<code>$ ssh -p 2223 username@172.26.0.200</code> 
- +===== Updating VirtualBox ===== 
-=== Upgrading 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 (''ps auxw | grep VBox'') and then shutting down or saving the state of each one.
 <file>[jmagochi@biovbox ~]$ VBoxManage controlvm CentOS savestate <file>[jmagochi@biovbox ~]$ VBoxManage controlvm CentOS savestate
 VirtualBox Command Line Management Interface Version 3.0.8 VirtualBox Command Line Management Interface Version 3.0.8
Line 57: Line 43:
 $ yum install virtualbox-3.1 $ yum install virtualbox-3.1
 </file> </file>
 +===== Commonly-used commands =====
 +==== List your VMs ====
 +<code>$ VBoxManage list vms</code>
 +==== List your running VMs ====
 +<code>$ VBoxManage list runningvms </code>
 +==== Autostart VMs at host boot ====
 +----
 +Two Methods:
 + - http://vboxtool.sourceforge.net/
 + - http://www.kernelhardware.org/virtualbox-auto-start-vm-centos-fedora-redhat/
  
-===== Expanding Virtual Disk ===== +VBoxTool currently consist only of set of scriptsWith this scripts, virtual  
-There is no way to expand a VDI What you have to do is create a new VDIboot the virtual machine to live cd, and copy over the filesystem (either via ''dd'', rsync, etc). +machines of VirtualBox in Linux headless server can be controlledStartstop,  
- +savebackup and show status of sessions in batch mode from the command line.
-Create new VDI +
- +
-Attach to virtual machine and boot with System Rescue CD +
- +
-Create two partitions with fdisk/cfdisk/partedwhatever: +
-  * 1: 100 MBboot, type "Linux" (83) +
-  * 2: 30 GBtype "Linux LVM" (8E) +
- +
-Format the boot partition as ext3 +
- +
-==== LVM setup ====+
  
-Create Physical Volume from device: +Usage and installation is tested only on Ubuntu. Please report if a specific  
-<code>pvcreate /dev/sdb2</code>+function is not working in another environment, say OpenSUSE, Fedora, etc.
  
-Create Volume Group from PV: +INSTALLATION
-<code>vgcreate VolGroup01 /dev/sdb2</code>+
  
-Create Logical Volumes in VG: +Note. Precede commands with 'sudo' when not operated as root.
-<code>lvcreate -L29G -nLogVol00 VolGroup01 +
-lvcreate -L512M -nLogVol01 VolGroup01</code>+
  
-Format the new partitions: +* Place the main script script/vboxtool in /usr/local/bin
-<code>mkfs.ext3 /dev/VolGroup01/LogVol00 +
-<code>mkswap /dev/VolGroup01/LogVol01</code>+
  
-<note important>Set the disk label on the boot partition to "/boot" using gparted (fstab loads the boot partition based on its label!)</note>+* Make vboxtool executable:  
 +    chmod +x /usr/local/bin/vboxtool
  
-Mount both root partitions: +* Place the init script script/vboxtoolinit in /etc/init.d
-<code>mount /dev/VolGroup01/LogVol00 /mnt/newroot +
-mount /dev/VolGroup00/LogVol00 /mnt/oldroot</code>+
  
-Copy everything over+* Make vboxtoolinit executable:  
-<code>rsync -xrlptgoEv --delete /mnt/oldroot/ /mnt/newroot/</code>+    chmod +x /etc/init.d/vboxtoolinit 
 +   
 +* Activate the init script vboxtoolinit: 
 +    update-rc.d vboxtoolinit defaults 99 10 
 +   
 +* Create a folder /etc/vboxtool. In here, two config files have to be created, see 
 +  configuration section below, type 'vboxtool help' for more instructions. 
 +   
 +Note. To remove vboxtoolinit from autostart: update-rc.d -f vboxtoolinit remove
  
-Mount both boot partitions: +CONFIGURATION
-<code>mount /dev/sdb1 /mnt/newboot +
-mount /dev/sda1 /mnt/oldboot</code>+
  
-Copy everything over: +Note. Configuration from vboxtool does *not* taking place on *running* sessions,  
-<code>rsync -xrlptgoEv --delete /mnt/oldboot/ /mnt/newboot/</code>+so save or stop all sessions before issueing the autostart command.
  
-Force SElinux to relabel all files on boot (or else SElinux will deny you to log in) +* Create /etc/vboxtool/machines.conf: 
-<code>touch /mnt/newroot/.autorelabel</code>+    <session name>,<VRDP-port>
  
-Unmount all mounted logical volumes 
  
-Install GRUB on the new VDI 
-<code>grub 
-> root (hd0,0) 
-> setup (hd0)</code> 
  
-==== Renaming the new volume group==== 
  
-Deativate all logical volumes 
-<code>lvchange -an /dev/mapper/VolGroup*</code> 
-Rename old volume group 
-<code>vgrename VolGroup00 VolGroupOld</code> 
-Rename new volume group 
-<code>vgrename VolGroup01 VolGroup00</code> 
  
-Now shutdown the machine and remove the old VDI.