From: Andrea Bolognani <abologna@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Marcel Apfelbaum <marcel@redhat.com>,
Laszlo Ersek <lersek@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide sample configuration files
Date: Thu, 09 Feb 2017 15:56:38 +0100 [thread overview]
Message-ID: <1486652198.3641.45.camel@redhat.com> (raw)
In-Reply-To: <20170209140804.onpj3pniqim3qxr4@kamzik.brq.redhat.com>
On Thu, 2017-02-09 at 15:08 +0100, Andrew Jones wrote:
[...]
> Actually, I don't think anything is stopping me from using this
> file that way. I'll have to try the file name override that I
> suggested below, but
>
> qemu -nodefaults -readconfig configfile -m $MEM -machine accel=tcg
>
> should certainly override correctly.
I just tried and at least overriding the amount of memory
definitely works :)
> > > I agree with the comments of others that we should be using
> > > the PL011 instead. We should also set it up such that the
> > > monitor is multiplexed, so ^C won't terminate the guest and
> > > ^A will allow us to go to the monitor.
> >
> > That sounds awesome, how do I actually make it work from
> > the configuration file though?
>
> Sorry, dunno :-)
I don't think there's a way to make it work without adding
some parameters to the command line, I'm afraid :(
But if you use '-serial mon:stdio' you can indeed switch
between the serial console and the QEMU monitor at will,
and as a (quite interesting) side-effect Ctrl+C will no
longer kill QEMU :)
By the way, switching between serial and monitor is not
done with Ctrl+A but with Ctrl+A-c, which is not the most
convenient shortcut if you're running your guests on a
remote host due to GNU screen using the very same one ;)
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2017-02-09 14:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 17:35 [Qemu-devel] [PATCH v5 0/2] docs: Improve sample configuration files Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 1/2] q35: " Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-08 18:11 ` Laszlo Ersek
2017-02-08 18:49 ` Andrea Bolognani
2017-02-08 19:34 ` Laszlo Ersek
2017-02-08 19:47 ` Andrea Bolognani
2017-02-09 9:49 ` Andrew Jones
2017-02-09 10:52 ` Andrea Bolognani
2017-02-08 18:32 ` Peter Maydell
2017-02-08 19:23 ` Laszlo Ersek
2017-02-08 19:40 ` Peter Maydell
2017-02-08 19:28 ` Andrea Bolognani
2017-02-08 19:36 ` Peter Maydell
2017-02-08 19:49 ` Laszlo Ersek
2017-02-09 13:53 ` Andrea Bolognani
2017-02-09 14:14 ` Andrew Jones
2017-02-08 19:36 ` Laszlo Ersek
2017-02-09 9:42 ` Andrew Jones
2017-02-09 9:57 ` Peter Maydell
2017-02-09 10:51 ` Andrea Bolognani
2017-02-09 12:28 ` Andrew Jones
2017-02-09 13:27 ` Andrea Bolognani
2017-02-09 14:08 ` Andrew Jones
2017-02-09 14:56 ` Andrea Bolognani [this message]
2017-02-09 15:26 ` Gerd Hoffmann
2017-02-09 15:10 ` Andrea Bolognani
2017-02-09 15:35 ` Andrew Jones
2017-02-09 16:11 ` Andrea Bolognani
2017-02-09 16:36 ` Andrew Jones
2017-02-09 17:06 ` Andrea Bolognani
2017-02-09 18:05 ` Andrew Jones
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=1486652198.3641.45.camel@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=kraxel@redhat.com \
--cc=lersek@redhat.com \
--cc=marcel@redhat.com \
--cc=peter.maydell@linaro.org \
--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).