From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mym5g-0005LI-FS for qemu-devel@nongnu.org; Fri, 16 Oct 2009 08:39:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mym5Z-0005Fc-SH for qemu-devel@nongnu.org; Fri, 16 Oct 2009 08:39:26 -0400 Received: from [199.232.76.173] (port=37646 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mym5Z-0005FU-IZ for qemu-devel@nongnu.org; Fri, 16 Oct 2009 08:39:21 -0400 Received: from mx1.redhat.com ([209.132.183.28]:59293) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mym5Z-0005l9-2v for qemu-devel@nongnu.org; Fri, 16 Oct 2009 08:39:21 -0400 Date: Fri, 16 Oct 2009 09:39:10 -0300 From: Luiz Capitulino Subject: Re: [Qemu-devel] [PATCH 6/9] QError: Add qdev not found error Message-ID: <20091016093910.6e4a1bca@doriath> In-Reply-To: <4AD8211B.9090004@redhat.com> References: <1255453026-18637-1-git-send-email-lcapitulino@redhat.com> <1255453026-18637-7-git-send-email-lcapitulino@redhat.com> <1255561330.29192.2.camel@slab.beaverton.ibm.com> <20091015103405.591e2f3b@doriath> <1255626960.29192.7.camel@slab.beaverton.ibm.com> <20091015145208.1d871f09@doriath> <1255630433.29192.16.camel@slab.beaverton.ibm.com> <20091015160839.7dbef5bf@doriath> <4AD8211B.9090004@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gerd Hoffmann Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, Hollis Blanchard On Fri, 16 Oct 2009 09:30:35 +0200 Gerd Hoffmann wrote: > Hi, > > > { "error": { "code": 404, > > "desc": "husb: host usb device 0.12 is already open" } } > > > > In case I'm right, there are two problems with it: > > > > 1. It's hard to retrieve the variable information > > Markus asked it already, I'm asking again: > > *Do we actually need the variable information?* That's a good question and to answer it properly I think we should have to go over all errors and check if any of them generate information which is not available from the context. There is also the compatibility issue, I'm not sure if it's ok to change the error output, we would have to check at least the majors QEMU users.