Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    D
    Hello all, Version 9.1.145 Release Signed of the Windows PV 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 release brings the new XCP-ng Standard VGA Display Driver as well as multiple bug fixes to all Windows drivers and guest tools components. Changes since 9.1.100 NEW: The XCP-ng Standard VGA Display Driver is now included in the package. Improved: XenClean is now a single executable that's more convenient to use. Improved: Better uninstalling of existing drivers. Fixes: Automatic time sync is now disabled by default. NTP sync with W32Time is recommended instead. Fixes: Xen Guest Agent now supports driver restarts and upgrades. Fixes: Fix uninstallation of individual drivers. Fixes: Improved stability and efficiency of Xenbus and Xenvbd. 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. Full Changelog: https://github.com/xcp-ng/win-pv-drivers/compare/v9.1.100...v9.1.145 Original build: https://github.com/xcp-ng/win-pv-drivers/actions/runs/23188455900

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    U
    Thank you all for your answers—now it's clear.

  • All Xen Orchestra related questions/reports

    3k Topics
    27k Posts
    M
    @benapetr Is your XO fully up to date? I remember that there was a bug that caused this spinning wheel / infinite loading on XO6 that got fixed already. Maybe the issue you faced is related to that. I do not know about compatibility with 8.2 but can imagine that it is not supported as it is EOL so probably no compatibility guaranteed by Vates.

  • Our hyperconverged storage solution

    43 Topics
    729 Posts
    SuperDuckGuyS
    @alcoralcor Thanks for the info. I thought maybe I was using too many disks, so I've tried creating disk groups of 3-4 drives with the same issue.

  • Non-English speakers

    33 Topics
    98 Posts
    J
    @yann Ce n'est pas de la PROD. Si ma compréhension est bonne, après recherche, le stockage vers la LUN NetAPP (iSCSI) a été perdu, la mode HA étant actif (les volumes HA n'était plus accessible). [10:05 xcp-ng-poc-1 ~]# xe vm-list The server could not join the liveset because the HA daemon could not access the heartbeat disk. [10:06 xcp-ng-poc-1 ~]# xe host-emergency-ha-disable Error: This operation is dangerous and may cause data loss. This operation must be forced (use --force). [10:06 xcp-ng-poc-1 ~]# xe host-emergency-ha-disable --force [10:06 xcp-ng-poc-1 ~]# xe-toolstack-restart Executing xe-toolstack-restart done. [10:07 xcp-ng-poc-1 ~]# Côté stockage [10:09 xcp-ng-poc-1 ~]# xe pbd-list sr-uuid=16ec6b11-6110-7a27-4d94-dfcc09f34d15 uuid ( RO) : be5ac5cc-bc70-4eef-8b01-a9ed98f83e23 host-uuid ( RO): 0219cb2e-46b8-4657-bfa4-c924b59e373a sr-uuid ( RO): 16ec6b11-6110-7a27-4d94-dfcc09f34d15 device-config (MRO): SCSIid: 3600a098038323566622b5a5977776557; targetIQN: iqn.1992-08.com.netapp:sn.89de0ec3fba011f0be0bd039eae42297:vs.8; targetport: 3260; target: 172.17.10.1; multihomelist: 172.17.10.1:3260,172.17.11.1:3260,172.17.1.1:3260,172.17.0.1:3260 currently-attached ( RO): false uuid ( RO) : a2dd4324-ce32-5a5e-768f-cc0df10dc49a host-uuid ( RO): cb9a2dc3-cc1d-4467-99eb-6896503b4e11 sr-uuid ( RO): 16ec6b11-6110-7a27-4d94-dfcc09f34d15 device-config (MRO): multiSession: 172.17.1.1,3260,iqn.1992-08.com.netapp:sn.89de0ec3fba011f0be0bd039eae42297:vs.8|172.17.0.1,3260,iqn.1992-08.com.netapp:sn.89de0ec3fba011f0be0bd039eae42297:vs.8|; target: 172.17.0.1; targetIQN: *; SCSIid: 3600a098038323566622b5a5977776557; multihomelist: 172.17.1.1:3260,172.17.10.1:3260,172.17.11.1:3260,172.17.0.1:3260 currently-attached ( RO): false [10:09 xcp-ng-poc-1 ~]# xe pbd-plug uuid=be5ac5cc-bc70-4eef-8b01-a9ed98f83e23 Error code: SR_BACKEND_FAILURE_47 Error parameters: , The SR is not available [opterr=no such volume group: VG_XenStorage-16ec6b11-6110-7a27-4d94-dfcc09f34d15], [10:10 xcp-ng-poc-1 ~]# Après ca, XO-Lite s'est correctement relancé.