We are not quite there yet, but virtual machines always remind me of Star Trek’s Holodeck – a virtual world, where the OS thinks it runs on a real machine, but it can be “paused” at will and shelved away until a later date.
To take advantage of this setup, and to play around with a school server, I have put together a VM of OLPC XS 0.7 This version has been installed, but not configured. To get started:
- Grab and install a copy of your favorite virtualization platform such as VMPlayer or Virtualbox. I use VirtualBox under Ubuntu 12.04 LTS, which is where I built this VM. Your experience with other VM environments may vary.
- Download the OVA file from http://dev.laptop.org/~sverma/xs/olpc-xs-0.7.ova.zip
- Unzip and check the md5sum hash of olpc-xs-0.7.ova. It should be 8eeed031780bc8d2c87915bc48ee27c8
In VirtualBox, go to File | Import Appliance and point to the OVA file. This will import the VM into your machine. Be sure to adjust the RAM etc. to your liking. I’ve set it at 1024MB.
- Start your VM. When booted up, login as root. Password is we’rejammin’ (and I hope you like jammin’ too!)
- As a good administrator, change the password to your liking.
- Remember, this VM is not configured, so set it up.
- For example, xs-setup olpcsf.org will set up your XS to run at schoolserver.olpcsf.org Choose a domain of your liking. Because this is in a VM, and can be turned off at the flick of a switch, anything is ok. Even microsoft.com is ok, but we won’t like you very much.
- Now, we need to set up the networking. The VM comes only with the lo interface. So, run xs-setup-network and this will set up eth0 as the LAN interface. This interface will be spewing IP addresses via DHCP when you reboot the VM. So, before you reboot the VM, set its networking to bridging, and bridge it with the interface that you want it to spew at. For instance, I chose to bridge eth0 in VM and eth0 on my host laptop. That way, if I connect a AP to eth0 on my host laptop, it will be serving IPs to any XO that connects to it. Make sense?
- All set? reboot
- When the VM comes back up, you will see that eth0 now has an IP (the XS runs at this IP). It will also be serving IPs via eth0.
- Next steps? Use your server to test out Moodle. Try adjusting the RAM and CPU allocations and see how the XS behaves. Use your VM to train teachers, impress friends, be a Trekkie and say “Computer, end program“.
- See http://wiki.laptop.org/go/XS_Installing_Software for more.