From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olaf Hering Subject: Re: HVM guests hanging in hpet_rtc_interrupt Date: Mon, 4 Feb 2013 15:25:40 +0100 Message-ID: <20130204142540.GA17824@aepfle.de> References: <20130131170718.GB19350@aepfle.de> <510FA33F02000078000BB71D@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <510FA33F02000078000BB71D@nat28.tlf.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Mon, Feb 04, Jan Beulich wrote: > So one question to you would be to clarify which hangs you see > where under what conditions (I'm particularly unclear about the > exact difference in behavior that you observe with xend vs xl). This is a list of dom0+domU combinations with plain 26502:d1bf3b21f783: pvops dom0 + pvops domU - very first domU hangs in hpet_rtc_interrupt - xl migrate domU localhost migration works, but new domU hangs in hpet_rtc_interrupt sles11 dom0 + sles11 domU - guest prints "hpet1: lost 2201 rtc interrupts" - xm migrate works I will retest more combinations with the source state above. Now I tried x86-HVM-RTC.patch, and the result is that the very first pvops guest boots fine, and also two xl migrate to localhost work fine! I will do some more testing to see if its consistent. Olaf