http://bugzilla.novell.com/show_bug.cgi?id=490770 User pgnet.trash@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=490770#c3 --- Comment #3 from pgnet _ <pgnet.trash@gmail.com> 2009-04-01 11:50:22 MDT --- (In reply to comment #2)

The crashes in the description have nothing in common with the crash in the DomU log - please clarify what the deal is here.

sorry, there's nothing i can clarify -- i simply shared what i did, and the output. perhaps more of the info your ruest below will clarify ...

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.

will do.

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.

by 'native kernel' here, do you mean booting _not_ to kernel-xen. but kernel-default?

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).

hm. ok. unfortunately it's been a long slog already getting bugs fixed to support these drives attached via sata_sil24 supported on -default & Dom0.

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.

i'll get started on more verbose logs ... thanks. -- 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.