public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Mikolaj Kucharski <mikolaj@kucharski.name>, kvm@vger.kernel.org
Subject: Re: Qemu vs Qemu-KVM
Date: Tue, 22 Dec 2009 10:53:34 +0200	[thread overview]
Message-ID: <4B30890E.5090705@redhat.com> (raw)
In-Reply-To: <20091221222114.GM12659@x40.openbsd.home.lan>

On 12/22/2009 12:21 AM, Mikolaj Kucharski wrote:
> On Mon, Dec 21, 2009 at 09:22:52AM +0200, Gleb Natapov wrote:
>    
>>> I have personal interest in resolving RedHat's bz #508801, unfortunately
>>> I cannot do that myself, so I wanted to ask on the list for help, but now
>>> I'm confused where should I go.
>>>
>>>        
>> Can you try kvm modules from latest kvm.git please? It looks like emulation of
>> "push %ds" fails and it was added after 2.6.32.
>>      
> Having following GIT repositories:
>
> git://git.kernel.org/pub/scm/virt/kvm/kvm.git
> git://git.kernel.org/pub/scm/virt/kvm/kvm-kmod.git
>
> Which one I should use to build my modules from? I would like to keep my
> system (Fedora 12) consistent and I don't want to have any parts built
> outside of rpm. I would like to contribute/help for RedHat's bz #508801
> resolution, but I need some directions.
>
>    

git clone git://git.kernel.org/pub/scm/virt/kvm/kvm-kmod.git

git submodule init
git submodule update
./configure
make sync
make
make install

> Is kvm.git whole Linux kernel

Yes.  kvm-kmod downloads it (via git submodule) and extracts the kvm 
bits (via make sync).

-- 
error compiling committee.c: too many arguments to function


      parent reply	other threads:[~2009-12-22  8:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 23:10 Qemu vs Qemu-KVM Mikolaj Kucharski
2009-12-21  7:22 ` Gleb Natapov
2009-12-21  9:33   ` Avi Kivity
2009-12-21 22:21   ` Mikolaj Kucharski
2009-12-22  7:15     ` Gleb Natapov
2009-12-22 14:20       ` Gleb Natapov
2009-12-22  8:53     ` Avi Kivity [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=4B30890E.5090705@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mikolaj@kucharski.name \
    /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