qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: William Dauchy <wdauchy@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] process naming not working when using a config file
Date: Wed, 2 Apr 2014 18:05:05 +0100	[thread overview]
Message-ID: <20140402170505.GO2586@work-vm> (raw)
In-Reply-To: <CAJ75kXbHLS+E0uvYUw=jR+HfhAtgJJiz_Uz7HmPbdjqx32BOEA@mail.gmail.com>

* William Dauchy (wdauchy@gmail.com) wrote:
> Hello,
> 
> I was using the qemu command line option:
> -name foo,process=foo
> in order to get a nice process naming on my linux box.
> 
> and so I could do
> $ ps axco pid,command | grep 'foo'
> 4242 foo
> 
> I switched to a config file with:
> [name]
>   guest = "foo"
>   process = "foo"
> 
> but now the previous `ps` command is empty and the process name is
> qemu-system-x86
> 
> I guess these options are not taken in consideration. I am using the
> last git version of qemu.

Thanks for the report; on an older version of Qemu that still has the -name
option, using the file gives an error (There is no option group 'name'),
but on the lastest one it does, as you say, just ignore it.

> Should I write a bug report for this?

You can add a launchpad entry if you like; however sicne I suspect
it's my rework of --name to use QemuOpts that broke it, I'll add it
to my list.

Thanks again for reporting it.

Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK

  reply	other threads:[~2014-04-02 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 15:50 [Qemu-devel] process naming not working when using a config file William Dauchy
2014-04-02 17:05 ` Dr. David Alan Gilbert [this message]
2014-04-02 17:16   ` William Dauchy

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=20140402170505.GO2586@work-vm \
    --to=dgilbert@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wdauchy@gmail.com \
    /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).