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

    XenClean | Cleanup Failed on Windows Server 2022 VM

    Management
    3
    1
    0 Votes
    3 Posts
    48 Views
    K
    @dinhngtu Thanks for the fast response, as always.
  • B

    New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

    News
    41
    1
    9 Votes
    41 Posts
    5k Views
    Tristis OrisT
    @benapetr said in New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client: you can switch between them nope, that just 2 from multiple nics. Need press add ip address to add other NICs. Now i see how it works.
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    452
    1 Votes
    452 Posts
    190k Views
    A
    @rzr installed updates will report back. Update - I had migrated vms back over to vhd prior to update release. I have migrated 2 vms back over to qcow2 and the initial backup ran successfull. Ran a second delta backup and that as well was successful with out issues. Backups happen very quickly now. But it appears the % and progress bar are working. When CBT is enabled on the vm vdi. They show up as needing to be coalesced. VMs without CBT enabled the vdis are coalesced. [image: 1776969120079-screenshot-2026-04-23-143142.png] Will continue to monitor. Once the coalesence hits 2 for the vm. The vm is skipped form future backups until cleared. (shutting down the vm will allow the coalescence to happen. 2026-04-23T19_52_34.694Z - backup NG.txt [image: 1776974212800-screenshot-2026-04-23-155432.png] [image: 1776974256962-screenshot-2026-04-23-155727.png]
  • D

    XCP-ng Windows PV tools announcements

    Moved News
    84
    0 Votes
    84 Posts
    12k Views
    D
    Hello all, XenClean 9.1.148 Prerelease is now available with a fix for error 1605 during execution. This is a XenClean-only prerelease. https://github.com/xcp-ng/win-pv-drivers/releases/tag/v9.1.148
  • U

    load-balancer : Affinity to Host groups

    Xen Orchestra
    6
    0 Votes
    6 Posts
    180 Views
    Mitchel-APDM
    @olivierlambert In my understanding, Anti affinity tags only looks for the tags that are attached to the VM. For example: Datacenter 1 Host 1 VM1-1 Host 2 VM1-2 Datacenter 2 Host 3 VM2-1 Host 4 VM2-2 VM1-1 and VM1-2 should be able to migrate to Host 1 and Host 2. VM2-1 and VM2-2 should be able to migrate to Host 3 and Host 4. But VM1-1 and VM1-2 should never be able to migrate to Host 3 and Host 4. VM2-1 and VM2-2 should never be able to migrate to Host 1 and Host 2. With the current (Anti) Affinity tags, it will only look to the tags attached to the VM, so in the example it would be possible for VM1-1 to go to Host 4, if VM2-2 would be at Host 3 together with VM2-1. But if we could tag the hosts, it would not be possible for VM1-1 and VM1-2 to be on Host 3 and Host 4
  • henri9813H

    Storage domain server & Rolling pool upgrade

    XCP-ng
    5
    0 Votes
    5 Posts
    139 Views
    henri9813H
    @gregoire said: @olivierlambert I added this feature request in the backlog regarding RPU improvements. Hello, Thanks all ! Totally agree with @poddingue , be able to exclude VM which has: PCI attached devices Local storage ( maybe ? ) Could be a great option !