On Fri, 2011-12-02 at 09:39 +0200, Pekka Enberg wrote: > On Fri, 2011-12-02 at 09:26 +0200, Pekka Enberg wrote: > >> On Fri, Dec 2, 2011 at 9:16 AM, Sasha Levin <levinsasha928@xxxxxxxxx> wrote: > >>> This patch adds a '--sandbox' argument when used in conjuction with a custom > >>> rootfs, it allows running a script or an executable in the guest environment > >>> by using executables and other files from the host. > >>> > >>> 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'. > >>> > >>> Suggested-by: Ingo Molnar <mingo@xxxxxxx> > >>> Signed-off-by: Sasha Levin <levinsasha928@xxxxxxxxx> > >> > >> Nice! How do I use this to run trinity sandboxed in a guest? > > On Fri, 2 Dec 2011, Sasha Levin wrote: > > Assuming you have trinity installed in /usr/bin or something similar in > > on the host (you can just 'cp trinity /usr/bin/'), just write this > > script: > > > > test-trinity.sh: > > #! /bin/bash > > trinity --mode=random --quiet -i > > > > and run using: > > ./kvm run -k [kernel to test] --sandbox test-trinity.sh > > Would it not be better to introduce a new command that works like 'perf > stat', for example: > > ./kvm sandbox -k <kernel to test> -- trinity --mode=random --quiet -i > > ? So basically proxy the first set of parameters to 'kvm run' and run the second one as the script? Thats possible as well. I did the '--sandbox' parameters so that we could pass a script that could do more complex testing in the guest, but it's also possible with your suggestion so we could do it that way as well. -- Sasha. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
