PMIP3 wiki

User Tools

Site Tools

You are here: index » other » vb » install
other:vb:install

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
other:vb:install [2015/01/09 11:57] – jypeterother:vb:install [2015/10/26 17:34] (current) – Added extra warning about VT-x in the BIOS jypeter
Line 3: Line 3:
 ===== Installing VB on a Windows host ===== ===== Installing VB on a Windows host =====
  
-  * Reboot your computer, [[other:bios|enter the BIOS]] and enable the //VT-x// setting+<note warning>Do not forget the **enable the //VT-x// setting** step below!\\ \\ Otherwise you will not be able to execute a 64bit Linux VB (and you will probably not even get an explicit error message about this)</note>
  
-  * download the latest //VirtualBox NN.NN.NN for Windows hosts// **AND** the matching //VirtualBox NN.NN.NN Oracle VM VirtualBox Extension Pack// from the [[https://www.virtualbox.org/wiki/Downloads|VirtualBox web site]]\\ You can also download the //User Manual// from the same page+  * Reboot your computer, [[other:bios|enter the BIOS]] and **enable the //VT-x// setting** 
 +    * if you are not used to making changes in the BIOS settings, ask somebody who knows...
  
-  * Execute the //exe// installer and accept the default settings, but do NOT choose to start VB at the end. **Warning**, the host network will very temporarily be stopped during the installation, so be sure not to have anything needing a permanent network (eg connection to an interactivr server) during the installation!+  * Download the latest version of VB from the [[https://www.virtualbox.org/|VirtualBox web site]] 
 +    * If the host where you are updating VB has no network connection, you probably also want to download the matching //VB Extension Pack// 
 +    * You can also download the //User Manual// from the same page
  
-  * Double click on the Extension_Pack installer, accept the license, etc...+  * Execute the VirtualBox-NN1234-Win.exe installer **as an Administrator** and accept the default settings. 
 +    *  **Warning**, the host network will very temporarily be stopped during the installation, so be sure not to have anything needing a permanent network connection (eg connection to an interactive server with Putty, Cygwin/X, ...) during the installation! 
 +    * Download and install the //VirtualBox Extension Pack// if VB tells you that a new pack is available
  
   * Change some basic Preferences:   * Change some basic Preferences:
     * If the VB is not already using English, change the language and restart VB if necessary\\ Fichier -> Paramètres -> Langue -> English     * If the VB is not already using English, change the language and restart VB if necessary\\ Fichier -> Paramètres -> Langue -> English
     * File -> Preferences -> Update -> Once per 2 weeks     * File -> Preferences -> Update -> Once per 2 weeks
-    * Determine where the VB settings, the virtual disk files and the temporary files (when you //suspend// the execution of the VB) will be stored. **Warning**, you should be careful to choose a place where you have enough space! You need as much space as the main disk image (eg 30 Gb) plus a few Gb for storing the state of the VB when you suspend it...\\ We will use the following path in this tutorial: E:\VirtualBox VMs\Fedora Core 20 CLIM_ESTIMR+    * Determine where the VB settings, the virtual disk files and the temporary files (when you //suspend// the execution of the VB) will be stored 
 +      * **Warning**, you should be careful to choose a place where you have enough space! You need as much space as the main disk image (eg 30 Gb) plus a few Gb for storing the state of the VB when you suspend it...\\ File -> Preferences -> General -> Default Machine Folder: ''X:\some_path\VirtualBox VMs\'' 
 +      * We will use the following path in this tutorial: ''E:\VirtualBox VMs\''
  
 ===== Installing the copy of a existing Linux guest ===== ===== Installing the copy of a existing Linux guest =====
Line 45: Line 52:
 === Creating the appliance on the source host=== === Creating the appliance on the source host===
  
 +  * Start VB
 +  * [[other:vb:update#cleaning_up_things|Clean the virtual machine]] to reduce the size of the appliance that will be created
   * Make sure that the virtual machine is stopped (//Powered Off// state)   * Make sure that the virtual machine is stopped (//Powered Off// state)
   * File -> Export Appliance   * File -> Export Appliance
   * Select the //Fedora Core 20 JYPclone// machine   * Select the //Fedora Core 20 JYPclone// machine
-  * In the //Storage settings// window, select an output directory with enough space to store the exported //ova// (FedoraCore20JYPclone.ova) file +  * In the //Storage settings// window, select an output directory with **enough space** to store the exported //ova// (''FedoraCore20JYPclone.ova'' or a more explicit file name, with the VB version and the export date, e.g. ''FedoraCore20JYPclone_4.3.28_150602.ova'') file 
-  * Just click //Export// in the Appliance settings window+    * A 30 Gb VM disk seems to produce a 11+ Gb compressed appliance file 
 +    * OVF 1.0 works reliably, and OVF 2.0 has to be tested (by JYP). The difference between the 2 formats is detailed in the [[http://www.dmtf.org/sites/default/files/DMTF_OVF_2%200_FAQ__Final_1.pdf|OVF 2.0 FAQ]] 
 +    * The appliance **can't** be stored on a FAT32 disk (where file size is limited to 2 Gb)! 
 +  * Just click //Export// in the Appliance settings window... and wait (20-30 minutes)!
  
 === Installing the appliance on the target host === === Installing the appliance on the target host ===
  
-  * Copy the appliance //ova// file to the target host +  * Copy the appliance //ova// file to the target host, or just have it on an external USB disk/stick connected to the host 
-  * File -> Import Appliance... : specify the //ova// file and import it\\ This will install a //Fedora Core 20 JYPclone// directory in //E:\VirtualBox VMs\// and you will get a //Fedora Core 20 JYPclone// machine in the left panel of the //Oracle VM VirtualBox Manager// window, with all the correct predefined settings. You may want to edit the settings to adapt the VM memory based on the memory available on the host!+  * File -> Import Appliance... : specify the //ova// (e.g. ''X:\some_path\FedoraCore20JYPclone_4.3.28_150602.ova'') file and import it\\ This will install a //Fedora Core 20 JYPclone// directory in //E:\VirtualBox VMs\// and you will get a //Fedora Core 20 JYPclone// machine in the left panel of the //Oracle VM VirtualBox Manager// window, with all the correct predefined settings. You may want to edit the settings to adapt the VM memory based on the memory available on the host!
  
  
Line 60: Line 72:
  
   * Select the //Fedora Core 20 JYPclone// machine and then click on //Start//   * Select the //Fedora Core 20 JYPclone// machine and then click on //Start//
 +    * Note: the first time you start VB, you will probably get some information message about the //Auto capture keyboard// and //mouse pointer integration//. Just click on the apropriate buttons so that these messages are not displayed the next time
  
   * Login with the root or an existing account   * Login with the root or an existing account
  
-  * [[other:vb:update|Update VB]]+  * [[other:vb:update|Update VB]]:unless the imported appliance was really recent, you may have to update the linux guest (if the installed Linux had some packages updated) and or update the Linux guest additions (if the VB you have installed is more recent than the VB that was used for exporting the Appliance)
  
   * Create an account for the final user of this VB   * Create an account for the final user of this VB
other/vb/install.1420801064.txt.gz · Last modified: 2015/01/09 11:57 by jypeter
Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki