I have raised issue https://github.com/xcp-ng/xcp/issues/439 for the above SR problem.

I upgraded to 8.2.0-beta to fix this issue nfs-storage-latency. Bellow are some tests done, if you need any specific tests just let me know.

I’m running XO from sources xo-server 5.67.0 xo-web 5.71.0

XEN-HOST-01 Dell R720
XEN-HOST-02 Dell R710
TrueNAS NFS Storage over 10GbE

I upgraded from 8.1.0 patched to 8.2.0-beta via ISO install. Install went through with no troubles. The host booted with no problems. All networks and storage was present.

All VMs booted and came back up with no issues and guest tools running. VMs consist of CentOS 7 & 8, Debian 9 & 10, Windows 10Pro

Successfully live migrated VMs from 8.1.0 host to 8.2.0-beta with no issues.

Attempted VM migration from 8.2.0-beta to 8.1.0 host failed as expected.

Successfully migrated VMs between 8.2.0-beta hosts.

Could not change pool master from 8.2.0-beta to 8.1.0 host. Get Unknown error from peer.

Successfully changed pool master with both hosts on 8.2.0-beta.

Both host on 8.2.0-beta, shut down host-02 which was not the pool master and the shared storage shows partially connected and no stats available for storage. Reboot host-02 and shared storage is now healthy and stats are back. Disabled host-02 and shutdown and still had the same issue as above. The only was to get stats back and get shares storage back to healthy and stats working is to forget the storage attached to host-02 that was shut down.

XCP-ng Center v20.04.00.32 will not connect to 8.2.0-beta hosts.

Had to reinstall xscontainer package to have docker container visibility in XO.

Feature request oped

https://github.com/vatesfr/xen-orchestra/issues/5391

brezlord created this issue in vatesfr/xen-orchestra

open Set pool wide Xen Motion Network #5391

@olivierlambert I think that the default behavior should be VMs stay on the SR that they are on. If you are taking a host down and moving the VMs to another host why would you move the VM storage location, that defeats one of the reasons you use shared storage.

With the latest updates to XO you can now select multiple VM to migrate and also select the migration network which is excellent. But if you have multiple SRs and one is set a default when you migrate VMs any VM that is not on the default SR will be moved to the default SR. Is this the expected behavior? I personally think this is not a good idea.

I agree, +1 for tree view.

Feature request oped

https://github.com/vatesfr/xen-orchestra/issues/5391

brezlord created this issue in vatesfr/xen-orchestra

open Set pool wide Xen Motion Network #5391

HI, @olivierlambert I think it would be good to be able to set a pool wide network that is used for Xen Motion of VMs in the same way vCenter lets you. I know you can select a network but this option is only available from the VM screen

When you select multiple VMs from the VMs overview page there is not option to select a network and the VMs move across the management network.

Also when you restart or shutdown a host there is no option to select a network for VMs to move across.

Should I open a feature request for this?

Kind Regards,
Simon

I have raised issue https://github.com/xcp-ng/xcp/issues/439 for the above SR problem.

Thanks for the info. So doing a ISO update is essentially like a fresh install but keeps settings.

I don't have any nVIDIA GPUs, sorry can't help there.

I'll boot the second host and get more info to raise an issue for the SR problem.

I upgraded to 8.2.0-beta to fix this issue nfs-storage-latency. Bellow are some tests done, if you need any specific tests just let me know.

I’m running XO from sources xo-server 5.67.0 xo-web 5.71.0

XEN-HOST-01 Dell R720
XEN-HOST-02 Dell R710
TrueNAS NFS Storage over 10GbE

I upgraded from 8.1.0 patched to 8.2.0-beta via ISO install. Install went through with no troubles. The host booted with no problems. All networks and storage was present.

All VMs booted and came back up with no issues and guest tools running. VMs consist of CentOS 7 & 8, Debian 9 & 10, Windows 10Pro

Successfully live migrated VMs from 8.1.0 host to 8.2.0-beta with no issues.

Attempted VM migration from 8.2.0-beta to 8.1.0 host failed as expected.

Successfully migrated VMs between 8.2.0-beta hosts.

Could not change pool master from 8.2.0-beta to 8.1.0 host. Get Unknown error from peer.

Successfully changed pool master with both hosts on 8.2.0-beta.

Both host on 8.2.0-beta, shut down host-02 which was not the pool master and the shared storage shows partially connected and no stats available for storage. Reboot host-02 and shared storage is now healthy and stats are back. Disabled host-02 and shutdown and still had the same issue as above. The only was to get stats back and get shares storage back to healthy and stats working is to forget the storage attached to host-02 that was shut down.

XCP-ng Center v20.04.00.32 will not connect to 8.2.0-beta hosts.

Had to reinstall xscontainer package to have docker container visibility in XO.