Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    dthenotD
    @Andrew Hello, 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). Is it still a problem? It might have multiple causes. If it's still an issue, could you share the logs: /var/log/{SMlog,xensource.log,daemon.log}. It contains information that could help us investigate. The VDI not detached cleanly means that the VDI still has a reference to the host it was running on before. It's might be caused by the xenopsd error earlier or maybe it's the cause. If you are sure no tapdisk are using the VDI, you can look at tap-ctl list output on each host. You can clean this reference with the script in /opt/xensource/sm/resetvdis.py single <VDI UUID>.

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    Y
    @yllar @mik @Pilow @marcvds Hello, we think we now understand better this issue. We think it's a Xen issue with regard to PCI devices on segment 0001 (which is your case) and not a dom0 driver issue. Could you give a try to this ISO installer please? Please note that this is a custom test ISO and it is therefore not officially supported, do not use it for production, it is just to confirm that it fixes your issue, we will release a supported ISO in the future (target date for now is June). unsupported test ISO for you to test: https://nextcloud.vates.tech/index.php/s/iHf8sqq39EqE683 Regards, Yann

  • All Xen Orchestra related questions/reports

    3k Topics
    28k Posts
    N
    @julienXOvates said: so you're actually trying to import those QCOW2 VDIs, not creating them, right ? Yes... @julienXOvates said: You'll have to wait for the import feature for QCOW2 which is coming soon. You should be able to create a brand new SR with QCOW2, but be aware of the known issue on ZFS with large VDIs Okay... @julienXOvates said: Did you install ZFS on your host ? I installed XCP-ng using the defaults and recommended settings, I do not remember if ZFS was a default: [09:28 xcp-kbbn ~]# df -Th Filesystem Type Size Used Avail Use% Mounted on devtmpfs devtmpfs 3.6G 16K 3.6G 1% /dev tmpfs tmpfs 3.6G 316K 3.6G 1% /dev/shm tmpfs tmpfs 3.6G 9.3M 3.6G 1% /run tmpfs tmpfs 3.6G 0 3.6G 0% /sys/fs/cgroup /dev/sdb1 ext3 18G 2.1G 15G 13% / /dev/sdb4 vfat 512M 3.3M 509M 1% /boot/efi /dev/sdb5 ext3 3.9G 88M 3.6G 3% /var/log 192.168.130.102:/media/KbbnNFS04/ITDocuments/ITDocuments/Iso nfs 1.9T 259G 1.6T 14% /run/sr-mount/d7f0d912-ddc4-ab46-6693-39a6b0d49a14 /dev/mapper/XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 2.6T 30G 2.5T 2% /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e tmpfs tmpfs 731M 0 731M 0% /run/user/0 [09:28 xcp-kbbn ~]# lsblk -f NAME FSTYPE LABEL UUID MOUNTPOINT sdf LVM2_member nl8bHb-caA4-aw3k-S1c2-rm3h-zfXc-4urbyC └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e sdd xfs KbbnNFS03 3ff0be13-df43-455f-8af5-bb5278378279 sdb ├─sdb4 vfat BOOT-TZOZOJ 1B19-9FAC /boot/efi ├─sdb2 ├─sdb5 ext3 logs-tzozoj d09535b9-cd49-4bac-8aeb-17872bda910e /var/log ├─sdb3 LVM2_member 0kSCqD-PNaB-0E2Q-xJ1o-rvTW-NAC0-zEzM6D │ └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e ├─sdb1 ext3 root-tzozoj 70792b7e-b92d-4913-a2cc-4ed6f8fe014e / └─sdb6 swap swap-tzozoj 46d5a332-2728-452e-9c30-1e837fb6cf25 [SWAP] tdc tda sde LVM2_member xRwg78-m9o1-mGki-KfO7-MSY3-gLjD-UKZjQo └─XSLocalEXT--d318a008--a239--821f--a9cd--1f1b657e492e-d318a008--a239--821f--a9cd--1f1b657e492e ext4 9cf95f7d-249b-45e3-9584-a02f1b2a367a /run/sr-mount/d318a008-a239-821f-a9cd-1f1b657e492e sdc xfs KbbnNFS02 765ca566-c434-45a5-9b9f-f066c770a7d4 sda xfs KbbnNFS01 a91987c0-1c2e-4e88-bcf6-fe7662e77cb6 tdd tdb but you can see sd(a,d,c) are from the 3 HDs I did not include in the install are ZFS, I attached them as SRs so I can move the data later to a Storage Device using this method: [15:27 xcp-kbbn NAS]# xe host-list uuid ( RO) : 9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 name-label ( RW): xcp-kbbn ----------------------------- Disk NAS ----------------------------- xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 1) [16:08 xcp-kbbn srv]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369 929ccfc5-b810-89c4-1cdd-e9ee77f38bcf ----------------------------- Disk KbbnNFS01 ----------------------------- 2) ln -s /dev/sda /srv/NAS/sda #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sda: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ----------------------------- Disk KbbnNFS03 ----------------------------- 2) ln -s /dev/sdd /srv/NAS/sdd #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sdd: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes ----------------------------- Disk KbbnNFS02 ----------------------------- 2) ln -s /dev/sdc /srv/NAS/sdc #although it might be better to use a stable identifier if you have multiple disks 3) xe sr-scan uuid=929ccfc5-b810-89c4-1cdd-e9ee77f38bcf (info from fdisk -l) Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes, 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes and both systems (well be converting the other one later) are Redhat 10s formatted with ZFS, and was importing from the other Redhat. Well this be a and/or the reason for the import failure?

  • 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.

  • Non-English speakers

    35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !