You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I wanted to migrate a VM to a new, freshly installed host. I ended up each time with an error: "INTERNAL_ERROR". After several hours of debugging, I found out my destination host doesn't have the feature HVM enable !
Describe the solution you'd like
I would like to have a warning on XO to tell me that HVM feature is not enabled on my host. I think that Home -> Host, in the warning button next to the host name is a good place to have this warning. It can save some debugging time to other
The HVM capabilities can be found with xe host-param-list uuid=<Host_UUID>
Describe alternatives you've considered
Maybe we can imagine a warning popup when the host is added to XO, but I think it would be more difficult to implement
Additional context
Thanks for the help and your work 🚀
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I wanted to migrate a VM to a new, freshly installed host. I ended up each time with an error: "INTERNAL_ERROR". After several hours of debugging, I found out my destination host doesn't have the feature HVM enable !
Describe the solution you'd like
I would like to have a warning on XO to tell me that HVM feature is not enabled on my host. I think that Home -> Host, in the warning button next to the host name is a good place to have this warning. It can save some debugging time to other
The HVM capabilities can be found with
xe host-param-list uuid=<Host_UUID>
If HVM is active :
If HVM is inactive :
Describe alternatives you've considered
Maybe we can imagine a warning popup when the host is added to XO, but I think it would be more difficult to implement
Additional context
Thanks for the help and your work 🚀
The text was updated successfully, but these errors were encountered: