From: Stephen Hemminger <shemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
To: Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: KVM binary incompatiablity
Date: Fri, 8 Feb 2008 16:04:27 -0800 [thread overview]
Message-ID: <20080208160427.7594c837@extreme> (raw)
In-Reply-To: <47ACD614.2080000-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
On Fri, 08 Feb 2008 16:22:12 -0600
Anthony Liguori <anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org> wrote:
> 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.
>
> Regards,
>
> Anthony Liguori
>
I'll see if I can get a backtrace, it isn't reliably reproducible.
--
Stephen Hemminger <stephen.hemminger-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
-------------------------------------------------------------------------
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/
prev parent reply other threads:[~2008-02-09 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 19:32 KVM binary incompatiablity Stephen Hemminger
2008-02-08 22:22 ` [kvm-devel] " Anthony Liguori
[not found] ` <47ACD614.2080000-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2008-02-09 0:04 ` Stephen Hemminger [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=20080208160427.7594c837@extreme \
--to=shemminger-ztmgi6mnkb3qt0dzr+alfa@public.gmane.org \
--cc=anthony-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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