https://bugzilla.novell.com/show_bug.cgi?id=425056
User jbeulich@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=425056#c9
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |hwit@a-domani.nl
--- Comment #9 from Jan Beulich 2008-10-01 00:28:32 MDT ---
If I am getting it right, Dom0, with the Oopses gone, is not directly
experiencing any problems anymore. If so, providing Dom0 logs isn't very useful
I'm afraid - we'd rather need the DomU logs.
Apart from that, assuming we indeed deal with a Xen problem here (and not with
an NFS one, which seem more likely to me at this point - but I assume there's
no way to know by experiment, i.e. set up the whole thing with multiple
machines), we'd still need the hypervisor messages (with "loglvl=all
guest_loglvl=all" added to the Xen command line) to be certain there are no
anomalies found by Xen.
Further, although (if the first statement if correct) Dom0 now seems to be
running fine for itself, we'd generally recommend not to run any services (in
this case, the NFS server) in Dom0.
Finally, please clarify whether it's just one of the DomU-s that's suffering
from the problem, or multiple/all of them. If just one, we'd want to understand
all the factors that distinguish it from the others. And please also clarify
whether it's just NFS hanging up in the DomU, the whole network, or the whole
VM.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.