From: Eric Blake <eblake@redhat.com>
To: Tomoki Sekiyama <tomoki.sekiyama@hds.com>, qemu-devel@nongnu.org
Cc: mitsuhiro.tanino@hds.com, mdroth@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v2] qga: Add 'mountpoints' argument to guest-fsfreeze-freeze command
Date: Tue, 20 May 2014 16:46:46 -0600 [thread overview]
Message-ID: <537BDB56.1010002@redhat.com> (raw)
In-Reply-To: <1400623296-8962-1-git-send-email-tomoki.sekiyama@hds.com>
[-- Attachment #1: Type: text/plain, Size: 2928 bytes --]
On 05/20/2014 04:01 PM, Tomoki Sekiyama wrote:
> The patch below is for the command to get filesystems list.
>
> ===
> From: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
You'll want to resend it as a series of patches as a top-level thread;
not everyone notices a patch buried as a reply.
>
> qga: Add guest-get-fs-info command
>
> Add command to get mounted filesystems information in the guest.
> The returned value contains a list of mountpoint paths and
> corresponding disks info such as disk bus type, drive address,
> and the disk controllers' PCI addresses, so that management layer
> such as libvirt can resolve the disk backends.
> In Linux guest, the disk information is resolved from sysfs.
>
> guest-get-fs-info command will return the following result:
>
> {"return":
> [{"name":"dm-1",
> "mountpoint":"/mnt/test",
> "disk":[
> {"bus-type":"scsi","bus":0,"unit":1,"target":0,
> "pci-controller":{"bus":0,"slot":10,"domain":0,"function":0}},
> {"bus-type":"ide","bus":0,"unit":0,"target":0,
> "pci-controller":{"bus":0,"slot":1,"domain":0,"function":1}}],
> "type":"xfs"},
Definitely looks like a useful set of information. I have not reviewed
the patch closely, but it looks like you have a good API for Linux. I'm
a bit worried that it might be hard to translate this API into non-Linux
guests, but it still seems generic enough; and the argument also holds
that if this command is not implemented, the guest does not support
partial freezing.
> +++ b/qga/qapi-schema.json
> @@ -646,3 +646,80 @@
> { 'command': 'guest-set-vcpus',
> 'data': {'vcpus': ['GuestLogicalProcessor'] },
> +
> +##
> +# @GuestFilesystemInfo
> +#
> +# @name: disk name
> +# @mountpoint: mount point path
> +# @type: file system type string
> +# @disk: an array of disk hardware informations that the volume lies on
s/informations/information/
> +#
> +# Since: 2.1
> +##
> +{ 'type': 'GuestFilesystemInfo',
> + 'data': {'name': 'str', 'mountpoint': 'str', 'type': 'str',
> + '*disk': ['GuestDiskAddress']} }
Why is the array optional? Is it something where an empty array has
different meaning than omitting the array altogether?
> +
> +##
> +# @guest-get-fs-info:
> +#
> +# Returns: The list of filesystems information mounted in the guest.
> +# The returned mountpoints may be specified to @guest-fsfreeze-freeze.
> +# Network filesystems (such as CIFS and NFS) are not listed.
> +#
> +# Since: 2.1
> +##
> +{ 'command': 'guest-get-fs-info',
> + 'returns': ['GuestFilesystemInfo'] }
Should this command support an optional input argument '*name':'str'
that filters the results to a one-element array about that one named
mountpoint?
--
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: 604 bytes --]
next prev parent reply other threads:[~2014-05-20 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140428152505.10474.3587.stgit@dhcp-17-12.bos.redhat.com>
2014-05-20 15:04 ` [Qemu-devel] [PATCH v2] qga: Add 'mountpoints' argument to guest-fsfreeze-freeze command Tomoki Sekiyama
[not found] ` <20140428152514.10474.67500.stgit@dhcp-17-12.bos.redhat.com>
2014-05-20 15:45 ` Eric Blake
2014-05-20 22:01 ` Tomoki Sekiyama
2014-05-20 22:46 ` Eric Blake [this message]
2014-05-21 19:28 ` Tomoki Sekiyama
2014-05-20 22:01 ` Tomoki Sekiyama
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=537BDB56.1010002@redhat.com \
--to=eblake@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mitsuhiro.tanino@hds.com \
--cc=qemu-devel@nongnu.org \
--cc=tomoki.sekiyama@hds.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).