XO does not show all VMs on a particular xs 6.2 node and other



  • I am experiencing some problems using XO.

    1. On a particular node (xs 6.2), named xen03, I have imported several VMs exported from an older node (xs 5.6) but XO only showed 3 not imported VMs. Moreover all non-running VMs were not shown as well.
      I tried to restart toolstack on that particular node (xen03) and SOME (not all) of the imported VMs appeared but not the non-running ones. No problems using XenCenter and no problems on other xs nodes. How to force XOA to reread the full VMs list from xen03?

    2. When I start an export from XenCenter, it correctly shows the progress of the task but XOA shows always 0% till the end (100%).

    3. Using XOA I am trying to migrate VMs from xen03 (xs 6.2) to xen07 (xcp-ng 8.0.0) but task does not start and I read no errors. Is it possible to migrate VM from xs 6.2 nodes to xcp-ng 8 ?

    If you prefer I can split the thread.

    Thanks in advance.



  • @by873 said in XO does not show all VMs on a particular xs 6.2 node and other:

    I tried to restart toolstack on that particular node (xen03) and SOME (not all) of the imported VMs appeared but not the non-running ones. No problems using XenCenter and no problems on other xs nodes. How to force XOA to reread the full VMs list from xen03?

    By default, XO only shows active VMs. Look at the filter near the top middle. You should see the entry power_state:running. Remove this and all of your VMs should now be visible.



  • I am not a XO expert but I am able to see there's a filter ... The problem of course is not the filter. If your reread carefully my post you can see that the problem exists also (and above all) with the running VMs that are not completely shown.

    Thanks.



  • Yes... I believe that understood what you wrote. I'm honestly not sure if XO still works with such an old version of XS. 🙂

    Therefore, I only tried to address to the portion re: restarting the toolstack and the non-running VMs still not being show. It's unclear from your response if you tried clearing out the entry field to the right of the filter dropdown. Alternatively, you could try selecting "None" from the filter dropdown.

    P.S. You can click on the person icon (bottom of left panel) to access your user prefs. There, you can change the default filter to something that meets your expectations.


  • Admin

    XO will work on older XS. The main issue could be related to duplicated uuids. Please open a support ticket so we could take a look remotely.



  • @olivierlambert said in XO does not show all VMs on a particular xs 6.2 node and other:

    XO will work on older XS. The main issue could be related to duplicated uuids. Please open a support ticket so we could take a look remotely.

    Yes, that's right, since such VMs were imported with "preserve=true" they have the same UUID and XOA shows only one of the two instances (sometime the old one and sometime the new one regardless of running state).
    The issue is already known:
    https://github.com/vatesfr/xen-orchestra/issues/4287

    Is there a way to change VM UUID without cloning one of the two instances?

    Please let me know if it's possible to perform VMs migration from xs 6.2 to a XCP-ng 7/8?

    P.S. I don't know where to open a support ticket since I am testing the free version.


  • Admin

    You really want to avoid duplicated UUID. It's a bad practice. By definition, UUIDs are meant to be... Unique. You solution could be to halt one of the two duplicated VM, fast clone it, and then remove the "original".

    There's no easy option in XO to handle those non unique UUID. Remove those VMs and go on 🙂



  • Yes, you are right infact the old instances are halted and are temporarily kept till I am not sure the imported ones are perfectly working on new node. Unfortunately in the meantime I need a way to manage boths and it means xencenter or cli. Thanks for having pointed my attention to the duplicated uiids problem.


Log in to reply
 

XCP-ng Pro Support