From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sasha Levin Subject: Re: [PATCH 2/2] kvm tools: Allow easily sandboxing applications within a guest Date: Sun, 04 Dec 2011 14:11:30 +0200 Message-ID: <1323000690.4205.3.camel@lappy> References: <1322810215-9647-1-git-send-email-levinsasha928@gmail.com> <1322810215-9647-2-git-send-email-levinsasha928@gmail.com> <4EDB4AAA.8090203@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: penberg@kernel.org, kvm@vger.kernel.org, mingo@elte.hu, asias.hejun@gmail.com, gorcunov@gmail.com To: Avi Kivity Return-path: Received: from mail-ee0-f46.google.com ([74.125.83.46]:55159 "EHLO mail-ee0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753136Ab1LDML5 (ORCPT ); Sun, 4 Dec 2011 07:11:57 -0500 Received: by eeaq14 with SMTP id q14so1480629eea.19 for ; Sun, 04 Dec 2011 04:11:56 -0800 (PST) In-Reply-To: <4EDB4AAA.8090203@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Sun, 2011-12-04 at 12:25 +0200, Avi Kivity wrote: > On 12/02/2011 09:16 AM, Sasha Levin wrote: > > This is useful when testing code that might cause problems on the host, or > > to automate kernel testing since it's now easy to link a kvm tools test > > script with 'git bisect run'. > > This tie-up into git bisect is a really cool idea. > > With device assignment, you can even bisect driver bugs this way. Yup, it makes bisecting most issues which are reproducible pretty easy. Yesterday I've managed to bisect the issue in '[BUG] net: kernel BUG at include/net/netns/generic.h:40!' without having to touch the process once. Obviously I was pretty happy :) -- Sasha.