Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    D
    Hello all, Version 9.2.350 Release of the Windows guest tools has been released. Download the latest release here: https://github.com/xcp-ng/win-pv-drivers/releases It will be integrated into the XCP-ng built-in tools ISO after a test period of 2 weeks. This major release brings a new Windows guest agent with many new features, plus multiple other improvements. To download XenClean, click here. The installer downloads also includes a copy of XenClean and XenBootFix. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Remember to carefully read XenClean docs before use. Note: Always download the latest XenClean/XenBootFix from https://github.com/xcp-ng/win-pv-drivers/releases Before installing Thank you for using our Windows PV tools. Please carefully read the instructions below. It is not necessary to run XenClean when upgrading from previous versions of the XCP-ng Windows guest tools, unless prompted by the installer. Not compatible with the "Manage Citrix PV drivers via Windows Update" option. You must disable this option before installing. Changes since 9.1.200 NEW: Overhauled Windows guest agent with many new features: Supports configuring guest IP addresses from within the host using xe vif-configure-ipv4 and xe vif-configure-ipv6. Session agent now gains a tray icon and About dialog. Improved clipboard sync stability and accuracy. Better reporting of OS versions. Time sync is now integrated with W32Time. NTP is now the only recommended setup for time sync on XCP-ng Windows guests. Improved: Update XSTDVGA to v0.1.211.1039; improve compatibility. Improved: Better reporting of IPv6 addresses. Fixed: Better network stability during high load. Fixed: Storage driver bug fixes. Fixed: Better installer resilience when the offboard task is pending. Help / Community support If you encounter installation/uninstallation errors, please try again with one of the following commands: For installing: msiexec.exe /i XenTools-x64.msi /log install.log For uninstalling: msiexec.exe /x XenTools-x64.msi /log uninstall.log Please include this log along with the file C:\Windows\INF\setupapi.dev.log in your bug report. These files will help us troubleshoot any installation issues. Additionally, please report any errors or BSOD you encounter during testing of this release. Your feedback is very appreciated. Discussion: https://xcp-ng.org/forum (preferred) Issue Tracker: https://github.com/xcp-ng/xcp/issues IRC: #xcp-ng and #xcp-ng-dev on irc.freenode.net Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.1.200...v9.2.350 Original build: https://github.com/xcp-ng/win-pv-drivers/actions/runs/31088530595

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    pandusenP
    @andriy.sultanov said: I'll try to see why other devices are omitted and how this can be fixed. Any news on this? I have been fighting with getting an Intel Arc Pro B50 to work on Linux for months and i suspect that, the fact that the audio device isn't present, is what makes Linux fail to load the driver correctly. Going the xen-cmdline way, seams to disable xe passthrough both in command line and in XO gui, causing all kinds of issues. Windows seems to be able to initialise the GPU driver without the audio device, but it is in some kind of borked state. You can send workload to the GPU but the drivers are complaining about "no-pci compatibility". XCP-ng 8.3 (latest patches) Fedora server 44 - Kernel 7.1.5-201 on latest Arc firmware as well.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    G
    @jb You have hit on something that ties into what I have discovered. Since July 1, on my XCP-ng / XO-CE cluster, the metadata and xo-config backup job only runs successfully when I have all 3 hosts in my cluster active, and after I have reset the tool stack on the Master host. Because I am running the XCP-ng and XO-CE on an off-grid solar/battery system, independent of my electric bill, I try to limit total power to 250 watts for all devices (network switches, iSCSI NAS, XCP-ng hosts, etc). Consequently, I run only one host on a regular basis. When it is necessary to update XCP-ng, I turn on all hosts and do a rolling pool update. If I manually perform a metadata and xo-config backup while all of the hosts are on, only then will the backup be successful. Before July 1, the metadata and xo-config back was always successful, whether it was scheduled or manual. Hopefully, this will turn on a light bulb in the head of a Vates engineer, and he or she will solve this issue!

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    131 Posts
    AtaxyaNetworkA
    @jeremie1977 Ah, oui effectivement je n'ai pas testé avec plusieurs disques ! Et j'ai du typo dans la doc, je vais faire une PR pour modifier Je pense que c'est du a la façon d'insérer les disques et les DVD coté XCP-ng. Je vais investiguer !