From: Jan Kiszka
Move all Ethernet-related interface configurations in to a single file.
This should make it easier to keep overview what is already there and
what might have to be added for new targets.
Signed-off-by: Jan Kiszka
---
recipes-core/customizations/customizations.bb | 6 ++
From: Jan Kiszka
This add the last missing pieces to support the Apollo Lake variant of
the Intel NUCs with up to 8GB of RAM. As noted when adding the Jailhouse
bits, this is limited to --latest at this point because of missing
relevant commits in the 0.9.1 release.
The NUC6CAY comes without a
From: Jan Kiszka
The significantly accelerates building ARM and ARM64 images. For us,
there is no reason to build natively.
Signed-off-by: Jan Kiszka
---
kas.yml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kas.yml b/kas.yml
index e7749bf..6ff8e47 100644
--- a/kas.yml
+++ b/kas.yml
From: Jan Kiszka
...as requested by dh.
Signed-off-by: Jan Kiszka
---
recipes-jailhouse/jailhouse/files/debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/recipes-jailhouse/jailhouse/files/debian/control
b/recipes-jailhouse/jailhouse/files/debian/control
index
From: Jan Kiszka
This prepares for multiple targets of the same architecture. This will
have some variations that result in different images.
Signed-off-by: Jan Kiszka
---
build-images.sh | 6 +++---
kas.yml | 2 +-
recipes-core/images/demo-image.bb
This flushes next of the jailhouse-images repo. Probably the most
important change is incorporation of the cross-build support that
upstream Isar just gained. It allows to build all (by now) 4 targets on
a quad-core i7 workstation in about 1:15h.
Futhermore, this adds support for a new target,
From: Jan Kiszka
This tags the images with the layer version and further information from
git as well as provides a proper description. The information can then
be retrieved from /etc/os-release on the target.
Signed-off-by: Jan Kiszka
---
conf/layer.conf | 2 ++
From: Jan Kiszka
Analogously to the kernel, rename the config for qemuamd64 and construct
its name in a python snippet. This will allow to add another machine
for the same architecture which will share the Jailhouse package with
qemuamd64.
Signed-off-by: Jan Kiszka
---
From: Jan Kiszka
This allows to call the script for testing purposes on all available
images without going through the interactive mode.
Signed-off-by: Jan Kiszka
---
build-images.sh | 8
1 file changed, 8 insertions(+)
diff --git a/build-images.sh b/build-images.sh
index
From: Jan Kiszka
The python build dependency needs to be specified as :native, see also
similar change on jailhouse package.
Signed-off-by: Jan Kiszka
---
recipes-core/non-root-initramfs/files/debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jan Kiszka
This requires dedicated configs for the system and the non-root Linux
cell. We only add them for 'latest' because 0.9.1 is lacking the
required EFI framebuffer and further fixes which are needed for this
target. Thus, NUC6CAY will be --latest only.
Signed-off-by: Jan Kiszka
From: Jan Kiszka
This ensures the jailhouse.ko module can also be found when the package
is installed on its own.
Signed-off-by: Jan Kiszka
---
recipes-jailhouse/jailhouse/files/debian/postinst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Jan Kiszka
In case multiple artifacts are found in the deploy directory, use the
ones with the highest version.
Signed-off-by: Jan Kiszka
---
start-qemu.sh | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/start-qemu.sh b/start-qemu.sh
index a9d0e5f..e60add0
From: Jan Kiszka
When cross-compiling, we need to specify the python build dependencies
as :native. Otherwise, the target python packages would be installed,
and they cannot run inside a host-targeted build environment.
Furthermore, ARCH and CROSS_COMPILE now need to be injected into the
build.
From: Jan Kiszka
Helps checking already during the build which revision is used.
Signed-off-by: Jan Kiszka
---
recipes-jailhouse/jailhouse/jailhouse_latest.bb | 5 +
1 file changed, 5 insertions(+)
diff --git a/recipes-jailhouse/jailhouse/jailhouse_latest.bb
From: Jan Kiszka
Apparently not needed, but it will cause issues when cross-build support
is available.
Signed-off-by: Jan Kiszka
---
recipes-core/non-root-initramfs/files/debian/control | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Jan Kiszka
The package already contains machine-specific artifacts. Once we have
multiple machines for the same architecture, also a different package
name will be needed to avoid clashes.
Signed-off-by: Jan Kiszka
---
recipes-core/customizations/customizations.bb | 2 ++
From: Jan Kiszka
This performs several smaller polish steps on the motd output:
- ensure that the initial history content is dumped, irrespective of
commands inserted into the history during runtime
- print "" by using '' as quotes
- wrap long command lines, but only for motd
From: Jan Kiszka
We will add another x86 target that will share the kernel with the
qemuamd64 machine. Prepare for this by renaming the defconfig and
constructing its name during the build in python snippet so that we can
easily add another machine later on.
Signed-off-by: Jan Kiszka
---
From: Jan Kiszka
Switch to a generic CPU type (a reasonable cleanup anyway) and enable
the required drivers, namely IWLWIFI, R8169, EFI framebuffer, USB HID,
and Realtek MMC.
Signed-off-by: Jan Kiszka
---
recipes-kernel/linux/files/x86-64_defconfig | 233
From: Jan Kiszka
Signed-off-by: Jan Kiszka
---
recipes-kernel/linux/files/orangepi-zero_defconfig | 2 +-
recipes-kernel/linux/files/qemuamd64_defconfig | 3 +--
recipes-kernel/linux/files/qemuarm64_defconfig | 3 ++-
recipes-kernel/linux/linux-jailhouse.bb| 6 +++---
4
From: Jan Kiszka
Use latest next which now contains cross-compilation support.
Signed-off-by: Jan Kiszka
---
kas.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kas.yml b/kas.yml
index 64e80c5..e7749bf 100644
--- a/kas.yml
+++ b/kas.yml
@@ -19,7 +19,7 @@ repos:
From: Jan Kiszka
Add the target-specific Jailhouse bash_history and some changes to make
Ethernet as well as ivshmem-net work. Wireless requires a network
specific config that the user has to create/install manually.
Signed-off-by: Jan Kiszka
---
Hi Peng,
Thank you for the answer.
I have inserted a printk in the handle_hvc to check whether it is called when
the driver runs. I could not see any output.
Any other function is executed before and acts as a filter, which does not call
handle_hvc?
Giovani
> >
> > On 2018-08-13 15:15,
2018年8月17日金曜日 1時53分29秒 UTC+9 J. Kiszka:
> On 2018-08-16 18:25, Chung-Fan Yang wrote:
> > Hello,
> >
> > I would like some help. I am trying to accomplish a root <-> non-root cell
> > communication.
> > I followed README.jailhouse in
> > https://github.com/henning-schild-work/ivshmem-guest-code
On 2018-08-16 18:25, Chung-Fan Yang wrote:
Hello,
I would like some help. I am trying to accomplish a root <-> non-root cell
communication.
I followed README.jailhouse in
https://github.com/henning-schild-work/ivshmem-guest-code to build to tools for
the root side and fired the ivshmem-demo
Am Thu, 16 Aug 2018 09:25:38 -0700
schrieb Chung-Fan Yang :
> Hello,
>
> I would like some help. I am trying to accomplish a root <-> non-root
> cell communication. I followed README.jailhouse in
> https://github.com/henning-schild-work/ivshmem-guest-code to build to
> tools for the root side
Hello,
I would like some help. I am trying to accomplish a root <-> non-root cell
communication.
I followed README.jailhouse in
https://github.com/henning-schild-work/ivshmem-guest-code to build to tools for
the root side and fired the ivshmem-demo as the non-root cell.
I can see the
2018年8月17日金曜日 0時02分10秒 UTC+9 Henning Schild:
> Am Thu, 16 Aug 2018 05:52:45 -0700
> schrieb Chung-Fan Yang :
>
> > Hello,
> >
> > I am using jailhouse on my Xeon machine with a super micro
> > motherboard. I was using kernel 4.4, which works fine, but upgraded
> > to kernel 4.13 today.
> >
> >
Am Thu, 16 Aug 2018 05:52:45 -0700
schrieb Chung-Fan Yang :
> Hello,
>
> I am using jailhouse on my Xeon machine with a super micro
> motherboard. I was using kernel 4.4, which works fine, but upgraded
> to kernel 4.13 today.
>
> After the update, when I enable jailhouse, it crashed with
>
>
2018年8月16日木曜日 22時47分26秒 UTC+9 Henning Schild:
> Am Thu, 16 Aug 2018 05:52:45 -0700
> schrieb Chung-Fan Yang :
>
> > Hello,
> >
> > I am using jailhouse on my Xeon machine with a super micro
> > motherboard. I was using kernel 4.4, which works fine, but upgraded
> > to kernel 4.13 today.
> >
> >
Am Thu, 16 Aug 2018 05:52:45 -0700
schrieb Chung-Fan Yang :
> Hello,
>
> I am using jailhouse on my Xeon machine with a super micro
> motherboard. I was using kernel 4.4, which works fine, but upgraded
> to kernel 4.13 today.
>
> After the update, when I enable jailhouse, it crashed with
>
>
Prepares consolidation of arch_cpu_resume/suspend. With this, we have
the same path on all architectures for suspending CPUs. This allows us
to consolidate code in the next step.
Signed-off-by: Ralf Ramsauer
---
hypervisor/arch/arm-common/control.c | 2 +-
On 08/15/2018 11:13 AM, Jan Kiszka wrote:
> On 2018-08-14 12:50, Ralf Ramsauer wrote:
>> Prepares consolidation of arch_cpu_resume/suspend. With this, we have
>> the same path on all architectures for suspending CPUs. This allows us
>> to consolidate code in the next step.
>>
>> Signed-off-by:
34 matches
Mail list logo
