zer0zer0

Members
  • Posts

    29
  • Joined

  • Last visited

Report Comments posted by zer0zer0

  1. 16 hours ago, np said:

    I've seen this asked a couple places by can't seem to find an response/answer.  I've added a new network interface to 6.10-rc2 (10G Mellanox) but I can't seem to reassign it to eth0.  I see references to "Settings > Network Settings > Interface Rules" but it seems to be gone now.

    Is this planned to be removed for 6.10?  Or just missing while 6.10 gets a polish?

     

    I can confirm that it's there on my 6.10.0-rc2 server with a Mellanox CX3 card as well, and I have used it to change the interface mapping

  2. I'm curious if this is the intended behavior when using the web gui on 6.10.0-rc2?

     

    If you use something like http://unraidserver.local it converts it to a really ugly url like this 
    https://a9673c7c842a20425e043d8330e376af784c757b2.unraid.net/

     

    And at the same time you can't get to it because it doesn't resolve nicely with pihole/unbound running on Unraid itself, and I had to go in and create a new local dns entry :(

  3. 19 minutes ago, StevenD said:

    I have been running that for a long time. Maybe thats why I havent seen this issue.

     

    I dont have a video card to pass through on my test unRAID VM, so I cant do any additional testing without taking down my main unraid box.


    I saw the boot freeze with just the hypervisor.cpuid.v0 = FALSE in the vmx file and no hardware pass through at all. 

    So it should be independent of video cards etc.  

  4. I'm seeing an issue when using ESXi and setting hypervisor.cpuid.v0 = FALSE in the vmx file.

    The system will not boot if you assign more than one cpu to the virtual machine.

     

    I'm using ESXi 6.7 with the latest patches and UnRAID 6.9.0-rc2.

    At first I thought it was an issue with passing through my Nvidia P400, but it happens even without any hardware passed through.

     

    My diagnostic zip file is attached.

    Here is a thread from another user discussing the same issue - 

     

     

     

     

    darkstor-diagnostics-20210111-1047.zip