search for: ray_col

2005/9/21, Cole, Ray <Ray_Cole@bmc.com>: > I saw something similar running Xen 2.0-testing on a machine with a P4. I''d been running on it just fine, but I decided to see how performance would be with and without hyperthreading enabled. So I went into the system setup and disabled hyperthreading. Domain 0 start...

I''ve seen this happen before, not sure why. I changed ''phy:'' to ''file:'' and it worked. I later rebooted and ''phy:'' worked again. So you might try ''file:'' rather than ''phy:''. -- Ray -----Original Message----- From: xen-users-bounces@lists.xensource.com

I had this exact same problem with 2.0.7. I had done a little investigation and found scheduled_work gets called to schedule the shutdown in the user domain kernel, but the shutdown work that gets scheduled never actually gets called. I''m glad someone else is seeing this same problem now :-) Like you, it worked a number of times in a row, then would fail, and it didn''t seem to

Just gave 3.0 a spin. Had been running 2.0.7 for the past 3 months or so without problems (aside from intermittent failure during live migration). Anyway, 3.0 seems to have an issue with my machine. It starts up the 4 domains that I''ve got defined (was running 6 user domains with 2.0.7, but two of those were running 2.4 kernels which I can''t seem to build with Xen 3.0 yet, and