Categories

  • All news regarding Xen and XCP-ng ecosystem

    144 Topics
    5k Posts
    rzrR
    @marcoi said: Applied the latest pushed updated to production, no major issues. Thank you for testing The only thing to note is my backup XCP config failed Sunday, (...) This morning the backup ran without issues. Glad it has finally to work, if problem occurs again feel free to ask about this feature in this subforum: https://xcp-ng.org/forum/category/21/backup

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    F
    Hardware update: Got a couple M9148 (4 port Matrox DP) and Wavlink WL-UG7500DH (4 port DP/HDMI) in to test. Configured a Win11 Pro VM with the Matrox driver. It broke the VM so severely that I had to re-pave. So, I pulled the card, swapped for a Wavlink and created another Win11 Pro VM - to which I assigned the Wavlink card and loaded their drivers. It works flawlessly. Both HDMI displays I had connected were instantly recognized in Device Manager and available. I then shut it down, created another VM with Mint 22.3 and assigned resources exactly per the Windows machine. Installed the Wavlink Ubuntu driver and DisplayLink. Rebooted. Still only see the XOA virtual (Console) screen regardless if I have the VM's VGA option turned on or not. The evdi driver is running as is the DisplayLink service. Looking at Xorg.0.log, I see EDID returns for the two HDMI monitors connected to the Wavlink card along with that from the virtual screen - but no screens other than the virtual one show in Display. Interesting bit: The GT730 card behaves EXACTLY the same way. Works great under Win11, driver initializes correctly in Mint but no display other than virtual. Going to post something on the DisplayLink support forum but find it odd that two different cards behave the same way in two different OSes.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    poddingueP
    Thanks for checking. That's useful, even if it points away from where I was looking. Clocks within a second of each other means drift probably isn't your problem, and I'd guess the MST/UTC difference is just how dom0 displays it, though I'm not sure. What I keep coming back to is that your full backups fail while the delta jobs on the same hosts never do. That's the same split in https://github.com/vatesfr/xen-orchestra/issues/9181, where full backups hit BodyTimeoutError on VMs with big disks or a lot of free space and the deltas are fine. If your failing VMs look like that, your dates and the MST/UTC detail would do more good on that issue than buried in here. MajorP93 created this issue in vatesfr/xen-orchestra open Full backup fails on large VMs / VMs with lots of free disk space #9181

  • Our hyperconverged storage solution

    49 Topics
    761 Posts
    J
    SM logs "Date","Time","Line","tsNs","id","clusterLoggingSource","detected_level","hostname","job","priority","service_name","syslog_identifier","unit" 2026-07-09T22:01:14.842Z,1783634474842,"[2060240][MainThread] ***** Failed to snapshot!: EXCEPTION <class 'linstorvolumemanager.LinstorVolumeManagerError'>, Unable to activate device path of `xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40` on node `ovbh-pprod-xen01`: SUCC:Successfully set property key(s): StorPoolName, SUCC:New resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' registered., SUCC:Volume with number '0' on resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' successfully registered, ERRO:(ovbh-pprod-xen05) Failed to adjust DRBD resource xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40, SUCC:(ovbh-pprod-xen04) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen04', SUCC:(ovbh-pprod-xen02) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen02', SUCC:(ovbh-pprod-xen01) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Created resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen01'",1783634474842687000,1783634474842687000_2194f1ea,xcp-ng,unknown,ovbh-pprod-xen01,systemd-journal,6,systemd-journal,SM,forkexecd.service 2026-07-09T22:01:15.206Z,1783634475206,"[2060240][MainThread] Raising exception [81, Failed to clone VDI [opterr=Unable to activate device path of `xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40` on node `ovbh-pprod-xen01`: SUCC:Successfully set property key(s): StorPoolName, SUCC:New resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' registered., SUCC:Volume with number '0' on resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' successfully registered, ERRO:(ovbh-pprod-xen05) Failed to adjust DRBD resource xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40, SUCC:(ovbh-pprod-xen04) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen04', SUCC:(ovbh-pprod-xen02) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen02', SUCC:(ovbh-pprod-xen01) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Created resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen01']]",1783634475206274000,1783634475206274000_2137a4ec,xcp-ng,unknown,ovbh-pprod-xen01,systemd-journal,6,systemd-journal,SM,forkexecd.service 2026-07-09T22:01:15.215Z,1783634475215,"[2060240][MainThread] ***** generic exception: vdi_snapshot: EXCEPTION <class 'xs_errors.SROSError'>, Failed to clone VDI [opterr=Unable to activate device path of `xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40` on node `ovbh-pprod-xen01`: SUCC:Successfully set property key(s): StorPoolName, SUCC:New resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' registered., SUCC:Volume with number '0' on resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' successfully registered, ERRO:(ovbh-pprod-xen05) Failed to adjust DRBD resource xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40, SUCC:(ovbh-pprod-xen04) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen04', SUCC:(ovbh-pprod-xen02) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen02', SUCC:(ovbh-pprod-xen01) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Created resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen01']",1783634475215733000,1783634475215733000_8881a7dc,xcp-ng,unknown,ovbh-pprod-xen01,systemd-journal,6,systemd-journal,SM,forkexecd.service 2026-07-09T22:01:15.228Z,1783634475228,"[2060240][MainThread] ***** LINSTOR resources on XCP-ng: EXCEPTION <class 'xs_errors.SROSError'>, Failed to clone VDI [opterr=Unable to activate device path of `xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40` on node `ovbh-pprod-xen01`: SUCC:Successfully set property key(s): StorPoolName, SUCC:New resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' registered., SUCC:Volume with number '0' on resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on node 'ovbh-pprod-xen01' successfully registered, ERRO:(ovbh-pprod-xen05) Failed to adjust DRBD resource xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40, SUCC:(ovbh-pprod-xen04) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen04', SUCC:(ovbh-pprod-xen02) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Added peer(s) 'ovbh-pprod-xen01' to resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen02', SUCC:(ovbh-pprod-xen01) Resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' [DRBD] adjusted., SUCC:Created resource 'xcp-volume-73b0bb04-2a8f-433d-b0bb-51a887fc4a40' on 'ovbh-pprod-xen01']",1783634475228432000,1783634475228432000_9ae0439a,xcp-ng,unknown,ovbh-pprod-xen01,systemd-journal,6,systemd-journal,SM,forkexecd.service Linstor controller and satellite logs Logs-A-data-2026-07-09 15_11_07.csv.txt

  • Non-English speakers

    36 Topics
    117 Posts
    B
    Merci beaucoup pour vos retours ! @nathanael-h : C'est l'étape suivante !!! J'ai découvert cluster API le mois dernier et j'ai déja testé sur d'autres plateforme ! ça déchire !!! Je ne savais pas qu'il y avait un support de XCP-ng ! Je finis ma série d'article pour une installation classique et je bascule sur cluster API ! @ataxyanetwork Merci pour ton repo. Je vais regarder ça