• Unraid slow VM boot times


    thenonsense
    • Annoyance

    Retrofit from bug reports sent via unraid web UI:

     

    Bug Description:

    Unraid VMs are slow to boot, and while they are typically normal after boot, a few times they are lagging during use.  Core usage is limited to a single core during boot, and the core is maxed @ 100%.

    These slow boots can take upwards of minutes, as opposed to normal boots of <10s.

    This issue did not exist on 6.5.3 and exists on every build 6.6.0rc1 and onwards.

    This issue appears to be limited to Threadripper chips?

    The issue manifests itself about 75% of boot sequences.  25% of the time the system may boot normally.

    How to reproduce:

    Obtain a Threadripper build (possibly more than 8 cores are needed).

    Update unraid to 6.5.3.

    Boot into any VM.  Most recommended is a Windows VM.  Repeat this process multiple times.  Note boot appears to be similar in performance to bare metal.

    Update unraid to >=6.6.0rc1

    Boot into the same VM multiple times.  Note for the majority of boots, the spinning circle lags heavily.  CPU usage hangs @ 100% on 1 core.

     

    Please keep me posted if there is any testing I can do.  I'm looking into how to compile unraid, but I believe I'm not incorporating all needed packages, and I can't seem to find any newer documentation on the process.  




    User Feedback

    Recommended Comments

    I did retest.  This bug report exists for the purpose of the conversation going on here:

    The bug is now logged as persistent from 6.6.0rc1 to 6.6.2.  

    Edited by thenonsense
    The above release was 6.6.2, not 6.6.3. A separate comment will be made for 6.6.3
    Link to comment

    The bug also exists in 6.6.3.  This report should be moved to stable releases.

    Edited by thenonsense
    Link to comment


    Guest
    This is now closed for further comments

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.


    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.