Hi,

Above steps given by Peter Chubb worked fine. I was able to get the output
through serial port.

But it executes the test suite and then stops. How can I get a shell prompt
so that I can test the kernel for virtualization?

My question may be completely wrong here but I'm new to this field. How can
one use seL4 kernel to install virtual OS on top of it on x86 architecture?


On Fri, Sep 5, 2014 at 5:10 AM, Peter Chubb <[email protected]>
wrote:

> >>>>> "Matthew" == Matthew Scaperoth <[email protected]> writes:
>
>
> Matthew> I am at the George Washington University working on
> Matthew> benchmarking the seL4 system. I am new to systems, and I am
> Matthew> having a hard time building a bootable USB image On Ubuntu
> Matthew> 14.04 x86. I understand that there is a Grub2 stanza on the
> Matthew> Downloads page <https://sel4.systems/Download/> on the SeL4
> Matthew> website, but I cannot find the sel4kernel and sel4rootserver
> Matthew> files in the system to build into a boot image.
>
> If you have built a seL4-based systemaccording to the instructions, the
> kernel and root server are in .../images/  They have different names
> according to what you've built.
>
> For example, sel4test names the root server
> sel4test-driver-image-ia32-pc99 and the kernel kernel-ia32-pc99
>
> I generally use syslinux to create a bootable USB stick, as the grub
> on my system wants to use EFI.
>
> Like this, assuming your flash drive is at /dev/sdb with a FAT
> partition at /dev/sdb1:
>
>   install-mbr /dev/sdb
>   syslinux --install /dev/sdb1
>   mount /dev/sdb1 /mnt
>   cp images/sel4test-driver-image-ia32-pc99 /mnt/rootserver
>   cp images/kernel-ia32-pc99 /mnt/sel4kernel
>   cat > /mnt/syslinux.cfg <<EOF
>   SERIAL 0 115200
>   DEFAULT seL4test
>   LABEL seL4test
>     kernel mboot.c32
>     append sel4kernel --- rootserver
>   EOF
>   cp /usr/lib/syslinux/modules/bios/mboot.c32 /mnt
>   cp /usr/lib/syslinux/modules/bios/libcom32.c32 /mnt
>   umount /mnt
>
>   use fdisk to make sure the first partition is bootable.
>
> And you're done.  Output will come on the serial port
>
>
> Hope this helps.
> --
> Dr Peter Chubb                                  peter.chubb AT
> nicta.com.au
> http://www.ssrg.nicta.com.au          Software Systems Research
> Group/NICTA
>
> _______________________________________________
> Devel mailing list
> [email protected]
> https://sel4.systems/lists/listinfo/devel
>



-- 
Aniruddha Bhide
+919970010287
_______________________________________________
Devel mailing list
[email protected]
https://sel4.systems/lists/listinfo/devel

Reply via email to