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

    V2V migrated VMs don't autostart

    Scheduled Pinned Locked Moved Unsolved Migrate to XCP-ng
    1 Posts 1 Posters 17 Views 1 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.
    • J
      jr-m4
      last edited by jr-m4

      I'm at the moment doing alot of test with V2V (applause on getting rid of the vddk-dependency btw 😄 )

      However, what I'm noticing is that the migrated VMs don't automatically start when the import has completed. This is contrary to current documentation.

      Is this a potential bug? Or am I missing something obvious?

      PS: The imports are all sucessfull. It's just the auto-start part that I'm noticing doesn't work.

      Cheers!

      Commit: dc573

      Template used for testig is: Rocky Linux 9

      1 Reply Last reply
      Reply Quote 1
      • J jr-m4 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