Re: Jailhouse on OrangePI PC2 and A35/A72 based board
Yes, that is correct.
When starting root cell,
jailhouse enable .cell
Thanks,
Bharat
On 07-Feb-2018 5:39 PM, "Jan Kiszka" wrote:
On 2018-02-07 10:27, bharat gohil wrote:
> Hi
>
> I was trying to Run jailhouse on two board i.e OrangePi PC2 and Quad core
A35/A72 based SoC.
>
> I am able run Jailhouse on OrangePI PC2 and ran simple application on
single core which blinks the LED which works fine on OrangePI PC2 board.
>
> But I have problem running Jailhouse on other board which has A35 and A72.
>
> I got following crash when enable Jailhouse on this board,
>
> Initializing Jailhouse hypervisor v0.8 (9-g5eec601-dirty) on CPU 0
> Code location: 0xc0200060
> Page pool usage after early setup: mem 61/16356, remap 48/131072
> Initializing processors:
> CPU 0... OK
> CPU 1... OK
> CPU 2... OK
> Adding virtual PCI device 00:00.0 to cell "Dione"
> Page pool usage after late setup: mem 66/16356, remap 53/131072
> FATAL: instruction abort at 0x40ebdee8
>
> FATAL: unhandled trap (exception class 0x20)
> Cell state before exception:
> pc: ff80008f0ee8 lr: ff80008f0ee8 spsr: 61c5 EL1
> sp: ffc02f003bb0 esr: 20 1 086
> x0: x1: x2:
> x3: x4: x5:
> x6: x7: x8:
> x9: x10: x11:
> x12: x13: x14:
> x15: x16: x17:
> x18: x19: ff80008f4910 x20: ff801000
> x21: ff801000 x22: x23: 0140
> x24: ff80008f4600 x25: ff8008d26de0 x26: ff801000
> x27: 02c4 x28: ffc02f00 x29: ffc02f003bb0
>
> Parking CPU 2 (Cell: "X")
>
> It generate exception at 0x40ebdee8 which is DDR address.
>
> I have mentioned DDR range including above address in to the root-cell
configuration like this,
> /* RAM */ {
> .phys_start = 0x4000,
> .virt_start = 0x4000,
> .size =0x02FF,
> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE
| JAILHOUSE_MEM_EXECUTE,
> },
>
> Can anyone help me to figure out what is the problem or how to debug and
resolve this issue?
Only the root cell is running at this point, right? There is no overlap
of other regions or the hypervisor region itself?
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.
Re: x86-64 Jailhouse demo image generation using Isar
Am Fri, 9 Feb 2018 16:23:11 +0100 schrieb "[ext] Jan Kiszka" : > 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 > -- 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.
Re: x86-64 Jailhouse demo image generation using Isar
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 -- 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.
x86-64 Jailhouse demo image generation using Isar
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 -- 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.
Re: jailhouse on X86
Am Thu, 8 Feb 2018 04:39:58 -0800 schrieb : > Jan, > I need some information for running jailhouse on x86. > I was able to create rootcell and non rootcell but not able see any > console logs after creating non rootcell. I want to know whether > Jailhouse will support displaying logs on serial console for x86. > Regards, Anil > On x86 your serial consoles are PIO-based. In qemu the two standard serial ports exist, so you always have one for the hypervisor and one for a cell. Real hardware usually does not have two UARTS, often you are lucky if you get one. There is "jailhouse console" to get access to the hypervisor console. If you have at least one UART you can share that between your cells, you might have to allow that cell to access the ports via the pio_bitmap in the config. And when you load the cell you might have to pass arguments to change the default. (look for con-base in README.md) If your machine does not have a UART it might be a good idea to add a serial-PCI card. Henning -- 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.
