@XCP-ng-JustGreat said:
Serious movement appears to be happening with respect to NV. See videos below cross-posted from this forum thread:
https://xcp-ng.org/forum/topic/8932/hardware-assisted-virtualization-is-not-enabled-on-this-host-even-though-platform-exp-nested-hvm-true-is-set/52
...
@XCP-ng-JustGreat Well after over a year and a half and AFAICT not much progress from upstream on NV support for Windows/Hyper-V in Xen and XCP-ng. It is discouraging that support from upstream for this feature has not come yet. So I think we, as users of XCP-ng and Xen who are interested in this feature could roll up our sleeves and start working on the problem again and hopefully jump start the process of getting this feature working in upstream Xen and XCP-ng. I will follow up with another post to propose what users of Xen and XCP-ng can do to help.
@poddingue there is a notion of appliance too (group of VMs)
https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands
where you can start/stop a group of VMs, never tried it, doesn't seem to have a boot order in the vAPP neither
@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.
