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
    • H

      Potential bug with Windows VM backup: "Body Timeout Error"

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      58
      3
      2 Votes
      58 Posts
      7k Views
      P
      @nikade Hey Nikade, Did you try to create a new job that will do a new chain ? Just for test.
    • DustyArmstrongD

      AMD 'Barcelo' passthrough issues - any success stories?

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      12
      1
      0 Votes
      12 Posts
      400 Views
      T
      @DustyArmstrong Thanks for responding to the GitHub issue. It’s great that more people want this working; it’s difficult to gain traction otherwise. Regarding your list, it’s correct. A reboot should be on the second place. You need to reboot only to detach your PCI device (video card) from its driver and assign it to the pciback driver instead on the next boot. This effectively creates a reservation for the device and allows you to dynamically assign it to VMs. Once your card is free from other kernel drivers, the rest doesn’t require a reboot.
    • AlexanderKA

      Nested Virtualization in xcp-ng

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      11
      0 Votes
      11 Posts
      137 Views
      P
      @AlexanderK Nested virtualisation still need lot of development to be functional reliably - see https://www.youtube.com/watch?v=8jKGYY1Bi_o and https://www.youtube.com/watch?v=3MxWvVTmY1s
    • P

      Timestamp lost in Continuous Replication

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      7
      2
      0 Votes
      7 Posts
      67 Views
      P
      The latest XCP-ng update had an update regarding NTP XAPI, XCP-ng's control plane, was updated to version 26.1.3. Added API for controlling NTP. This might be a longshot and I don't know it this has anything to do with my "problem" The timestamp on ContRep VM's has always been in UTC I'm using Stockholm SE as timezone and other bugs regarding presentation of time have been fixed but not this one,