From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pending Disk I/O requests during live VM migration
Date: Thu, 4 Oct 2007 19:30:15 +0300 [thread overview]
Message-ID: <f43fc5580710040930t589a22ebj669af91504956193@mail.gmail.com> (raw)
In-Reply-To: <47050E64.5070901@cc.gatech.edu>
On 10/4/07, Kaushik Bhandankar <kaushikb@cc.gatech.edu> wrote:
> I am trying to implement functionality in fully-virtualized xen wherein
> the responses to the pending disk I/O requests during live VM migration
> get trasnsferred to the new VMM form the old VMM. Specifically, I am
> looking at IDE disk (tools/ioemu/hw/ide.c)
You should ask Xen related questions in xen lists. At least in Qemu
pending I/O are flushed before VM save in vl.c:5522.
next prev parent reply other threads:[~2007-10-04 16:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 16:01 [Qemu-devel] Pending Disk I/O requests during live VM migration Kaushik Bhandankar
2007-10-04 16:30 ` Blue Swirl [this message]
2007-10-04 16:43 ` Kaushik Bhandankar
2007-10-04 17:05 ` Blue Swirl
2007-10-11 22:00 ` Kaushik Bhandankar
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=f43fc5580710040930t589a22ebj669af91504956193@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).