If this someone needs in the Futuere: I found a way to set the licence server to localhost, so the IP address would no loger appear in the "General Tab": Run on each host: xe host-apply-edition edition=XCP-ng Free/Libre Edition license-server-address="localhost"

@thelearner https://xcp-ng.org/forum/post/20637 fixed! issue was virtualization was not enabled in BIOS settings logs on XOA was not good enough xcp-ng center gave me a better error log message of HVM is Required for this Operation thanks!

@thenorthernlight So I was able to open up the host and remove all PCIE cards and riser cards. At a glace everything appears to have made proper contact, however after reseating the cards and booting again and sure enough it appears to work again. I did not have to run any testing in the bios although the server does do a pre boot inventory check each time for changes. Host is HPE Proliant DL380 G9.

https://access.redhat.com/solutions/5347091 System fails to mount filesystem on multipath partition during boot time in RHEL8 Solution Verified - Updated May 31 2021 at 2:25 PM - English Environment Red Hat Enterprise Linux 8 dracut-049-27.git20190906.el8.x86_64 Issue System fails to mount filesystem created on multipath partition during boot time in RHEL8. Raw [ 235.191955] testsystem systemd[1]: Mounting /sysroot... [ 235.398136] testsystem kernel: SGI XFS with ACLs, security attributes, no debug enabled [ 235.398913] testsystem mount[2922]: mount: /sysroot: /dev/sdb4 already mounted or mount point busy. [ 235.399207] testsystem systemd[1]: sysroot.mount: Mount process exited, code=exited status=32 [ 235.399259] testsystem systemd[1]: sysroot.mount: Failed with result 'exit-code'. [ 235.399480] testsystem systemd[1]: Failed to mount /sysroot. Resolution Upgrade dracut package to dracut-049-135.git20210121.el8 as per RHBA-2021:1661 As a workaround, rebuild initramfs with /lib/udev/rules.d/11-dm-parts.rules. Raw dracut -f -v --include /lib/udev/rules.d/11-dm-parts.rules /lib/udev/rules.d/11-dm-parts.rules Or create /etc/dracut.conf.d/part.conf with below lines and rebuild initramfs image. #vi /etc/dracut.conf.d/part.conf install_items+=/lib/udev/rules.d/11-dm-parts.rules Root Cause dracut doesn't install /lib/udev/rules.d/11-dm-parts.rules, which is what changes the link priority for kpartx partition devices, which should make /dev/disk/by-uuid point to multipath devices instead of the scsi path devices. Diagnostic Steps Check boot logs and verify whether root filesystem mounted using sdX device or mpath device. Raw [ 235.185721] testsystem systemd[1]: Starting File System Check on /dev/disk/by-uuid/3a9fc23b-e95d-44a2-b95c-9651799f8c77... [ 235.190597] testsystem systemd-fsck[2920]: fsck.none doesn't exist, not checking file system on /dev/disk/by-uuid/3a9fc23b-e95d-44a2-b95c-9651799f8c77. [ 235.191192] testsystem systemd[1]: Started File System Check on /dev/disk/by-uuid/3a9fc23b-e95d-44a2-b95c-9651799f8c77. [ 235.191955] testsystem systemd[1]: Mounting /sysroot... [ 235.398913] testsystem mount[2922]: mount: /sysroot: /dev/sdb4 already mounted or mount point busy. Verify /lib/udev/rules.d/11-dm-parts.rules rule available in initramfs image. Raw lsinitrd initramfs-4.18.0-193.el8.x86_64.img |grep dm-parts |wc -l 0 Rebuild initramfs image with /usr/lib/udev/rules.d/11-dm-parts.rules. Raw #lsinitrd initramfs-4.18.0-193.el8.x86_64.img |grep dm-parts Arguments: -f -v -a 'multipath' --include '/usr/lib/udev/rules.d/11-dm-parts.rules' '/usr/lib/udev/rules.d/11-dm-parts.rules' -rw-r--r-- 1 root root 1442 Dec 17 2019 usr/lib/udev/rules.d/11-dm-parts.rules

No worries Enjoy!

Great to know So it works as "expected". That would be wonderful to have your XCP-ng hosts covered by our support so you get the entire stack supported!

We won't change the default behavior before having a LARGE use base using it without any problem And if I wonder about the risk on Linux, I have 0 knowledge on Windows based OS.

@danp Thanks!

It's not a failure/problem of XO, but your hosts (as you can see the same issue persists despite using xe, XCP-ng Center or XO). Have you checked the disk space? Also raise the memory in the dom0.

Short answer: you can't. Long answer: you can "cheat" with dynamic memory. But in general, I would avoid it.

After removing the GPU I am unable to replicate the issue. I have put the GPU back in and still cannot get the issue to happen again. Issue must have been some hardware related issue, but I'm still at a loss as to how things happened the way they did.

@larrysawyer there are two diffrent options: https://xcp-ng.org/docs/guests.html#windows The first one is opensource and the second is from critix. Check out the website and choose on, or test both (snapshot of your vm and test -> revert if it fails )

This issue is now fixed for every 8.2 user through the latest train of updates: https://xcp-ng.org/blog/2021/12/08/december-2021-xcp-ng-updates/

@dannierothmann indeed, but by definition the xsconsole only seems to state VM data not pool. I was more worried about it not being a full backup. but then in the same take, i like the idea of a VM only meta on XO. I'm going to put this to bed next week. I'm going to export and compare backup files. place bets..

There's not enough memory for the ballooning driver to grow, and this cause a domain crash. Going to the bottom of this is not simple I'm afraid.

@olivierlambert i see.., i was seeing them as one install. I have completed actions, thanks

I don't know how it behaves in this case. I think it might stay with the same feature as before removing the older hosts from the pool. You can check the CPU features before and after with: xe pool-param-get uuid=<POOL UUID> param-name=cpu_info Example output: features_hvm_host: 1fcbfbff-f7ba2223-2d93fbff-00000403-00000001-00000281-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000; features_hvm: 1fcbfbff-f7ba2223-2d93fbff-00000403-00000001-00000281-00000000-00000000-00001000-9c000400-00000000-00000000-00000000-00000000-00000000; features_pv_host: 1fc9cbf5-f6b82203-2991cbf5-00000003-00000001-00000201-00000000-00000000-00001000-8c000400-00000000-00000000-00000000-00000000-00000000; features_pv: 1fc9cbf5-f6b82203-2991cbf5-00000003-00000001-00000201-00000000-00000000-00001000-8c000400-00000000-00000000-00000000-00000000-00000000; socket_count: 4; cpu_count: 80; vendor: GenuineIntel

@pierre-briec I'm happy it's solved, and happy i was right