From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
Programmingkid <programmingkidx@gmail.com>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] feature idea: allow user to run custom scripts
Date: Tue, 29 Sep 2015 14:11:10 +0100 [thread overview]
Message-ID: <20150929131109.GI3810@work-vm> (raw)
In-Reply-To: <CAFEAcA-XhjL5=u=y5c53c8iifT8obWvTub5+Fwv46WPZ1Luhzw@mail.gmail.com>
* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 28 September 2015 at 20:43, Programmingkid <programmingkidx@gmail.com> wrote:
> >
> > On Sep 28, 2015, at 3:29 AM, Markus Armbruster wrote:
> >
> >> Programmingkid <programmingkidx@gmail.com> writes:
> >>> A menu item
> >>> that displays a file open dialog is very easy to use. The user just selects
> >>> a file and QEMU loads and runs all the commands in it. This feature
> >>> would make QEMU easier to use. It would also make QEMU easily
> >>> expandable. Typing long commands in the monitor is difficult and
> >>> error prone. Saving these commands in a file would make it much
> >>> easier for the user. An example command someone could put in a
> >>> file is sending Control-Alt-Delete to the emulator. Another command
> >>> could be mounting an image file. This feature would make things
> >>> much easier for the user.
> >>
> >> You didn't mention you're talking about a *GUI* feature.
> >
> > I'm thinking it would be easier to send in the patch rather than talk about
> > what this feature could be.
>
> I think Markus and I are trying to save you that effort by
> pointing out that this is a VM management layer feature,
> not a core QEMU feature.
OK, so I'm going to agree with Programmingkid here.
I think this would be a useful feature to have in QEMU; I've
got gratuitous hacks in some of my test scripts that work
around it not being there.
I think there are two possible things, both of which seem fairly
easy:
1) Add a -chardev from file that works in this case
(I don't think the current chardev file works does it?)
2) A 'source' like command.
Dave
>
> thanks
> -- PMM
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-09-29 13:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 3:39 [Qemu-devel] feature idea: allow user to run custom scripts Programmingkid
2015-09-27 10:13 ` Peter Maydell
2015-09-27 18:53 ` Peter Crosthwaite
2015-09-28 1:49 ` Programmingkid
2015-09-28 2:30 ` Michael Roth
2015-09-28 3:10 ` Programmingkid
2015-09-28 7:29 ` Markus Armbruster
2015-09-28 19:43 ` Programmingkid
2015-09-28 19:44 ` Peter Maydell
2015-09-28 19:48 ` Programmingkid
2015-09-29 13:11 ` Dr. David Alan Gilbert [this message]
2015-09-29 13:17 ` Programmingkid
2015-09-29 13:23 ` Dr. David Alan Gilbert
2015-09-30 5:01 ` Paolo Bonzini
2015-09-29 13:24 ` Peter Maydell
2015-09-29 13:31 ` Dr. David Alan Gilbert
2015-09-30 7:48 ` Markus Armbruster
2015-09-30 8:14 ` Dr. David Alan Gilbert
2015-09-30 10:53 ` Peter Maydell
2015-09-30 14:23 ` Programmingkid
2015-10-01 10:36 ` Paolo Bonzini
2015-10-02 11:20 ` Kevin Wolf
2015-10-01 7:06 ` Markus Armbruster
2015-10-02 12:33 ` Daniel P. Berrange
2015-10-02 13:28 ` Programmingkid
2015-10-01 6:55 ` Markus Armbruster
2015-10-01 8:01 ` Dr. David Alan Gilbert
2015-10-02 12:30 ` Daniel P. Berrange
2015-10-02 13:33 ` Dr. David Alan Gilbert
2015-10-02 14:28 ` Daniel P. Berrange
2015-10-02 14:37 ` Programmingkid
2015-10-02 16:21 ` Eric Blake
2015-10-02 17:57 ` Programmingkid
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=20150929131109.GI3810@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=crosthwaitepeter@gmail.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=peter.maydell@linaro.org \
--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).