Boby

You might be able to achieve the same using the below command xe host-declare-dead uuid=host_uuid https://docs.xenserver.com/en-us/xenserver/8/command-line-interface.html#host-declare-dead This call is dangerous and can cause data loss if the host is not actually dead. You may want to test it on a Test XS pool to ensure it meets your requirements.

Hello Ross, Can you give an approximate time difference and the RAM size of the VMs at both places for Live Migration/vMotion ? With our new XenServer 8 (not CH 8.2Cu1) we have a new compress and migrate option that might benefit you : https://docs.xenserver.com/en-us/xenserver/8/vms/migrate.html#live-migration If you have tested XenServer 8 and if you are still seeing the problem as highly concerning , would you be able to log that as a support ticket ? Regards Boby

Was this a host that was getting updates earlier and failed recently ? Can you attach /var/log/xensource.log from your host here ? ( Assuming there is no proxy )

Hello Eric, Supplemental packs (including driver disks) are used to modify and extend the functionality of the XenServer host, by installing software into the control domain (dom0) , this is different from host updates. Currently, Internet access is a necessity for XenServer 8 updates. Rfer : https://docs.xenserver.com/en-us/xenserver/8/update/apply-updates-using-xc To provide update notifications, XenCenter requires internet access. If your XenCenter is behind a firewall, ensure that it has access to the updates.ops.xenserver.com domain. To receive the updates, your XenServer hosts require internet access. If your hosts are behind a firewall, ensure that they have access to subdomains of ops.xenserver.com. However you should be able to use a proxy server and apply the updates. Refer : https://docs.xenserver.com/en-us/xenserver/8/update/apply-updates-using-xc#configure-updates-for-your-pool (Optional) Under Proxy Server, specify a proxy to use when synchronizing with the update channel. This proxy server is used for communication between the host and the public CDN.

Can you ensure that none of your VMs are actively using it ? Can you try to run the following on all the hosts in the pool and see if you are getting an output ? tap-ctl list | grep -i 8e18c874

@Steven Schoch Do you believe you can log this as a ticket at https://bugs.xenserver.com/ ?