Chris wrote:
...sounds like you want to do away with a dedicated storage server and just run
say a primary xVM hypervisor and standby xVM hypervisor, using
snapshot/send/receive to copy the ZVOLs for the virtual disks to the standby
node. Is that correct?
I think you still run the risk of an inconsistent
filesystem on the standby node unless your guests are configured with
filesystems that are guaranteed to be consistent, like ZFS.
Ditto. Some vendors/partners have integrated storage and virtualization
products so that a snapshot request to the VM will quiesce the guest file
system before the snapshot is taken, allowing for a consistent snapshot of the
guest. xVM with ZFS isn't there yet.
Technically even quiescing the file system isn't really enough. This
will only ensure your file system is consistent, however, unless less
you are running ACID compliant applications its still possible that an
application has not completed write(s) to make its data files consistent.
Short answer: xVM isn't ready for serious use.
I don't know if I would go that far. We've been running a cluster of xVM
machines hosting various sites for Sun organizations, and we've been
quite happy with the stability and performance of xVM Xen. Are there
rough edges? Sure. Is xVM Xen stable enough to stay running for months?
So far, for us, yes.
--joe
_______________________________________________
xen-discuss mailing list
[email protected]
