On Thu, Sep 08, 2011 at 02:12:27PM -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Sep 08, 2011 at 01:32:12PM -0400, Konrad Rzeszutek Wilk wrote:
> > On Wed, Sep 07, 2011 at 09:50:47AM -0400, Konrad Rzeszutek Wilk wrote:
> > > On Wed, Aug 31, 2011 at 03:07:22PM +0200, Andreas Olsowski wrote:
> > > > A little update, i now have all machines running on xen-4.1-testing
> > > > with xen/stable-2.6.32.x
> > > > That gave me the possiblity for additional tests.
> > > >
> > > > (I also tested xm/xend in addtion to xl/libxl, to make sure its not
> > > > a xl/libxl problem.)
> > > >
> > > > I took the liberty to create a new test result matrix that should
> > > > provide a better overview (in case someone else wants to get the
> > > > whole picture):
> > >
> > > So.. I don't think the issue I am seeing is exactly the same. This is
> > > what 'xl' gives me:
> >
> > Scratch that. I am seeing the error below if I:
> >
> > 1) Create guest on 4GB machine
> > 2) Migrate it to the 32GB box (guest still works)
> > 3) Migrate it to the 4GB box (guest dies - error below shows up and
> > guest is dead).
> >
> > With 3.1-rc5 virgin - both Dom0 and DomU. Also Xen 4.1-testing on top of
> > this.
> >
> > I tried just creating a guest on the 32GB and migrating it - and while
> > it did migrate it was stuck in a hypercall_page call or crashed later on.
> >
> > Andreas,
> >
> > Thanks for reporting this.
>
> Oh wait. At some point you said that 2.6.32.43 worked for you.. Is that still
> the case?
Can you please try one thing for me - can you make sure the boxes have exact
same
amount of memory? You can do 'mem=X' on the Xen hypervisor line to set that.
I think the problem you are running into is that you are migrating between
different CPU families... Is the /proc/cpuinfo drastically different between
the boxes?
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home