http://bugzilla.novell.com/show_bug.cgi?id=490770
User jbeulich@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=490770#c16
Jan Beulich
is the req't for 'swiotlb=force' simply an expected cmd line addition (as above), or a bug?
This is the obvious consequence of using iommu=nodac on a system with memory above the 4Gb address boundary.
is 'swiotlb=force' appropriate, or should a specific value (e.g., =128 ...) be used?
Specifying just a number won't do anything in a DomU; if the default of 64Mb doesn't suit you, then you could use e.g. "swiotlb=128,force".
Apr 19 10:50:32 server kernel: pciback 0000:04:08.0: Driver tried to write to a read-only configuration space field at offset 0x40, size 4. This may be harmless, but if you have problems with your device: Apr 19 10:50:32 server kernel: 1) see permissive attribute in sysfs Apr 19 10:50:32 server kernel: 2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.
noting,
"... tried to write to a read-only configuration space field ..."
Just do as you're told - if you're having problems, enable permissive mode on this device, and possibly report the device details.
-> PCI: Fatal: No config space access function found PCI: setting up Xen PCI frontend stub ...
unclear if it's related to this current issue, or something new ...
This is going to be that way in all DomU-s. It's perhaps a little confusing, but no reason to worry. With that, is the problem reported here resolved? -- 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.