From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44604) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tfti2-0001Xg-Cc for qemu-devel@nongnu.org; Tue, 04 Dec 2012 09:43:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Tfti1-0002tR-6k for qemu-devel@nongnu.org; Tue, 04 Dec 2012 09:42:54 -0500 Received: from mx1.redhat.com ([209.132.183.28]:18716) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Tfti0-0002tI-V4 for qemu-devel@nongnu.org; Tue, 04 Dec 2012 09:42:53 -0500 Message-ID: <50BE0BD8.2010501@redhat.com> Date: Tue, 04 Dec 2012 15:42:32 +0100 From: =?ISO-8859-1?Q?J=E1n_Tomko?= MIME-Version: 1.0 References: <50BCCB77.1080404@redhat.com> <20121204094628.1518b973@doriath.home> In-Reply-To: <20121204094628.1518b973@doriath.home> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] detecting seccomp sandbox capability via QMP List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: qemu-devel@nongnu.org, otubo@linux.vnet.ibm.com On 12/04/12 12:46, Luiz Capitulino wrote: > On Mon, 03 Dec 2012 16:55:35 +0100 > J=E1n Tomko wrote: >=20 >> Hello, >> >> is there a way to check if QEMU was compiled with --enable-seccomp via= QMP? >=20 > Not that I'm aware of. Could you describe your use-case? It's for libvirt. The detection is broken since the switch from parsing -help output to QMP and I wanted to fix it. Assuming it's supported if we do capabilities detection via QMP (since libvirt 1.0.0 and QEMU 1.2) would work except for this case: If seccomp sandbox was requested in /etc/libvirt/qemu.conf, but it was compiled out from qemu, libvirt would try to run QEMU with -sandbox on instead of printing an error earlier. Jan