Actually Alma Linux does have a variant for v2 CPUs so they can run 10.0. Just look for x86_64 v2 on the downloads page.

@Danp I do not, I did not know it was needed. Last cmd run, blew away old SR, using new pool. Type "xsconsole" for access to the management console. [00:09 localhost ~]# xe sr-list uuid ( RO) : bda59d9a-5655-e903-c569-02c8e1c84465 name-label ( RW): VM-Pool name-description ( RW): host ( RO): localhost type ( RO): ext content-type ( RO): user uuid ( RO) : 5ee50bda-201e-633c-ea4c-4ba32b2a0428 name-label ( RW): casaHOS-NextCloud name-description ( RW): casaHOS-NextCloud host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : ae10e37f-237a-d62e-8146-1b9aeeae0562 name-label ( RW): TrueNAS-ISO name-description ( RW): ISOs on trunas host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 405be593-196a-e6c1-1154-737d870ca2c8 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): localhost type ( RO): udev content-type ( RO): iso uuid ( RO) : d076f279-50f3-906a-f29b-a20822dba819 name-label ( RW): Local-ISO name-description ( RW): host ( RO): <not in database> type ( RO): iso content-type ( RO): iso uuid ( RO) : c360423b-dbc3-833c-a77c-9f7cae7102d5 name-label ( RW): USB-ISO name-description ( RW): host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 7acdd6e8-90ba-8657-2a0a-ffbcca86d405 name-label ( RW): casaHOS-Qbitorrent name-description ( RW): casaHOS-Qbitorrent host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : a8875f36-cfbe-f46e-c59f-88fff7d122c1 name-label ( RW): XCP-ng Tools name-description ( RW): XCP-ng Tools ISOs host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 9551e268-d298-8b69-fc1c-15f466ca2b09 name-label ( RW): casHOS-JellyFin name-description ( RW): casHOS-JellyFin host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : eae7b525-517f-6473-d052-0415c7991752 name-label ( RW): casaHOS-immich name-description ( RW): casaHOS-immich host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : 3ae63e9d-33cd-57ff-759a-f939968f1d69 name-label ( RW): Removable storage name-description ( RW): host ( RO): localhost type ( RO): udev content-type ( RO): disk uuid ( RO) : 27384ca2-a23c-d5c7-a3fc-e2ac755d356c name-label ( RW): Main-Pool-XCP name-description ( RW): host ( RO): localhost type ( RO): ext content-type ( RO): user [00:13 localhost ~]# xe sr-list uuid ( RO) : bda59d9a-5655-e903-c569-02c8e1c84465 name-label ( RW): VM-Pool name-description ( RW): host ( RO): <not in database> type ( RO): ext content-type ( RO): user uuid ( RO) : 5ee50bda-201e-633c-ea4c-4ba32b2a0428 name-label ( RW): casaHOS-NextCloud name-description ( RW): casaHOS-NextCloud host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : ae10e37f-237a-d62e-8146-1b9aeeae0562 name-label ( RW): TrueNAS-ISO name-description ( RW): ISOs on trunas host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 405be593-196a-e6c1-1154-737d870ca2c8 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): localhost type ( RO): udev content-type ( RO): iso uuid ( RO) : d076f279-50f3-906a-f29b-a20822dba819 name-label ( RW): Local-ISO name-description ( RW): host ( RO): <not in database> type ( RO): iso content-type ( RO): iso uuid ( RO) : c360423b-dbc3-833c-a77c-9f7cae7102d5 name-label ( RW): USB-ISO name-description ( RW): host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 7acdd6e8-90ba-8657-2a0a-ffbcca86d405 name-label ( RW): casaHOS-Qbitorrent name-description ( RW): casaHOS-Qbitorrent host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : a8875f36-cfbe-f46e-c59f-88fff7d122c1 name-label ( RW): XCP-ng Tools name-description ( RW): XCP-ng Tools ISOs host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 9551e268-d298-8b69-fc1c-15f466ca2b09 name-label ( RW): casHOS-JellyFin name-description ( RW): casHOS-JellyFin host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : eae7b525-517f-6473-d052-0415c7991752 name-label ( RW): casaHOS-immich name-description ( RW): casaHOS-immich host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : 3ae63e9d-33cd-57ff-759a-f939968f1d69 name-label ( RW): Removable storage name-description ( RW): host ( RO): localhost type ( RO): udev content-type ( RO): disk uuid ( RO) : 27384ca2-a23c-d5c7-a3fc-e2ac755d356c name-label ( RW): Main-Pool-XCP name-description ( RW): host ( RO): localhost type ( RO): ext content-type ( RO): user [00:17 localhost ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sdb 8:16 0 465.7G 0 disk ├─sdb4 8:20 0 512M 0 part /boot/efi ├─sdb2 8:18 0 18G 0 part ├─sdb5 8:21 0 4G 0 part /var/log ├─sdb3 8:19 0 424.2G 0 part ├─sdb1 8:17 0 18G 0 part / └─sdb6 8:22 0 1G 0 part [SWAP] sdc 8:32 1 57.3G 0 disk ├─sdc2 8:34 1 32M 0 part └─sdc1 8:33 1 57.3G 0 part sda 8:0 0 7.5T 0 disk └─XSLocalEXT--27384ca2--a23c--d5c7--a3fc--e2ac755d356c-27384ca2--a23c--d5c7--a3fc--e2ac755d356c 253:0 0 7.5T 0 lvm /run/sr-mount/27384ca2-a23c-d5c7-a3fc-e2ac755d356c [00:20 localhost ~]# mount | grep sr-mount 10.10.10.1:/mnt/Deadpool/cos-appdata/cos-immich/eae7b525-517f-6473-d052-0415c7991752 on /run/sr-mount/eae7b525-517f-6473-d052-0415c7991752 type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=200,retrans=4,sec=sys,clientaddr=10.10.10.2,local_lock=none,addr=10.10.10.1) /dev/mapper/XSLocalEXT--27384ca2--a23c--d5c7--a3fc--e2ac755d356c-27384ca2--a23c--d5c7--a3fc--e2ac755d356c on /run/sr-mount/27384ca2-a23c-d5c7-a3fc-e2ac755d356c type ext4 (rw,relatime) 10.10.10.1:/mnt/Deadpool/cos-downloads/7acdd6e8-90ba-8657-2a0a-ffbcca86d405 on /run/sr-mount/7acdd6e8-90ba-8657-2a0a-ffbcca86d405 type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=200,retrans=4,sec=sys,clientaddr=10.10.10.2,local_lock=none,addr=10.10.10.1) 10.10.10.1:/mnt/Deadpool/cos-media/9551e268-d298-8b69-fc1c-15f466ca2b09 on /run/sr-mount/9551e268-d298-8b69-fc1c-15f466ca2b09 type nfs (rw,relatime,vers=3,rsize=1048576,wsize=1048576,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=200,retrans=4,sec=sys,mountaddr=10.10.10.1,mountvers=3,mountport=39057,mountproto=tcp,local_lock=none,addr=10.10.10.1) 10.10.10.1:/mnt/Deadpool/AppShare/ISO-Tank on /run/sr-mount/ae10e37f-237a-d62e-8146-1b9aeeae0562 type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,acdirmin=0,acdirmax=0,soft,proto=tcp,timeo=200,retrans=4,sec=sys,clientaddr=10.10.10.2,local_lock=none,addr=10.10.10.1) [00:20 localhost ~]# mount | grep bda59d9a || echo "VM-Pool not mounted" VM-Pool not mounted [00:24 localhost ~]# xe sr-forget uuid=bda59d9a-5655-e903-c569-02c8e1c84465 --force [00:24 localhost ~]# xe sr-forget uuid=bda59d9a-5655-e903-c569-02c8e1c84465 The uuid you supplied was invalid. type: SR uuid: bda59d9a-5655-e903-c569-02c8e1c84465 [00:24 localhost ~]# lsblk -a NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT tdg 254:6 0 250G 0 disk sdb 8:16 0 465.7G 0 disk ├─sdb4 8:20 0 512M 0 part /boot/efi ├─sdb2 8:18 0 18G 0 part ├─sdb5 8:21 0 4G 0 part /var/log ├─sdb3 8:19 0 424.2G 0 part ├─sdb1 8:17 0 18G 0 part / └─sdb6 8:22 0 1G 0 part [SWAP] tde 254:4 0 1.2T 0 disk tdc 254:2 0 6.4G 1 disk tda 254:0 0 1.2T 0 disk tdh 254:7 0 3.1G 1 disk sdc 8:32 1 57.3G 0 disk ├─sdc2 8:34 1 32M 0 part └─sdc1 8:33 1 57.3G 0 part tdf 254:5 0 4.7G 1 disk sda 8:0 0 7.5T 0 disk └─XSLocalEXT--27384ca2--a23c--d5c7--a3fc--e2ac755d356c-27384ca2--a23c--d5c7--a3fc--e2ac755d356c 253:0 0 7.5T 0 lvm /run/sr-mount/27384ca2-a23c-d5c7-a3fc-e2ac755d356c tdd 254:3 0 900G 0 disk tdb 254:1 0 500G 0 disk [07:48 localhost ~]# xe sr-list uuid ( RO) : 5ee50bda-201e-633c-ea4c-4ba32b2a0428 name-label ( RW): casaHOS-NextCloud name-description ( RW): casaHOS-NextCloud host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : ae10e37f-237a-d62e-8146-1b9aeeae0562 name-label ( RW): TrueNAS-ISO name-description ( RW): ISOs on trunas host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 405be593-196a-e6c1-1154-737d870ca2c8 name-label ( RW): DVD drives name-description ( RW): Physical DVD drives host ( RO): localhost type ( RO): udev content-type ( RO): iso uuid ( RO) : d076f279-50f3-906a-f29b-a20822dba819 name-label ( RW): Local-ISO name-description ( RW): host ( RO): <not in database> type ( RO): iso content-type ( RO): iso uuid ( RO) : c360423b-dbc3-833c-a77c-9f7cae7102d5 name-label ( RW): USB-ISO name-description ( RW): host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 7acdd6e8-90ba-8657-2a0a-ffbcca86d405 name-label ( RW): casaHOS-Qbitorrent name-description ( RW): casaHOS-Qbitorrent host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : a8875f36-cfbe-f46e-c59f-88fff7d122c1 name-label ( RW): XCP-ng Tools name-description ( RW): XCP-ng Tools ISOs host ( RO): localhost type ( RO): iso content-type ( RO): iso uuid ( RO) : 9551e268-d298-8b69-fc1c-15f466ca2b09 name-label ( RW): casHOS-JellyFin name-description ( RW): casHOS-JellyFin host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : eae7b525-517f-6473-d052-0415c7991752 name-label ( RW): casaHOS-immich name-description ( RW): casaHOS-immich host ( RO): localhost type ( RO): nfs content-type ( RO): user uuid ( RO) : 3ae63e9d-33cd-57ff-759a-f939968f1d69 name-label ( RW): Removable storage name-description ( RW): host ( RO): localhost type ( RO): udev content-type ( RO): disk uuid ( RO) : 27384ca2-a23c-d5c7-a3fc-e2ac755d356c name-label ( RW): Main-Pool-XCP name-description ( RW): host ( RO): localhost type ( RO): ext content-type ( RO): user [07:48 localhost ~]#

Another thing that I noticed: despite enabling remote syslog (to graylog) for all XCP-ng hosts in the pool /var/log gets filled up to 100%. Adding remote syslog seem to not change usage of /var/log at all. Official XCP-ng documentation states otherwise here: https://docs.xcp-ng.org/installation/install-xcp-ng/#installation-on-usb-drives The linked part of the documentation indicates that configuring remote syslog can be a possible solution for /var/log space constraints which seems to be not the case. I feel like logging could use some investigation by Vates in general.

Great! Keep us posted

Hi Forza, Have you finished migrating the workloads? If you are still looking for an easy migration solution, you can try Vinchin Backup & Recovery. It will replace the driver during migration intelligently.

@olivierlambert Thank you for the reply. There was a thread on here about the iso not being mounted properly and I commented about having power off the vm and back and it will load the iso. This is specifically true with the 0.4.0 for linux. Image pulled from the XO Hub will not mount the ios if the vm is powered on. There is Yellow Explanation mark next to it. Power off vm and power on vm iso is ok. Reboot vm does not let the ios to work.

@AtaxyaNetwork @Pilow @bvitnik Ok, knowing that the p2 partition was likely an old backup was exactly the breadcrumb that I needed. I confirmed via chroot and xsconsole that p2 was xcp-ng v8.2.1, and that p1 was v8.3. Then I was able to check the initrd files there. Namely I needed to see the updated dates and the kernel version. Thankfully, I saw initrd files on the backup that were the correct kernel and hadn't been disturbed. I then just cloned the initrd files from the backup partition to the p1 partition and BOOM. We booted right up. Much appreciated for the assistance, everyone. I'll still need to figure out why my disks are disconnecting, but that will be another post for another day.

@Pilow Yes, we monitor observability metrics for guest OSes via other means but being able to see this info via the Xen Orchestra web UI along with the other metrics in the Stats tab definitely has is benefits, especially when performing initial troublehshooting or when dealing with groups in our org that only have access to the XO interface and not the other metrics dashboards. Don't get me wrong, I definitely appreciate all of the work that you are all doing to get these tools working and can't wait to start using them in production. I just need to make sure that they work as expected.

@zpvS9 said in Error installing windows PV drivers 9.0.9137: I have this error too installing the new PV driver, after uninstalling Citrix driver, reboot, execute XenClean, reboot again, it said that an unsupported device is still present. I must uninstall the device by showing hidden device in Device manager and the Windows PV driver now install. So adding this step in XenClean would be appreciated. encountered the same problem with hidden base system that i needed manually uninstall to get the tools to work.

@rustylh We really need more information to even begin. What version of XCP-ng are you using? What hardware are you using to run XCP-ng? What is the underlying storage where the VM resides on? What OS is the VM running? How are you taking snapshots, XO? How old was the snapshot? Were the guest utilities installed into the VM? You do know snapshots are not backups, right?

Helped if i read the error message.... raise RuntimeError(f"{vm_type} {vm_uuid} is {power_state}, expected Halted; refusing to fix") Shut down vm ran the fix again, and fix applied. Edit - I did have to disable secure boot on windows vms for them to boot afterwards.

So first, it's not an XO issue, which helps to diagnose it. Then, it might be a subtle XCP-ng bug indeed.

said in Unable to enable High Availability - INTERNAL_ERROR(Not_found): said in Unable to enable High Availability - INTERNAL_ERROR(Not_found): @psafont Would designating a new pool master do the same thing? I ran the above command and its had no effect Well, I tried changing the pool master and when VMHost11 was the master I was able to enable HA. Switching back to VMHost13 as the master now so will see how that goes Everything is working as expected/hoped. So for anyone reading through this and wants a TL;DR Issue was related to the pool master setting, changing the pool master to a different host and then back to the original fixed the incorrect settings allowing HA to be enabled

@lastcmaster Hi, it's a known issue that guest agent versions are not reported after migration or suspend. Other functionalities (poweroff/reboot, suspend, network change etc.) should continue to work normally.

@flakpyro said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu said in VM start stuck on "Guest has not initialized the display (yet).": You must run secureboot-certs clear if you're updating from 1.2.0-2.4 or 1.2.0-3.1 and have previously run secureboot-certs install with the above versions installed. Should we run this before installing the update or after 1.2.0-3.2 has been installed? You should run that preferably after updating all hosts. @lukasz_s said in VM start stuck on "Guest has not initialized the display (yet).": @dinhngtu thanks for advice i've upgraded varstored and varstored-tools: rpm -qa | grep varstored varstored-1.2.0-3.2 varstored-tools-1.2.0-3.2 than i've cleared varstore with secureboot-certs clear should taht folder contain more files ? ls /usr/share/varstored/ KEK.uth PK.auth db.auth what about dbx file ? That file is not shipped with varstored nor needed for now. We're validating the final 1.2.0-3.2 and preparing our guidance for the official update.

@dinhngtu I'll try this on the next VM that exhibits the behavior as to not interrupt the end users on the completed VMs.

I have updated the drivers for the Realtek RTL812x 2.5/5/10G cards. So far they are working correctly. There are a few minor issues that Realtek needs to fix (for the next version, they say). Also the new Realtek firmware has not been added to XCP (but it's not required). The standard included 8125 driver for XCP 8.3 is not updated. To use the new driver install the new alt version of the 8125 driver. To support the 8126 install the required 8125 alt version first and then the new 8126 driver. The 8127 driver is also available for the new 10GB chips (I just got a production PCIe card for testing). The first issue I see with this card is, it is only a PCIe x1 card, so for full performance you need PCIe 4.0... There are other 8127 chips that support x2 so they will better support PCIe 3.0. Realtek will keep releasing new versions of the chips that will require updates to the drivers to function correctly. Even current versions of Linux needs updates to support the newer chips.