[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121021125933.GC19535@gmail.com>
Date:	Sun, 21 Oct 2012 14:59:33 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Dave Airlie <airlied@...il.com>, Borislav Petkov <bp@...en8.de>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Pekka Enberg <penberg@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Avi Kivity <avi@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
* Christoph Hellwig <hch@...radead.org> wrote:
> On Sun, Oct 21, 2012 at 01:07:31PM +1000, Dave Airlie wrote:
> > Why couldn't this script just be a wrapper around qemu
> 
> It can be.  Here is my ususual one:
> 
> #!/bin/sh
> 
> /opt/qemu/bin/qemu-system-x86_64 \
> 	-m 1500 \
> 	-enable-kvm \
> 	-drive if=none,file=/home/hch/qemu-root.img,cache=none,id=root \
You are wrong on three counts:
 - As I mentioned it in my first mail to you this is not the 
   same as 'vm run': you still have a qemu-root.img while 
   tools/kvm does not ...
   'vm run' works without having any disk image around, it just 
   uses the existing distro binaries and boots them, sharing the 
   host file system.
 - automatic, transparent host filesystem sharing is another 
   useful feature: I can copy files in/out of the virtual 
   machine using the host filesystem.
 - transparent networking is up and running straight away
But yeah, I guess if you ignore enough key tools/kvm/ features 
then you will eventually be right: it's really just the same as 
Qemu and has no place in the kernel repo ;-)
Thanks,
	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
Powered by blists - more mailing lists
 
