@planedrop said:
@Chuckz wouldn't the better solution here be to prioritize making Core Isolation work within XCP-ng guests rather than focusing on nested virtualization?
Nested virt has other issues and again should not really be used with high priority VMs.
I guess that's the whole thing I'm getting at, nested virt isn't the fix for this specific issue.
@planedrop That would be cool if core isolation could work directly in XCP-ng guests without help of nested Hyper-V. I already asked @stormi if this is possible in earlier post today:
Chuckz said:
Does XCP-ng support core isolation in Windows 11 guests via some mechanism other than by nested virtualization? I presume that I cannot get core isolation to work in Windows guests because of lack of NV support in Xen.
So far no reply to that question but I only asked earlier today. I presume it is a complex technical question that cannot be answered without discussion with upstream Xen developers.
@dthenot said:
@ccooke Hello,
You should be able to make the XOSTOR SR work again if you update sm and sm-fairlock on the other hosts.
yum update sm sm-fairlock
Then you should be able to re-plug the SR on the master and proceed with the RPU.
Hello,
Had the same problem, the command resolved the issue. It needs to be run on every host. Everything is working fine again. However, I had to complete the pool update manually.