linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Airlie <airlied@gmail.com>, Borislav Petkov <bp@alien8.de>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Pekka Enberg <penberg@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Avi Kivity <avi@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Linux KVM tool for v3.7-rc0
Date: Sun, 21 Oct 2012 14:59:33 +0200	[thread overview]
Message-ID: <20121021125933.GC19535@gmail.com> (raw)
In-Reply-To: <20121021110329.GA7024@infradead.org>


* Christoph Hellwig <hch@infradead.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

  reply	other threads:[~2012-10-21 12:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 11:34 [GIT PULL] Linux KVM tool for v3.7-rc0 Pekka Enberg
2012-10-12 17:27 ` Christoph Hellwig
2012-10-18 10:03   ` Ingo Molnar
2012-10-18 10:31     ` Pekka Enberg
2012-10-16  2:41 ` Stephen Rothwell
2012-10-16 14:50   ` Linus Torvalds
2012-10-20  7:04     ` Stephen Rothwell
2012-10-20 18:14       ` Borislav Petkov
2012-10-21  3:07         ` Dave Airlie
2012-10-21  3:46           ` Yinghai Lu
2012-10-21 11:03           ` Christoph Hellwig
2012-10-21 12:59             ` Ingo Molnar [this message]
2012-10-21 14:02               ` richard -rw- weinberger
2012-10-21 15:03                 ` Ingo Molnar
2012-10-21 17:15                   ` Borislav Petkov
2012-10-21 17:40                     ` Markus Trippelsdorf
2012-10-21 17:51                       ` Ingo Molnar
2012-10-21 17:54                         ` Markus Trippelsdorf
2012-10-21 18:04                           ` Markus Trippelsdorf
2012-10-21 18:10                             ` Ingo Molnar
2012-10-22  9:26                               ` Avi Kivity
2012-10-21 18:09                           ` Ingo Molnar
2012-10-21 15:39                 ` Pekka Enberg
2012-10-22  9:24                   ` Avi Kivity
2012-10-22 10:16                     ` Gleb Natapov
2012-10-23  2:20                       ` Asias He
2012-10-31 15:05                         ` Gleb Natapov
2012-10-21 11:18           ` Borislav Petkov
2012-10-21 11:29             ` richard -rw- weinberger
2012-10-21 22:16               ` Theodore Ts'o
2012-11-14  5:24       ` Stephen Rothwell
2012-11-14  6:02         ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121021125933.GC19535@gmail.com \
    --to=mingo@kernel.org \
    --cc=airlied@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=bp@alien8.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).