From: Stefan Hajnoczi <stefanha@gmail.com>
To: Bug 1391942 <1391942@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1391942] [NEW] Unnecessary events option of the trace argument with UST backend
Date: Wed, 7 Jan 2015 14:35:25 +0000 [thread overview]
Message-ID: <20150107143525.GD22440@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <20141112160138.19244.98743.malonedeb@gac.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Wed, Nov 12, 2014 at 04:01:38PM -0000, Francis Deslauriers wrote:
> When running configure with the --enable-trace-backends=ust option and compiling.
> The user should not have to specify a the "events" and "file" options because they are not used with that tracing framework.
>
> Right now, in order the use this option the need to specify a dummy
> events file.
>
> This fails:
> $> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace -m 512
> qemu-system-x86_64: -trace -m: Invalid parameter '-m'
>
> This works:
> $> qemu-system-x86_64 -hda debian_wheezy_amd64_standard.qcow2 -trace events=dummy-events.txt -m 512
> VNC server running on `127.0.0.1:5900'
>
> I am using version:
> $> qemu-system-x86_64 --version
> QEMU emulator version 2.1.90, Copyright (c) 2003-2008 Fabrice Bellard
What happens when you pass no -trace option?
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-07 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 16:01 [Qemu-devel] [Bug 1391942] [NEW] Unnecessary events option of the trace argument with UST backend Francis Deslauriers
2015-01-07 14:35 ` Stefan Hajnoczi [this message]
2015-01-07 16:20 ` [Qemu-devel] [Bug 1391942] " Francis Deslauriers
2020-11-19 20:48 ` Thomas Huth
2021-01-19 4:17 ` Launchpad Bug Tracker
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=20150107143525.GD22440@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=1391942@bugs.launchpad.net \
--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).