public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: KVM list <kvm@vger.kernel.org>
Subject: Re: [ANNOUNCE] kvm-85 release
Date: Mon, 27 Apr 2009 17:58:06 +0300	[thread overview]
Message-ID: <49F5C7FE.40300@redhat.com> (raw)
In-Reply-To: <1240843319.12942.45.camel@blaa>

Mark McLoughlin wrote:
> Hi Avi,
>
> On Tue, 2009-04-21 at 12:32 +0300, Avi Kivity wrote:
>
>   
>> Again a long delayed release; I'll try to reduce the lag between
>> releases.
>>
>> kvm-85 comes in two flavors: the traditional kernel+qemu package 
>> (kvm-85.tar.gz), as well as separate qemu (qemu-kvm-devel-85.tar.gz) 
>>     
>
> I packaged this in Fedora 12 as qemu-0.10.50 and noticed a couple of
> small problems with the qemu-kvm-devel tarball:
>
>   - No kernel/include/asm symlink, so it was building with the system 
>     headers and not finding e.g. KVM_FEATURE_CLOCKSOURCE
>   

This is already fixed in the new repository.

>   - An empty kvm-85 dir
>   

I need to rewrite my release script anyway.

> And for anyone else doing similar packaging, I've also:
>
>   - Disabled pwritev() support until glibc stops writing random junk. 
>     See https://bugzilla.redhat.com/497429
>
>   - Added Pauline's boot=on -help string patch
>
>   - Fixed the arm target build with the patch I just sent
>   

I hope to release kvm-86 soon.

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


      parent reply	other threads:[~2009-04-27 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-21  9:32 [ANNOUNCE] kvm-85 release Avi Kivity
2009-04-27 14:41 ` Mark McLoughlin
2009-04-27 14:45   ` Alexander Graf
2009-04-27 14:50     ` Christoph Hellwig
2009-04-27 15:34       ` Mark McLoughlin
2009-04-27 14:58   ` 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=49F5C7FE.40300@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox