... | ... | @@ -247,7 +247,17 @@ Important caveats: |
|
|
)
|
|
|
|
|
|
note that you can generally migrate *to* the *newer* nodes, just
|
|
|
not back to the old ones.
|
|
|
not back to the old ones. but in practice, it's safer to just avoid
|
|
|
doing live migrations between Ganeti releases, state doesn't carry
|
|
|
well across major Qemu and KVM versions, and you might also find
|
|
|
that the entire VM *does* migrate, but is hung. For example, this
|
|
|
is the console after a failed migration:
|
|
|
|
|
|
root@chi-node-01:~# gnt-instance console static-gitlab-shim.torproject.org
|
|
|
Instance static-gitlab-shim.torproject.org is paused, unpausing
|
|
|
|
|
|
ie. it's hung. the `qemu` process had to be killed to recover from
|
|
|
that failed migration, on the node.
|
|
|
|
|
|
a workaround for this issue is to use `failover` instead of
|
|
|
`migrate`, which involves a shutdown. another workaround might be
|
... | ... | |