From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751729Ab1GYIiA (ORCPT ); Mon, 25 Jul 2011 04:38:00 -0400 Received: from cantor2.suse.de ([195.135.220.15]:33012 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751340Ab1GYIhz convert rfc822-to-8bit (ORCPT ); Mon, 25 Jul 2011 04:37:55 -0400 Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Alexander Graf In-Reply-To: Date: Mon, 25 Jul 2011 10:37:51 +0200 Cc: 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 Content-Transfer-Encoding: 8BIT Message-Id: References: <4E2CA6DE.4040900@web.de> <20110725075305.GA32294@elte.hu> <0EAA5203-D598-4CBA-B8D2-AB371A7689A9@suse.de> To: Pekka Enberg X-Mailer: Apple Mail (2.1084) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25.07.2011, at 10:30, Pekka Enberg wrote: > 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. I like perf. Really. But I still don't see why it wouldn't be able to live in its own tree either. > [ Yes, yes, I know people apparently use virtio-manager for lauching Qemu so > they don't need to figure out the setup themselves. But now you have *three* > separate components (KVM, Qemu, virtio-manager) which is a completely Having the split between KVM and user space is necessary. One lives in kernel space, the other one in user space. The split between qemu and virt-manager is something I don't like either. But then again I don't like virt-manager :). But what does this have to do with pulling something into the kernel? And reimplementing something that's already been there? > different direction we're taking. Hell, we even went ahead and wrote our own > mini-BIOS just to keep things in one unified tree. ] Yes, making sure that you have even more non-working non-Linux OSs. Alex