[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] HVM domain with write caching going on somewhere to disk
> On 8/11/07 10:40, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote: > > > I've noticed before that any changes made in a Windows HVM domain > > shortly before an 'xm shutdown' don't ever get written out... > > > > Anyway, is there a way to make sure that the qemu stuff doesn't do any > > write caching at all? > > I don't think qemu caches writes internally, and also I believe that > outstanding I/O requests are serviced before a domain is shut down Are they serviced before a domain is destroyed (eg 'xm destroy')? Maybe that's what I was using when I noticed it... > Could > there be a problem with data ending up in the buffer cache in dom0 kernel? Hmmm... shouldn't the DomU->qemu->device and DomU->blkbackend->device path's both have visibility to the same buffer cache though? Maybe the problem isn't what I thought it was. It seems strange that windows would boot almost completely using my PV drivers and then barf at the last minute though. Thanks James _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |