Emulating the XO: Difference between revisions

From OLPC
Jump to navigation Jump to search
(rephrase + Linux use report)
Line 38: Line 38:
VMWare and probably also for VirtualBox). You need a newer version of QEMU compiled from
VMWare and probably also for VirtualBox). You need a newer version of QEMU compiled from
a recent SVN snapshot which allows to specify a cpu type of athlon with 3DNow support.
a recent SVN snapshot which allows to specify a cpu type of athlon with 3DNow support.

:(The VMWare image referenced above by Bert avoids the ''3dNow!'' issue because he substituted a stock Fedora kernel.) --[[User:FGrose|FGrose]] 06:22, 11 January 2009 (UTC)


qemu from the debian experimental repository already (Nov 2008) supports <tt>-cpu athlon</tt> with 3dnow.
qemu from the debian experimental repository already (Nov 2008) supports <tt>-cpu athlon</tt> with 3dnow.

Revision as of 06:22, 11 January 2009

  english | español日本語한국어portuguêsрусский HowTo [ID# 190891]  +/-  
modify 

<< Developers/Setup

laptop-in-laptop

Emulators and Virtual Servers allow you to run a "virtual" computer on any machine.

Strictly speaking, with emulators it is not usually a specific system that is emulated but a generic x86 processor with Sugar, so this emulation has some limits. The customized devices on an XO cannot be emulated, and some peripherals in your PC may not be supported through the emulated XO.

Emulators convert the code written/compiled for a particular system to the host computer's architecture. Virtualisation Servers differ from Emulation by that the code doesn't have to be converted; they run the operating system on the host CPU. Virtualisation is much faster than an emulator because of this.

See the Developer's Manual for a discussion of the merits of various packages and the ways you might want to use emulation in the development process. Keep in mind that emulation is NOT perfect.


Emulators

At present, QEMU is used most frequently. It is both an Emulator and a Virtual Server, and runs on many operating systems.

If you are running Linux, there is an experimental olpc-xo-qemu to simplify using QEMU for emulation. Feedback encouraged. MitchellNCharity 15:03, 6 January 2008 (EST)
If you are running Windows, there is an experimental package to simplify using QEMU for emulation. Feedback encouraged. Mwarren 00:20, 15 November 2008 (UTC)

VMWare is also popular. Bert Freudenberg has created an VMWare image of Release 8.2, Build 767, which he describes in this blog entry.

For Windows, the first comment on the blog page provides instructions on how the archive may be extracted and used.
This image has also been tested successfully with VMWare Server and Player for Linux. --FGrose 07:30, 7 January 2009 (UTC)
For Mac OS X, see this Mac Quick Start tip page.

Release 8.2 and Joyride 2.6.25 kernel-based images require support for AMD's 3DNow! extensions

The 2.6.25 kernel used in the current (Sep 2008) builds checks for the availability of the 3DNow extension and if it does not find it refuses to boot. This makes it impossible to use the current devel-ext3 images under stock QEMU (same for VMWare and probably also for VirtualBox). You need a newer version of QEMU compiled from a recent SVN snapshot which allows to specify a cpu type of athlon with 3DNow support.

(The VMWare image referenced above by Bert avoids the 3dNow! issue because he substituted a stock Fedora kernel.) --FGrose 06:22, 11 January 2009 (UTC)

qemu from the debian experimental repository already (Nov 2008) supports -cpu athlon with 3dnow.

A Windows binary of QEMU compiled from a recent SVN snapshot (svn-4887, 2008-09-24) is available from the OLPC forum at Nabble. More installation details, including libusb0.dll and KQEMU installation, are available on the Emulating the XO/Quick Start/Windows page.

Build recommendations

For running XO disk images on an emulator, you must use an ext3 image, not the JFFS2 image which is for on-board NAND flash memory. =) Please note that the build you want to run may only be available in JFFS2; if so, check older builds. Some builds are better than others and the most recent one will not always work.

OUTDATED status

Please add your own findings to User Feedback on Images.

joyride builds generally work (as of build 1400). Presence service (mesh view and collaboration) won't work by default, because they are configured with a presence service providing jabber server of ship2.jabber.laptop.org, which doesn't yet exist. There is an overloaded and fragile jabber.laptop.org which may be used in the meantime. -- MitchellNCharity 22:42, 14 December 2007 (EST)

Another jabber server alternative is: jabber.xochat.org (typically 60 to 80 people online) --ixo 03:29, 5 January 2008 (EST)
Please be aware that the xochat.org server is also overloaded, and the load is proportional to the product of the number of registrees times the current number of users, for the reasons documented at XMPP_Extensions. So don't connect (and thus automatically register) unless you will really be contributing, and/or set up your own ejabberd server. NealMcBurnett 15:39, 7 January 2008 (EST)

I've had good luck with all of the ship2 builds under VMware Workstation 6. -- Ed Borasky (Znmeb), 15 December 2007.



External links