From: Avi Kivity <avi@redhat.com>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, KVM list <kvm@vger.kernel.org>
Subject: Re: kvm-kmod.git
Date: Mon, 01 Jun 2009 21:19:55 +0300 [thread overview]
Message-ID: <4A241BCB.8090505@redhat.com> (raw)
In-Reply-To: <20090601181559.GC6411@us.ibm.com>
Ryan Harper wrote:
> % cd kvm
> % git checkout -f 2.6.29-stable origins/maint/2.6.29
> % cd ../kvm-kmod.git
> % ./configure
> % make LINUX=../kvm sync
> ./sync -v kvm-devel -l ../kvm
> Traceback (most recent call last):
> File "./sync", line 207, in <module>
> source_sync(arch)
> File "./sync", line 200, in source_sync
> hack(T, arch, i)
> File "./sync", line 123, in hack
> _hack(T + '/' + file, arch)
> File "./sync", line 114, in _hack
> data = file(fname).read()
> IOError: [Errno 2] No such file or directory: 'source/timer.c'
> make: *** [sync] Error 1
>
> kvm.git on branch kvm-85:
> % make LINUX=/home/rharper/work/git/kvm sync
> ./sync -v kvm-devel -l /home/rharper/work/git/kvm
> Traceback (most recent call last):
> File "./sync", line 207, in <module>
> source_sync(arch)
> File "./sync", line 200, in source_sync
> hack(T, arch, i)
> File "./sync", line 123, in hack
> _hack(T + '/' + file, arch)
> File "./sync", line 114, in _hack
> data = file(fname).read()
> IOError: [Errno 2] No such file or directory: 'source/eventfd.c'
> make: *** [sync] Error 1
>
> kvm.git on branch kvm-86:
> % make LINUX=/home/rharper/work/git/kvm sync
> ./sync -v kvm-devel -l /home/rharper/work/git/kvm
> Traceback (most recent call last):
> File "./sync", line 207, in <module>
> source_sync(arch)
> File "./sync", line 200, in source_sync
> hack(T, arch, i)
> File "./sync", line 123, in hack
> _hack(T + '/' + file, arch)
> File "./sync", line 114, in _hack
> data = file(fname).read()
> IOError: [Errno 2] No such file or directory: 'source/eventfd.c'
> make: *** [sync] Error 1
>
>
> only branch master seems to work with kvm-kmod
>
>
Well there are differences in the source trees, so they need different
hacking. There is a branch for 2.6.30 in kvm-kmod.git, but 2.6.29 is
slightly different and doesn't have a branch. You can just remove the
offending files from ./sync, there's a good chance it will work.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-06-01 18:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 12:32 kvm-kmod.git Avi Kivity
2009-04-27 14:08 ` kvm-kmod.git Farkas Levente
2009-04-27 14:56 ` kvm-kmod.git Avi Kivity
2009-04-27 17:18 ` kvm-kmod.git Cam Macdonell
2009-04-28 6:39 ` kvm-kmod.git Avi Kivity
2009-04-28 10:20 ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:24 ` kvm-kmod.git Avi Kivity
2009-04-28 10:34 ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 10:53 ` kvm-kmod.git Avi Kivity
2009-04-28 10:53 ` kvm-kmod.git Michael S. Tsirkin
2009-04-28 11:00 ` kvm-kmod.git Avi Kivity
2009-06-01 16:53 ` kvm-kmod.git Ryan Harper
2009-06-01 17:01 ` kvm-kmod.git Avi Kivity
2009-06-01 18:00 ` kvm-kmod.git Ryan Harper
2009-06-01 18:17 ` kvm-kmod.git Avi Kivity
2009-06-01 18:15 ` kvm-kmod.git Ryan Harper
2009-06-01 18:19 ` Avi Kivity [this message]
2009-06-01 18:47 ` kvm-kmod.git Ryan Harper
2009-06-01 19:40 ` kvm-kmod.git Avi Kivity
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=4A241BCB.8090505@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ryanh@us.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.