[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] A migration framework for external devices

Anthony Liguori wrote:

If the Xend is always listening for migrations on a well-known port, it is trivially easy to start migrating domains to that host. If the port number isn't decided until the time of migration (and better yet, is decided through a secure channel like SSH), it makes it difficult to determine when a port is open to migrate to and which port that is.

All you are doing with the dynamic port is making it harder for the novice. It is good design but not security. (How many network services do you know of that gain security by using variable ports?)

All devices have to have their state migrated in some form. There's already code to handle that in Xend (via the S-Expression configuration file). The only reason TPM migration doesn't just work is that the current state migration is unidirectional and TPM requires bidirectional state synchronization.

I was thinking far beyond the front-end devices themselves and considering the physical devices on the target machine, many of which will be dual-ported storage, vlans, and other things that need physical configuration in order to support the migrated virtual devices.

That is still a missing piece in the migration solution.

All that's strictly required here is the ability to transfer the TPM state. This is just a little bit of additional code in XendCheckpoint that ran after suspend to transfer the TPM state.

Sorry, I disagree. A lot more is required for migration to be a useful solution.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.