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

    Access XOA Logs via API?

    REST API
    6
    0 Votes
    6 Posts
    155 Views
    T
    @MathieuRA The context for my question is I created an app to control my VMs and though my app said a VM started it really didn't. When I went into the logs I noticed an error, so my thought is to be able to check the logs would be helpful to find out if there is an error or not. Let me update my app because I'm thinking I can get around not having access to the logs. Thank you for the prompt response! Have a blessed day!
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    298
    1 Votes
    298 Posts
    116k Views
    stormiS
    New security and maintenance update candidate for you to test! A hardware issue was found in AMD Zen 5 CPU devices, related to how random numbers are generated. It's best fixed via a firmware update, but we also provide updated microcode to mitigate it, and Xen is updated to support loading the newer microcode. We also publish other non-urgent updates which we had in the pipe for the next update release. Security updates: amd-microcode: This release fixes vulnerability CVE-2025-62626 in AMD Zen 5 CPUs microcode that may generate excessive number of zeros in random outputs, potentially compromising cryptographic security. xen: Introduce support for the new Linux AMD microcode container format (multiple blobs per CPU), Address the XSA-476 vulnerability (CVE-2025-58149), low severity on XCP-ng (affects an unsupported feature of Xen) Enable passthrough of devices on non-zero PCI segments. Improve performance of resumed or migrated VMs by supporting superpage restoration Fix detection of the Self Snooping feature on capable Intel CPUs gpumon, xcp-featured: rebuilt for updated XAPI qemu: Synchronize with XenServer's fix for the Windows Server 2025 NVMe write cache issue that we fixed previously Fix device passthrough with devices in a PCI segment different from 0 sm: Upstream changes: Robustify CBT enable/disable calls to prevent errors. Various fixes regarding SCSI commands/functions. Add tolerance in the GC during leaf coalesce. Improves GC logging and corrects rare race conditions. Our changes Use serial instead of SCSI ID for SR on USB devices to prevent bad match. Explicit error message during LVM metadata generation when VDI type is missing. Correct and robustify LINSTOR deletion algorithm to manage in-use volumes. Avoid throwing LINSTOR exceptions in case of impossible temporary volume deletion in order to properly terminate higher-level API calls. Prevent XOSTOR operations if LINSTOR versions mismatches on a pool. varstored: Restore and update the default dbx for new VMs. That's the main change for users: we now embed the latest UEFI certificates with XCP-ng, making pools ready for secure boot out of the box. We'll update the documentation to explain how to handle the transition for existing pools (ranging from "nothing to do" to "do something to ensure that future certificate updates become automatically the pool's default). Fix the format of the default included KEK/db/dbx to ensure safe updates Fix an issue with UEFI variable length limit xapi: Support up to 16 VIFs (virtual network interfaces) per VM (previously: 7) Runnable metrics: runnable_any runnable_vcpus Various fixes, optimizations, small improvements, and foundational changes (such as getting prepared for a newer version of ocaml) gpumon xcp-featured: rebuild for updated XAPI. xcp-ng-pv-tools: Properly detect Red Hat 10 and its derivatives, when installing the Linux guest agent Update Windows Tools to 9.1.100 xcp-ng-release: fix benign "unary operator expected" error, displayed when connecting from some terminal software xha: Nothing of note, minor changes such as logging typos... xo-lite: version 0.17.0 [VM/New] Fix the default topology by setting the platform:cores-per-socket value correctly (PR #9136) [Host/HostSystemResourceManagement] Fix display when control domain memory is undefined (PR [#9197]) xsconsole: Prepare for a future feature. Optional packages updated: qlogic-netxtreme2-alt: alternate driver for NetXtreme2 updated to version 7.15.24. qlogic-qla2xxx-alt: alternate driver qla2xxx updated to version 10.02.14.01_k Test on XCP-ng 8.3 yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot The usual update rules apply: pool coordinator first, etc. Versions: amd-microcode: 20251203-1.1.xcpng8.3 gpumon: 24.1.0-71.1.xcpng8.3 qemu: 4.2.1-5.2.15.1.xcpng8.3 sm: 3.2.12-16.1.xcpng8.3 varstored: 1.2.0-3.4.xcpng8.3 xapi: 25.33.1-2.1.xcpng8.3 xcp-featured: 1.1.8-3.xcpng8.3 xcp-ng-pv-tools: 8.3-15.xcpng8.3 xcp-ng-release: 8.3.0-35 xen: 4.17.5-23.1.xcpng8.3 xha: 25.2.0-1.1.xcpng8.3 xo-lite: 0.17.0-1.xcpng8.3 xsconsole: 11.0.9.1-1.1.xcpng8.3.3 Optional packages: qlogic-netxtreme2-alt: 7.15.24-1.xcpng8.3 qlogic-qla2xxx-alt: 10.02.14.01_k-1.xcpng8.3 What to test Normal use and anything else you want to test. Test window before official release of the updates 2 days.
  • M

    log_fs_usage / /var/log directory on pool master filling up constantly

    XCP-ng
    17
    1
    0 Votes
    17 Posts
    341 Views
    M
    Another thing that I noticed: despite enabling remote syslog (to graylog) for all XCP-ng hosts in the pool /var/log gets filled up to 100%. Adding remote syslog seem to not change usage of /var/log at all. Official XCP-ng documentation states otherwise here: https://docs.xcp-ng.org/installation/install-xcp-ng/#installation-on-usb-drives The linked part of the documentation indicates that configuring remote syslog can be a possible solution for /var/log space constraints which seems to be not the case. I feel like logging could use some investigation by Vates in general.
  • U

    XCP-ng 8.3 and Dell R660 - crash during boot, halts remainder of installer process (bnxt_en?)

    Hardware
    24
    0 Votes
    24 Posts
    2k Views
    stormiS
    The installer is built. We are testing it, then we will be able to provide it to you so you can test it in turn.
  • N

    Fibre Channel on Lenovo (Hardware Compatibility)?

    Hardware
    1
    0 Votes
    1 Posts
    25 Views
    No one has replied
  • A

    Xen Orchestra from source ignores config.toml from /etc/xo-server/

    Xen Orchestra
    2
    0 Votes
    2 Posts
    83 Views
    A
    Ok I've figured out root cause. My config override has only one option: ignoreVmSnapshotResources = true And I had to change it with adding [selfService] on a line below Also I found out that override config for XO5 interface needs to have absolute paths to xo-web and @XenOrchestra in it. With relative paths it didn't work.
  • M

    LUKS Secured VM via Cloud Config

    Xen Orchestra
    1
    0 Votes
    1 Posts
    30 Views
    No one has replied
  • ForzaF

    Retention for log files and audit logs

    Xen Orchestra
    6
    0 Votes
    6 Posts
    599 Views
    E
    I would like to suggest to configure a remote syslog server. it centralizes all the log s and give you full control over the retention. It would also avoid situation where a disk full would impact your logging as well XCP-ng or XOA host operations. For your XCP-NG host go to you POOl, select Advanced tab and configure the Remote syslog host section to point to your syslog server. For XOA, you can follow the instruction here : https://docs.xen-orchestra.com/backups#send-xo-logs-to-an-external-syslog-server
  • A

    Users cannot modify topology settings for VM's

    Management
    1
    0 Votes
    1 Posts
    31 Views
    No one has replied
  • P

    Xen Orchestra from Sources backups Failing.

    Management
    8
    0 Votes
    8 Posts
    686 Views
    P
    If one day, some sad soul encounters these errors and nothing seems to be working or making sense you may have the same issue I did. Back story: Earlier this year, I had a Pool with 3 hosts. Through a series of unfortunate events. The Master died, I recovered as best as I could and assumed all was well as I rebuilt the environment since all of my vm's appeared to be working (except Xen Orchestra). I tried different versions (Ubuntu, Debian, XOA, XO via Docker, etc.). Error: backupNg.runJob { "id": "ea4a9d00-db35-45a9-8a15-f700891d55c6", "schedule": "0811579b-8ad3-4f29-8581-15a35c9c4597" } { "library": "SSL routines", "reason": "tlsv1 unrecognized name", "code": "ERR_SSL_TLSV1_UNRECOGNIZED_NAME", "call": { "duration": 21, "method": "session.login_with_password", "params": "* obfuscated *" } } [image: 1765346178618-a19c2386-f194-4268-af87-3c2307bb9cdd-image.png] In my case, my database was corrupted. By rejoining host to the same damaged pool, the issue remained. In was confusing since an old instance of xen orchestra running Ubuntu 18.04 was the only instance that could run backups successfully. Newer instances could do everything except run backups. Either way, hopefully this never happens to you. If it does, your servers backend database might be the issue. Thanks again to everyone that helped me figure this out throughout the year!