This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
other:vb:update [2015/05/26 08:52] jypeter Updated the guest additions update |
other:vb:update [2016/01/20 13:12] jypeter Slight updates |
||
---|---|---|---|
Line 2: | Line 2: | ||
<note important>Important reminder: | <note important>Important reminder: | ||
+ | * //VB// : VirtualBox | ||
+ | * //VM// : a Virtual Machine running inside VB | ||
* VB //host//: the machine and operating system where the VB program is running. | * VB //host//: the machine and operating system where the VB program is running. | ||
- | * VB //guest//: the operating system running **inside** VB. | + | * VB //guest//: the operating system running **inside** VB (aka //VM//). |
</note> | </note> | ||
+ | |||
+ | ===== When should you update the VB? ===== | ||
+ | |||
+ | <note warning>If you are not used to installing and debugging VB, you may want to play it safe and **not update VB**. Many things are fixed in a new version, but things can also break (e.g. network access, graphics, ...) and you may have to use the VB forum to get everything working again... | ||
+ | |||
+ | It is safe to update the Linux running inside VB</note> | ||
+ | |||
+ | VB will periodically check if a new version is available. You can also check that manually by doing: //File --> Check for updates...// | ||
+ | |||
===== Updating the VirtualBox program on the host ===== | ===== Updating the VirtualBox program on the host ===== | ||
- | * Download the latest version of VB, and the matching VB additions file from the [[https://www.virtualbox.org/|VirtualBox web site]] | + | * Click on the link that VB will display in a pop-up window when there is a new version, or download the latest version of VB from the [[https://www.virtualbox.org/|VirtualBox web site]] |
- | * Execute the VirtualBox-NN1234-Win.exe installer | + | * If the host where you are updating VB has no network connection, you probably also want to download the matching //VB Extension Pack// |
- | * Execute VB and download and install the updated //VirtualBox Extension Pack// if VB tells you that a new pack is available | + | * You can also download an updated version of the //User Manual// from the same page |
- | * Do not forget to update the guest additions (see below) | + | * Make sure that: |
+ | * Your VB guest is in the //Powered Off// state (i.e. you have exited the guest with a proper Linux shut down last time you used the guest) | ||
+ | * VB is not running (e.g. you don't have an open //Oracle VM VirtualBox Manager// window) | ||
+ | * Execute the VirtualBox-vvvv-NNNN-Win.exe installer **as an Administrator** (e.g. right-click on the installer and select //run as Administrator//). | ||
+ | * Accept all the default settings | ||
+ | * Make sure you don't have another program using the network when the installer warns you about having to temporarily stop the network | ||
+ | * Choose to start VB at the end of the installation, and accept to download and install the updated //Oracle VM VirtualBox Extension Pack// when VB tells you that a new pack is available | ||
+ | * Reboot the computer if VB asks for it (otherwise, you may get weird error messages when trying to restart the guest) | ||
+ | * Start the VM, optionally [[#updating_linux|update the linux guest]] and no not forget to [[#updating_the_linux_guest_additions|update the guest additions]] | ||
==== Note about the manual update of the extension pack ==== | ==== Note about the manual update of the extension pack ==== | ||
Line 22: | Line 41: | ||
* or **2)** Go to the directory where the VM is installed (e.g. ''E:\VirtualBox\VirtualBox VMs\Fedora Core 20 CLIM_ESTIMR'') and double click on the ''XXXXX.vbox'' setting file located in this directory | * or **2)** Go to the directory where the VM is installed (e.g. ''E:\VirtualBox\VirtualBox VMs\Fedora Core 20 CLIM_ESTIMR'') and double click on the ''XXXXX.vbox'' setting file located in this directory | ||
+ | ==== Cleaning up things ==== | ||
+ | |||
+ | After updating VB, you can remove the downloaded extension packs from ''C:\Users\your_login\.VirtualBox'' (i.e. all the ''Oracle_VM_VirtualBox_Extension_Pack-NNNN.vbox-extpack'' files) | ||
===== Updating the Linux guest system ===== | ===== Updating the Linux guest system ===== | ||
Line 31: | Line 53: | ||
* On the LSCE network: **yum update** | * On the LSCE network: **yum update** | ||
* Outside LSCE: **yum %%--%%disablerepo lsce update** | * Outside LSCE: **yum %%--%%disablerepo lsce update** | ||
+ | |||
+ | Note: You will know you have updated the //Linux kernel//, if ''yum update'' displays something like the following: | ||
+ | <code>Installing: | ||
+ | kernel x86_64 3.19.8-100.fc20 updates 34 M | ||
+ | kernel-devel x86_64 3.19.8-100.fc20 updates 9.3 M | ||
+ | kernel-modules-extra x86_64 3.19.8-100.fc20 updates 2.1 M</code> | ||
+ | |||
=== Cleaning up things === | === Cleaning up things === | ||
Line 73: | Line 102: | ||
* //many other subtle things...// | * //many other subtle things...// | ||
- | You have to update the guest additions //after// you update the **Linux guest kernel** or you after update the **main VirtualBox program** running on the host | + | You should update the guest additions: |
+ | * after updating the **Linux guest kernel** (no need to update the guest additions after non kernel updates) | ||
+ | * after updating the **main VirtualBox program** running on the host | ||
+ | Guest additions updating steps: | ||
+ | * If you have just updated the Linux kernel (when doing a Linux update), make sure you reboot the Linux guest before you reinstall the guest additions, so that the new kernel is running when you install the guest additions! | ||
* In the VB window (the one where the guest is running), select //Devices->Insert Guest Additions CD Image...//. A //virtual// CD icon should appear on the desktop of the Linux guest | * In the VB window (the one where the guest is running), select //Devices->Insert Guest Additions CD Image...//. A //virtual// CD icon should appear on the desktop of the Linux guest | ||
* Click on //Force unmount// in the popup Window, if a previous virtual CD is still present | * Click on //Force unmount// in the popup Window, if a previous virtual CD is still present | ||
Line 80: | Line 113: | ||
* Become root in a window: ''sudo su -'' | * Become root in a window: ''sudo su -'' | ||
* Check where the CD image has been installed: ''df -h'' | * Check where the CD image has been installed: ''df -h'' | ||
- | * The CD should be available in ''/run/media/your_login/VBOXADDITIONS_NNNN'' | + | * The CD should be available in ''/run/media/your_login/VBOXADDITIONS_vvvv_NNNN'' |
- | * If the CD icon has appeared on the Linux desktop, but you see nothing in /run/media, right-click on the CD icon and select //Mount volume// | + | * If the CD icon has appeared on the Linux desktop, but you don't see any subdirectory in ''/run/media'', right-click on the CD icon and select //Mount volume// |
- | * Go to the additions' directory: ''cd /run/media/your_login/VBOXADDITIONS_NNNN'' | + | * Go to the additions' directory: ''cd /run/media/your_login/VBOXADDITIONS_vvvv_NNNN'' |
* Run the installation script: ''./VBoxLinuxAdditions.run'' | * Run the installation script: ''./VBoxLinuxAdditions.run'' | ||
* Reboot: ''shutdown -r now'' | * Reboot: ''shutdown -r now'' | ||
- | * Virtually eject the CD image by selecting in the VB window, //Device->CD/DVD Devices->Remove disk from virtual drive// | + | * Log in |
+ | * Virtually eject the CD image by selecting in the VB window, //Device->Optical Drives->Remove disk from virtual drive// | ||
* Note: click in //Force unmount// in the popup Window, if necessary | * Note: click in //Force unmount// in the popup Window, if necessary | ||
* The //virtual// CD icon should disappear from the desktop of the Linux guest | * The //virtual// CD icon should disappear from the desktop of the Linux guest |