"dev001x" 02/03/11 9:34 PM >>> it would be helpful for me to get some clarity as to WHY our kernel config has "CONFIG_XEN_PCIDEV_BACKEND=m" and "CONFIG_XEN_PCIDEV_BACKEND_VPCI=y". i.e., why not BOTH as module or BOTH compiled in?
The latter can't be =m (it's really a choice which model pciback is to use).
there seems to be some consistent opinion @ xen-devel that compiled-in is arguably 'better' ...
... with whatever 'better' here means.
in any case, i've found the problems, have a workaound, and will endeavor to write them up in a bugreport. knowing a bit more abt kernel config choice(s) will be helpful.
This coming up again and again, my answer is always the same: Whatever can be a module and isn't going to be used on the *vast* majority of systems, should be a module. Jan -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org