public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Glauber Costa <glommer@gmail.com>, Avi Kivity <avi@redhat.com>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: VMX ideas
Date: Mon, 3 Nov 2008 10:26:08 +0000	[thread overview]
Message-ID: <20081103102608.GA26142@redhat.com> (raw)
In-Reply-To: <BAE30A90-9910-46DF-8044-840C23E692FE@suse.de>

On Mon, Nov 03, 2008 at 08:24:49AM +0100, Alexander Graf wrote:
> 
> 
> Am 03.11.2008 um 00:36 schrieb "Glauber Costa" <glommer@gmail.com>:
> 
> >On Sun, Nov 2, 2008 at 2:18 PM, Avi Kivity <avi@redhat.com> wrote:
> >>Avi Kivity wrote:
> >>>
> >>>Daniel P. Berrange wrote:
> >>>>
> >>>>Yes, on Fedora, if you install the 'kvm' userspace package, we  
> >>>>drop a
> >>>>script into /etc/sysconfig/modules/kvm.modules that cause kvm- 
> >>>>intel.ko
> >>>>or kvm-amd.ko to be loaded at boot time.
> >>>>
> >>>
> >>>Does the postinstall also load the modules?  If not, users who don't
> >>>reboot are in for an unpleasant surprise.
> >>>
> >>
> >>I checked and it doesn't.
> >Funny. Rawhide version does exactly that.
> 
> So when a Fedora user installs the kvm userspace, he can't run vmware/ 
> parallels/vbox and the like without fiddling?

Fedora focuses on making the best possible free software experiance, 
without compromising it for sake of closed source software. If vendors
of out of tree kernel modules want a good experiance for their users,
they can work to get the neccessary support merged in upstream kernel
trees. Many vendors over the years have shipped out of tree network
or disk drivers - we don't avoid loading the in kernel driver just in
case in conflicts with a out of tree replacement nic/disk module. The
same applies for virtualization - one in tree kernel module should be
made to be sufficient for all userspace apps that want to use virt.
KVM is the only in tree virt module at this time, so we load it by
default. If the KVM module isn't sufficient to other userspace virt 
apps, then they need to work with the kernel community to address that,
not create many out of tree modules duplicating each other's functionality.


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

      reply	other threads:[~2008-11-03 10:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 14:52 VMX ideas Alexander Graf
2008-10-29 15:01 ` Joerg Roedel
2008-10-29 15:11   ` Alexander Graf
2008-10-29 15:36 ` Gerd Hoffmann
2008-10-29 15:45   ` Anthony Liguori
2008-10-29 17:15     ` Alexander Graf
2008-10-29 17:18   ` Alexander Graf
2008-11-02 10:28   ` Avi Kivity
2008-11-03  7:32     ` Alexander Graf
2008-11-02 10:26 ` Avi Kivity
2008-11-02 16:11   ` Daniel P. Berrange
2008-11-02 16:15     ` Avi Kivity
2008-11-02 16:18       ` Avi Kivity
2008-11-02 23:36         ` Glauber Costa
2008-11-03  7:24           ` Alexander Graf
2008-11-03 10:26             ` Daniel P. Berrange [this message]

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=20081103102608.GA26142@redhat.com \
    --to=berrange@redhat.com \
    --cc=agraf@suse.de \
    --cc=avi@redhat.com \
    --cc=glommer@gmail.com \
    --cc=kvm@vger.kernel.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