From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Wolf Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1 Date: Mon, 25 Jul 2011 14:24:47 +0200 Message-ID: <4E2D608F.6020606@redhat.com> References: <4E2CA6DE.4040900@web.de> <20110725075305.GA32294@elte.hu> <0EAA5203-D598-4CBA-B8D2-AB371A7689A9@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Graf , Ingo Molnar , Jan Kiszka , torvalds@linux-foundation.org, avi@redhat.com, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, gorcunov@gmail.com, levinsasha928@gmail.com, asias.hejun@gmail.com, prasadjoshi124@gmail.com To: Pekka Enberg Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27312 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750970Ab1GYMWJ (ORCPT ); Mon, 25 Jul 2011 08:22:09 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: Am 25.07.2011 10:30, schrieb Pekka Enberg: > Hi Alexander, > > On Mon, Jul 25, 2011 at 11:14 AM, Alexander Graf wrote: >>> So i wanted to have a lightweight tool that allows me to test KVM and >>> tools/kvm/ does that very nicely: i type './kvm run' and i can test a >>> native bzImage (which has some virtualization options enabled as >>> well) on the _host_ distro i am running, booting to a text shell >>> prompt. >> >> I do that all the time. >> >> $ qemu-kvm -nographic -kernel arch/x86/boot/bzImage -append console=ttyS0 >> >> does the exact same thing. If that's too much typing for you, make it a bash alias. > > You know, they said the same thing about oprofile. All you needed to do was to > write few simple shell scripts to make it work. One of the key > features of tools/kvm > is 'as little configuration as possible' and I can assure you that > bash alias is really > not a solution for that. You've just chosen a different default. I'd argue that most users (i.e. not developers of the tool or the kernel) actually want to run with a disk image and graphics. You can type "qemu-kvm harddisk.img" and that's it. This is clearly superior to something as tedious as "./kvm run -d harddisk.img --sdl" and I can assure you that a bash alias is really not a solution for that. So, as always, which set of command line switches works better for you depends entirely on your use case. Kevin