Red Hat Bugzilla – Bug 241714
64bit Xen DomU goes 100% CPU busy
Last modified: 2008-01-08 08:14:43 EST
Description of problem:
Version-Release number of selected component (if applicable):
Running either hts or applying updates causes DomU to go 100% CPU busy and the
console is unresponsive.
Steps to Reproduce:
1. Create 64 bit Xen guest (i.e. use steps from hts)
2. Run hts certify, or yum -y update
3. DomU will become 100% CPU bust and unresponsive
DomU will become 100% CPU bust and unresponsive
Completion of tests/updates.
System works OK in 32 bit testing.
H/W Fujitsu S7110 Notebook
2 GB and 4 GB RAM tested
Intel T7200 Core 2 Duo
Reran certification test on notebook. DomU froze after 15 minutes.
I had an iostat and top running in terminals, and both stopped responding. No
useful information on either.
No messages in /var/log/messages
I will be happy to run any monitor script that you provide.
Performing hardware cert on another Fujitsu notebook, the E8410:
T7300 Intel Core 2 Duo
Same issue, DomU freezes during certification with CPU at 100% busy
32 bit OK, 64 bit freezes.
System was updated to latest available updates on 26JUN07
Created attachment 158008 [details]
xen logs -- wrong logs -- PLEASE DELETE
Here is a tgz containing the xen logs, the DomU guest always froze/hung
Created attachment 158014 [details]
xen logs - 64 bit
Here are the xen logs from the failed attempts at h/w certification under RHEL5
I believe that you are attempting to use a RHEL-5 Fully virtualized guest; is
that correct? If so, I think this is the same issue as BZ 234160. In that
case, this issue should be fixed by 5.1. Can you please confirm that this is
indeed what you are attempting?
Yes, my issue appears to be a duplicate of 234160.
OK, thanks for clarifying. I'm going to close this out as a duplicate of that bug.
*** This bug has been marked as a duplicate of 234160 ***
Using the RHEL5.1 beta, Andy Prowse reports.....
On Mon, 2007-07-30 at 20:52 -0400, Andy Prowse wrote:
> I have had the 64 bit DomU up for 8 hours so far, and have run the hts
> test in it OK. Looks like the issue I was experiencing with RHEL5
> x86_64 is fixed.