xilo

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by xilo

  1. 4 minutes ago, Squid said:

    The go file is a simple bash script that is executed every time you boot the server.  You can add whatever you need to it.  The "preferred" way to however run scripts at startup would be via the user scripts plugin, but I took a wild guess that what you needed would have to be run earlier in the bootup sequence than when user scripts would execute it.

    You're right.  I think using syslinux.cfg is probably the easiest way to get what I want.   Thanks for the help and knowledge.

     

    For future reference / to aid those ever in this situation, this is my modified statement:

     

    Quote

    kernel /bzimage
    append initrd=/bzroot ixgbe.allow_unsupported_sfp=1 kvm-intel.nested=1 kvm-intel.enable_apicv=0

     

  2. 3 minutes ago, Squid said:

    unRaid runs from RAM, and there is no persistent folders anywhere (except for /boot)  You would need to make those changes via appropriate commands within /config/go on the flash drive.

    Thank you for the quick reply!  Could you elaborate a bit on how to make these changes in /config/go?  I'm a bit new to unraid.  I modified the syslinux.cfg file and that seems to be working, but is there a cleaner way to do what i'm looking for?

  3. Hi,

     

    I am trying to add the following options to the kvm.conf file in /etc/modprobe.d so that I can enable nested virutalization. 

     

    Quote

    options kvm_intel nested=1 enable_apicv=n

    options kvm ignore_msrs=1

     

    It appears the kvm.conf file is overwritten at start-up, and I am having trouble finding where to set these options to be persistent.  Can anyone help me?

     

    I am looking to do this so that I am able to deploy three ESXi hosts within KVM on Unraid to create an NSX-T lab.

  4. 5 hours ago, dee31797 said:

    I haven't tried this with macvlan networking recently, but I'm pretty sure it works.  

     

    Can you send me the docker container logs as well as the dhcpd.conf file?

    Posting the issue/resolution:

     

    Looks like I was missing a required declaration for the subnet in which the containers network interface resided.  The service wouldnt start without this.  Adding this subnet (even without a range/pool assigned) allowed the service to start and begin responding to DHCP Discover and dhcp requests on the configured subnets in the dhcpd.conf file.

  5. 16 minutes ago, Squid said:

    I'll save you the time.  Don't bother.  Both are affected. But it is my belief that this is something related to specific nzbs as some work fine no problems, but my experience showed that the same nzb would fail consistently.   I tried going back a couple of versions on lsio to no avail before I tried binhex, and then just switched to sab.  

    Kind of early to tell, but I did a 250 nzb download test and we didn't hang on a single one.  It looks promising, but I won't get my hopes up.

  6. 1 hour ago, jonathanm said:

    You may want to amend your report disclosing that it is concerning a docker container, not a full install. I don't believe the issue occurs on a normal install, but I could be wrong. Please read through this thread to get a sense of the history and what has already been tried to troubleshoot the issue.

    Done.  Thank you for the suggestion.  I have read through this thread already, but sometimes hard to follow for me.  NZBGet author suggested building the container mysef/compiling within the container.  I believe this is beyond my skill set, so I am going to try the nzbget container from linuxserver.io to see if I have any luck before I give up and go back to Sabnzbd.