VMware: Difference between revisions
(→Setup: Give a bit more advice on what images to choose.) |
DanielDrake (talk | contribs) No edit summary |
||
(15 intermediate revisions by 10 users not shown) | |||
Line 1: | Line 1: | ||
<big><b><font color=red>For current information on emulation of OLPC software images, see [[Emulating the XO]]</font></b></big> |
|||
{{Deprecated}} |
|||
{{emulation-nav}} |
{{emulation-nav}} |
||
[http://www.vmware.com/ VMWare] (Workstation, Player) is an emulator released as commercial software. The player version is distributed free of charge (Gratis). It runs on either Win32 or Linux host machines, allowing you to run OLPC images within the virtual machine. A Mac version is also available, VMWare Fusion, however this is not provided free of charge (a free 30-day evaluation is available). |
|||
You can decide either to emulate an XO via downloaded images, or to build a [[#Developer's Desktop Emulation|developer's desktop image]] starting from a stock Fedora 7. Both approaches are discussed here. |
You can decide either to emulate an XO via downloaded images, or to build a [[#Developer's Desktop Emulation|developer's desktop image]] starting from a stock Fedora 7. Both approaches are discussed here. |
||
See Also: |
|||
= Caveats = |
|||
* There is [http://www.moka5.com:80/products/getstarted.html apparently] a free wrapper that lets you use the VMWare player similarly to VMWare Workstation on MS Windows platforms. |
|||
⚫ | |||
= |
= Caveats = |
||
⚫ | |||
VMWare's primary advantages for OLPC developers are: |
|||
VMWare seems to have the highest performance of the emulation solutions available, but the difference between it and Qemu + KQemu is fairly minimal. |
|||
* You may already have it |
|||
hl |
|||
* It's fast (generally slightly faster than Qemu with KQemu) |
|||
* It's got a slick GUI front-end (for the full versions) |
|||
* There is (paid) support available from VMWare for their products |
|||
That said, VMWare is comparatively less well supported by the project. We are attempting to improve support, but we will generally prioritize [[Qemu]] support before VMWare support. |
|||
== Snapshots == |
|||
Allow you to take a complete copy of a system at any point in time (even while running) in order to checkpoint changes and allow you to return to the previous state. |
|||
Note that this is ''not'' an overlay system such as [[Qemu]]'s copy-on-write system, it copies the whole disk (and memory), so will take considerably more hard-disk space. |
|||
== File Sharing == |
|||
You can use your host machine to edit files and "upload" them to your virtual XO via and IP-based file-transfer mechanism: |
|||
* source-code-control (git, bzr, svn) |
|||
* sftp, scp |
|||
* rsync |
|||
* editor-based virtual file-systems |
|||
Direct file-sharing support is available in commercial versions of VMWare with the VMWare tools installed on the client OS. |
|||
= Emulating the XO = |
|||
An emulated XO image is recommended for developers working on Activities (as distinct from Sugar and other core libraries). It is also recommended for those who want to test their software or who may not have enough computer power to run a developer's image. |
|||
The XO images have the advantage of being faster than a "developer's desktop" image. They are also much easier to maintain (sugar-jhbuild can be quite time consuming). You should be sure to use source-code-control storing to another machine (such as your host machine) for all of your code so that you do not lose work when updating to a newer image. |
|||
== Compatibility == |
|||
Recent builds, particularly Ship.2 builds, should all work reasonably well with VMWare. |
|||
= Setup = |
= Setup = |
||
Line 51: | Line 22: | ||
The VMWare/VirtualBox images are converted from the official images using a simple downloading script. You can either use a pre-converted image (recommended) or download and [[VMware/Convert|convert the official images yourself]]. |
The VMWare/VirtualBox images are converted from the official images using a simple downloading script. You can either use a pre-converted image (recommended) or download and [[VMware/Convert|convert the official images yourself]]. |
||
Mac Users may want to check out [http://www.edgargonzalez.com/2006/11/21/emulating-the-olpc-xo-on-a-mac-osx/ this article]. |
Mac Users may want to check out [http://www.edgargonzalez.com/2006/11/21/emulating-the-olpc-xo-on-a-mac-osx/ this article] or use [[User:Probono|OLPC4Mac]], a script that creates an OLPC image for VMware Fusion on the Mac automatically. |
||
== Pre-converted Images == |
== Pre-converted Images == |
||
Pre-converted images |
Pre-converted images ''used to be'' generated from the latest release and made available at http://dev.laptop.org/pub/virtualbox/ |
||
[[OS images]] explains the different kinds of builds. |
|||
* "Joyride" versions are the current development builds, that is, the most bleeding-edge builds available |
|||
* "Ship.2" versions are the builds targeted for release on real mass-production laptops used by real children (think of them as stable-enough to test for shipping) |
|||
** "Official" versions are the builds which have been found stable enough to be released for general consumption (note: currently these builds are not being converted, the ship.2 builds of the same number should be the equivalent of the official releases) |
|||
Choose a reasonably recent version (within the last few weeks) whenever possible. Keep in mind that Joyride builds may be broken! Discussions on the OLPC-devel mailing list will discuss broken builds when they happen. |
Choose a reasonably recent version (within the last few weeks) whenever possible. Keep in mind that Joyride builds may be broken! Discussions on the OLPC-devel mailing list will discuss broken builds when they happen. |
||
Images created after 2007-12-22 should have a VMWare 6.0-format -6.vmx and -6.vmxf file in the downloadable zip file. These files are not yet tested, but VMWare 6.0 should allow you to use USB keys and the like more reliably within the emulated images. |
|||
See: [[Developers/Setup# Configuration and Usage|Configuration and Usage]] -- describes how to set up the new image for development work |
See: [[Developers/Setup# Configuration and Usage|Configuration and Usage]] -- describes how to set up the new image for development work |
||
Line 127: | Line 98: | ||
* The next steps will take the better part of a day to complete, if not more on a slower machine (You'll be running an emulator ''within'' an emulator!) |
* The next steps will take the better part of a day to complete, if not more on a slower machine (You'll be running an emulator ''within'' an emulator!) |
||
* Create a new virtual machine and do a base Fedora |
* Create a new virtual machine and do a base Fedora (or Ubuntu) install on it |
||
** Do not install any extra packages (will be done later) |
** Do not install any extra packages (will be done later) |
||
** Make sure you give the disk at least 15GB max size. If you have the disk space, preallocate it now. That will give you a twofold increase in performance |
** Make sure you give the disk at least 15GB max size. If you have the disk space, preallocate it now. That will give you a twofold increase in performance |
||
Line 136: | Line 107: | ||
Once you have your working Fedora 7 or Ubuntu image under emulation, see the instructions for setting up [[Sugar with sugar-jhbuild]] for your new (emulated) platform: |
Once you have your working Fedora 7 or Ubuntu image under emulation, see the instructions for setting up [[Sugar with sugar-jhbuild]] for your new (emulated) platform: |
||
* [[Sugar on Fedora |
* [[Sugar on Fedora]] |
||
* [[Sugar on Ubuntu]] |
* [[Sugar on Ubuntu Linux]] |
||
The <code>update</code> step will download approximately 1.6GB of data (using compression so probably around 400MB in actual download). The build phase will also take a few hours. On a 2.4Ghz Core2 duo iMac with 3GB ram it took about two hours. |
The <code>update</code> step will download approximately 1.6GB of data (using compression so probably around 400MB in actual download). The build phase will also take a few hours. On a 2.4Ghz Core2 duo iMac with 3GB ram it took about two hours. |
Latest revision as of 16:15, 8 February 2011
For current information on emulation of OLPC software images, see Emulating the XO
You can decide either to emulate an XO via downloaded images, or to build a developer's desktop image starting from a stock Fedora 7. Both approaches are discussed here. See Also:
CaveatsOn Linux, VMWare setup requires a package of kernel modules (as do all high-speed emulation options we are aware of). VMWare seems to have the highest performance of the emulation solutions available, but the difference between it and Qemu + KQemu is fairly minimal. hl SetupThe VMWare/VirtualBox images are converted from the official images using a simple downloading script. You can either use a pre-converted image (recommended) or download and convert the official images yourself. Mac Users may want to check out this article or use OLPC4Mac, a script that creates an OLPC image for VMware Fusion on the Mac automatically. Pre-converted ImagesPre-converted images used to be generated from the latest release and made available at http://dev.laptop.org/pub/virtualbox/ OS images explains the different kinds of builds. Choose a reasonably recent version (within the last few weeks) whenever possible. Keep in mind that Joyride builds may be broken! Discussions on the OLPC-devel mailing list will discuss broken builds when they happen. Images created after 2007-12-22 should have a VMWare 6.0-format -6.vmx and -6.vmxf file in the downloadable zip file. These files are not yet tested, but VMWare 6.0 should allow you to use USB keys and the like more reliably within the emulated images. See: Configuration and Usage -- describes how to set up the new image for development work TipsTo get access to the root console, that is, virtual console 1:
Use full-screen mode:
OLPC ClonesVMware Workstation has a nifty feature called "Linked Clones." This enables users to deploy virtual machines based on the "template virtual machine" that take up very little space. For example, I can make a OLPC virtual machine, turn it into a template, make a clone, and the clone will take up ~6 megs of disk space when not running. When running, it will consume more diskspace as ram. Why?It is now extremely easy to test mesh networking and networking activities in general. The folks at OLPC Austria have done something similar with qemu, but that requires additional software to manage a virtual ethernet network. VMware workstation provides more networking support out the box. In addition, the clones would take less disk space than it would to run multiple instances of qemu images. Creating the Template OLPC Virtual Machine
Deploying Clones From The Template OLPC Virtual Machine
VMWare Tools
Ed Borasky, 5 December 2007: I've downloaded ship2 build650 and built a virtual machine from it following the above instructions. Unfortunately:
Developer's Desktop EmulationFor development on the core Sugar system (as distinct from activities), you likely need an emulated sugar-jhbuild system so that you can keep up to the most recent versions of all core packages. System Requirements:
The quickest way to get started creating a jhbuild (developer's desktop) is:
Once you have your working Fedora 7 or Ubuntu image under emulation, see the instructions for setting up Sugar with sugar-jhbuild for your new (emulated) platform: The See:
|