[Qemu-devel] process naming not working when using a config file

[Qemu-devel] process naming not working when using a config file

[William Dauchy]

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.
Should I write a bug report for this?

Thanks,
-- 
William

Re: [Qemu-devel] process naming not working when using a config file

[Dr. David Alan Gilbert]

* 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

Re: [Qemu-devel] process naming not working when using a config file

[William Dauchy]

Hello Dave,

Thanks for your quick reply.

On Wed, Apr 2, 2014 at 7:05 PM, Dr. David Alan Gilbert
<dgilbert@redhat.com> wrote:
> 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.

If it's already on your todo list, that's ok for me.

Thanks,

-- 
William