:SlapinFace: should have know that but didn't double check it.. anyways thanks!

To answer your last question, you can sort of make this work, you can set a "home" server for each VM where it will try to start first, if home server isn't available it will start on any other available server. If you want absolute separation then you'll have to make 2 pools and split them there. You should still be able to live migrate the VMs between pools but you won't be able to share your SR between pools.

@jstorgaard Updated packages are now available for you to test: https://github.com/xcp-ng/xcp/issues/434#issuecomment-688786905 olivierlambert created this issue in xcp-ng/xcp closed Backport Xen patch to support Ice Lake and Comet Lake CPUs #434

Just wanted to bump the post I get his error too. Doesn't really affect my situation much, I'm able to access XOA just fine after rebooting the server, but the one time I had the computer hooked up to a screen I did notice the message last a long time, and actually never reached the console.

Just nothing right now. VMs will continue to run. You won't be able to send orders (like moving VM, stop, or start new VMs). If your master is down for good, you can emergency transition the master to a slave (but you must be SURE the previous master won't come back!).

I have no idea

Hi Thanks for the help - found the icon Add Host (after a lot of searching ) J.

Which is exactly the right behavior! Perfect Thanks for the feedback.

Yes, system profile seems the most obvious thing to me. Double check it's on "Performance" on both hosts.

Buggy ACPI tables is sadly more common on non-enterprise grade hardware Might be related or not, but thanks for the feedback about frequency

@olivierlambert Ok, thanks. I will create another topic for the display issue.

Ah, probably won't work then, I'll try NFS async, thanks!

Shutdown the host properly and report if those VM boots. Try to disable/enable power on via Xen Orchestra, there's an issue in XCP-ng Center with this setting.

RTFM https://xcp-ng.org/docs/compute.html#pci-passthrough You can also passtrough multiple devices. If you wanted to passtrough another device at 00:19.0 just append it to the parameter. [root@xen ~]# xe vm-param-set other-config:pci=0/0000:04:01.0,0/0000:00:19.0 uuid=<vm uuid>

@xTITUS-MAXIMUSx Thanks for the tip. I went to the bios and enabled the Intel Virtualization Technology and I thought I was done. After further research I recognized there are two steps to Enable the Intel Virtualization Technology. https://us.informatiweb.net/tutorials/it/bios/enable-iommu-or-vt-d-in-your-bios.html Advanced >> CPU configuration >> Intel Virtualization Technology >> Enable Advanced >> System Agent Configuration >> VT-d >> Enable

It seems I got a kernel panic for some other reason with 5.4.21. It's all working now, thanks.

Please take time to read carefully the previous link I send. If you can't spot it, re-read it slowly, you might see this link: https://xenbits.xen.org/docs/unstable/support-matrix.html

It should work, yes.

Hi @mauricio_hps This is a XCP-ng forum, please try with XCP-ng https://xcp-ng.org