qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] feature idea: allow user to run custom scripts


From: Dr. David Alan Gilbert
Subject: Re: [Qemu-devel] feature idea: allow user to run custom scripts
Date: Tue, 29 Sep 2015 14:23:17 +0100
User-agent: Mutt/1.5.24 (2015-08-30)

* Programmingkid (address@hidden) wrote:
> 
> On Sep 29, 2015, at 9:11 AM, Dr. David Alan Gilbert wrote:
> 
> > * Peter Maydell (address@hidden) wrote:
> >> On 28 September 2015 at 20:43, Programmingkid <address@hidden> wrote:
> >>> 
> >>> On Sep 28, 2015, at 3:29 AM, Markus Armbruster wrote:
> >>> 
> >>>> Programmingkid <address@hidden> 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.
> 
> My idea was to just send the command to the monitor as if the user typed them 
> up.

Yeh, I'm not sure how easily that'll be to glue into the monitor,
because the monitor has a parser that's fed somehow from the chardev.

Dave
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK



reply via email to

[Prev in Thread] Current Thread [Next in Thread]