On 09/07/2012 08:06 AM, Daniel Veillard wrote:
On Fri, Sep 07, 2012 at 01:29:25PM +0200, Ján Tomko wrote:
On 09/07/12 05:25, Daniel Veillard wrote:
The problem is that libvirt and qemu releases are a priori not
tied, doing what you suggest would mean to try to guess the actual
qemu versio
On Fri, Sep 07, 2012 at 01:29:25PM +0200, Ján Tomko wrote:
> On 09/07/12 05:25, Daniel Veillard wrote:
> >
> > The problem is that libvirt and qemu releases are a priori not
> > tied, doing what you suggest would mean to try to guess the actual
> > qemu version used by the guest and then switch
On 09/07/12 05:25, Daniel Veillard wrote:
>
> The problem is that libvirt and qemu releases are a priori not
> tied, doing what you suggest would mean to try to guess the actual
> qemu version used by the guest and then switch on or off, which would
> somehow be at odd with the overall driver co
On Thu, Sep 06, 2012 at 11:53:06AM -0400, Corey Bryant wrote:
>
>
> On 09/06/2012 02:45 AM, Daniel Veillard wrote:
> >On Thu, Sep 06, 2012 at 02:27:19PM +0800, Daniel Veillard wrote:
> >>On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
> >>>QEMU (since 1.2-rc0) supports setting up a sys
On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
> QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
> libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
> -sandbox on on qemu command line.
>
> This patch detects this capability by searching for -sa
On 09/06/2012 02:27 AM, Daniel Veillard wrote:
On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
-sandbox on on qemu command line.
This patch de
On 09/06/2012 02:45 AM, Daniel Veillard wrote:
On Thu, Sep 06, 2012 at 02:27:19PM +0800, Daniel Veillard wrote:
On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
libseccomp on linux kernel from 3.5-rc1. This is enab
On Thu, Sep 06, 2012 at 02:27:19PM +0800, Daniel Veillard wrote:
> On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
> > QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
> > libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
> > -sandbox on on qemu c
On Mon, Sep 03, 2012 at 02:03:39PM +0200, Ján Tomko wrote:
> QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
> libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
> -sandbox on on qemu command line.
>
> This patch detects this capability by searching for -sa
On 09/03/2012 03:07 PM, Doug Goldstein wrote:
> On Mon, Sep 3, 2012 at 7:03 AM, Ján Tomko wrote:
>> QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
>> libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
>> -sandbox on on qemu command line.
>
>
>
> There's
On Mon, Sep 3, 2012 at 7:03 AM, Ján Tomko wrote:
> QEMU (since 1.2-rc0) supports setting up a syscall whitelist through
> libseccomp on linux kernel from 3.5-rc1. This is enabled by specifying
> -sandbox on on qemu command line.
There's a big push to not rely on -help scraping, please work with
11 matches
Mail list logo
