[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] out-of-memory problem when restoring ballooneddomains



No, unfortunately that didn't help.  (I was already running
2.0-testing from this morning PST, so I guess I already had most
(all?) of the patches, but I guess it was worth a try...)

Perhaps it is not related to memory... When I try
to restore only t1 and t3, they also fail with 'Error: 1'

Perhaps it is because t1 and t3 both did run on CPU 0 while
t2 did run on CPU 1 (at least it says '(cpu 0)' in {t1,t3}.saved.

It was only a guess that it was memory related.  Could there
be some other explanation - CPU related?

Perhaps it is useful to see the trace from xend...
I started it with /usr/sbin/xend trace_start and
I cut out the relevant part (I think), where xend starts
to process the request to restore t3.saved.  It
eventually ends up at _perform_err which logs the
error I mentioned earlier: 

[2005-03-10 12:43:44 xend] ERROR (SrvBase:162) op=restore: 1
None


Thanks again for looking into this! 

/Lars





On Thu, 2005-03-10 at 20:58 +0000, Ian Pratt wrote:
> Please can you try this out with 2.0.5 -- there have been a bunch of
> fixes in these general areas, though I'm not sure it'll be fixed for
> you.
> Ian 
> 
> > -----Original Message-----
> > From: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx 
> > [mailto:xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of 
> > Lars Rasmusson
> > Sent: 10 March 2005 20:54
> > To: Keir Fraser
> > Cc: xen-devel; Mark Williamson
> > Subject: Re: [Xen-devel] out-of-memory problem when restoring 
> > ballooneddomains
> > 
> > The /var/log/xend.log gets these three lines added when I 
> > have restored
> > t3 and t2, and try to restore t1
> > 
> > [2005-03-10 12:43:43 xend] INFO (XendMigrate:413) restore BEGIN:
> > ['restore', ['id', '2'], ['file', '/home/testlars/t1.saved']]
> > [2005-03-10 12:43:44 xend] ERROR (SrvBase:162) op=restore: 1
> > None
> > 
> > Nothing is written into /var/log/xend-debug.log
> > 
> > /Lars
> > 
> > 
> > On Thu, 2005-03-10 at 19:44 +0000, Keir Fraser wrote:
> > > On 10 Mar 2005, at 18:54, Lars Rasmusson wrote:
> > > 
> > > > So all domains have 128 Mb, and xen seems to count the 
> > memory fine...
> > > >
> > > > (FYI I'm using xen-2.0-testing, checked out from bitkeeper this 
> > > > morning)
> > > 
> > > Very odd. Does /var/xen/xend-debug.log contain anything interesting?
> > > We'll have to see if we can reproduce this -- my guess 
> > would be a tools 
> > > hiccup as xen seems to be dealing with the scenario as expected.
> > > 
> > >   -- Keir
> > > 
> > 
> > 
> > -------------------------------------------------------
> > SF email is sponsored by - The IT Product Guide
> > Read honest & candid reviews on hundreds of IT Products from 
> > real users.
> > Discover which products truly live up to the hype. Start reading now.
> > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > https://lists.sourceforge.net/lists/listinfo/xen-devel
> > 

Attachment: xend.trace.txt
Description: Text document


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.