[okl4-developer] 2.1 Ubuntu VMware VM

[Geoff White]

>
> I have a 2.1 based VMware VM that has a fully installed Ubuntu 8.04 desktop
> system with OKL4 and OKLinux sources installed along with the appropriate
> toolchain. The OKLinux kernel  configs and some of the sources are modified
> a little to enable LANCE ethernet support so the target VM can actually
> communicate with the outside world if you are running it under VMware
> Workstation/Player or ESX.  The compressed tar ball is 1.5GB.  I'd like to
> turn this over to OK-Labs or get it up on the wiki as a torrent.  What
> shoukd the next step be?  Here is the README.txt...


How to use this package to do OKL4 development.
------------------------------------------------

Hello, if your reading this, chances are that you have successfully booted
up the OKL4 VM that runs under VMware platforms:  The package contains:

    oklinux.vmx - virtual machine definition for an Ubuntu 8.04 VM that
            acts as the "development" platform for the 2.1
release of OKL4 and OKLinux

    oklinux.vmdk - the Virtual disk that contains all of the software
            oklinux-s00x.vmdk - upto 2G "segments containing the
    virtual disk for the Ubuntu system

    iguana-vm.vmx - virtual machine definition for the intel IA32
        "target" machine
    iguana-vm.vmdk, iguana-vm-flat.vmdk  - 100MB virtual disk that will
            hold the bootable OKL4 image

There may be other files in the directory, but these are the files that are
absolutely necessary for development to take place.

This directory is a little different from the typical VMware VM directory.
It actually contains TWO VMs, one is the development machine, one is fhe
target.  The directory contains TWO .vmx definitions as well as TWO virtual
disks.  Note tht the iguana-vm.vmdk is "shared" between the two VMs, BUT
NEVER WHEN BOTH VMS are powered on at the same time. Essentially we start up
the development VM with the iguana-vm.vmdk connected, we build our target
image, and load it onto this disk, urrently via the command:

dd if=.../build/image/c.img of=/dev/sdb bs=1024

Thic creates a bootable image that the iguana-vm will boot from when it is
powered on.  This disk is ALWAYS connected to the iguana-vm Virtual Machine,
but only connected to the oklinux VM when you are loading a compiled image
onto this disk to be used y the iguana-vm.

You can build the basic OKL4 with OKLinux by executing the script
./buildme

in the okl4_2.1 directory.  It will build everything in okl4_2.1/build and
start up the image in the qemu emulator.
To break out of the qemu emulator, perform cntl-a-x

You can do some basic testing via Qemu, when you are ready,
cd build/images
dd if=c.img of=/dev/sdb bs=1024

when this completes, shutdown the development machine. When  it's powered
off, edit settings and remove the iguana-vm.vmdk (100MB) from the oklinux VM
definition.  Once you have done that, you can power on the oklinux VM and
when it is completely booted up, open Gtkterm, this is connected to
/dev/ttys0 of the development machine, the other side is (virtually)
connected to /dev/ttys0 of the target VM, iguana-vm.  Now, if your using
Vmware workstation, go to File->Open-> browse to
oklinux->iguana-vm->iguana-vm.vmx
checkto make sure the 100MB iguana-vm disk is connected. Power on this VM
and then switch back to the oklinux console, you should see output spewing
out of the Gtkterm window and, if your lucky, a # prompt  when the spew
stops ;)


How to change and remake the kernel for OKLinux
------------------------------------------------

make sure to add ncurses support to your version of ubuntu


cd linux/kernel-2.6.23-v2/
then copy l4linux_config_<arch> to .config
make menuconfig ARCH=l4 SYSTEM=i386
select your desired configuration with the curses gui
then copy .config to l4_linux_config_ia32_whatever
make mrproper

And add some code to tools/machines.py for a new target using your new
linux configuration file.

To enable DMA so that the VMware virtual ethernet device can perform DMA...
commented out the BUG() assert on line 149 in
.../include/asm-l4/i386/dma-mapping.h
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.okl4.org/pipermail/developer/attachments/20080610/6f867341/attachment.htm