All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: dlaor@redhat.com
Cc: Chris Wright <chrisw@sous-sol.org>,
	Juan Quintela <quintela@redhat.com>,
	chrisw@redhat.com,
	"Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Ayal Baron <abaron@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Oct 19
Date: Tue, 19 Oct 2010 15:03:50 +0200	[thread overview]
Message-ID: <4CBD9736.2060902@redhat.com> (raw)
In-Reply-To: <4CBD960D.8020806@redhat.com>

  On 10/19/2010 02:58 PM, Dor Laor wrote:
> On 10/19/2010 02:55 PM, Avi Kivity wrote:
>> On 10/19/2010 02:48 PM, Dor Laor wrote:
>>> On 10/19/2010 04:11 AM, Chris Wright wrote:
>>>> * Juan Quintela (quintela@redhat.com) wrote:
>>>>>
>>>>> Please send in any agenda items you are interested in covering.
>>>>
>>>> - 0.13.X -stable handoff
>>>> - 0.14 planning
>>>> - threadlet work
>>>> - virtfs proposals
>>>>
>>>
>>> - Live snapshots
>>> - We were asked to add this feature for external qcow2
>>> images. Will simple approach of fsync + tracking each requested
>>> backing file (it can be per vDisk) and re-open the new image would
>>> be accepted?
>>> - Integration with FS freeze for consistent guest app snapshot
>>> Many apps do not sync their ram state to disk correctly or frequent
>>> enough. Physical world backup software calls fs freeze on xfs and
>>> VSS for windows to make the backup consistent.
>>> In order to integrated this with live snapshots we need a guest
>>> agent to trigger the guest fs freeze.
>>> We can either have qemu communicate with the agent directly through
>>> virtio-serial or have a mgmt daemon use virtio-serial to
>>> communicate with the guest in addition to QMP messages about the
>>> live snapshot state.
>>> Preferences? The first solution complicates qemu while the second
>>> complicates mgmt.
>>
>> Third option, make the freeze path management -> qemu -> virtio-blk ->
>> guest kernel -> file systems. The advantage is that it's easy to
>> associate file systems with a block device this way.
>
> OTH the userspace freeze path already exist and now you create another 
> path. 

I guess we would still have a userspace daemon; instead of talking to 
virtio-serial it talks to virtio-blk.  So:

   management -> qemu -> virtio-blk -> guest driver -> kernel fs 
resolver -> daemon -> apps

Yuck.

> What about FS that span over LVM with multiple drives? IDE/SCSI?

Good points.

-- 
error compiling committee.c: too many arguments to function


WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: dlaor@redhat.com
Cc: chrisw@redhat.com, kvm@vger.kernel.org,
	Juan Quintela <quintela@redhat.com>,
	qemu-devel@nongnu.org, Chris Wright <chrisw@sous-sol.org>,
	Ayal Baron <abaron@redhat.com>,
	"Venkateswararao Jujjuri (JV)" <jvrao@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Oct 19
Date: Tue, 19 Oct 2010 15:03:50 +0200	[thread overview]
Message-ID: <4CBD9736.2060902@redhat.com> (raw)
In-Reply-To: <4CBD960D.8020806@redhat.com>

  On 10/19/2010 02:58 PM, Dor Laor wrote:
> On 10/19/2010 02:55 PM, Avi Kivity wrote:
>> On 10/19/2010 02:48 PM, Dor Laor wrote:
>>> On 10/19/2010 04:11 AM, Chris Wright wrote:
>>>> * Juan Quintela (quintela@redhat.com) wrote:
>>>>>
>>>>> Please send in any agenda items you are interested in covering.
>>>>
>>>> - 0.13.X -stable handoff
>>>> - 0.14 planning
>>>> - threadlet work
>>>> - virtfs proposals
>>>>
>>>
>>> - Live snapshots
>>> - We were asked to add this feature for external qcow2
>>> images. Will simple approach of fsync + tracking each requested
>>> backing file (it can be per vDisk) and re-open the new image would
>>> be accepted?
>>> - Integration with FS freeze for consistent guest app snapshot
>>> Many apps do not sync their ram state to disk correctly or frequent
>>> enough. Physical world backup software calls fs freeze on xfs and
>>> VSS for windows to make the backup consistent.
>>> In order to integrated this with live snapshots we need a guest
>>> agent to trigger the guest fs freeze.
>>> We can either have qemu communicate with the agent directly through
>>> virtio-serial or have a mgmt daemon use virtio-serial to
>>> communicate with the guest in addition to QMP messages about the
>>> live snapshot state.
>>> Preferences? The first solution complicates qemu while the second
>>> complicates mgmt.
>>
>> Third option, make the freeze path management -> qemu -> virtio-blk ->
>> guest kernel -> file systems. The advantage is that it's easy to
>> associate file systems with a block device this way.
>
> OTH the userspace freeze path already exist and now you create another 
> path. 

I guess we would still have a userspace daemon; instead of talking to 
virtio-serial it talks to virtio-blk.  So:

   management -> qemu -> virtio-blk -> guest driver -> kernel fs 
resolver -> daemon -> apps

Yuck.

> What about FS that span over LVM with multiple drives? IDE/SCSI?

Good points.

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2010-10-19 13:03 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18 15:43 KVM call agenda for Oct 19 Juan Quintela
2010-10-18 15:43 ` [Qemu-devel] " Juan Quintela
2010-10-19  2:11 ` Chris Wright
2010-10-19  2:11   ` [Qemu-devel] " Chris Wright
2010-10-19 12:48   ` Dor Laor
2010-10-19 12:48     ` Dor Laor
2010-10-19 12:55     ` Avi Kivity
2010-10-19 12:55       ` Avi Kivity
2010-10-19 12:58       ` Dor Laor
2010-10-19 12:58         ` Dor Laor
2010-10-19 13:03         ` Avi Kivity [this message]
2010-10-19 13:03           ` Avi Kivity
2010-10-19 13:18           ` Anthony Liguori
2010-10-19 13:18             ` Anthony Liguori
2010-10-19 13:22     ` Anthony Liguori
2010-10-19 13:22       ` Anthony Liguori
2010-10-19 13:27       ` Avi Kivity
2010-10-19 13:27         ` Avi Kivity
2010-10-19 13:33         ` Anthony Liguori
2010-10-19 13:33           ` Anthony Liguori
2010-10-19 13:38           ` Stefan Hajnoczi
2010-10-19 13:38             ` Stefan Hajnoczi
2010-10-19 13:55             ` Avi Kivity
2010-10-19 13:55               ` Avi Kivity
2010-10-19 13:28     ` Anthony Liguori
2010-10-19 13:28       ` Anthony Liguori
     [not found] <314565543.45891287507100965.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 16:54 ` Ayal Baron
2010-10-19 16:54   ` Ayal Baron
2010-10-19 17:09   ` Anthony Liguori
2010-10-19 17:09     ` Anthony Liguori
2010-10-20  9:18     ` Kevin Wolf
2010-10-20  9:18       ` Kevin Wolf
2010-10-20  9:41       ` Ayal Baron
2010-10-20  9:41         ` Ayal Baron
2010-10-20 13:05       ` Anthony Liguori
2010-10-20 13:05         ` Anthony Liguori
     [not found] <512838278.79671287521779658.JavaMail.root@zmail07.collab.prod.int.phx2.redhat.com>
2010-10-19 20:57 ` Ayal Baron
2010-10-19 20:57   ` Ayal Baron
2010-10-19 21:19   ` Anthony Liguori
2010-10-19 21:19     ` Anthony Liguori

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=4CBD9736.2060902@redhat.com \
    --to=avi@redhat.com \
    --cc=abaron@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=chrisw@sous-sol.org \
    --cc=dlaor@redhat.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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.