From 07c022e7fbf40800f274f1f05514581070fb6c58 Mon Sep 17 00:00:00 2001 From: Steve Sheppard Date: Mon, 20 Sep 2010 18:57:18 -0400 Subject: [PATCH] add tags for areas that need more content; --- 1.6/admin/ServersideInstallationVirtual.xml | 33 ++++++++++++++++----- 1 file changed, 26 insertions(+), 7 deletions(-) diff --git a/1.6/admin/ServersideInstallationVirtual.xml b/1.6/admin/ServersideInstallationVirtual.xml index ee111d95d8..97aaee11e5 100644 --- a/1.6/admin/ServersideInstallationVirtual.xml +++ b/1.6/admin/ServersideInstallationVirtual.xml @@ -148,8 +148,9 @@ There are some performance limitations to running Evergreen in a virtualized env ZZZ-REVIEW - ADD LIST OF OTHER PREBUILS IMAGES + ADD LIST OF OTHER PREBUILT IMAGES + ADD LIST OF OTHER PREBUILT IMAGES After successfully installing VirtualBox (see for details), continue with the following procedure. Refer to the accompanying figures for further information: Start VirtualBox for the first time and select FileVirtualBox Media ManagerAdd to locate the prebuilt software image just downloaded (the example shows it was extracted from the original .ZIP file into a temporary directory C:\temp). See for details. @@ -274,12 +275,30 @@ There are some performance limitations to running Evergreen in a virtualized env We recommend this approach if you need to configure the Linux system in any special way, or if you require Evergreen to target some specific chores. This will require a detailed review of both Linux and Evergreen configuration details. You are essentially doing a normal Evergreen installation on a Linux system; it just happens that Linux is running within a virtualized environment. Refer to for information on the normal Evergreen installation, then continue with this section. In this example, we assume that the application "VirtualBox" has already been installed and started: - A standard Ubuntu distribution, the so-called "Guest" operating system, is installed in the running "VirtualBox" environment. - ZZZ-REVIEWADD DETAILS ON MANUAL INSTALLATION OF LINUX - The Ubuntu distribution is started ("booted") just as if it existed on a real, physical system. - ZZZ-REVIEWADD DETAILS ON MANUAL INSTALLATION OF VM LINUX BOOT SEQUENCE - Evergreen is installed on the running Ubuntu distribution, just as if installing on a standalone system. - ZZZ-REVIEWADD DETAILS ON MANUAL INSTALLATION OF EVERGREEN + + A standard Ubuntu distribution, the so-called "Guest" operating system, is installed in the running "VirtualBox" environment. + + ZZZ-REVIEW + ADD DETAILS ON MANUAL INSTALLATION OF LINUX + + ADD DETAILS ON MANUAL INSTALLATION OF LINUX + + + The Ubuntu distribution is started ("booted") just as if it existed on a real, physical system. + + ZZZ-REVIEW + ADD DETAILS ON MANUAL INSTALLATION OF VM LINUX BOOT SEQUENCE + + ADD DETAILS ON MANUAL INSTALLATION OF VM LINUX BOOT SEQUENCE + + + Evergreen is installed on the running Ubuntu distribution, just as if installing on a standalone system. + + ZZZ-REVIEW + ADD DETAILS ON MANUAL INSTALLATION OF EVERGREEN + + ADD DETAILS ON MANUAL INSTALLATION OF EVERGREEN + At this point, the Windows system is hosting an Ubuntu system, which itself is hosting the Evergreen distribution. So far as Evergreen is concerned, it is happily executing in a standard Ubuntu environment and behaves exactly as if it were executing on a standalone Ubuntu system. Of course, there are limitations to how well a virtualized Ubuntu system emulates a real one. The "VirtualBox" application itself consumes memory, and it contributes to the CPU load on the Windows host system. The emulated Ubuntu system will have less available memory and will execute more slowly than if it were a standalone system, therefore Evergreen itself will inherit some limitations from this overall environment. -- 2.43.2