On 13.02.19 13:00, Henning Schild wrote:
Am Wed, 13 Feb 2019 07:54:54 +0000
schrieb Burak Atalay <burak.ata...@rohde-schwarz.com>:
Hello everyone,
I am trying to run a non-root Linux cell, however I am encountering
an error. I followed the documentation and I am using your modified
Linux kernel from queues/jailhouse. When I issue the command
"jailhouse cell linux
configs/x86/linux-x86-demo.cell /path/to/bzImage" I get the following
error:
FATAL: Unhandled MSR write: c8f
RIP: 0xffffffff9646c084 RSP: 0xffffa9ea41a2be08 FLAGS: 246
RAX: 0x0000000000000000 RBX: 0xffff9b46e06fe000 RCX:
0x0000000000000c8f RDX: 0x0000000000000000 RSI: 0x0000000000000000
RDI: 0x0000000000000c8f CS: 10 BASE: 0x0000000000000000 AR-BYTES:
a09b EFER.LMA 1 CR0: 0x0000000080050033 CR3: 0x00000001c920a001
CR4: 0x00000000003626e0 EFER: 0x0000000000000d01
Parking CPU 1 (Cell: "RootCell")
Ignoring NMI IPI to CPU1
At this point the machine is still functional, when I issue a
"jailhouse cell list" command I see the following:
ID Name State Assigned CPUs Failed
CPUs 0 RootCell Running
0-31 1 1 linux-x86-demo
invalid 1-3 1
However I am unable to shutdown or destroy the linux cell with
respective shutdown and destroy commands. Since I failed to run a
non-root Linux cell, I tried to run the other demo cells, like
tiny-demo and apic. When I issue the command "jailhouse cell create
configs/x86/tiny-demo.cell" I get the following error:
FATAL: Unhandled MSR write: c8f
RIP: 0xffffffffafe6c084 RSP: 0xffffb302c1a5be08 FLAGS: 246
RAX: 0x0000000000000000 RBX: 0xffff89b4e069f000 RCX:
0x0000000000000c8f RDX: 0x0000000000000000 RSI: 0x0000000000000000
RDI: 0x0000000000000c8f CS: 10 BASE: 0x0000000000000000 AR-BYTES:
a09b EFER.LMA 1 CR0: 0x0000000080050033 CR3: 0x00000001a1c0a001
CR4: 0x00000000003626e0 EFER: 0x0000000000000d01
Parking CPU 2 (Cell: "RootCell")
Ignoring NMI IPI to CPU2
Since the errors for both non-root cells are similar, my assumption
is that the problem is not related to my config file for the Linux
cell or the kernel. In any case, I am attaching my sysconfig for the
root cell, the data collected by "jailhouse config collect", and my
config file for the Linux kernel.
Could you help me with this issue?
From the MSR i would guess CONFIG_INTEL_RDT in both your kernels. If
you look up the RIP in the System.map of your kernel, you be able to
find out which code caused the access.
The MSR is IA32_PQR_ASSOC
I did not look into the details of the feature. Your options are:
- Allow access to the MSR, after an assessment whether that is a good
idea
- disable the feature in the kernels
The latter is the safe answer: Jailhouse owns this resource and should manage it
(we support L3 CAT). We do not virtualize it, so the guest needs to step aside.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
--
You received this message because you are subscribed to the Google Groups
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
