Jump to content

cmon_google_wtf

Members
  • Posts

    25
  • Joined

  • Last visited

Report Comments posted by cmon_google_wtf

  1. EDIT: Holy stinky dog-poo! Okay kids, this all works using *exactly* the below xml (w/e/f your naming convention), just make sure when you create the *script, that you specify it with the shebang...

    Script: 

    #!/bin/sh
    exec /usr/libexec/virtiofsd -o sandbox=chroot "$@"

     

    XML:

      <memoryBacking>
        <source type='memfd'/>
        <access mode='shared'/>
      </memoryBacking>    
    ----
        <filesystem type='mount' accessmode='passthrough'>
          <driver type='virtiofs'/>
          <binary path='/usr/libexec/virtiofsd-script'/>
          <source dir='/mnt/user/domains'/>
          <target dir='unraidshare'/>
        </filesystem>

    After you get it running, mount with the usual mount commands, in my case:

    sudo mount -t virtiofs unraidshare /mnt/unraiddata/

     

    ---------See above!!! These are for notes of my progress...--------

    Spoiler

    This be an old thread, but relevant once again as we are now in Unraid 6.10-rc4. I have created a file creatively called `virtiofsd-script` and input it into my xml as follows:

      <memoryBacking>
        <source type='memfd'/>
        <access mode='shared'/>
      </memoryBacking>    
    ----
        <filesystem type='mount' accessmode='passthrough'>
          <driver type='virtiofs'/>
          <binary path='/usr/libexec/virtiofsd-script'/>
          <source dir='/mnt/user/domains'/>
          <target dir='unraidshare'/>
        </filesystem>

    But I am still having no joy. 

     

    To plagiarize myself from the Unraid Discord, I have the following:

    Quote

    To note, I have added a file with ```exec /usr/libexec/virtiofsd -o sandbox=chroot "$@"``` in it, resulting in:

    Execution error
    internal error: virtiofsd died unexpectedly

     

    Without that file, or just not pointing the `<binary>` path at it, I get the longer error of:

     

    internal error: qemu unexpectedly closed the monitor: 2022-04-10T21:24:51.687704Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"unraidshare","bus":"pci.1","addr":"0x0"}: Failed to write msg. Wrote -1 instead of 12. 2022-04-10T21:24:51.687766Z qemu-system-x86_64: -device {"driver":"vhost-user-fs-pci","id":"fs0","chardev":"chr-vu-fs0","tag":"unraidshare","bus":"pci.1","addr":"0x0"}: vhost_backend_init failed: Protocol error

    Any help or insight I could get would be awesome! Happy, of course, to play around with different things to try to get it working as requested/recommended as well. Its just for a blockchain node, so, nothing that can't be replaced, and I would really like that performance increase!

     

    • Like 1
    • Thanks 1
×
×
  • Create New...