• [6.9.2] VMs marked as autostart do not restart after stopping and starting the array

    ElectricBadger

    By ElectricBadger

      • Annoyance

    If I stop the array and then restart it, all Docker containers that have autostart set to ON are restarted. The same does not apply to VMs: they only autostart after a full reboot, and must be restarted manually in this case.

     

    This is really annoying, as I usually forget to do this and don't notice until I try to use something that's running on a VM and find it's not working.

     

    Would it be possible for autostart to be consistent between Docker and VMs, and for both to autostart things after an array stop/start?

    celestia-diagnostics-20220219-1402.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB

    This is done on purpose, so if for example something is incorrectly passed-through to a VM (or it is after a config change) you have the chance to correct after disabling array auto-start, if not array might be inaccessible after that VM starts.

    Link to comment
    JonathanM

    VM startup is easy to manipulate with scripts, I have a user script that pings an IP and starts the VM only after that IP is responding.

     

    I recommend disabling autostart on your VM's and script them instead, definitely keeping a way to disable startup for troubleshooting purposes. A few minutes delay to kill the startup script if you need to, or reading the presence of a specific file on the flash drive, so deleting or renaming that file keeps the VM from starting.

     

     

    Link to comment


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • 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.