Some news about the AVATT BIOS


It’s been a long time since my last post… many happened in the meanwhile, but I almost forgot about this blog.

This time I’ll talk again about my progress on the AVATT project, at whichI worked ever since last summer’s GSoC. I got it built with KVM support (using buildrom), and I achieved starting an OpenBSD ISO image inside it. Soon after the boot, the image crashes with a strange error message, caused by missing Thread Local Storage(TLS) support from uClibc. The image also contains busybox and ncurses, and its compressed size is just a bit under 2MBytes.

Since the uClibc developers haven’t yet developed TLS support (and think I’m not yet ready to do it myself), I decided to move on to another virtualization software, namely OpenVZ. To ease my work – which previously suffered from buildrom’s way of compiling the coreboot payload, that is not a cross-compiling toolchain so everything was made to compile using hackish compiler flags – I also decided to switch to a real toolchain, namely Buildroot. This eases a lot the process of compiling a Linux userland payload, making a lot easier the lives of those who want to make something similar to LBDistro.

So, now I’m working on porting AVATT to OpenVZ. I currently have a ROM image containing a kernel patched with OpenVZ support, and I’m working on the vzctl port to buildroot. See the AVATT wiki page for more, or maybe you can try it yourself, building it from source.

Stay tuned…there’s more to come soon!



2 thoughts on “Some news about the AVATT BIOS

  1. I got trouble building buildroot with wrong use of lzma on rootfs using your -git_avatt_clone
    can you email me ,I will send you the tail_err_msg
    thank you

    • Hello wangji,
      A possible reason could be that your payload won’t fit in your ROM image. Make sure your image is at least 2MB, but for certain configurations even more may be needed. Try with 4MB and report if it works.

      Please email me that log, maybe I can figure it out easier.

      Thanks for your comment,

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s