Hi,
I am using jailhouse in an Intel x86 hardware and I am having some
problems to start ivshmem-net driver in a root cell, in order to
communicate with a Linux inmate cell.
I have successfully use this driver to stablish a communication between
two Linux inmate cells, but the driver fails when I load it in the root
cell.
Can anyone help me in understanding this issue and debbuging the
problem?
In the root cell configuration file I have addeded the following:
mem_regions:
/* IVSHMEM shared memory region (networking) */
{
.phys_start = 0x3f100000,
.virt_start = 0x3f100000,
.size = 0xff000,
.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
JAILHOUSE_MEM_ROOTSHARED,
},
pci_devices:
/* IVSHMEM (networking) */
{
.type = JAILHOUSE_PCI_TYPE_IVSHMEM,
.domain = 0x0000,
.bdf = 0x0f << 3, //This doesn't conflict with other bdf
.bar_mask = {
0xffffff00, 0xffffffff, 0x00000000,
0x00000000, 0xffffffe0, 0xffffffff,
},
.num_msix_vectors = 1,
.shmem_region = 0, //This is pointing to the mem_region above
.shmem_protocol = JAILHOUSE_SHMEM_PROTO_VETH,
},
And when I run:
$ ./tools/jailhouse enable configs/root.cell
The driver ivshmem-net is loaded and the following message is printed
in the kernel log
[ 20.956367] ivshmem-net 0000:00:0f.0: invalid IVPosition -1
I noticed when I was debbuging this issue that the function
ivshmem_register_mmio is not called when ivshmem-net driver tries to
get the ivpos value. I suspected then that value of bar0_address and
bar4_address may be wrong. Is there an way to know what would be the
expected value for this addresses? Or is there any other thing I should
check to try to debug this?
Best regards,
Otavio
--
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
