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

    VM autostart

    Scheduled Pinned Locked Moved Xen Orchestra
    4 Posts 3 Posters 1.2k 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.
    • A Offline
      adriangabura
      last edited by

      Hello,
      After a power outage I checked why some things were not working, so for some reason on a XCP-NG 8.2.1 system with XO xo-server 5.93.1 xo-web 5.96.0 some VMs on this given host were not auto starting... Never had this issue, and XO works fine for the other machines... What could possibly be the issue, do you know of any way to debug this and get to the bottom?

      Yeah I build XO myself, but as I said there are absolutely no issues with other machines... Which is weird.

      I recently reinstalled the said problematic host and relogged in to XO with it.

      Thanks!

      DarkbeldinD 1 Reply Last reply Reply Quote 0
      • DarkbeldinD Offline
        Darkbeldin Vates 🪐 Pro Support Team @adriangabura
        last edited by

        adriangabura Was this VM on "auto power on" mode cause that's not by default?

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          adriangabura @Darkbeldin
          last edited by

          Darkbeldin I think so...
          To clarify I exported all vms from 8.1 wiped the drives and did a clean XCP-ng 8.2 install. Then I imported the VMs via XO. As far as I know auto-power-on wasn't enabled, I think I enabled it by clicking it. I haven't had the opportunity to do more restart tests because this server is always on for various tasks...

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by

            Try to disable/enable autostart in Advanced section of your VM. That might do the trick.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post