From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52316 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OCt5W-0002qS-G6 for qemu-devel@nongnu.org; Fri, 14 May 2010 07:29:55 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OCt5U-0002GY-SX for qemu-devel@nongnu.org; Fri, 14 May 2010 07:29:54 -0400 Received: from mx1.redhat.com ([209.132.183.28]:29374) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OCt5U-0002GT-Kz for qemu-devel@nongnu.org; Fri, 14 May 2010 07:29:52 -0400 Received: from int-mx03.intmail.prod.int.phx2.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.16]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o4EBTpXr027389 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Fri, 14 May 2010 07:29:51 -0400 Message-ID: <4BED3418.9020501@redhat.com> Date: Fri, 14 May 2010 13:29:28 +0200 From: Kevin Wolf MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc References: <1273086712-29163-1-git-send-email-lcapitulino@redhat.com> <1273086712-29163-2-git-send-email-lcapitulino@redhat.com> <20100512181712.5637f26f@redhat.com> In-Reply-To: <20100512181712.5637f26f@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: bazulay@redhat.com, juzhang@redhat.com, Markus Armbruster , qemu-devel@nongnu.org Am 12.05.2010 23:17, schrieb Luiz Capitulino: > On Wed, 12 May 2010 18:48:38 +0200 > Markus Armbruster wrote: > >>> +query-block >>> +----------- >>> + >>> +Show the block devices. >>> + >>> +Each block device information is stored in a json-object and the returned value >>> +is a json-array of all devices. >>> + >>> +Each json-object contain the following: >>> + >>> +- "device": device name (json-string) >>> +- "type": device type (json-string) >> >> Possible values? "hd", "cdrom", "floppy". Code also has "unknown", but >> when it uses that, it's badly broken. > > Yes, but you didn't mean we shouldn't use 'unknown', right? > >>> +- "removable": true if the device is removable, false otherwise (json-bool) >>> +- "locked": true if the device is locked, false otherwise (json-bool) >>> +- "inserted": only present if the device is inserted, it is a json-object >>> + containing the following: >>> + - "file": device file name (json-string) >>> + - "ro": true if read-only, false otherwise (json-bool) >>> + - "drv": driver format name (json-string) >> >> Possible values? > > I got the following list by grepping the code. Kevin, can you confirm it's > correct? > > "blkdebug", "bochs", "cloop", "cow", "dmg", "file", "file", "ftp", "ftps", > "host_cdrom", "host_cdrom", "host_device", "host_device", "host_floppy", > "http", "https", "nbd", "parallels", "qcow", "qcow2", "raw", "tftp", "vdi", > "vmdk", "vpc", "vvfat" Looks right. But you probably don't want to mention those drivers twice that are present in both raw-posix.c and raw-win32.c. Kevin