VirtualBox
| modify |
Emulation with VirtualBox
VirtualBox is an emulator released under dual-license as either GPL or commercial software. It runs on either Mac, Win32 or Linux host machines, allowing you to run OLPC images within the virtual machine.
Compatibility
- Official OLPC build 557 is known to work under VirtualBox with both sound and networking (tested on Linux AMD64 host).
- Official OLPC build 625 is known to work under VirtualBox with networking (tested on Ubuntu Gutsy Linux AMD64 host). aptitude install virtualbox virtualbox-ose-modules-2.6.22-14-generic
Caveats
- TamTam's CSound library does not appear to be working with build 557.
- For OLPC work you will likely need to use the GPL VirtualBox release or a purchased copy, as OLPC work does not qualify as either evaluation or personal use. The GPL version does not support the "shared folders" feature. You will need to use samba, ssh, rsync, or another standard Unix mechanism to share files with the image.
- "Personal Use" requires that you use the product on the same Host Computer where you installed it yourself and that no more than one client connect to that Host Computer at a time for the purpose of displaying Guest Computers remotely.[1]. Volunteer OLPC work thus seems likely to qualify as personal use, no? MitchellNCharity 00:57, 2 September 2007 (EDT)
- In any cases, Personal use is when you install the product on one or more PCs yourself and you make use of it (or even your friend, sister and grandmother). It doesn't matter whether you just use it for fun or run your multi-million euro business with it. Also, if you install it on your work PC at some large company, this is still personal use. However, if you are an administrator and want to deploy it to the 500 desktops in your company, this would not qualify as personal use. Well, you could ask each of your 500 employees to install VirtualBox but don't you think we deserve some money in this case? We'd even assist you with any issue you might have. [2] It seems to be "Personal Use" even covers installing the software at work. And same clause goes as far as you can do business with it. Hsaito 23:02, 25 August 2008 (UTC)
- On Linux, VirtualBox setup requires a package of kernel modules
Setup
The VMWare/VirtualBox images are converted from the official images using a simple downloading script. You can either download and convert the official images yourself or use a pre-converted image.
Downloading a Pre-converted Image
Pre-converted images are made available periodically to support those who do not have Qemu's tools installed on their workstations. Choose the .zip file for the version you require.
The pre-converted images do not include VirtualBox Machines. Once you have unzipped the downloaded file, continue working from "Create a new VirtualBox Machine" below...
Building an Image from Scratch
- Download an official devel-ext3 image (<thefile>.img.bz2)
- bunzip2 <thefile>.img.bz2 - or - ( Windows: bzip2 -d <thefile>.img.bz2 using bzip2.exe from http://www.bzip.org/downloads.html )
- VBoxManage convertdd <thefile>.img <thefile>.vdi
- VBoxManage registerimage disk /full/path/to/directory/<thefile>.vdi
Create a new VirtualBox Machine
- OS Type Linux 2.6
- Base Memory 512 (recommended for development work, 256 more closely simulates an XO)
- Boot disk, "Existing", choose
- <thefile>.vdi (if using hand-built image)
- <thefile>.vmdk (if using pre-built image)
Edit "Machine" Settings:
- Choose "Audio", "Enable Audio",
- "ALSA Audio Driver" (for linux hosts)
- "DirectSound Driver" (for Windows hosts)
by kupito
Configure
Once you have booted the machine, you will need to specify a name for yourself and choose an XO colour. You will then need to configure the collaboration server. To do this, pull up the developer's console (<alt>+<=>), and use the "vi" or "nano" editor to change the configuration file ~/.sugar/default/config /home/olpc/.sugar/default/config to change the "server=" line to "server=olpc.collabora.co.uk".
If the GUI does not come up after choosing XO color: ctrl-alt-f2 to get to command prompt, login as root, make the change above and then reboot.
When this is done, reboot. The virtual XO should now have networking and sound support and should show you a network view with other XOs logged on.