@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

@indyj The problem appears to be in the 5.15 kernel as well but the workaround seems to fix the issue.

Hmm I have no idea but I think it might be because of more recent of Xen not supporting the OS itself

Could you set up netconsole with your guest. This is a kernel feature that allows you to send the console to a netcat/nc client over the network. You add the configuraton to the kernel command line. https://www.kernel.org/doc/html/latest/networking/netconsole.html

@danp said in This server is a different version to the master: 5.601 You are rigth, the problem was there. I didn´t found any package related to the schema version, but are rigth, so I've look into this. Here a problem like mine, and the key to resolv it. As my host0 was not updated, it was working with schema version 5.601. just a xe-tools-restart was enough to update the schema version to 5.602 and now they match. Thanks!

@olivierlambert Perfect, thanks again for your time!

@noship Hello. The secure boot feature is currently available as pre-release code. My personal experience is that it works well for my use case. Some others are reporting boot issues after installing the updates so it continues to evolve and is not yet released for production. Search the forum for UEFI and you will find the relevant threads for obtaining and installing secure boot support. Here's one: https://xcp-ng.org/docs/guides.html#guest-uefi-secure-boot

Hi, Can you be more specific? It's not clear to me

@olivierlambert Thank for for the link.. I obviously still a lot more reading to do:)

Yes, as it's the recommended tool to manage your VMs

@greg_e I just stick it in the host because i had empty x8 pci slot and i need the GPU right now all those GPU are actually used up. It works for my use which is very basic 2D autocad.

@heman I had to use this when I didn't follow directions on my XCP-NG lab system. Also a note to Freenas/Truenas users, make sure you "keep" a few old versions when you are upgrading things on your NAS, for exactly the same reasons. Yup, had to roll back on one of my production NAS this summer, nearly had a heart attack when stuff booted back up and none of the shares were accessible.