http://bugzilla.novell.com/show_bug.cgi?id=559047
http://bugzilla.novell.com/show_bug.cgi?id=559047#c7
Dion Kant changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|g.w.kant@hunenet.nl |
--- Comment #7 from Dion Kant 2009-12-06 09:25:06 UTC ---
1. & 3. Response on "knowing whether with "mem=4G" on the Xen command line the
issue also happens would be useful to know"
Both systems are stable with the mem=4G option. The HP Proliant seems to have
an issue with the cciss driver. In all situations (Xen, Non-Xen) the
performance of the driver is horrible, but that is a different problem. What
may be interesting however is that the error from the cciss driver
(end_request: I/O error, dev cciss/c0d0, sector 0) which is reported by dom0
only occurs from the moment a domU starts running.
2. Response on "If you feel comfortable with re-building the kernel, trying
the debugging patch in that bug would also be very useful"
I did not try to rebuild the kernel with the available patch from <a
href="show_bug.cgi?id=553690" title="NEEDINFO - Xenified kernel crashes during
F12 PV DomU's install packages deployment phase">bug 553690</a>, yet. I will
try this and report if I manage.
4. Response on "For both cases, I'd also like to understand whether the
presence of any DomU is a required prerequisite for the bug to occur."
Running only the dom0 with a lot of I/O seems to be fine. Even in the situation
where, one or more domU's are running (doing almost nothing) with a lot of I/O
on dom0, the bug does not manifest itself. This is true irrespective of
limiting dom0 memory with the dom0_mem parameter.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.