public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Alexey Eremenko <al4321@gmail.com>
Cc: kvm-devel@lists.sourceforge.net
Subject: Re: [ANNOUNCE] kvm-guest-drivers-linux-1
Date: Thu, 06 Mar 2008 09:59:03 -0600	[thread overview]
Message-ID: <47D014C7.9080908@codemonkey.ws> (raw)
In-Reply-To: <7fac565a0803060212k522f853er2c35d3530ce876bb@mail.gmail.com>

Alexey Eremenko wrote:
> Very nice !
>
> 1. How about releasing those in ISO format instead (or in addition
> to...) tarballs?
>   

It's not a bad idea.  What we really need is for people to submit 
spec/deb files for older distros.  Then it's a matter of compiling those 
RPMs/debs and putting them on an ISO.

> 2. I have a problem compiling it.
> "make sync LINUX=." fails.
>
> I have read the README:
> "Where /path/to/kernel is the path to a recent kernel tree containing virtio
> drivers.  At the moment, this must be Rusty Russell's virtio patch queue[1]
> applied on top of Linus' git tree[2]."
>   

The released tarball has already done a "make sync".  The README is out 
of date, it should work against Linus' latest git tree.

> What does it means ? That I need kernel-2.6.25 sources?
> Well, since we release a tarball, can we include part of 2.6.25 ?
> It is a bit unclear, what must I do to compile it.
>   

It should just be a matter of doing a make && make install in the guest.

Regards,

Anthony Liguori



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  reply	other threads:[~2008-03-06 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  9:26 [ANNOUNCE] kvm-guest-drivers-linux-1 Avi Kivity
     [not found] ` <7fac565a0803060148k418756f1sb558993f9a5aad1c@mail.gmail.com>
2008-03-06 10:12   ` Alexey Eremenko
2008-03-06 15:59     ` Anthony Liguori [this message]
2008-03-06 10:31 ` Jun Koi
2008-03-06 11:08   ` Thomas Mueller
2008-03-06 14:29   ` Balaji Rao
2008-03-06 16:00     ` Anthony Liguori
2008-03-06 22:19 ` Iain Paton
2008-03-07  2:52   ` Paul Collins
2008-03-16 14:47     ` 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=47D014C7.9080908@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=al4321@gmail.com \
    --cc=kvm-devel@lists.sourceforge.net \
    /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