From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Levon Subject: Re: SHUTDOWN_crash and vcpu deferrals Date: Mon, 23 Feb 2009 11:54:09 -0500 Message-ID: <20090223165409.GC13663@movementarian.org> References: <20090220210155.GA5872@movementarian.org> <20090220220305.GB5872@movementarian.org> <18850.54270.292354.695330@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <18850.54270.292354.695330@mariner.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Jackson Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On Mon, Feb 23, 2009 at 04:51:10PM +0000, Ian Jackson wrote: > > (The comment being completely incorrect), but then the crash doesn't > > work because of the bug I pointed out. > > I wrote that comment. I haven't been following this bit of xend. Do > you mean that nowadays if you say > on_crash = 'restart' > and the domain immediately crashes on boot, you don't get an infinite > restart loop ? One of the most common causes of qemu `crashing' is AFAIK this has been the case since forever: rst = self._readVm('xend/previous_restart_time') if rst: rst = float(rst) timeout = now - rst if timeout < MINIMUM_RESTART_TIME: log.error( 'VM %s restarting too fast (%f seconds since the last ' 'restart). Refusing to restart to avoid loops.', self.info['name_label'], timeout) self.destroy() return self._writeVm('xend/previous_restart_time', str(now)) This is from 3.1.4. Perhaps it was broken when you tried it, but it certainly seems to do its intended job on 3.3.2pre for me. regards, john