Re: ioremap error while loading non rootcell

2018-08-02 Thread anilappana 
On Friday, July 6, 2018 at 4:29:37 PM UTC+5:30, J. Kiszka wrote:
> On 2018-07-06 09:39, anilapp...@gmail.com wrote:
> > On Thursday, July 5, 2018 at 7:59:49 PM UTC+5:30, J. Kiszka wrote:
> >> On 2018-07-05 14:24, anilapp...@gmail.com wrote:
> >>> On Wednesday, June 27, 2018 at 11:03:19 PM UTC+5:30, J. Kiszka wrote:
>  On 2018-06-27 19:21, anilapp...@gmail.com wrote:
> > On Tuesday, June 26, 2018 at 2:55:36 PM UTC+5:30, J. Kiszka wrote:
> >> On 2018-06-26 09:16, anilapp...@gmail.com wrote:
> >>> On Monday, June 25, 2018 at 9:27:11 PM UTC+5:30, J. Kiszka wrote:
>  On 2018-06-25 15:09, anilapp...@gmail.com wrote:
> > Please find the error log and config file
> > Error Log:
> > 
> > [root@beast jailhouse]# jailhouse cell linux 
> > configs/x86/6gb-non-rootcell.cell ../images/bzImage-redhawk -i 
> > ../images/initrd-full.img -c "console=ttyS0,115200 8250.nr_uarts=1"
> >
> > Traceback (most recent call last):
> >   File "/usr/local/libexec/jailhouse/jailhouse-cell-linux", line 
> > 859, in 
> > cell = JailhouseCell(config)
> >   File "/usr/local/libexec/jailhouse/jailhouse-cell-linux", line 
> > 780, in __init__
> > raise e
> > IOError: [Errno 22] Invalid argument
> >
> > This is what i added in non-root-cell config
> > -
> >
> > /* high RAM - 1 */ {
> > .phys_start = 0x40410,
> > .virt_start = 0x0020,
> > .size = 0x6000,
> > .flags = JAILHOUSE_MEM_READ | 
> > JAILHOUSE_MEM_WRITE |
> > JAILHOUSE_MEM_EXECUTE | 
> > JAILHOUSE_MEM_DMA |
> > JAILHOUSE_MEM_LOADABLE,
> > },
> > /* high RAM - 2 */ {
> > .phys_start = 0x46410,
> > .virt_start = 0x1,
> > .size = 0x6000,
> > .flags = JAILHOUSE_MEM_READ | 
> > JAILHOUSE_MEM_WRITE |
> > JAILHOUSE_MEM_EXECUTE | 
> > JAILHOUSE_MEM_DMA |
> > JAILHOUSE_MEM_LOADABLE,
> > },
> > /* high RAM - 3*/ {
> > .phys_start = 0x4C410,
> > .virt_start = 0x18000,
> > .size = 0x6000,
> > .flags = JAILHOUSE_MEM_READ | 
> > JAILHOUSE_MEM_WRITE |
> > JAILHOUSE_MEM_EXECUTE | 
> > JAILHOUSE_MEM_DMA |
> > JAILHOUSE_MEM_LOADABLE,
> > },
> >
> > I have attached my non-root cell config can you please take a look 
> > at once.
> 
>  And the very same command line with the very same binaries loads and
>  runs the kernel when you just leave out that last memory region?
> 
> 
>  Please also write out the config that "cell linux" generates:
> 
>  jailhouse cell linux configs/x86/6gb-non-rootcell.cell ../images \
>  /bzImage-redhawk -i ../images/initrd-full.img \
>  -c "console=ttyS0,115200 8250.nr_uarts=1" -w boot.config
> 
>  Interesting is the output of the command as it lists the individual 
>  load
>  steps to be executed, specifically the target addresses.
> 
>  Jan
> 
>  -- 
>  Siemens AG, Corporate Technology, CT RDA IOT SES-DE
>  Corporate Competence Center Embedded Linux
> >>>
> >>> Hi Jan,
> >>> Yes, If I leave out the last memory region every thing work. But if I 
> >>> include this region we are getting above error from the tool( 
> >>> jailhouse cell-linux).
> >>>
> >>> I run below command to get individual load steps. In both cases it 
> >>> shows same
> >>> addresses.
> >>>
> >>> jailhouse cell linux configs/x86/6gb-non-rootcell.cell 
> >>> ../images/bzImage-redhawk -i ../images/initrd-full.img -c 
> >>> "console=ttyS0,115200 8250.nr_uarts=1" -w boot.conf 
> >>> Boot parameters written. Start Linux with the following commands 
> >>> (adjusting paths as needed):
> >>>
> >>> jailhouse cell create configs/x86/6gb-non-rootcell.cell
> >>> jailhouse cell load non-rootcell-1 linux-loader.bin -a 0x0 
> >>> ../images/bzImage-redhawk -a 0xffba00 ../images/initrd-full.img -a 
> >>> 0x63f5000 boot.conf -a 0x1000
> >>> jailhouse cell start non-rootcell-1
> >>
>

size limit of non rootcell

2018-08-02 Thread anilappana 
Hi jan,
what is the size limit of non rootcell that I can load. It was mentioned that 
up to 2GB. But I could load till 1.9GB only.
Regards,
Anil

-- 
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: virtual network interface on x86

2018-04-12 Thread anilappana 
On Monday, April 9, 2018 at 4:37:28 PM UTC+5:30, J. Kiszka wrote:
> On 2018-04-09 13:04, anilapp...@gmail.com wrote:
> > On Monday, April 9, 2018 at 11:55:26 AM UTC+5:30, J. Kiszka wrote:
> >> On 2018-04-08 11:59, anilapp...@gmail.com wrote:
> >>> On Saturday, April 7, 2018 at 3:24:13 PM UTC+5:30, Jan Kiszka wrote:
>  On 2018-04-07 06:01, anilapp...@gmail.com wrote:
> > Hi Henning,
> > Thanks for understanding our issue for ready to help us. I want to 
> > inform one more failure which we observed we after non rootcell bootup( 
> > it shows io remap failed).
> >
> >
> >
> > 0.403714] cpuidle: using governor ladder
> > [0.412705] cpuidle: using governor menu
> > [0.416813] PCI: Using configuration type 1 for base access
> > [0.422401] PCI: ashok JH PCI MMCONFIG
> > [0.426159] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
> > 0x8000-0x8fff] (base 0x8000)
> > [0.435469] [ cut here ]
> > [0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121 
> > __ioremap_caller+0x286/0x360
> > [0.448536] ioremap on RAM at 0x8000 - 0x8fff
> > [0.454974] Modules linked in:
> > [0.458050] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
> > 4.9.47-rt37+-RedHawk-7.4-custom #27
> > [0.466216]  c962bd10 8155da23 c962bd60 
> > 
> > [0.473666]  c962bd50 81077d1b 0079 
> > 1000
> > [0.481119]  0002 81d95e3f 8000 
> > 
> > [0.488573] Call Trace:
> > [0.491021]  [] dump_stack+0x85/0xc2
> > [0.496159]  [] __warn+0xcb/0xf0
> > [0.500945]  [] ? pci_mmcfg_arch_map+0x2f/0x70
> > [0.506947]  [] warn_slowpath_fmt+0x4f/0x60
> > [0.512685]  [] __ioremap_caller+0x286/0x360
> > [0.518510]  [] ? vprintk_default+0x29/0x40
> > [0.524249]  [] ? printk+0x48/0x50
> > [0.529213]  [] ? pcibios_resource_survey+0x70/0x70
> > [0.535641]  [] ioremap_nocache+0x17/0x20
> > [0.541205]  [] pci_mmcfg_arch_map+0x2f/0x70
> > [0.547029]  [] pci_mmcfg_arch_init+0x1d/0x42
> > [0.552941]  [] jailhouse_pci_arch_init+0x40/0x44
> > [0.559197]  [] pci_arch_init+0x3b/0x66
> > [0.564588]  [] do_one_initcall+0x50/0x190
> > [0.570238]  [] ? parse_args+0x26a/0x3f0
> > [0.575717]  [] kernel_init_freeable+0x1cf/0x257
> > [0.581887]  [] ? rest_init+0x90/0x90
> > [0.587102]  [] kernel_init+0xe/0x120
> > [0.592321]  [] ret_from_fork+0x2a/0x40
> > [0.597728] ---[ end trace 38a36dc7a73d77e3 ]---
> > [0.602349] PCI: can't map MMCONFIG at [mem 0x8000-0x8fff]
> > [0.609402] kworker/u4:4 (63) used greatest stack depth: 13512 bytes 
> > left
> >
> >
> > I attached complete logs for your reference. we will try with what ever 
> > the inputs you gave to us and will let you know. I am also sharing 
> > rootcell and non root cell configs which we are using.
> 
>  You configured a conflict here: The shared memory region is also a RAM
>  region for the cell.
> 
>  Jan
> >>>
> >>> Jan,
> >>> we added below region for shared memory
> >>>
> >>>.phys_start = 0x40410, 
> >>>   
> >>>  .virt_start = 0x40410, 
> >>>.size = 0x10, 
> >>> This is not RAM region. I attached iomem file for by Machine. Can you 
> >>> please check.
> >>>
> >>
> >> Ah, sorry, it's not the shared memory, it's the MMCONFIG region:
> >>
> >> [0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121 
> >> __ioremap_caller+0x286/0x360
> >> [0.448536] ioremap on RAM at 0x8000 - 0x8fff
> >>
> >> because of (fixed)
> >>
> >>.platform_info = {
> >>.pci_mmconfig_base = 0x8000,
> >>.pci_mmconfig_end_bus = 0xff,
> >>
> >>
> >> vs. 
> >>
> >>/* high RAM */ 
> >>{
> >> .phys_start = 0x40430/*0x40110*/,
> >> .virt_start = 0x0020,
> >> .size = 0xC000, /*1GB*/
> >> /*.size = 0x3200, */   /*800MB try*/   
> >> /*0x1BF0, 400MB rajmohan*/ /*0xC80*/
> >> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
> >>JAILHOUSE_MEM_EXECUTE | JAILHOUSE_MEM_DMA |
> >>JAILHOUSE_MEM_LOADABLE,
> >>},
> >>
> >> BTW, I would recommend to cleanup your configs. They are... hard to read
> >> now.
> >>
> >> Jan
> >> -- 
> >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> >> Corporate Competence Center Embedded Linux
> > 
> > Hi

Re: virtual network interface on x86

2018-04-09 Thread anilappana 
On Monday, April 9, 2018 at 11:55:26 AM UTC+5:30, J. Kiszka wrote:
> On 2018-04-08 11:59, anilapp...@gmail.com wrote:
> > On Saturday, April 7, 2018 at 3:24:13 PM UTC+5:30, Jan Kiszka wrote:
> >> On 2018-04-07 06:01, anilapp...@gmail.com wrote:
> >>> Hi Henning,
> >>> Thanks for understanding our issue for ready to help us. I want to inform 
> >>> one more failure which we observed we after non rootcell bootup( it shows 
> >>> io remap failed).
> >>>
> >>>
> >>>
> >>> 0.403714] cpuidle: using governor ladder
> >>> [0.412705] cpuidle: using governor menu
> >>> [0.416813] PCI: Using configuration type 1 for base access
> >>> [0.422401] PCI: ashok JH PCI MMCONFIG
> >>> [0.426159] PCI: MMCONFIG for domain  [bus 00-ff] at [mem 
> >>> 0x8000-0x8fff] (base 0x8000)
> >>> [0.435469] [ cut here ]
> >>> [0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121 
> >>> __ioremap_caller+0x286/0x360
> >>> [0.448536] ioremap on RAM at 0x8000 - 0x8fff
> >>> [0.454974] Modules linked in:
> >>> [0.458050] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 
> >>> 4.9.47-rt37+-RedHawk-7.4-custom #27
> >>> [0.466216]  c962bd10 8155da23 c962bd60 
> >>> 
> >>> [0.473666]  c962bd50 81077d1b 0079 
> >>> 1000
> >>> [0.481119]  0002 81d95e3f 8000 
> >>> 
> >>> [0.488573] Call Trace:
> >>> [0.491021]  [] dump_stack+0x85/0xc2
> >>> [0.496159]  [] __warn+0xcb/0xf0
> >>> [0.500945]  [] ? pci_mmcfg_arch_map+0x2f/0x70
> >>> [0.506947]  [] warn_slowpath_fmt+0x4f/0x60
> >>> [0.512685]  [] __ioremap_caller+0x286/0x360
> >>> [0.518510]  [] ? vprintk_default+0x29/0x40
> >>> [0.524249]  [] ? printk+0x48/0x50
> >>> [0.529213]  [] ? pcibios_resource_survey+0x70/0x70
> >>> [0.535641]  [] ioremap_nocache+0x17/0x20
> >>> [0.541205]  [] pci_mmcfg_arch_map+0x2f/0x70
> >>> [0.547029]  [] pci_mmcfg_arch_init+0x1d/0x42
> >>> [0.552941]  [] jailhouse_pci_arch_init+0x40/0x44
> >>> [0.559197]  [] pci_arch_init+0x3b/0x66
> >>> [0.564588]  [] do_one_initcall+0x50/0x190
> >>> [0.570238]  [] ? parse_args+0x26a/0x3f0
> >>> [0.575717]  [] kernel_init_freeable+0x1cf/0x257
> >>> [0.581887]  [] ? rest_init+0x90/0x90
> >>> [0.587102]  [] kernel_init+0xe/0x120
> >>> [0.592321]  [] ret_from_fork+0x2a/0x40
> >>> [0.597728] ---[ end trace 38a36dc7a73d77e3 ]---
> >>> [0.602349] PCI: can't map MMCONFIG at [mem 0x8000-0x8fff]
> >>> [0.609402] kworker/u4:4 (63) used greatest stack depth: 13512 bytes 
> >>> left
> >>>
> >>>
> >>> I attached complete logs for your reference. we will try with what ever 
> >>> the inputs you gave to us and will let you know. I am also sharing 
> >>> rootcell and non root cell configs which we are using.
> >>
> >> You configured a conflict here: The shared memory region is also a RAM
> >> region for the cell.
> >>
> >> Jan
> > 
> > Jan,
> > we added below region for shared memory
> > 
> >.phys_start = 0x40410,   
> > 
> >  .virt_start = 0x40410, 
> >.size = 0x10, 
> > This is not RAM region. I attached iomem file for by Machine. Can you 
> > please check.
> > 
> 
> Ah, sorry, it's not the shared memory, it's the MMCONFIG region:
> 
> [0.440098] WARNING: CPU: 0 PID: 1 at arch/x86/mm/ioremap.c:121 
> __ioremap_caller+0x286/0x360
> [0.448536] ioremap on RAM at 0x8000 - 0x8fff
> 
> because of (fixed)
> 
>   .platform_info = {
>   .pci_mmconfig_base = 0x8000,
>   .pci_mmconfig_end_bus = 0xff,
> 
> 
> vs. 
> 
>/* high RAM */ 
>{
> .phys_start = 0x40430/*0x40110*/,
> .virt_start = 0x0020,
> .size = 0xC000, /*1GB*/
> /*.size = 0x3200, */  /*800MB try*/   
> /*0x1BF0, 400MB rajmohan*/ /*0xC80*/
> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
>   JAILHOUSE_MEM_EXECUTE | JAILHOUSE_MEM_DMA |
>   JAILHOUSE_MEM_LOADABLE,
>},
> 
> BTW, I would recommend to cleanup your configs. They are... hard to read
> now.
> 
> Jan
> -- 
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux

Hi Jan,

>From the above config, pci_mmconfig_base = 0x8000(2GB)  & phys_start = 
>0x40430, size is 0xC000 (1GB)Our hypervisor start addresses is 
>0x4(16Gb).
How will they conflict?
Regards,
Anil

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop

virtual network interface on x86

2018-04-06 Thread anilappana 
Hi Jan,
  We are trying to establish the connection between root cell to non-root cell 
on x86 using ivshmem-net driver.


we did below modifications in root cell and non root cell configurations.

  // PCI device
{
.type = JAILHOUSE_PCI_TYPE_IVSHMEM,
.domain = 0x0,
.bdf = 0x0e << 3,
.bar_mask = {
0xff00, 0x, 0x,
0x, 0xffe0, 0x,
},
.num_msix_vectors = 1,
.shmem_region = 3,
.shmem_protocol = JAILHOUSE_SHMEM_PROTO_VETH,
},

/* MemRegion: 40410 : IVSHMEM :JH-added */
{
.phys_start = 0x40410,
.virt_start = 0x40410,
.size = 0x10,
.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
 JAILHOUSE_MEM_ROOTSHARED,
},


After adding above changes, we are able to see the virtual network interface in 
non-root cell but it is not working(ping is not happening and we are not able 
to see the interrupts).

I am adding below logs for your reference.


[root@localhost ~]# cat /proc/iomem
.
  0001-000100ff : ivshmem-net
00010100-0001011f : :00:0e.0
00040410-0004041f : ivshmem-net
.

[root@localhost ~]# cat /proc/interrupts
   CPU0   CPU1
  4:   1271  0   IO-APIC-4-fasteoi   serial
 24:404  0   PCI-MSI-524288-edge  enp1s0f0
 25:  0  0   PCI-MSI-229376-edge  ivshmem-net[:00:0e.0]


[rooot@localhost ~]# lspci -s 0e -vvv
00:0e.0 Unassigned class [ff01]: Red Hat, Inc Inter-VM shared memory
Subsystem: Red Hat, Inc Inter-VM shared memory
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR-   mtu 16384
inet 192.168.1.55  netmask 255.255.0.0  broadcast 192.168.255.255
ether 9a:28:41:e8:3b:14  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp1s0f0: flags=4163  mtu 1500
inet 192.168.1.35  netmask 255.255.0.0  broadcast 192.168.255.255
inet6 fe80::21b:78ff:fe56:abec  prefixlen 64  scopeid 0x20
ether 00:1b:78:56:ab:ec  txqueuelen 1000  (Ethernet)
RX packets 457  bytes 46827 (45.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 7  bytes 596 (596.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 11  memory 0xc72a-c72c  

Can you please help us to resolve.

we have below points which we need some input 

a. we want to know are we missing any configuration? 
b. we used external NIC and configured to non rootcell. should we assign any 
physical NIC to non rootcell to make virtual network interface working?
c.we didn't see that increment in interrupt count. Are we missing any thing 
here?

Regards,
Anil 




-- 
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

2018-04-03 Thread anilappana 
On Tuesday, April 3, 2018 at 3:18:34 PM UTC+5:30, Ralf Ramsauer wrote:
> On 04/03/2018 11:37 AM, anilapp...@gmail.com wrote:
> > On Tuesday, April 3, 2018 at 2:56:29 PM UTC+5:30, Ralf Ramsauer wrote:
> >> Hi Anil,
> >>
> >> On 04/03/2018 10:55 AM, Anil Kumar wrote:
> >>> Jan,
> >>> Thanks for your response. My use case is I want load more than 2 non
> >>> root cells & want to check whether non rootcells booted with out any
> >>> issues. Also I should
> >>> be able to login to non rootcell( which we created) to communicate to
> >> Are you running Linux in your non-root cells? You could simply use ssh
> >> over ivshmem-net...
> >>> another non rootcell(with shared memory). I don't want to use net
> >>> console. Can it be possible
> >>> to create virtual console and use them while loading non rootcells for
> >>> early console logs?
> >> There's no such thing like a 'real' virtual console in Jailhouse, but,
> >> as Henning already mentioned, you could use the hypervisor debug console
> >> for output and use jailhouse console to receive the cell's messages.
> >> Note that multiple non-root cells using this consoles may of course
> >> collide and scramble output, so it's better to start one cell after the
> >> other when using this method.
> >>
> >>   Ralf
> >>> Regards,
> >>> Anil
> >>>
> >>> On Tue, Apr 3, 2018 at 1:58 PM, Jan Kiszka  >>> > wrote:
> >>>
> >>> On 2018-04-03 08:32, anilapp...@gmail.com
> >>>  wrote:
> >>> > On Friday, February 9, 2018 at 3:04:55 PM UTC+5:30, Henning Schild
> >>> wrote:
> >>> >> 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
> >>> >
> >>> > Hi Henning,
> >>> > Thanks for your reply. But I want load  multiple non rootcells.
> >>> For this I need multiple consoles. So I want to create virtual
> >>> serial console and use them to load and capture logs& early console
> >>> logs. Can you help me how can I get these
> >>> > log messages & create virtual console.
> >>>
> >>> You can set up netconsoles via ivshmem-net, but that will not give you
> >>> early messages. However, there is usually no need for them after the
> >>> initial setup phase. Or what is your use case?
> >>>
> >>> Jan
> >>>
> >>>
> >>> -- 
> >>> 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.
> > 
> > Hi Ralf,
> > Yes I am loading linux on other non rootcells as well. But If we use ssh to 
> > login to non rootcell and If network is down, I wont be login to non 
> > rootcell. So I dont want to use this method. I am searching for other 
> > alternative other than this. In practical,I should be able to go to non 
> > rootcell with out network support. we got struck with capturing early 
> > console logs( to proceed with our thoughts). Then make sure that network 
> > isn't down :-)
> 
> Try to get one cell working (e.g., by redirecting the UART to the cell,
> so you're able to see output and you can control it) and duplicate the
> setup.
> 
> Otherwise you will have to implement your own virtual console support,
> but that's pointless, as we already have that: ivshmem-net. ssh over
> ivshmem-net is nothing else than the virtual console that you want.
> 
>   Ralf
> > Regards,
> > Anil
> >

I agree that. But I am

Re: jailhouse on X86

2018-04-03 Thread anilappana 
On Tuesday, April 3, 2018 at 2:56:29 PM UTC+5:30, Ralf Ramsauer wrote:
> Hi Anil,
> 
> On 04/03/2018 10:55 AM, Anil Kumar wrote:
> > Jan,
> > Thanks for your response. My use case is I want load more than 2 non
> > root cells & want to check whether non rootcells booted with out any
> > issues. Also I should
> > be able to login to non rootcell( which we created) to communicate to
> Are you running Linux in your non-root cells? You could simply use ssh
> over ivshmem-net...
> > another non rootcell(with shared memory). I don't want to use net
> > console. Can it be possible
> > to create virtual console and use them while loading non rootcells for
> > early console logs?
> There's no such thing like a 'real' virtual console in Jailhouse, but,
> as Henning already mentioned, you could use the hypervisor debug console
> for output and use jailhouse console to receive the cell's messages.
> Note that multiple non-root cells using this consoles may of course
> collide and scramble output, so it's better to start one cell after the
> other when using this method.
> 
>   Ralf
> > Regards,
> > Anil
> > 
> > On Tue, Apr 3, 2018 at 1:58 PM, Jan Kiszka  > > wrote:
> > 
> > On 2018-04-03 08:32, anilapp...@gmail.com
> >  wrote:
> > > On Friday, February 9, 2018 at 3:04:55 PM UTC+5:30, Henning Schild
> > wrote:
> > >> 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
> > >
> > > Hi Henning,
> > > Thanks for your reply. But I want load  multiple non rootcells.
> > For this I need multiple consoles. So I want to create virtual
> > serial console and use them to load and capture logs& early console
> > logs. Can you help me how can I get these
> > > log messages & create virtual console.
> > 
> > You can set up netconsoles via ivshmem-net, but that will not give you
> > early messages. However, there is usually no need for them after the
> > initial setup phase. Or what is your use case?
> > 
> > Jan
> > 
> > 
> > -- 
> > 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.

Hi Ralf,
Yes I am loading linux on other non rootcells as well. But If we use ssh to 
login to non rootcell and If network is down, I wont be login to non rootcell. 
So I dont want to use this method. I am searching for other alternative other 
than this. In practical,I should be able to go to non rootcell with out network 
support. we got struck with capturing early console logs( to proceed with our 
thoughts). 
Regards,
Anil

-- 
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

2018-04-03 Thread anilappana 
On Friday, February 9, 2018 at 3:04:55 PM UTC+5:30, Henning Schild wrote:
> 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

Hi Henning,
Thanks for your reply. But I want load  multiple non rootcells. For this I need 
multiple consoles. So I want to create virtual serial console and use them to 
load and capture logs& early console logs. Can you help me how can I get these
log messages & create virtual console.
Regards,
Anil

-- 
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.

Unhandled VM-Exit, reason 3qualification 0vectoring info:

2018-03-21 Thread anilappana 
Hi Jan/Henning,
we are using jailhouse on x86 xeon pc. please find below file for /proc/iomem 
and find attached rootcell and non rootcell config files.  This is the console 
out.  

Adding PCI device ff:1f.2 to cell "RootCell"Page pool usage after late setup: 
mem 464/16328, remap 66078/131072Activating hypervisorWARNING: Overflow during 
MMIO region registration!CAT: Shrunk root cell bitmask to 000cCAT: Using 
COS 1 with bitmask 0003 for cell RedHawk 4.9.47 non rootWARNING: Overflow 
during MMIO region registration!Created cell "RedHawk 4.9.47 non root"Page pool 
usage after cell creation: mem 2537/16328, remap 66078/131072Cell "RedHawk 
4.9.47 non root" can be loadedCPU 2 received SIPI, vector 100Started cell 
"RedHawk 4.9.47 non root"CPU 3 received SIPI, vector 100FATAL: Unhandled 
VM-Exit, reason 3qualification 0vectoring info: 0 interrupt info: 0RIP: 
0xaa8eca00 RSP: 0x8dc95f208fd8 FLAGS: 46RAX: 0x0020 
RBX: 0x0008 RCX: 0x0001RDX: 0x RSI: 
0xaaec74c0 RDI: 0x8dc95f226b00CS: 10 BASE: 0x 
AR-BYTES: a09b EFER.LMA 1CR0: 0x80050033 CR3: 0x00084bc13002 CR4: 
0x003626e0EFER: 0x0d01Parking CPU 8 (Cell: 
"RootCell")FATAL: Unhandled VM-Exit, reason 3qualification 0vectoring info: 0 
interrupt info: 0RIP: 0x RSP: 0x8dc95f208fd8 FLAGS: 46RAX: 
0x0020 RBX: 0x0008 RCX: 0x0001RDX: 
0x RSI: 0xaaec74c0 RDI: 0x8dc95f226b00CS: 10 BASE: 
0x AR-BYTES: a09b EFER.LMA 1CR0: 0x80050033 CR3: 
0x00084bc13002 CR4: 0x003626e0EFER: 0x0d01Parking CPU 8 
(Cell: "RootCell")

can you please help what could be the reason for this error.

Regards,
Anil

-- 
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.
/*
 * Jailhouse, a Linux-based partitioning hypervisor
 *
 * Copyright (c) Siemens AG, 2014-2017
 *
 * This work is licensed under the terms of the GNU GPL, version 2.  See
 * the COPYING file in the top-level directory.
 *
 * Alternatively, you can use or redistribute this file under the following
 * BSD license:
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 * THE POSSIBILITY OF SUCH DAMAGE.
 *
 * Configuration for Supermicro X10DRi
 * created with '/usr/local/libexec/jailhouse/jailhouse config create --mem-inmates 3072M x86-root-3136M.c'
 *
 * NOTE: This config expects the following to be appended to your kernel cmdline
 *   "memmap=0xc400$0x4"
 */

#include 
#include 

#define ARRAY_SIZE(a) (sizeof(a) / sizeof((a)[0]))

struct {
	struct jailhouse_system header;
	__u64 cpus[1];
	struct jailhouse_memory mem_regions[88];
	struct jailhouse_irqchip irqchips[3];
	__u8 pio_bitmap[0x2000];
	struct jailhouse_pci_device pci_devices[176];
	struct jailhouse_pci_capability pci_caps[90];
} __attribute__((packed)) config = {
	.header = {
		.signature = JAILHOUSE_SYSTEM_SIGNATURE,
		.revision = JAILHOUSE_CONFIG_REVISION,
		.hypervisor_memory = {
			.phys_start = 0x4,
			.size = 0x400,
		},
		.debug_console = {
			.address = 0x3f8,
			.flags = JAILHOUSE_CON1_TYPE_8250 |
 JAILHOUSE_CON1_ACCESS_PIO |
 JAILHOUSE_CON1_REGDIST_1 |
 JAILHOUSE_CON2_TYPE_ROOTPAGE,
		},
		.platform_info = {
			.pci_mmconfig_base = 0x8000,
			.pci_mmconfig_end_bus = 0xff,
			.x86 = {
.pm_timer_address = 0x408,
.vtd_interrupt_limit = 256,
.iommu_units = {
	{
		.base = 0xfbffc000,
		.size = 0x1000,
	},
	{

Re: jailhouse config size issue while accessing memory region

2018-03-21 Thread anilappana 
On Wednesday, March 21, 2018 at 8:54:00 PM UTC+5:30, Henning Schild wrote:
> Am Wed, 21 Mar 2018 07:31:43 -0700
> schrieb :
> 
> > Hi Jan,
> > we are working on jailhouse on x86 and facing some issues with
> > system(root cell) config. This is one of the issue while
> > accessing /proc/iomem for our system x86 (xeon)
> > 
> >   7933d018-7933d018 : APEI ERST
> >   7933d01c-7933d021 : APEI ERST
> >   7933d028-7933d039 : APEI ERST
> >   7933d040-7933d04c : APEI ERST
> >   7933d050-7933f04f : APEI ERST
> 
> This is just a part of /proc/iomem, so far i do not understand where
> the issue/problem is.
> 
> > we are doing memory size check  while accessing memory regions from
> > rootcell config.
> 
> What does that mean? Did you modify jailhouse or are you processing the
> configs somehow? Or are you talking about a check inside an unmodified
> jailhouse?
> 
> > From the above information in /proc/iomem, jailhouse
> > generating config file with "zero" size.
> 
> The first line will result in size 0, in the others the size should get
> rounded up to at least one page.
> 
> > we want to know is there any
> > issue with creating size for some of the memory regions.
> 
> The example you sent is incomplete and the generator might not be able
> to handle those lines correctly. The start should be page-alligned.
> On the Xeons i have, i see similar lines but they are behind a
> "reserverd" and should be ignored.
> 
> Please send the output of "jailhouse config collect /tmp/target.tar"
> and explain you problem in more detail.
> 
> Henning
> 
> > Regards,
> > Anil
> >

Hi Henning,
Thanks for your reply. please find my rootcell config generated by jailhouse 
and system /proc/iomem files.
Regards,
Anil

-- 
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.
sudo  cat /proc/iomem 
[sudo] password for xeon: 
-0fff : Reserved
1000-000997ff : System RAM
00099800-0009 : Reserved
000a-000b : PCI Bus :00
000c-000c7fff : Video ROM
000c8000-000c8fff : Adapter ROM
000c9000-000c9fff : Adapter ROM
000ca000-000cafff : Adapter ROM
000e-000f : Reserved
  000f-000f : System ROM
0010-3aff : System RAM
3b00-6eff : Reserved
6f00-79161fff : System RAM
79162000-79a5efff : Reserved
  7933d018-7933d018 : APEI ERST
  7933d01c-7933d021 : APEI ERST
  7933d028-7933d039 : APEI ERST
  7933d040-7933d04c : APEI ERST
  7933d050-7933f04f : APEI ERST
79a5f000-79f77fff : ACPI Non-volatile Storage
79f78000-8fff : Reserved
  8000-8fff : PCI MMCONFIG  [bus 00-ff]
9000-c7ffbfff : PCI Bus :00
  9000-900f : PCI Bus :03
9000-9001 : :03:00.0
9002-9003 : :03:00.0
9004-9005 : :03:00.1
9006-9007 : :03:00.1
  c600-c70f : PCI Bus :05
c600-c70f : PCI Bus :06
  c600-c6ff : :06:00.0
  c700-c701 : :06:00.0
  c710-c71f : PCI Bus :03
c710-c711 : :03:00.1
  c710-c711 : igb
c712-c713 : :03:00.0
  c712-c713 : igb
c714-c7143fff : :03:00.1
  c714-c7143fff : igb
c7144000-c7147fff : :03:00.0
  c7144000-c7147fff : igb
  c720-c72f : PCI Bus :01
c720-c721 : :01:00.1
c722-c723 : :01:00.1
  c722-c723 : e1000e
c724-c725 : :01:00.1
  c724-c725 : e1000e
c726-c727 : :01:00.0
c728-c729 : :01:00.0
  c728-c729 : e1000e
c72a-c72b : :01:00.0
  c72a-c72b : e1000e
  c730-c730 : :00:14.0
c730-c730 : xhci-hcd
  c731-c7313fff : :00:04.7
c731-c7313fff : ioatdma
  c7314000-c7317fff : :00:04.6
c7314000-c7317fff : ioatdma
  c7318000-c731bfff : :00:04.5
c7318000-c731bfff : ioatdma
  c731c000-c731 : :00:04.4
c731c000-c731 : ioatdma
  c732-c7323fff : :00:04.3
c732-c7323fff : ioatdma
  c7324000-c7327fff : :00:04.2
c7324000-c7327fff : ioatdma
  c7328000-c732bfff : :00:04.1
c7328000-c732bfff : ioatdma
  c732c000-c732 : :00:04.0
c732c000-c732 : ioatdma
  c7331000-c73310ff : :00:1f.3
  c7332000-c73327ff : :00:1f.2
c7332000-c73327ff : ahci
  c7333000-c7ff : :00:1d.0
c7333000-c7ff : ehci_hcd
  c7334000-c73343ff : :00:1a.0
c7334000-c73343ff : ehci_hcd
  c7336000-c733600f : :00:16.1
  c7337000-c733700f : :00:16.0
  c7338000-c73387ff : :00:11.4
c7338000-c73387ff : ahci
  c7339000-c7339fff : :00:05.4
c7ffc000-c7ffcfff : dmar1
c800-fbffbfff : PCI Bus :80
  fbf0-fbf03fff : :80:04.7
fbf0-fbf03fff

jailhouse config size issue while accessing memory region

2018-03-21 Thread anilappana 
Hi Jan,
we are working on jailhouse on x86 and facing some issues with system(root 
cell) config. This is one of the issue while accessing /proc/iomem for our 
system x86 (xeon)

  7933d018-7933d018 : APEI ERST
  7933d01c-7933d021 : APEI ERST
  7933d028-7933d039 : APEI ERST
  7933d040-7933d04c : APEI ERST
  7933d050-7933f04f : APEI ERST

we are doing memory size check  while accessing memory regions from rootcell 
config. From the above information in /proc/iomem, jailhouse generating config 
file with "zero" size. we want to know is there any issue with creating size 
for some of the memory regions.

Regards,
Anil

-- 
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.

shared memory application to run on non rootcell

2018-03-06 Thread anilappana 
Jan,
we are tying to access( read & write) from shared memory region between root 
cell and non rootcell. I cant use ivshm-shared.bin file because  I want to load 
another linux kernel on non rootcell. After booting into non rootcell, how can 
I write into shared memory region and trigger interrupt so that root cell can 
receive it. I am using minimal file system in non rootcell and I cant compile 
and create some application on non rootcell.
Can I create ivshm-shared memory application instead of binary in rootcell. If 
yes, I can use this application to run on non rootcell to write into share 
memory region.
please suggest me is there any way to achieve this.
Regards,
Anil

-- 
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.

need application executa

2018-03-06 Thread anilappana 
Jan,
we are tying to access( read & write) from shared memory region between root 
cell and non rootcell. I cant use ivshm-shared.bin file because  I want to load 
another linux kernel on non rootcell. After booting into non rootcell, how can 
I write into shared memory region and trigger interrupt so that root cell can 
receive it. I am using minimal file system in non rootcell and I cant compile 
and create some application on non rootcell.

Can I create ivshm-shared memory application instead of binary in rootcell. If 
yes, I can use this application to run on non rootcell to write into share 
memory region.
please suggest me is there any way to achieve this.
Regards,
Anil

-- 
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.

jailhouse patch for 4.9 kernel

2018-02-15 Thread anilappana 
Hi Jan,
We are trying bring up linux kernel based on 4.9.47 on non rootcell for X86 
architecture.can you please provide link for jailhouse patch.
Regards,
Anil

-- 
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.

jailhouse on X86

2018-02-08 Thread anilappana 
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

-- 
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.

Jaillhouse on X86

2018-02-05 Thread anilappana 
Hi,
I am trying to load jailhouse on CentOS but I am getting following error while 
creating rootcell config file.

root@localhost jailhouse]# jailhouse config create x86config.c
Traceback (most recent call last):
  File "/usr/local/libexec/jailhouse/jailhouse-config-create", line 1180, in 

dmar_regions)
  File "/usr/local/libexec/jailhouse/jailhouse-config-create", line 757, in 
parse_dmar
f = input_open('/sys/firmware/acpi/tables/DMAR', 'rb')
  File "/usr/local/libexec/jailhouse/jailhouse-config-create", line 155, in 
input_open
raise e
IOError: [Errno 2] No such file or directory: '//sys/firmware/acpi/tables/DMAR'

Can anyone help us to create rootcell config file.
Regards,
Anil

-- 
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: Need support for non root cell configuration on X86

2018-01-24 Thread anilappana 
Hi Jan,
Thanks for you input. I tried adding this configuration in non root cell. But I 
got same output.
I tired allocating more memory for hyperviser (memmap=512M)
With this change, I got below output on console.


following error is throwing when loading non-root cell linux :
Created cell "linux-x86-demo"
Page pool usage after cell creation: mem 804/16328, remap 65611/131072
Cell "linux-x86-demo" can be loaded
CPU 2 received SIPI, vector 100
CPU 1 received SIPI, vector 100
CPU 3 received SIPI, vector 100
Started cell "linux-x86-demo"
FATAL: Invalid PIO write, port: a1 size: 1
RIP: 0x81023961 RSP: 0x82803f10 FLAGS: 96
RAX: 0x RBX: 0x RCX: 0x032a
RDX: 0x0001 RSI: 0x0096 RDI: 0x828404a0
CS: 10 BASE: 0x AR-BYTES: a09b EFER.LMA 1
CR0: 0x80050033 CR3: 0x02821000 CR4: 0x000426b0
EFER: 0x0d01
Parking CPU 2 (Cell: "linux-x86-demo")

can you please let me know is there any thing I missed in my rootcell or non 
rootcell configuration.
Regards,
Anil

-- 
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.

Need support for non root cell configuration on X86

2018-01-23 Thread anilappana 
Hi,
I want to load kernel and rootfs on non rootcell with my laptop configuration 
ie X86 (Lenova G50, I5 processor). I was able to create root cell with 
jailhouse tool(jailhouse create config command).I also modified non root cell 
configuration but I am not sure what is the memory configuration I should use.
Below is the error which I am getting with non root cell.

sudo jailhouse cell linux configs/linux-x86-demo.cell
/path/vmlinuz-4.14.0-rc4  -i /path/rootfs.tar  -c "console=ttyS0,115200"

Traceback (most recent call last):
  File "/usr/local/libexec/jailhouse/jailhouse-cell-linux", line 786, in 

cell.load(args.initrd.read(), arch.ramdisk_address())
  File "/usr/local/libexec/jailhouse/jailhouse-cell-linux", line 712, in load
fcntl.ioctl(self.dev, self.JAILHOUSE_CELL_LOAD, load)
IOError: [Errno 22] Invalid argument

I also added 
GRUB_CMDLINE_LINUX_DEFAULT="memmap=66M\\\$0x3b00".  in /etc/default/grub


Please find attachment for the configuration(rootcell, non rootcell and iomem) 
that I used  for my machine.can someone help me about this non rootcell 
configuration to boot kernel and rootfs on X86.
Anil

-- 
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.
/*
 * Jailhouse, a Linux-based partitioning hypervisor
 *
 * Copyright (c) Siemens AG, 2014-2017
 *
 * This work is licensed under the terms of the GNU GPL, version 2.  See
 * the COPYING file in the top-level directory.
 *
 * Alternatively, you can use or redistribute this file under the following
 * BSD license:
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 *
 * 1. Redistributions of source code must retain the above copyright
 *notice, this list of conditions and the following disclaimer.
 *
 * 2. Redistributions in binary form must reproduce the above copyright
 *notice, this list of conditions and the following disclaimer in the
 *documentation and/or other materials provided with the distribution.
 *
 * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
 * AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
 * LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
 * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
 * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 * THE POSSIBILITY OF SUCH DAMAGE.
 *
 * Configuration for LENOVO 80E5
 * created with '/usr/local/libexec/jailhouse/jailhouse config create new86.c'
 *
 * NOTE: This config expects the following to be appended to your kernel cmdline
 *   "memmap=0x420$0x3b00"
 */

#include 
#include 

#define ARRAY_SIZE(a) (sizeof(a) / sizeof((a)[0]))

struct {
	struct jailhouse_system header;
	__u64 cpus[1];
	struct jailhouse_memory mem_regions[53];
	struct jailhouse_irqchip irqchips[1];
	__u8 pio_bitmap[0x2000];
	struct jailhouse_pci_device pci_devices[15];
	struct jailhouse_pci_capability pci_caps[48];
} __attribute__((packed)) config = {
	.header = {
		.signature = JAILHOUSE_SYSTEM_SIGNATURE,
		.revision = JAILHOUSE_CONFIG_REVISION,
		.hypervisor_memory = {
			.phys_start = 0x3b00,
			.size = 0x400,
		},
		.debug_console = {
			.address = 0x3f8,
			.flags = JAILHOUSE_CON1_TYPE_8250 |
 JAILHOUSE_CON1_ACCESS_PIO |
 JAILHOUSE_CON1_REGDIST_1 |
 JAILHOUSE_CON2_TYPE_ROOTPAGE,
		},
		.platform_info = {
			.pci_mmconfig_base = 0xe000,
			.pci_mmconfig_end_bus = 0xff,
			.x86 = {
.pm_timer_address = 0x1808,
.vtd_interrupt_limit = 256,
.iommu_units = {
	{
		.base = 0xfed9,
		.size = 0x1000,
	},
	{
		.base = 0xfed91000,
		.size = 0x1000,
	},
},
			},
		},
		.root_cell = {
			.name = "RootCell",
			.cpu_set_size = sizeof(config.cpus),
			.num_memory_regions = ARRAY_SIZE(config.mem_regions),
			.num_irqchips = ARRAY_SIZE(config.irqchips),
			.pio_bitmap_size = ARRAY_SIZE(config.pio_bitmap),
			.num_pci_devices = ARRAY_SIZE(config.pci_devices),
			.num_pci_caps = ARRAY_SIZE(config.pci_caps),
		},
	},

	.cpus = {
		0x000f,
	},

	.mem_regions = {
		/* MemRegion: -0fff : Reserved */
		{
			.phys_start = 0x0,
			.virt_start = 0x0,
			.size = 0x1000,
			.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE,
		},
		/* MemRegion: 1000-00057fff : System RAM */
		{