qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: xen-devel@lists.xensource.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	jan.kiszka@siemens.com, qemu-devel@nongnu.org, avi@redhat.com,
	Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] [PATCH v6 2/6] Introduce "save_devices"
Date: Fri, 16 Mar 2012 09:36:21 -0600	[thread overview]
Message-ID: <4F635DF5.8020207@redhat.com> (raw)
In-Reply-To: <20120315173456.0f297edf@doriath.home>

[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]

On 03/15/2012 02:34 PM, Luiz Capitulino wrote:
> On Thu, 15 Mar 2012 15:16:15 -0500
> Anthony Liguori <anthony@codemonkey.ws> wrote:
> 
>> On 03/15/2012 01:19 PM, Stefano Stabellini wrote:
>>> - add an "is_ram" flag to SaveStateEntry;
>>>
>>> - register_savevm_live sets is_ram for live_savevm devices;
>>>
>>> - introduce a "save_devices" QAPI command that can be used to save
>>> the state of all devices, but not the RAM or the block devices of the
>>> VM.
>>>

>>> +SQMP
>>> +save_devices
>>> +-------
>>> +
>>> +Save the state of all devices to file. The RAM and the block devices
>>> +of the VM are not saved by this command.
>>> +
>>> +Arguments:
>>> +
>>> +- "filename": the file to save the state of the devices to as binary
>>> +data. See save_devices.txt for a description of the binary format.
>>> +
>>> +Example:
>>> +
>>> +->  { "execute": "save_devices", "arguments": { "filename": "/tmp/save" } }

Why are we adding yet another command without support for passing in an
fd instead of having qemu open the file name?  Libvirt really does want
to move to an ability to pass in fds, and the more commands we add that
open files, the harder converting them all will be.

-- 
Eric Blake   eblake@redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]

  parent reply	other threads:[~2012-03-16 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15 18:14 [Qemu-devel] [PATCH v6 0/6] save/restore on Xen Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 1/6] cirrus_vga: do not reset videoram Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 2/6] Introduce "save_devices" Stefano Stabellini
2012-03-15 20:16   ` Anthony Liguori
2012-03-15 20:34     ` Luiz Capitulino
2012-03-16 11:41       ` Stefano Stabellini
2012-03-16 15:36       ` Eric Blake [this message]
2012-03-16 16:10         ` Stefano Stabellini
2012-03-16 11:35     ` Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 3/6] Set runstate to INMIGRATE earlier Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 4/6] xen: record physmap changes to xenstore Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 5/6] xen mapcache: check if memory region has moved Stefano Stabellini
2012-03-15 18:19 ` [Qemu-devel] [PATCH v6 6/6] xen: do not allocate RAM during INMIGRATE runstate Stefano Stabellini

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=4F635DF5.8020207@redhat.com \
    --to=eblake@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@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 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).