other:vb:update
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
other:vb:update [2015/10/21 09:57] – [Updating the VirtualBox program on the host] Improved section jypeter | other:vb:update [2016/09/19 17:19] (current) – [Updating Linux] Improved... jypeter | ||
---|---|---|---|
Line 2: | Line 2: | ||
<note important> | <note important> | ||
+ | * //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//). |
</ | </ | ||
Line 12: | Line 14: | ||
It is safe to update the Linux running inside VB</ | It is safe to update the Linux running inside VB</ | ||
- | VB will periodically check if a new version is available. You can also check that manually by doing: //Help --> Check for updates...// | + | 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 | + | * Click on the link that VB will display in a pop-up window when there is a new version, or download |
* If the host where you are updating VB has no network connection, you probably also want to download the matching //VB Extension Pack// | * 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 an updated version of the //User Manual// from the same page | * You can also download an updated version of the //User Manual// from the same page | ||
* Make sure that: | * 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) | * 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 | + | * VB is not running |
- | * Execute the VirtualBox-NN1234-Win.exe installer **as an Administrator** (e.g. right-click on the installer and select //run as Administrator// | + | * Execute the VirtualBox-vvvv-NNNN-Win.exe installer **as an Administrator** (e.g. right-click on the installer and select //run as Administrator// |
- | * Download | + | * 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, | ||
* Reboot the computer if VB asks for it (otherwise, you may get weird error messages when trying to restart the guest) | * Reboot the computer if VB asks for it (otherwise, you may get weird error messages when trying to restart the guest) | ||
- | * Do not forget to update the guest additions | + | * Start the VM, optionally [[# |
==== Note about the manual update of the extension pack ==== | ==== Note about the manual update of the extension pack ==== | ||
Line 72: | Line 76: | ||
du -sh / | du -sh / | ||
</ | </ | ||
+ | |||
+ | Recent machines (Fedora Core 22 and later) may use '' | ||
+ | * **dnf** (/ | ||
+ | * **PackageKit** (/ | ||
It's also a good thing to clean the //journal// (note: limiting the journal size probably has to be done only once) | It's also a good thing to clean the //journal// (note: limiting the journal size probably has to be done only once) | ||
Line 87: | Line 95: | ||
</ | </ | ||
+ | Note: **abrt** ([[http:// | ||
==== Updating the Linux guest additions ==== | ==== Updating the Linux guest additions ==== | ||
Line 99: | Line 108: | ||
You should update the guest additions: | You should update the guest additions: | ||
- | * after updating the **Linux guest kernel** | + | * after updating the **Linux guest kernel** |
* after updating the **main VirtualBox program** running on the host | * after updating the **main VirtualBox program** running on the host | ||
Line 106: | Line 115: | ||
* In the VB window (the one where the guest is running), select // | * In the VB window (the one where the guest is running), select // | ||
* 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 | ||
+ | * Right-click on the CD icon and choose //Mount Volume// | ||
* Click on //Cancel// if you get a popup window displaying //This medium contains software intended to be automatically started. Would you like to run it?// | * Click on //Cancel// if you get a popup window displaying //This medium contains software intended to be automatically started. Would you like to run it?// | ||
* Become root in a window: '' | * Become root in a window: '' | ||
* Check where the CD image has been installed: '' | * Check where the CD image has been installed: '' | ||
- | * The CD should be available in ''/ | + | * The CD should be available in ''/ |
* If the CD icon has appeared on the Linux desktop, but you don't see any subdirectory in ''/ | * If the CD icon has appeared on the Linux desktop, but you don't see any subdirectory in ''/ | ||
- | * Go to the additions' | + | * Go to the additions' |
* Run the installation script: '' | * Run the installation script: '' | ||
* Reboot: '' | * Reboot: '' | ||
- | * Virtually eject the CD image by selecting in the VB window, // | + | |
+ | | ||
* 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 | ||
Line 130: | Line 141: | ||
If you want some details about how the graphics are handled by the current installation of you VB (i.e. **is your VM using the graphics card of the Windows host** or is it running is it use the sloooow software mode?), you can use the following commands | If you want some details about how the graphics are handled by the current installation of you VB (i.e. **is your VM using the graphics card of the Windows host** or is it running is it use the sloooow software mode?), you can use the following commands | ||
- | * **glxgears**: if things work correctly, you will get a window with smoothly rotating gears (you can make the window fullscreen and check that it is still working) and the terminal will display some frames per second statistics | + | * '' |
+ | | ||
* You may get some warning and error messages, but you should be good if the gears are rotating smoothly | * You may get some warning and error messages, but you should be good if the gears are rotating smoothly | ||
- | * You can run the //glxinfo// command and you should see a reference to your graphics card if the video is indeed using it\\ **glxinfo | \grep -i opengl**\\ OpenGL vendor string: Humper\\ OpenGL renderer string: Chromium \\ OpenGL version string: 2.1 Chromium 1.9\\ **NVIDIA card =>** OpenGL shading language version string: 4.40 **NVIDIA** via Cg compiler\\ **Intel HD Graphics xxxx card =>** OpenGL shading language version string: 4.00 - **Build 10.18.10.3993**\\ OpenGL extensions: | + | * You can run the //glxinfo// command and you should see a reference to your graphics card if the video is indeed using it\\ '' |
- | * You can get some additional information (including the screen resolution) with the // | + | * You can get some additional information (including the screen resolution) with the // |
other/vb/update.1445414236.txt.gz · Last modified: 2015/10/21 09:57 by jypeter