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

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      621
      1 Votes
      621 Posts
      428k Views
      acebmxerA
      @rzr said: We pushed the tested packages along a xen security update to the xcp-ng-updates repository, check blog post for summary and related advisories: https://xcp-ng.org/blog/2026/07/28/july-2026-updates-1-for-xcp-ng-8-3-lts/ Just updated my homelab hosts. [10:45 xcp-ng-disjqdnc ~]# yum clean metadata Loaded plugins: fastestmirror Cleaning repos: xcp-ng-base xcp-ng-updates 6 metadata files removed 4 sqlite files removed 0 metadata files removed [10:45 xcp-ng-disjqdnc ~]# yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Excluding mirror: updates.xcp-ng.org * xcp-ng-base: mirrors.xcp-ng.org Excluding mirror: updates.xcp-ng.org * xcp-ng-updates: mirrors.xcp-ng.org xcp-ng-base/signature | 473 B 00:00:00 xcp-ng-base/signature | 3.0 kB 00:00:00 !!! xcp-ng-updates/signature | 473 B 00:00:00 xcp-ng-updates/signature | 3.0 kB 00:00:00 !!! (1/2): xcp-ng-base/primary_db | 3.9 MB 00:00:00 (2/2): xcp-ng-updates/primary_db | 1.6 MB 00:00:01 Resolving Dependencies --> Running transaction check ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-libs.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update ---> Package xen-tools.x86_64 0:4.17.6-9.3.xcpng8.3 will be updated ---> Package xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 will be an update --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================ Package Arch Version Repository Size ============================================================================================================================================ Updating: xen-dom0-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 704 k xen-dom0-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.0 M xen-hypervisor x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 2.4 M xen-libs x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 66 k xen-tools x86_64 4.17.6-9.3.1.xcpng8.3 xcp-ng-updates 47 k Transaction Summary ============================================================================================================================================ Upgrade 5 Packages Total download size: 5.2 M Is this ok [y/d/N]: y Downloading packages: Delta RPMs disabled because /usr/bin/applydeltarpm not installed. (1/5): xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.0 MB 00:00:00 (2/5): xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 704 kB 00:00:00 (3/5): xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 66 kB 00:00:00 (4/5): xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 2.4 MB 00:00:00 (5/5): xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64.rpm | 47 kB 00:00:00 -------------------------------------------------------------------------------------------------------------------------------------------- Total 2.9 MB/s | 5.2 MB 00:00:01 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 1/10 Updating : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 2/10 Updating : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 3/10 Updating : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 4/10 Updating : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10 Cleanup : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 6/10 Cleanup : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10 Cleanup : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 8/10 Cleanup : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 9/10 Cleanup : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10 Verifying : xen-dom0-tools-4.17.6-9.3.1.xcpng8.3.x86_64 1/10 Verifying : xen-dom0-libs-4.17.6-9.3.1.xcpng8.3.x86_64 2/10 Verifying : xen-hypervisor-4.17.6-9.3.1.xcpng8.3.x86_64 3/10 Verifying : xen-libs-4.17.6-9.3.1.xcpng8.3.x86_64 4/10 Verifying : xen-tools-4.17.6-9.3.1.xcpng8.3.x86_64 5/10 Verifying : xen-libs-4.17.6-9.3.xcpng8.3.x86_64 6/10 Verifying : xen-dom0-tools-4.17.6-9.3.xcpng8.3.x86_64 7/10 Verifying : xen-hypervisor-4.17.6-9.3.xcpng8.3.x86_64 8/10 Verifying : xen-tools-4.17.6-9.3.xcpng8.3.x86_64 9/10 Verifying : xen-dom0-libs-4.17.6-9.3.xcpng8.3.x86_64 10/10 Updated: xen-dom0-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-dom0-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-hypervisor.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-libs.x86_64 0:4.17.6-9.3.1.xcpng8.3 xen-tools.x86_64 0:4.17.6-9.3.1.xcpng8.3
    • K

      Intermittent Xen blkfront I/O stalls: all guest tags busy while tapdisk reports zero outstanding requests

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      7
      0 Votes
      7 Posts
      355 Views
      A
      Hello @kazual82 Sorry for the delay, I was working on a gdb script for you before I was preempt. Yes, I'm curious about GDB backtraces and ring dump. I'm puzzled because even if we miss a notification from the frontend, tapdisk periodically checks blkif ring, so he must see the request with a delay at least. Can you also share your daemon.log and SMlog?
    • D

      CR - Cannot start copy because suspended

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      17
      0 Votes
      17 Posts
      546 Views
      poddingueP
      Good news that it sorted itself out. Both changes went in at once and the next run came back clean on the ADDS VMs too, so I don't think there's anything left to pin down here, and I'd rather say that than invent an explanation after the fact. Your question about the snapshot modes was the useful thing to come out of this thread. I went looking, they genuinely aren't documented anywhere, and that's written up on our side now If the fall back to a full ever comes back on the ADDS VMs specifically, that would deserve its own thread with the SMlog output @tjkreidl asked for, since nobody got to look at that part.