LKML Archive on
help / color / mirror / Atom feed
From: Anthony Liguori <>
To: Stephen Hemminger <>
Cc: Avi Kivity <>,,
Subject: Re: [kvm-devel] KVM binary incompatiablity
Date: Fri, 08 Feb 2008 16:22:12 -0600	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20080208113236.55b2ead1@extreme>

Stephen Hemminger wrote:
> I notice that recent KVM is incompatiable with older versions.
> Using a KVM image created on 2.6.24 will crash on 2.6.25 (or
> vice versa). It appears that Ubuntu Hardy has incorporated the 2.6.25
> update even though it claims to be 2.6.24.

This isn't intentional.  What is the guest and how does it crash?

I've been using the same image for most of KVM's development life cycle 
without having issues.


Anthony Liguori

> This is reproducible on Intel (64bit) kernel.  Was this intentional?
> is it documented? 
> -------------------------------------------------------------------------
> This email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> _______________________________________________
> kvm-devel mailing list

  reply	other threads:[~2008-02-08 22:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 19:32 Stephen Hemminger
2008-02-08 22:22 ` Anthony Liguori [this message]
2008-02-09  0:04   ` [kvm-devel] " Stephen Hemminger

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [kvm-devel] KVM binary incompatiablity' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).