1. Home
  2. Popular
Log in to post
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    742
    1 Votes
    742 Posts
    881k Views
    acebmxerA
    @dinhngtu Here are the extracted Xen hypervisor, Dom0 kernel, and toolstack/storage manager logs tracking the exact window of the NFS storage deadlock on Oct 27 between 13:00 and 15:00. During this window, xe task-list was completely blank, and user VMs went into an uninterruptible B H state (turning into zombie D P H domains upon an xl destroy attempt). Physical hardware interfaces showed zero errors or discards via ethtool. Looking closely at crash_window_SMlog.log, there is a clear locking deadlock right at the start of the backup run (13:00:38): "Failed to lock /var/lock/sm/96fd7d5a-1985-80be-5776-6ace7f651a41/sr on first attempt, blocked by PID 86371" It looks like the parallel multi-stream VHD storage exports/NBD operations lock-contended the SR control handles so badly that the underlying sm/blktap layer deadlocked entirely. I have attached the full log bundle containing: xen_hypervisor.log (Xen ring buffer / xl dmesg) crash_window_kernel.log (Dom0 kernel events from /var/log/kern.log) crash_window_SMlog.log (Storage manager tracks from /var/log/SMlog.1) xapi_crash.log (Toolstack logs from /var/log/xensource.log.1) https://drive.google.com/drive/folders/1uCnWXArfgyvS1gPl3mViUl8G1-DBOGzD?usp=sharing - due to file size and type i could not upload here. So i posted it on my google drive.
  • D

    Node.js October 21, 2026 Security Releases

    Xen Orchestra
    5
    0 Votes
    5 Posts
    774 Views
    acebmxerA
    @willamcorlin, If you are using my installer script (https://github.com/acebmxer/install_xen_orchestra), there are two quick ways to verify the active Node.js version. @poddingue can you confirm this is correct? 1. During the Update/Install Process The script explicitly pulls the active environment version and prints it out against your NODE_VERSION target in the logs: ❯ node -v v24.22.1 [INFO] Node.js v24.22.1 satisfies configured version 24 — no runtime change needed [INFO] Installing Node.js 24... [INFO] Node.js 24 requirement satisfied (installed: v24.22.1) 2. Verifying the Live Service Runtime To be absolutely certain that the running systemd daemon is executing the correct binary instance after a restart, you can check the status of the xo-server unit: sudo systemctl status xo-server.service Look at the CGroup line in the output. It maps directly to the active path and flags (such as the heap memory allocations set by the script): CGroup: /system.slice/xo-server.service └─18540 /usr/bin/node --max-old-space-size=5410 /opt/xen-orchestra/packages/xo-server/dist/cli.mjs You can then run /usr/bin/node -v (or whatever path is reflected there) to double-check that the active service binary is indeed on the patched release line (v24.22.1, v22.23.4, etc.).
  • B

    Native Ceph RBD SM driver for XCP-ng

    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.