From: "Daniel P. Berrange" <berrange@redhat.com>
To: Andrew Warfield <andrew.warfield@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
Anthony Liguori <anthony@codemonkey.ws>,
Jim Burnes <jvburnes@gmail.com>
Subject: Re: Re: [Xen-devel] Re: Writing a tool for Shared Persistent Windows Boot Image
Date: Sun, 1 Jul 2007 22:55:35 +0100 [thread overview]
Message-ID: <20070701215535.GA30726@redhat.com> (raw)
In-Reply-To: <20070701214137.GA27274@redhat.com>
On Sun, Jul 01, 2007 at 10:41:37PM +0100, Daniel P. Berrange wrote:
> On Sun, Jul 01, 2007 at 01:28:56PM -0700, Andrew Warfield wrote:
> > The problem with this approach is that you end up using two instances
> > of whatever virtual disk code you want. In the case of raw writes to
> > an image file (tap:aio) this is more or less okay, except for the fact
> > that qemu has a bad habit of buffering writes and so you can get stuck
> > in a nasty late write race when you switch from emulated writes over
> > to using pv drivers.
>
> AFAIR, if the guest OS sends a flush request to the IDE device, then
> QEMU should immediately be flushing the data to disk in the host - if
> it doesn't, then this is already a potential data corrupter if either
> the guest or host crashes because journaling fileystems rely on the
> fact that when they ask for a journal flush it is not buffered in RAM.
>
> I don't think a guest OS would ever be activating both the IDE and
> paravirt drivers for a device though would it ? You either load IDE
> drivers, or paravirt at any given time. If you've got a guest using
> PV drivers, then the only point where the IDE interface would come
> into play is for the initial BIOS boot process & that should be
> read-only access.
Thinking about it from the safety POV, the QEMU process could register
a xenstore watch to be notified when the paravirt frontend driver
connected to the backend. At this time it could forceably disable the
IDE device associated with the backend, thus ensuring you never have
two concurrently active data paths to the same underlying disk.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2007-07-01 21:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-21 16:41 Writing a tool for Shared Persistent Windows Boot Image Jim Burnes
2007-06-21 18:11 ` Anthony Liguori
[not found] ` <13A934B9-F615-4838-8D26-4E33F0BCFF2E@gmail.com>
2007-06-21 20:39 ` Anthony Liguori
[not found] ` <37B43CC2-BED7-4336-9CC4-0CE1C7894458@gmail.com>
[not found] ` <467AF0C6.5010101@codemonkey.ws>
2007-06-28 18:18 ` Jim Burnes
2007-06-28 18:27 ` [Xen-devel] " Daniel P. Berrange
2007-06-28 19:15 ` Jim Burnes
2007-06-29 14:38 ` Re: [Xen-devel] " Andrew Warfield
2007-06-29 14:42 ` Daniel P. Berrange
2007-06-29 16:18 ` [Xen-users] " Andrew Warfield
2007-06-29 19:00 ` Re: [Xen-devel] " Jim Burnes
2007-06-29 19:07 ` [Xen-users] " Jim Burnes
2007-06-30 6:21 ` Ian Campbell
2007-06-29 20:16 ` Re: [Xen-devel] " Daniel P. Berrange
2007-06-29 20:32 ` [Xen-users] " Jim Burnes
2007-06-29 21:27 ` Re: [Xen-devel] " Daniel P. Berrange
2007-07-01 20:28 ` Andrew Warfield
2007-07-01 21:41 ` Daniel P. Berrange
2007-07-01 21:55 ` Daniel P. Berrange [this message]
2007-06-21 22:03 ` Alan Cox
2007-06-28 17:40 ` Jim Burnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070701215535.GA30726@redhat.com \
--to=berrange@redhat.com \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=anthony@codemonkey.ws \
--cc=jvburnes@gmail.com \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.