https://bugzilla.novell.com/show_bug.cgi?id=490770
User jbeulich@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=490770#c2
Jan Beulich changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
Info Provider| |pgnet.trash@gmail.com
--- Comment #2 from Jan Beulich 2009-04-01 02:25:58 MDT ---
The crashes in the description have nothing in common with the crash in the
DomU log - please clarify what the deal is here.
Also, we will need the *full* hypervisor/dom0 log (with loglvl=all
guest_loglvl=all added to the Xen command line), not just a fragment from
/var/log/messages. In case you force pciback to load early, I'd also like to
ask to provide us with a native kernel's boot messages in order to identify
where in the loading of the drivers for the passed through devices the problems
begin.
Further, reducing the complexity would certainly help isolating the real issue
here (which seems to start with the drive identification itself having issues,
and perhaps even with the loading of the forcedeth driver), so for debugging
purposes
- passing through any other devices (namely the NIC) should be avoided
- passing through the SATA controller should intially be done without any
complex disk configurations attached, ideally even without any disk that is
needed during boot of the guest (in particular, its root and swap volumes).
Finally, without knowing how much memory the system has (due to the lack of
complete logs), it might be that your setup is simply missing a swiotlb= option
on the DomU kernel command line.
--
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.