VirtualBox/Preparing a disk image

Instructions for preparing a VirtualBox disk image from a SoaS iso image file.

(Taken from Dave Bauer's posting at http://schools.sugarlabs.org/mod/forum/discuss.php?d=27.)

Create a new VM.
Choose Linux->Fedora
Choose 256MB
Create a new disk image, 2GB
Finish.
Download the lastest SoaS, http://download.sugarlabs.org/soas/snapshots/2/?C=M;O=D, for Fedora-11-beta.
Mount SoaS ISO as a CD-ROM in the newly created VM.
Change Network Adapter to Intel Pro/1000 MT Desktop (82540EM)
- recommended by VirtualBox for modern hosts -- Default of PCnet-FAST III (Am79C973) also worked on Ubuntu 8.10 and Vista hosts.
- Select Attached to: Host Interface -- allows local networking for SSH connections to probe the file system.
Boot VM
Type you name and startup Sugar.
Open Terminal.
su -
parted /dev/sda
mklabel msdos -- make partition table
mkpartfs primary ext2 0 2048
toggle 1 boot
quit
umount /dev/sda1 -- F-11 auto mounts the disk, so unmount it for the next script
/mnt/live/LiveOS/livecd-iso-to-disk --overlay-size-mb 256 --home-size-mb 256 /dev/sr0 /dev/sda1
- the --overlay-size-mb NNN option creates space for persistence of changes on the disk; otherwise, a liveOS disk is read-only.
- the --home-size-mb NNN option creates space for saving the /home/liveuser folder if you want to update the OS image while keeping the user files. In this case, skip the new disk creation and parted steps and leave out the --home-size-mb NNN option at this step and continue on. ~~(This option causes login problems on VirtualBox with the liveuser account and should be skipped for now.)~~
shutdown -h now
Unmount CDROM in Vbox config
Boot VM
Open Terminal
su -
yum install dkms gcc make ppl binutils glibc-devel glibc-headers kernel-headers kernel-devel

Soas2-20090325 (Fedora 10.92) fails on VirtualBox at this point for lack of disk expansion. See this bug report (Trac #633).

go to VirtualBox Devices Menu->Install Guest Additions
mkdir /mnt/cdrom
mount /dev/sr0 /mnt/cdrom
cd /mnt/cdrom
./VBoxLinuxAdditions-x86.run
- (This stalled on two trials; had to reboot and restart.)
- If upgrading from one VirtualBox version to another, start with fresh virtual disks and machines built with the new versions to avoid breakage.
reboot
Edit /etc/X11/xorg.conf to match the following section: (This is for 1200x900 (XO) and other resolutions.)

# Default xorg.conf for Xorg 1.5+ without PCI_TXT_IDS_PATH enabled.
#
# This file was created by VirtualBox Additions installer as it
# was unable to find any existing configuration file for X.
 
Section "Device"
       Identifier "VirtualBox Video Card"
       Driver "vboxvideo"
EndSection
#
# From example in section 4.3.2 of the VirtualBox Help manual:
#
Section "Screen"
       Identifier "Default Screen"
       Device "VirtualBox Video Card"
       Monitor "Generic Monitor"
       DefaultDepth 16
       SubSection "Display"
               Depth 16
               Modes "1200x900" "1024x768" "800x600" "640x480"
       EndSubSection
EndSection

Finally,

Open Terminal
Terminal
rm -rf ~/.sugar (if distributing image)
su -
shutdown -h now
Now you can share the VDI file.

It would be wise to maintain a clone of your virtual disk image to restart if the working copy is damaged:

From host command line (Windows cmd, or Linux terminal) See VirtualBox Help section 8.14.
- VBoxManage clonehd <uuid>|<filename> <outputfile> [-format VDI|VMDK|VHD|RAW|<other>] [-remember]
Reclone any virtual hard disks you would like to archive.

To enable SSH communications, we need to open the firewall for SSH, permit no password for the ssh deamon, and start the sshd service:

in Terminal,
su -
system-config-firewall
1. close the startup warning dialog
2. check mark the SSH service
3. click the apply action button, approve change
4. File>Quit
pico /etc/ssh/sshd_config
1. [add] PermitEmptyPasswords yes
2. ^O (WriteOut), <Enter> on File Name to Write: /etc/ssh/sshd_config , ^X (Exit)
chkconfig --level 345 sshd on
service sshd start