1. Home
  2. Popular
Log in to post
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    211
    1 Votes
    211 Posts
    22k Views
    gduperreyG
    @manilx We recently upgraded our Koji build system. This may have caused disruptions in this recent update release yesterday, where an XML file was generated multiple times. This has now been fixed and should not happen again. This may explain the issue encountered this time, particularly with the notification of updates via XO. Note that normally yum metadata expires after a few hours and so it should normally return to normal on its own.
  • D

    VM UUID via dmidecode does not match VM ID in xen-orchestra

    Infrastructure as Code
    9
    0 Votes
    9 Posts
    39 Views
    olivierlambertO
    No, it's fine, as long the issue contains all the relevant details it's fine
  • Tristis OrisT

    What metadata restore really do?

    Backup
    5
    0 Votes
    5 Posts
    47 Views
    Tristis OrisT
    @psafont is it safe to remove it on production pool? whenever the SDN controller is turned on. so, i can do something on new host, before joining into pool to generate this cert?
  • Y

    Trial period extension for on-going tests

    Xen Orchestra
    3
    0 Votes
    3 Posts
    30 Views
    Y
    @olivierlambert Thank you Olivier
  • M

    Confirming health checks work

    Backup
    8
    1
    0 Votes
    8 Posts
    101 Views
    olivierlambertO
    It's better to have it to get handy options like IP addresses displayed and so on.
  • P

    Windows 2008 Guest tools

    Migrate to XCP-ng
    18
    0 Votes
    18 Posts
    2k Views
    olivierlambertO
    You can also avoid using PV drivers, it will work.
  • D

    Error importing a VM exported from XCP 8.3 to XCP 8.3

    Compute
    4
    0 Votes
    4 Posts
    41 Views
    J
    I experienced the same issue! What I found was that just doing a "yum update" was not enough, though it was needed. When I was initially getting the error, I was trying to import on a host that was not the master of the pool. After I designated that host as the pool master, the same command worked easily. I had to do both the update and import on the master only.
  • henri9813H

    Unable to add new node to pool using XOSTOR

    XOSTOR
    9
    0 Votes
    9 Posts
    72 Views
    henri9813H
    Hello @ronan-a Just to be sure, you want logs of the node which want to join or the master ? Bonne journée