XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • O

      Host time and XOA time are not consistent with each other

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Xen Orchestra
      3
      0 Votes
      3 Posts
      84 Views
      poddingueP
      @tjkreidl has it right, I think: the host and the XO VM each keep their own clock, so both of them need a working NTP source. The page he means is probably this one: https://docs.xcp-ng.org/management/hosts-pools#time-synchronization-ntp. There are two older threads with this warning, and in both it seems to have come down to one side not reaching any NTP server, once because NTP was never set on the host (https://xcp-ng.org/forum/post/86396) and once because DNS broke after an update (https://xcp-ng.org/forum/post/97429). Could you run chronyc sources on the host and timedatectl on the XO VM right after a reboot, and tell us whether you're on XOA or XO built from sources? Olivier mentioned in one of those threads that XOA comes with an NTP client while a from-sources install leaves that part to you, but I'm not sure that alone explains why it shows up after every reboot.
    • Y

      iGPU PCI passthrough: new experimental packages need testers

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      19
      1 Votes
      19 Posts
      2k Views
      S
      @yannsionneau Is it going to be a long time before iGPU PoC packages are ready to be included in the standard XCP-ng update packages?
    • florentF

      V2V in XO 6: a brand new migration wizard, with Auto-pilot docking 🛬

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      18
      5
      0 Votes
      18 Posts
      607 Views
      johnnezeroJ
      @Danp Very good, we have a dedicated V2V XOA setup that I can switch to the "Latest" channel when 6.11 is released (as it only handles the V2V migrations for the current pool were moving off VMware). Unfortunately we have experience "buggy" issues when running the "Latest" release on our PROD XOA (and I was told it can be expected), which is why were a bit gun-shy of running it there. Thanks again for all the info, and Happy Day:)