From: Henning Schild <henning.schild@siemens.com>
To: "[ext] Jan Kiszka" <jan.kiszka@siemens.com>
Cc: 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 18:13:41 +0100 [thread overview]
Message-ID: <20180209181341.341d5331@mmd1pvb1c.ad001.siemens.net> (raw)
In-Reply-To: <f6422971-d8c4-dcfa-04cb-cf224c1ed6dd@siemens.com>
Am Fri, 9 Feb 2018 16:23:11 +0100
schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
> 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
Works as expected, cool!
> - log into the machine (root/root) and play with Jailhouse
That was a little tricky, but "dpkg -L jailhouse" told me where to look
for some of the files i needed.
> Jailhouse config files are installed under /etc/jailhouse, inmate
> images /usr/libexec/jailhouse/demos.
And now i read this ... ok my bad for not reading my mails carefully ;).
Henning
> Jan
>
> [1] https://github.com/siemens/jailhouse-images
>
prev parent reply other threads:[~2018-02-09 17:13 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
2018-02-09 17:13 ` Henning Schild [this message]
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=20180209181341.341d5331@mmd1pvb1c.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jailhouse-dev@googlegroups.com \
--cc=jan.kiszka@siemens.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