From: Kip Macy <kip.macy@gmail.com>
To: Teemu Koponen <tkoponen@iki.fi>
Cc: xen-devel@lists.xensource.com
Subject: Re: Re: Linux-XenU kernel panic in allocs after live migration
Date: Wed, 11 May 2005 10:51:51 -0700 [thread overview]
Message-ID: <b1fa291705051110517b319627@mail.gmail.com> (raw)
In-Reply-To: <4a0e51347de5615e6834feeb7ab08655@iki.fi>
Based on what you've reported it should work. I know someone who
should be testing this today.
-Kip
> I wonder how sensitive Linux kernel is to underlying CPU changes, even
> though it is compiled to support only of a certain type CPU? In this
> specific case I'm trying to migrate between Athlon XP and Pentium-M
> domain-0 hosts, with a Linux domain-U kernel that is compiled to
> support Pentium-MMX class processor. Is this really a dead-end
> (translation: SUE) or should it work as I initially assumed?
>
> Teemu
>
> --
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2005-05-11 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 21:04 Linux-XenU kernel panic in allocs after live migration Teemu Koponen
2005-05-11 15:31 ` Teemu Koponen
2005-05-11 17:51 ` Kip Macy [this message]
2005-05-12 11:22 ` Teemu Koponen
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=b1fa291705051110517b319627@mail.gmail.com \
--to=kip.macy@gmail.com \
--cc=tkoponen@iki.fi \
--cc=xen-devel@lists.xensource.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.