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

      Timestamp lost in Continuous Replication

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

      AMD 'Barcelo' passthrough issues - any success stories?

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      11
      1
      0 Votes
      11 Posts
      373 Views
      DustyArmstrongD
      @timemaster5 Ah very cool, thank you for looking into this and the comprehensive write up, great work. I went on a small journey to try various workarounds but didn't get as far as yourself and others, particularly as my use-case is only a "nice-to-have". Most everything I found was in relation to Proxmox and others. Little did I know when I thought I was helping you over on Github, you would actually end up helping me! As I understand from your notes, the full procedure would be: Enable passthrough for the GPU on the host Apply the patched wrapper to enable custom model args and respect platform vga Disable emulated VGA via platform:vga=none Apply the config to the VM via -device loader options Reboot the host Mount the GPU to the VM and boot it up
    • AlexanderKA

      Nested Virtualization in xcp-ng

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

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

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      55
      3
      2 Votes
      55 Posts
      6k Views
      nikadeN
      Did anyone try to patch xo and xcp-ng to the latest and did you have any luck with backups since then? Im on XO (Xen Orchestra, commit 449e7 and Master, commit 2aff8) and the latest xcp-ng 8.3 with all patches installed and im still seeing the "Body timeout error" on 4/8 vm's: [image: 1773477836132-068493da-8294-4a11-957b-7e71640b787f-image.jpeg] Some works tho: [image: 1773477912038-33942c1a-1240-4897-9836-90a13c55de1b-image.jpeg] Observium has a 20Gb VDI with 15Gb used, jupiter has a 20Gb VDI with 12Gb used. Let me know if you want any logs from my XO or XCP and I'll happily provide them.