public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Jailhouse <jailhouse-dev@googlegroups.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: x86-64 Jailhouse demo image generation using Isar
Date: Fri, 9 Feb 2018 16:43:19 +0100	[thread overview]
Message-ID: <e53760da-b8d8-4ac8-9226-9046bc54c48f@siemens.com> (raw)
In-Reply-To: <f6422971-d8c4-dcfa-04cb-cf224c1ed6dd@siemens.com>

On 2018-02-09 16:23, Jan Kiszka wrote:
> Hi all,
> 
> cross-posting to two communities as this is of common interested:
> 
> I've just uploaded a new side-project of Jailhouse. It's called
> jailhouse-images [1], and it aims at generating all what is required to
> try out Jailhouse in QEMU/KVM environment.
> 
> It does this by using the Isar image builder for Debian. So this project
> may also serve the Isar project as reference and test case.
> 
> I didn't write a README yet, but the project is almost self explaining:
> 
> - make sure you have docker installed and can launch privileged
>   containers and qemu-system-x86_64 in a recent version (2.9 is fine
>   e.g.)
> 
> - clone the jailhouse-images project [1]
> 
> - run ./build-images.sh (takes about 15 minutes on a decent notebook
>   with decent Internet)
> 
> - run ./start-qemu.sh x86
> 
> - log into the machine (root/root) and play with Jailhouse
> 
> Jailhouse config files are installed under /etc/jailhouse, inmate images
> /usr/libexec/jailhouse/demos.
> 
> Jan
> 
> [1] https://github.com/siemens/jailhouse-images
> 

Forgot to mention some things:

1. Feedback if the whole setup works for others would be very welcome!

2. This actually stresses yet another OSS project of us: kas [2]. It's
   being used for Isar layer configuration management and bitbake setup
   along with its build container kasproject/kas-isar for Isar.

3. One already planned feature for jailhouse-images is support for a
   qemu-amd64 image, probably also stressing qemu-static vs. cross build
   support.

We could also include support for bootable images of some of our
reference boards at some point, but we will need some more tuning on
Isar for that first (on wic in particular). And, eventually, this
builder could spit out images for automated tests as well.

Jan

[2] https://github.com/siemens/kas

-- 
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-02-09 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09 15:23 Jan Kiszka
2018-02-09 15:43 ` Jan Kiszka [this message]
2018-02-09 17:13 ` Henning Schild

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e53760da-b8d8-4ac8-9226-9046bc54c48f@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jailhouse-dev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox