[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


  • To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
  • Date: Thu, 08 Nov 2007 11:23:59 +0000
  • Delivery-date: Thu, 08 Nov 2007 03:25:02 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acgh89hmOjf1UcT/R7S91fG2xpfbEgAAJyu6AAAMH9AAAKHtpAAACubgAACgnTI=
  • Thread-topic: [Xen-devel] HVM domain with write caching going on somewhere to disk

On 8/11/07 11:08, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

>> No, it's trickier than that. Blkback sends I/O requests direct into
> the
>> block subsystem, bypassing the buffer cache. You can see there's
> potential
>> for confusion therefore!
> 
> Ah yes. That would probably do it. So I need to make sure that the
> buffer cache is flushed (eg async writes in qemu?)... or maybe get qemu
> to talk direct to the block subsystem in the same way... any
> suggestions? I've already butchered ioemu to get this working so far
> (changed the PCI ID's of the IDE interface so Windows won't detect it)
> so I'm not afraid of doing more of it :)

Qemu-dm should probably be specifying O_DIRECT when it opens guest storage
volumes. There was discussion about this quite some time ago, but I don't
think any patch was ever floated.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

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