From: Jeremy Fitzhardinge <jeremy@goop.org>
To: xming <xmingske@gmail.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
virtualization@lists.linux-foundation.org
Subject: Re: Xen paravirt frontend block hang
Date: Tue, 18 Mar 2008 09:02:55 -0700 [thread overview]
Message-ID: <47DFE7AF.7090402@goop.org> (raw)
In-Reply-To: <519a8b110802070612j2a1717f3s6aa25eeea8b7d18a@mail.gmail.com>
xming wrote:
> On Feb 7, 2008 5:09 AM, Jeremy Fitzhardinge <jeremy@goop.org> wrote:
>
>> xming wrote:
>>
>>> But I do have one problem after I upgraded to xen 3.2, the 2.6.23.x domU do
>>> not boot any more and 2.6.24 does boot but will hang after cpufreq changes
>>> the frequency.
>>>
>>>
>> Interesting. Do you mean dom0 cpufreq frequency changes will cause the
>> domU to hang?
>>
>> J
>>
>>
>
> Yes, when Dom0 changes freq while domU is doing something will trigger this.
> When using "on demand" will trigger this very eassily.
>
> This is from xm top when a domU hangs:
>
> test32 ------ 4018 98.8 131072 6.4 131072
> 6.4 1 1 4516 50087 1 0 433908 300403
> 3084907223
>
> So it appers to be running (eating CPU) sometimes the state is "r"
> sometimes "-",
> but both console and network are dead.
>
Which version of Xen did you try this on? Some versions of xen-unstable
had horribly broken cpufreq support, in which it was failing to keep
track of cpu speed changes. Current versions should be OK.
J
next prev parent reply other threads:[~2008-03-18 16:02 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-26 19:33 Xen paravirt frontend block hang Christopher S. Aker
2007-12-28 23:14 ` Jeremy Fitzhardinge
2007-12-29 1:12 ` Christopher S. Aker
2007-12-29 6:00 ` Jeremy Fitzhardinge
2008-01-29 0:22 ` Christopher S. Aker
2008-01-29 0:40 ` Jeremy Fitzhardinge
2008-01-29 1:04 ` Christopher S. Aker
2008-02-06 12:37 ` xming
2008-02-07 4:09 ` Jeremy Fitzhardinge
2008-02-07 14:12 ` xming
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-02-28 20:03 ` Jeremy Fitzhardinge
2008-03-18 16:02 ` Jeremy Fitzhardinge [this message]
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-02-28 20:00 ` Jeremy Fitzhardinge
2008-03-02 0:43 ` Christopher S. Aker
2008-03-02 0:43 ` Christopher S. Aker
2008-03-02 15:35 ` Jeremy Fitzhardinge
2008-03-02 15:35 ` Jeremy Fitzhardinge
2008-03-02 15:35 ` Jeremy Fitzhardinge
2008-03-02 16:03 ` Christopher S. Aker
2008-03-02 16:03 ` Christopher S. Aker
2008-03-02 16:03 ` Christopher S. Aker
2008-03-18 16:01 ` [Xen-devel] " Jeremy Fitzhardinge
2008-03-18 16:01 ` Jeremy Fitzhardinge
2008-03-18 16:01 ` Jeremy Fitzhardinge
2008-03-25 1:37 ` [Xen-devel] " Christopher S. Aker
2008-03-25 1:37 ` Christopher S. Aker
2008-03-25 1:37 ` [Xen-devel] " Christopher S. Aker
2008-03-02 0:43 ` Christopher S. Aker
2008-02-28 20:00 ` Jeremy Fitzhardinge
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=47DFE7AF.7090402@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=virtualization@lists.linux-foundation.org \
--cc=xmingske@gmail.com \
/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.