Hi Moustafa,

I already added `CONFIG_UIO_IVSHMEM=y` in my kernel configuration and
can easily load `uio_ivshmem` on the target image.

Also, I am trying `virtio-ivshmem-console` so, is there any need for
`CONFIG_IVSHMEM_NET=y` to be added in the defconfig?


Thanks and regards,
Anmol



On Wed, Jan 5, 2022 at 11:06 PM Moustafa Nofal
<[email protected]> wrote:
>
> Hi,
> I faced this problem on BCM2711 RPi4, my mistake was missing kernel 
> configuration flags:
> CONFIG_IVSHMEM_NET=y
> CONFIG_UIO_IVSHMEM=y
> So, if they are missing from your configuration, I advise you to see the 
> defconfig from jailhouse-images.
> Moustafa Noufale
>
> On Wednesday, 5 January 2022 at 16:49:32 UTC+1 [email protected] wrote:
>>
>> Hi,
>>
>> Thank you for your response, that problem is now resolved, now I am facing 
>> this issue:
>>
>> When executing(after `modprobe uio_ivshmem`):
>> `
>> ``
>>
>> root:~# ./virtio-ivshmem-console /dev/uio0 disk.img
>> ./virtio-ivshmem-console: cannot open /sys/class/uio/uio0/maps/map2/size: No 
>> such file or directory
>>
>> ```
>>
>> I am facing the above issue, please let me know how should I resolve this?
>>
>> Thanks and Regards,
>> Anmol
>> On Wednesday, December 15, 2021 at 2:57:18 PM UTC+5:30 [email protected] 
>> wrote:
>>>
>>> On 13.12.21 16:48, Anmol wrote:
>>> > Hi,
>>> >
>>> > I am trying to get virtio-over-ivshmem working with Xilinx-MPSoC(arm64)
>>> > board.
>>> >
>>> > Things I have prepared/setup:
>>> > -> Collected the patches of virtio-ivshmem from `queues/jailhouse-5.14`
>>> > and applied them to the `xilinx_rebase_v5.4`.
>>> >
>>> > These patches includes:
>>> >  - uio: Enable read-only mappings (with some modifications, as xilinx
>>> > `renamed uio.c -> uio_core.c & unified into uio.ko`)
>>> >         - WIP-ivshmem-Add-header-file
>>> >         - WIP-virtio-Add-virtio-over-ivshmem-transport-driver
>>> >         - WIP-uio-Add-driver-for-inter-VM-shared-memory-device
>>> >         - WIP-tools-Add-virtio-ivshmem-console-demo
>>> >         - WIP-tools-Add-virtio-ivshmem-block-demo
>>> >  - virtio: ivshmem: check peer_state early
>>> >
>>> > -> Cross-Compiled `virtio-ivshmem-{console, block}`.
>>> > -> Added common shared PCI devices to the root and non-root cell.
>>> > -> Root cell contains (`uio_ivshmem` driver)
>>> > -> I can see `/dev/uio0`.
>>> > -> Non-root cells contain (contain `virtio_ivshmem`).
>>> >
>>> > -> Also, after loading the jailhouse it's showing PCI devices I have 
>>> > added:
>>> >
>>> > ```
>>> > Adding virtual PCI device 00:0c.0 to cell "ZynqMP-ZCU102"
>>> > Adding virtual PCI device 00:0d.0 to cell "ZynqMP-ZCU102"
>>> >
>>> > ```
>>> >
>>> > After testing it, I am getting this(even after cross compiling the
>>> > application):,
>>> >
>>> > root:~# ./virtio-ivshmem-console /dev/uio0 disk.img
>>> > -sh: ./virtio-ivshmem-console: cannot execute binary file: Exec format 
>>> > error
>>> >
>>> > I am a little confused here, please let me know about anything I am 
>>> > missing.
>>> >
>>>
>>> Double-check with "file virtio-ivshmem-console" if that binary is really
>>> of the right type. Also use "ldd virtio-ivshmem-console" on the target
>>> to see if it lacks some dependencies there (due to mismatch in toolchains).
>>>
>>> Jan
>>>
>>> --
>>> Siemens AG, T RDA IOT
>>> Corporate Competence Center Embedded Linux
>
> --
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jailhouse" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jailhouse-dev/TA_ZVlnBciU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jailhouse-dev/04690e24-6aed-4856-aa81-f56f493821e0n%40googlegroups.com.

-- 
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/CAC%2ByH-ZsR5AqLjCuK%2By5ePczmiMK7upnkh3O%2Bppq8nEzC%3Dj1TA%40mail.gmail.com.

Reply via email to