xpra icon
Bug tracker and wiki

Changes between Initial Version and Version 1 of Ticket #1387


Ignore:
Timestamp:
12/26/16 08:28:27 (4 years ago)
Author:
Antoine Martin
Comment:

(made some minor edits to the description - also tested with Fedora 25 at both ends)

Notes:

  • if the socket /tmp/ivshmem_socket is left behind, the ivshmem-server command will fail with "cannot bind". (run with -v -F to get more details, then just remove the file if unused)
  • running as root: I assume we can just chmod the socket? (not tested)
  • rather than insmod, I used (personal preference / easier) depmod -a;modprobe uio_ivshmem
  • how do I read and write to the mmap file? I have tried variations on https://github.com/henning-schild/ivshmem-guest-code/blob/master/tests/DumpSum/VM/mmap.py (changed to write to the /dev/uio0 file) and I get "Invalid argument" every single time.. The only code example that does not fail is "writedump" but this accesses the file as a file, not as shared memory. What am I missing?

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #1387

    • Property Owner changed from Antoine Martin to pingberlin
  • Ticket #1387 – Description

    initial v1  
    11I recently discovered the vsock-support of xpra and tested it succesfully as described here: #983
    22
    3 Kvm also provides a shared memory device, but there does not seem to be a possibility to enable xpras mmap-support when using --bind-vsock (or --bind-tcp).
     3Kvm also provides a shared memory device, but there does not seem to be a possibility to enable xpra's mmap-support when using --bind-vsock (or --bind-tcp).
    44
    55My xpra version is: {{{xpra-1.0-1.r14502.fc24.x86_64}}}
     
    2222* 2. guest:
    2323  * install dependencies:
    24     * {{{ git clone https://gitorious.org/nahanni/guest-code.git }}}
    2524    * {{{ sudo dnf install kernel-devel }}}
    2625    * {{{ sudo dnf update kernel }}}
     
    3332    * {{{ sudo insmod /lib/modules/4.8.15300.fc25.x86_64/kernel/drivers/uio/uio_ivshmem.ko }}}
    3433  * verify the existence of your shared memory dev:
    35     * ls -la /dev/uio0
     34    * {{{ls -la /dev/uio0}}}
    3635
    3736