From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: downscript not run when using quit in monitor
Date: Tue, 24 Feb 2009 09:45:15 +0100 [thread overview]
Message-ID: <49A3B39B.4030701@web.de> (raw)
In-Reply-To: <01a73bd5af90e953f04f6ad80b151087@iem.pw.edu.pl>
[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]
Jędrzej Kalinowski wrote:
> On Thu, 19 Feb 2009 11:27:19 +0100, Jędrzej Kalinowski
> <kalinoj1@iem.pw.edu.pl> wrote:
>> Hello,
>>
>> I'm using qemu to simulate various network booting scenarios w pxe/gPXE.
>> I use my ifup / ifdown script to set up / destroy tap devices form the
> qemu
>> instance.
>>
>> However if I 'quit' qemu from the monitor - the downscript is not
> executed.
>> Is it by design or should it be classified as a bug?
>> If it's fine - how can I close the machine properly (with downscript
>> execution) in -curses mode? It has no OS loaded - it didn't succeded to
>> boot from pxe..
>>
>
> Following is a trivial patch I needed to apply to make downscripts
> execute...
> Maybe will save a few seconds to someone..
>
> Cheers - Jędrzej
>
> --- monitor.c.orig 2009-02-22 19:13:22.000000000 +0100
> +++ monitor.c 2009-02-22 18:53:17.000000000 +0100
> @@ -380,6 +380,7 @@
>
> static void do_quit(void)
> {
> + net_cleanup();
> exit(0);
> }
>
Generally, this looks reasonable to me. But to catch also other exits,
you probably want to install an atexit handler. And please post your
patches with signed-off and an easily extractable commit comment.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-02-24 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 10:27 [Qemu-devel] downscript not run when using quit in monitor Jędrzej Kalinowski
2009-02-24 0:41 ` Jędrzej Kalinowski
2009-02-24 8:45 ` Jan Kiszka [this message]
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=49A3B39B.4030701@web.de \
--to=jan.kiszka@web.de \
--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).