qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
	Programmingkid <programmingkidx@gmail.com>
Cc: "qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] drive_add: file names with spaces
Date: Mon, 30 Oct 2017 21:02:33 +0100	[thread overview]
Message-ID: <40acf44f-a8d2-890e-556b-02f551b05f2d@redhat.com> (raw)
In-Reply-To: <20171030143220.GA5438@work-vm>

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

On 10/30/2017 03:32 PM, Dr. David Alan Gilbert wrote:

> Now, the real challenge is how to deal with a filename with a comma in;
>    drive_add 1 "file=foo,bar"
>    Could not open 'foo': No such file or directory
> 

Does HMP use the QemuOpts parser?  If so, try:

drive_add 1 "file=foo,,bar"

(that is, reproduce the double-comma escaping mechanism that we use on
the command line).

But I haven't personally tried this, so I have no idea if it will help.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org


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

  parent reply	other threads:[~2017-10-30 20:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  4:44 [Qemu-devel] drive_add: file names with spaces Programmingkid
2017-10-28  6:00 ` Eric Blake
2017-10-29 10:21   ` Dr. David Alan Gilbert
2017-10-30  1:38     ` Programmingkid
2017-10-30 14:32       ` Dr. David Alan Gilbert
2017-10-30 15:22         ` Programmingkid
2017-10-30 17:03           ` Dr. David Alan Gilbert
2017-10-30 20:02         ` Eric Blake [this message]
2017-10-30 20:15           ` Dr. David Alan Gilbert

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=40acf44f-a8d2-890e-556b-02f551b05f2d@redhat.com \
    --to=eblake@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /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).