Am 11.11.2011 01:11, schrieb Anthony Liguori:
> I did a brain dump of my understanding of the various storage requirements 
> for 
> live migration.  I think it's accurate but I may have misunderstand some 
> details 
> so I would appreciate review.
> 
> I think given sections (1) and (2), the only viable thing is to require 
> cache=none unless we get new interfaces to flush caches.

Yes, I think we should strongly recommend cache=none/directsync, but not
enforce it. As you said, for clustered filesystems other options should
work, so we should allow users to choose to make use of that.

> Section (3) talks about image formats.  As I mentioned elsewhere in the 
> thread, 
> I think the best we can do right now is have a block layer interface to 
> quiesce 
> the image format.  I think reopen may be a viable short term strategy for 
> qcow2 
> but I think for raw, we should just make the quiesce operation a nop.

I don't agree with making it a nop on raw. You say it's safe without any
further action if you avoid online resize, but we don't disallow online
resize during migration, so this is an invalid assumption. And did you
review all the code to make sure that we don't cache more?

I believe it's better anyway to have all formats behave the same.

Kevin

Reply via email to