VMware: Difference between revisions
DanielDrake (talk | contribs) No edit summary |
DanielDrake (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
{{Dated}} |
|||
<big><b><font color=red>For current information on emulation of OLPC software images, see [[Emulating the XO]]</font></b></big> |
<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}} |
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:
|