XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VM autostart stopped working

    Scheduled Pinned Locked Moved Unsolved XCP-ng
    3 Posts 2 Posters 41 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • O Offline
      Octopuss
      last edited by

      I have no idea what happened. I simply restarted my home server after some time and two out of the four VMs simply didn't start despite being configured to do so in XO-CE.
      I googled up some thread where someone suggested flipping the autostart setting off and on via the console, which I did, but the VMS still refuse to autostart. They do start manually just fine.

      I have also set every VM's autostart to disabled and then disabled the pool-wide autostart setting, rebooted the server, re-enabled everything, rebooted, and it's still not working 😞
      Can anyone tell me what to do here, what to check? I don't really understand this system or Linux in general, everything I do is by copying what I find on internet or by trial and error.
      I literally changed nothing about the server and it's just not working all of a sudden 😞

      O 1 Reply Last reply Reply Quote 0
      • O Offline
        Octopuss @Octopuss
        last edited by Octopuss

        I removed the start-delay parameter from one of the VMs (only this one has it) and now it works again.
        I don't get it.
        No idea how to achieve a startup delay for a specific VM though. There's also "auto_poweron_delay" and I don't understand what the difference from "start-delay" is.

        poddingueP 1 Reply Last reply Reply Quote 0
        • poddingueP Online
          poddingue Vates 🪐 @Octopuss
          last edited by

          Glad the start-delay removal got that VM going again. I checked and it's a real, documented XCP-ng parameter, "the delay to wait before a call to start up the VM returns", so that explains the behavior.
          I couldn't find auto_poweron_delay documented anywhere in the XCP-ng or XO docs, so I'm not sure if it's something XO's advanced VM settings expose under a different name, or something unrelated you picked up while googling. 🤷
          If you check the VM's Advanced tab in XO and see what's actually set there, that would help pin down which setting you're really dealing with.
          Either way this looks like a gap in the autostart guide, since it doesn't mention that start-delay can interact with autostart at all.

          1 Reply Last reply Reply Quote 0
          • poddingueP poddingue marked this topic as a question

          Hello! It looks like you're interested in this conversation, but you don't have an account yet.

          Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

          With your input, this post could be even better 💗

          Register Login
          • First post
            Last post