From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Programmingkid <programmingkidx@gmail.com>,
"qemu-devel@nongnu.org qemu-devel" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] drive_add: file names with spaces
Date: Sun, 29 Oct 2017 10:21:07 +0000 [thread overview]
Message-ID: <20171029102106.GA2841@work-vm> (raw)
In-Reply-To: <38c3125f-b050-c0ba-282f-bc1e9e11d297@redhat.com>
* Eric Blake (eblake@redhat.com) wrote:
> On 10/28/2017 06:44 AM, Programmingkid wrote:
> > I'm trying to use an image file that has spaces in its file name (and sometimes in the path) to be used as a USB flash drive. When I try adding the image file using the drive_add command I see this error: drive_add: extraneous characters at the end of the line
> >
> > I have tried using single and double quotes around the file name but this does not help. Is there a way to use files that have spaces in it's name with drive_add?
>
> Not in HMP, which lacks quoting. (Unless you want to patch HMP to learn
> quoting)
I think it's already got that code at least in some places.
monitor_parse_arguments calls get_str, and get_str understands " wrapped
arguments.
drive_add 1 "file=foo bar"
gives me:
Could not open 'foo bar': No such file or directory
so I think that's doing the right thing.
Dave
> But using spaces in filenames works fine in QMP.
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc. +1-919-301-3266
> Virtualization: qemu.org | libvirt.org
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-10-29 10:21 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 [this message]
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
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=20171029102106.GA2841@work-vm \
--to=dgilbert@redhat.com \
--cc=eblake@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).