Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    A
    @stormi I'm also getting error on some VMs while trying to export a disk and also trying to even start some VMs from NFS (that were fine before). xo-server[565]: 2026-05-13T02:53:15.746Z xo:api WARN admin | vm.start(...) [2s] =!> XapiError: INTERNAL_ERROR(xenopsd internal error: Storage_error ([S(Illegal_transition);[[S(Activated);S(RO)];[S(Activated);S(RW)]]])) xo-server[565]: 2026-05-13T02:53:40.652Z xo:api WARN admin | vm.start(...) [3s] =!> XapiError: SR_BACKEND_FAILURE_46(, The VDI is not available [opterr=VDI 399734eb-5965-4799-ac36-f6dd774db867 not detached cleanly], )
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    T
    Hello, I have a project where I need to replace a physical Windows PC with a VM running on XCP-ng. Current use case: The physical PC continuously broadcasts audio through a 3.5 mm jack output connected to external speakers/amplifier. I want to migrate this workload to a Windows VM hosted on XCP-ng. The VM will mainly be used for continuous audio playback. I would like to know the best and most stable solution regarding audio support on XCP-ng. Questions: Does XCP-ng officially support audio devices for Windows VMs? Is USB sound card passthrough the recommended approach? Has anyone successfully used a USB audio adapter with Windows 11 VM on XCP-ng for continuous audio output? Are there recommended compatible USB sound cards/chipsets? Is PCI passthrough of an internal sound card supported/reliable on XCP-ng? Any known stability issues for 24/7 audio playback? Would Windows 11 be better than Windows Server for this use case? Environment: Hypervisor: XCP-ng Guest OS planned: Windows 11 Audio output required: physical 3.5 mm jack Goal: replace a physical audio broadcasting PC Thank you for your feedback and recommendations.
  • 3k Topics
    28k Posts
    olivierlambertO
    Ping @julienxovates
  • Our hyperconverged storage solution

    47 Topics
    745 Posts
    J
    @Mathieu-L linstor n l was included in my original post. All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted. May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted. When xen04 was restarted, that is when this issue happened. I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !