From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:55150) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZViFf-0000fN-32 for qemu-devel@nongnu.org; Sat, 29 Aug 2015 11:41:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZViFb-0007aB-NX for qemu-devel@nongnu.org; Sat, 29 Aug 2015 11:41:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47201) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZViFb-0007a5-IM for qemu-devel@nongnu.org; Sat, 29 Aug 2015 11:41:03 -0400 References: From: Max Reitz Message-ID: <55E1D289.9000202@redhat.com> Date: Sat, 29 Aug 2015 17:40:57 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="pUieg18tq7T9BPrRgNQ9lekAGjBL4KFhH" Subject: Re: [Qemu-devel] Mount image file feature List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: G 3 , Peter Maydell , qemu-devel qemu-devel This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --pUieg18tq7T9BPrRgNQ9lekAGjBL4KFhH Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 27.08.2015 03:05, G 3 wrote: > I want to share files between my host and guest computer. A feature I > want to add would be a new menu item in the Machine menu called "Mount > Image File...". When the user selects it, a file open dialog box > displays. The user can then select the image file with the file he want= s > to use. After pushing the OK button, the image file would be mounted > like a USB flash drive. This menu item would only show up if there is > usb support in the guest machine. >=20 > Would you be open to accepting such a feature? Generally I'd expect this to be functionality exposed by the management layer. For instance using virt-manager, this can be achived as follows: Switch to "Details", then click "Add Hardware", choose "Storage" and "USB" as the "Bus type". Choose the image, click "Finish", done. The main problem I see with adding this functionality to qemu itself would be having to get even further into the GUI business, which hasn't worked out too well so far=E2=80=A6 If we didn't care about that, than we'd have to think about the implementation. Internally, we'd probably call QMP's blockdev-add to open the image file, and then QMP's device_add to add the USB device. So then qemu would use its own management interfaces to execute the operation, which seems a bit strange to me, further hinting at the fact that we probably should leave this to the management layer. Max --pUieg18tq7T9BPrRgNQ9lekAGjBL4KFhH Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJV4dKJAAoJEDuxQgLoOKyt6WsH/0aqQQW5hgcjTl3G5koGfgRm QpzJtRGUAxg4zpzruSEHuj6f8AIytduNPTDiK/zPJ7jj7D0SeJvRRSzQ1y77j1Oy y0Y3GvSEpLQAsPqPCaisI8eDcXR1bo/P7fxtUh6NlmWBTaE0w1YWVjrmL6PYn1Uf EnLk2Vohu21rMhozFxmbksL3pj6L9P9opsibO1gu3OZJ7ZnLPm2gzUoEpd6p92DQ j1rBgFy0Cj9gcvA5BxAAJP11y9FiB0KyiTbgdaMHSM8GNJcddLoA7L0nfVvHVeZD MjWmhWPrp9Bni/1xrs7zQOmU40c3xuCc8e/aFy4BbPV8OrwToHeXA04ruGBwsWM= =8wvu -----END PGP SIGNATURE----- --pUieg18tq7T9BPrRgNQ9lekAGjBL4KFhH--