@stormi Tested the new edk package at looks good to me. was able to reboot linux and freebsd VMs without a hitch with UEFI boot mode.

Installed on my Test pool with 2 HP EliteDesk 800 G3 mini. Except the no stats in XenOrchestra. Did some VM migragration between hosts, reboot testes (only Linux VMs though) and so far no issues.

Upgraded my dev Pool

2 HP EliteDesk 800 G3 Mini
One with i5 6500T and one i7 6700T
Both 32GB RAM, SATA and NVMe Storage
1x Intel NIC
1x RTL8139 NIC

Updated Master first and then the second node. No issues so far.

@wtdrisco There should be no Problem if the core counts don't match. you just can't place a VM that has 32vCPUs on the 24 core host.

But one thing you should have equal over all hosts is the amount of network interfaces and also have them configured equally (which should be done by XOA/XO form sources). Otherwise a VM might not migrate because a network Interface is missing on the target host.

Also passed through hardware might prevent migrating to another host.

I run a pool with two diffrent hosts, one has 8 Cores and one only 4 cores, also one has 64 GB RAM and the other one has only 32GB and in this limitations I can easily migrate VMs back and forth between hosts.

@Murf There is a blog post about using XenOrchestra for a dynamic inventory.
https://xen-orchestra.com/blog/virtops3-ansible-with-xen-orchestra/

Creating VMs is usually a job done by terraform and not ansible. I know there is an ansible collection for VMWare which can do that but as far as I know there is no collection that is able to manage VMs and sadly Satellite's virt-who doesn't seem to have XenOrchestra support at the moment and since RedHat is pushing OpenShift I don't think it will ever come.

But there was a wish for a colletion on the DevOps Megathread
https://xcp-ng.org/forum/post/88993

Backup management with the Terraform provider would be a great feature. Maybe also for an upcoming ansible module. I always struggle to find the right backup for a VM since I grouped them in logical groups. So one Backup may handle multiple VMs and Sometimes it would be just easier to edit some IaC then the GUI, especially when I destroy a VM, I always forget to check if Backups exists.

Installed the patches on my lab pool and both hosts are up and running and no issues so far.

On an HP EliteDesk 800 G3 35W Mini i5 6500T

XTF:
with no-exec-sp:
All Test SKIP/SUCCESS

with exec-sp:
Hard Freeze.

dom0 Test all Tests passed.

Installed on a HP EliteDesg 800 G3 Mini running 6VMs Linux nad FreeBSD all iwith UEFI one Linux with vTPM so far no issues. Will keep monitoring and testing.

@stormi Yeah sure, just thought it may help with the issue that was reported if the container used is outdated.

But anyways to the topic of XPC-NG 8.3beta. Are there any updates planned in the near future it has been a while since I recieved Updates on my test cluster. And while I don't run an AMD Processor on my test cluster there were security fixes for 8.2 but they didn't made to my 8.3 or did the repo config change and I missed that?

Installed the patches on my lab pool and both hosts are up and running and no issues so far.

@andriy.sultanov
I ran it for a minute.

rrd2csv.txt

@andriy.sultanov
Same issue after another reboot. The stats on host just flatline. No CPU usage or anything.
See screenshot

I attached log files
daemon.log.txt xcp-rrdd-plugins.log.txt xensource.log.txt

Installed on my Test pool with 2 HP EliteDesk 800 G3 mini. Except the no stats in XenOrchestra. Did some VM migragration between hosts, reboot testes (only Linux VMs though) and so far no issues.

@Greg_E according to the Knowledge base of Redhawks it is den Witz Intel CPUs. So you AMD isn‘t affected

@bberndt you Rocky/Alma 9 will be fine since it's a bug in the kernel for 8 only.

@Greg_E They are all running for a while but none where upgrades from RHEL 7 to RHEL 8. I don't do LEAPPs that gives me more often errors than it works. What I did though on one is replacing the System VDI with a newer one, but that was Alma 8 to Alma 9 and that one has no issues.

@Greg_E said in XCP vm fails to boot after newest kernel applied.:

@bberndt
I just installed a fresh Alma 8, did yum update to see what would happen, and it's still working. Gave out the same kernel as above.

This was installed UEFI on XCP-ng 8.3 which was a fresh install a few days ago from a nightly (near release?) ISO. It was installed to an NFS share, 2 cores and 4GB with an Intel i1000 interface. Xenserver tools 8.4.0-1 installed.

There are no extra packages installed yet, could this be a package conflict.

Anything else I can check to see why mine works and others are failing?

Hmm....I did the same and that VM died just like any other with the broken kernel.
Although I used the Cloud Image so not completly new install from scratch.
Maybe I'll check building a new cloud image what will happen then.

@Murf There is a blog post about using XenOrchestra for a dynamic inventory.
https://xen-orchestra.com/blog/virtops3-ansible-with-xen-orchestra/

Creating VMs is usually a job done by terraform and not ansible. I know there is an ansible collection for VMWare which can do that but as far as I know there is no collection that is able to manage VMs and sadly Satellite's virt-who doesn't seem to have XenOrchestra support at the moment and since RedHat is pushing OpenShift I don't think it will ever come.

But there was a wish for a colletion on the DevOps Megathread
https://xcp-ng.org/forum/post/88993

Upgraded my dev Pool

2 HP EliteDesk 800 G3 Mini
One with i5 6500T and one i7 6700T
Both 32GB RAM, SATA and NVMe Storage
1x Intel NIC
1x RTL8139 NIC

Updated Master first and then the second node. No issues so far.