From: Olaf Hering <olaf@aepfle.de>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xen.org
Subject: Re: HVM guests hanging in hpet_rtc_interrupt
Date: Mon, 4 Feb 2013 15:25:40 +0100 [thread overview]
Message-ID: <20130204142540.GA17824@aepfle.de> (raw)
In-Reply-To: <510FA33F02000078000BB71D@nat28.tlf.novell.com>
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
next prev parent reply other threads:[~2013-02-04 14:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 17:07 HVM guests hanging in hpet_rtc_interrupt Olaf Hering
2013-01-31 17:12 ` Ian Campbell
2013-01-31 18:09 ` Olaf Hering
2013-01-31 18:46 ` Olaf Hering
2013-02-04 8:21 ` Jan Beulich
2013-02-04 8:47 ` Jan Beulich
2013-02-04 9:49 ` Olaf Hering
2013-02-04 14:03 ` Olaf Hering
2013-02-04 14:13 ` Jan Beulich
2013-02-04 11:02 ` Jan Beulich
2013-02-04 14:25 ` Olaf Hering [this message]
2013-02-04 14:44 ` Olaf Hering
2013-02-04 15:27 ` Olaf Hering
2013-02-04 15:43 ` Ian Campbell
2013-02-04 15:50 ` Olaf Hering
2013-02-04 15:56 ` Ian Campbell
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=20130204142540.GA17824@aepfle.de \
--to=olaf@aepfle.de \
--cc=JBeulich@suse.com \
--cc=xen-devel@lists.xen.org \
/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.