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

      AMD 'Barcelo' passthrough issues - any success stories?

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      12
      1
      0 Votes
      12 Posts
      395 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.
    • P

      Timestamp lost in Continuous Replication

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      7
      2
      0 Votes
      7 Posts
      65 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,
    • H

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

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      56
      3
      2 Votes
      56 Posts
      7k Views
      C
      @nikade I did install the 97 XCP patches and that night the VM that was failing to backup was able to successfully backup. It had a 500GB secondary drive that was formatted but totally empty. I had not yet patched my XO from source to the latest, it was maybe 24 commits behind. On Friday I updated it so I will find out on Monday if those backups continued to work but I assume they did.
    • AlexanderKA

      Nested Virtualization in xcp-ng

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      11
      0 Votes
      11 Posts
      136 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
    • A

      "NOT_SUPPORTED_DURING_UPGRADE()" error after yesterday's update

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      24
      0 Votes
      24 Posts
      1k Views
      M
      @MajorP93 said: -disable HA on pool level -disable load balancer plugin -upgrade master -upgrade all other nodes -restart toolstack on master -restart toolstack on all other nodes -live migrate all VMs running on master to other node(s) -reboot master -reboot next node (live migrate all VMs running on that particular node away before doing so) -repeat until all nodes have been rebooted (one node at a time) -re-enable HA on pool level -re-enable load balancer plugin Never had any issues with that. No downtime for none of the VMs. update time again. and same issue I followed these steps -upgrade master -upgrade all other nodes -restart toolstack on master -restart toolstack on all other nodes -live migrate all VMs running on master to other node(s) -reboot master now cant migrate anything else. live migration : NOT_SUPPORTED_DURING_UPGRADE warm migration: fails and VM shuts down immediately and needs to be forced back to life CR backup to another server : NOT_SUPPORTED_DURING_UPGRADE