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
      744
      1 Votes
      744 Posts
      882k Views
      acebmxerA
      @anthoineb Since I had to physical power cycle to clear the I/O block and recover the host, the live kernel state and any active blocked PIDs from the window of the deadlock were cleared upon reboot. Checking the host right now, there are currently no processes sitting in an uninterruptible sleep (D) state, and tap-ctl list shows the standard operational mappings for the running VMs: # tap-ctl list 5175 0 0 vhd /var/run/sr-mount/4991d4aa-ed84-599b-7d19-97f2f943a366/8d3ce0d6-7d4d-40b0-a99f-09daab8d55e1.vhd 5720 1 0 vhd /var/run/sr-mount/4991d4aa-ed84-599b-7d19-97f2f943a366/1c200822-5a23-4afa-93cd-d0d89c076191.vhd 6941 2 0 vhd /var/run/sr-mount/4991d4aa-ed84-599b-7d19-97f2f943a366/0fac203e-4740-4f95-a78c-a3630e591e76.vhd # ps aux | awk '$8 ~ /D/' (Returned empty) Got it regarding the lock retry behavior in SMlog—thanks for clarifying that component. I am pulling the full un-truncated kern.log.1 from yesterday to add to the Google Drive folder so you can inspect the historical kernel call traces right when the backup stream hit the wall. I have uploaded the raw kern.log.1 file directly to the shared folder. Let me know if you want to add the exact file name context anywhere else in the message.
    • D

      Node.js October 21, 2026 Security Releases

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      6
      0 Votes
      6 Posts
      827 Views
      poddingueP
      @acebmxer I haven't run your script, so I can't vouch for the log lines, but the systemctl status check looks like the safer of the two to me. It shows the binary the service is really running. Whichever node comes first in your shell can be a different one if more than one Node is installed. For XOA I'd go with what @Danp said above.
    • B

      Native Ceph RBD SM driver for XCP-ng

      Watching Ignoring Scheduled Pinned Locked Moved Development
      37
      3 Votes
      37 Posts
      9k Views
      dicode-nlD
      @nick.lloyd I guess you haven't installed the newer kernel modules then? Those would fix the new auth method and the msrg2 protocol. Also, the SMAPIv3 is better then the SMAPIv1, then you don;t need qcow2. All snapshots, cbt etc are then ceph-native.
    • V

      Incremental Backup Question

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      2
      1
      0 Votes
      2 Posts
      21 Views
      poddingueP
      Hi, @Velocity1192 . On v6 first: creating and editing backup jobs still happens in XO 5 for now, XO 6 shows the jobs but doesn't create them yet (https://docs.xen-orchestra.com/backups-and-dr/backups-in-xo6). For the schedule, @abudef asked almost the same question earlier this year. @Pilow's answer there is clearer than anything I'd write: https://xcp-ng.org/forum/post/104108. As I read it, you either use one daily schedule plus the "Full backup interval" setting (the full lands N runs after the chain starts), or two schedules on the same job with "Force full backup" ticked on the Sunday one. That second way is how you get to pick the day, and he says not to mix the two. One thing to expect, from @Danp in another thread (https://xcp-ng.org/forum/post/91943) : the oldest backup is always a full and old deltas get merged into it, so for a while you'll see two fulls on the remote rather than weeks 1 and 2 being deleted. I don't think the scheduler can say "every other Sunday". I might be wrong there; someone who runs this kind of plan may know a trick.
    • B

      Missing vdi which is a base for a delta

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      7
      0 Votes
      7 Posts
      159 Views
      poddingueP
      @blueh2o thanks for the log. In that run 16 of the 56 VMs failed this way, and each one names a different missing base, so it doesn't look like one damaged chain to me. That's past what I can work out on my own, so @Team-XO-Backend, this one has a version and a full job log attached above now if someone can take a look.