hi, anmol,
could you please share your ideal to fix the issue "cannot open /dev/uio0: 
No such file or directory"
I have the same issue now.

On Friday, August 20, 2021 at 9:53:11 PM UTC+8 [email protected] wrote:

> It's working :)
>
> qemux86-64:~# ./virtio-ivshmem-block /dev/uio0 disk.img
> Waiting for peer to be ready...
>
> Thanks and Regards,
> Anmol
>
> On Fri, Aug 20, 2021 at 6:49 PM Jan Kiszka <[email protected]> wrote:
> >
> > On 20.08.21 14:46, Anmol wrote:
> > > On Fri, Aug 20, 2021 at 5:53 PM Jan Kiszka <[email protected]> wrote:
> > >>
> > >> On 20.08.21 14:02, Anmol wrote:
> > >>> Hello,
> > >>>
> > >>> On Thu, Aug 19, 2021 at 7:22 PM Jan Kiszka <[email protected]> wrote:
> > >>>>
> > >>>> On 19.08.21 15:42, Anmol wrote:
> > >>>>> Hello,
> > >>>>>
> > >>>>> On Sat, Aug 14, 2021 at 8:20 PM Jan Kiszka <[email protected]> 
> wrote:
> > >>>>>>
> > >>>>>> On 11.08.21 20:36, Anmol wrote:
> > >>>>>>
> > >>>>>> The echo should not show any response, but when you do an lspci 
> -k, you
> > >>>>>> should see that the targeting devices are now driven by 
> uio_ivshmem. If
> > >>>>>> not, the IDs might not be correct yet, or the devices are missing.
> > >>>>>>
> > >>>>>> Also check the kernel console of the cell where you issued this 
> echo.
> > >>>>>>
> > >>>>>
> > >>>>> I have added the PCI devices to both the cells and set the
> > >>>>> `.shmem_dev_id` accordingly, please have a look at the cell config.
> > >>>>> files I have sent.
> > >>>>>
> > >>>>> here's the `lspci -k` output:
> > >>>>> qemux86-64:~# lspci -k
> > >>>>> 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express 
> DRAM Controller
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> 00:01.0 VGA compatible controller: Red Hat, Inc. Virtio GPU (rev 
> 01)
> > >>>>> Subsystem: Red Hat, Inc. Virtio GPU
> > >>>>> Kernel driver in use: virtio-pci
> > >>>>> 00:02.0 Ethernet controller: Red Hat, Inc. Virtio network device
> > >>>>> Subsystem: Red Hat, Inc. Virtio network device
> > >>>>> Kernel driver in use: virtio-pci
> > >>>>> 00:03.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG
> > >>>>> Subsystem: Red Hat, Inc. Virtio RNG
> > >>>>> Kernel driver in use: virtio-pci
> > >>>>> 00:04.0 SCSI storage controller: Red Hat, Inc. Virtio block device
> > >>>>> Subsystem: Red Hat, Inc. Virtio block device
> > >>>>> Kernel driver in use: virtio-pci
> > >>>>> 00:1b.0 Audio device: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6
> > >>>>> Family) High Definition Audio Controller (rev 01)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: snd_hda_intel
> > >>>>> 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB
> > >>>>> UHCI Controller #1 (rev 03)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: uhci_hcd
> > >>>>> 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB
> > >>>>> UHCI Controller #2 (rev 03)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: uhci_hcd
> > >>>>> 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB
> > >>>>> UHCI Controller #3 (rev 03)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: uhci_hcd
> > >>>>> 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2
> > >>>>> EHCI Controller #1 (rev 03)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: ehci-pci
> > >>>>> 00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface
> > >>>>> Controller (rev 02)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> 00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH 
> (ICH9R/DO/DH)
> > >>>>> 6 port SATA Controller [AHCI mode] (rev 02)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: ahci
> > >>>>> 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus 
> Controller (rev 02)
> > >>>>> Subsystem: Red Hat, Inc. QEMU Virtual Machine
> > >>>>> Kernel driver in use: i801_smbus
> > >>>>>
> > >>>>
> > >>>> Is this taken while Jailhouse was enabled? It's missing your ivshmem
> > >>>> devices (00:0c.0 - 00:0f.0).
> > >>>>
> > >>>
> > >>> I did some changes to the root-cell config files, and now it’s 
> showing
> > >>> the PCI device 00:0c.0 (I have added defined macro for VIRTIO_BLK
> > >>> only):
> > >>>
> > >>> qemux86-64:~# lspci -k
> > >>> .
> > >>> .
> > >>> .
> > >>> 00:0c.0 Unassigned class [ff80]: Siemens AG Device 4106
> > >>> Subsystem: Siemens AG Device 4106
> > >>> .
> > >>> .
> > >>> .
> > >>>
> > >>> But it’s not showing any association with the `uio_ivshmem`, and also
> > >>> I am still not able to find the `/dev/uio0`.
> > >>>
> > >>
> > >> And now
> > >>
> > >> echo "110a 4106 110a 4106 ffc002 ffffff" > 
> /sys/bus/pci/drivers/uio_ivshmem/new_id
> > >>
> > >> again.
> > >>
> > >
> > > Here's the full log:
> > >
> > > qemux86-64:~# jailhouse enable /usr/share/jailhouse/cells/qemu-agl.cell
> > > qemux86-64:~# modprobe uio_ivshmem
> > > qemux86-64:~# lsmod
> > > Module Size Used by
> > > virtio_gpu 65536 0
> > > virtio_dma_buf 16384 1 virtio_gpu
> > > virtio_net 53248 0
> > > net_failover 16384 1 virtio_net
> > > failover 16384 1 net_failover
> > > jailhouse 36864 1
> > > qemux86-64:~# echo "110a 4106 110a 4106 ffc002 ffffff" >
> > > /sys/bus/pci/drivers/uio_ivshmem/new_id
> >
> > ffc0... -> back-end device
> >
> > > qemux86-64:~# lspci -k
> > > .
> > > .
> > > .
> > > 00:0c.0 Unassigned class [ff80]: Siemens AG Device 4106
> >
> > ff80 -> you have a front-end device here
> >
> > You are either running that in the non-root cell or you misconfigured
> > the root cell (JAILHOUSE_SHMEM_PROTO_VIRTIO_BACK is needed).
> >
> > 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/ff786d5c-affd-4f94-9411-04bd223a8bc0n%40googlegroups.com.

Reply via email to