From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41977) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVObH-0004aP-Fs for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:05:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WVObB-0004AB-Aq for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:05:19 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WVObB-0004A5-3w for qemu-devel@nongnu.org; Wed, 02 Apr 2014 13:05:13 -0400 Date: Wed, 2 Apr 2014 18:05:05 +0100 From: "Dr. David Alan Gilbert" Message-ID: <20140402170505.GO2586@work-vm> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Qemu-devel] process naming not working when using a config file List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: William Dauchy Cc: QEMU Developers * 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