On Fri, Oct 16, 2009 at 08:45:25AM -0700, Joseph Mocker wrote: > Chris wrote: ... > >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.
Yepp. So we for example have a "cron job" on the windows servers, which shuts it down automatically at 4am. On Dom0 a cron job starts at 4pm as well, which checks all DomU states for at most an hour. If a DomU is in shutoff state, a new snapshot for its ZFS vol[s] gets created and after that the DomU gets restarted. So the WinAdmin has still enough freedom to decide, when a snapshot/backup for his DomU should be made ... > >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. No problems wrt. stability for ~1 year, as long as one gives not more than 1 vcpu to Win DomU (but this is snv_b98 - not sure, whether it is fixed in more recent versions ...). Regards, jel. -- Otto-von-Guericke University http://www.cs.uni-magdeburg.de/ Department of Computer Science Geb. 29 R 027, Universitaetsplatz 2 39106 Magdeburg, Germany Tel: +49 391 67 12768 _______________________________________________ xen-discuss mailing list [email protected]
