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
Restoration of a VM snapshot on a remote node fails. When the headnode flag is used for remote minimega instances which appears to be the default, the remote nodes try to obtain the snapshot disk image from the head node. Since the snapshot disk image is not on the head node, restoration of the VM on the remote node fails. One quick fix is to just override the default minimega deploy flags to exclude the headnode flag. While excluding the headnode flag will offer a quick fix, should minimega fail to restore a VM when the disk snapshot exists on the node hosting the VM? Should an alternative workflow exist for restoration of VM snapshots on remote nodes with the headnode flag? This might be a more appropriate issue for the minimega repository but since Phenix encapsulates the restoration of a VM, it seemed appropriate to also log the issue in the Phenix repository.
The text was updated successfully, but these errors were encountered:
Restoration of a VM snapshot on a remote node fails. When the
headnode
flag is used for remote minimega instances which appears to be the default, the remote nodes try to obtain the snapshot disk image from the head node. Since the snapshot disk image is not on the head node, restoration of the VM on the remote node fails. One quick fix is to just override the default minimega deploy flags to exclude theheadnode
flag. While excluding theheadnode
flag will offer a quick fix, should minimega fail to restore a VM when the disk snapshot exists on the node hosting the VM? Should an alternative workflow exist for restoration of VM snapshots on remote nodes with theheadnode
flag? This might be a more appropriate issue for the minimega repository but since Phenix encapsulates the restoration of a VM, it seemed appropriate to also log the issue in the Phenix repository.The text was updated successfully, but these errors were encountered: