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#c13
pgnet _
So from the serial log it is clear that this is the same box that earlier did have problems even in native using sata_sil24. The kernel workaround to address this requires that the kernel recognizes the particular PCI bridge used on your system. Obviously, the DomU cannot know this because it doesn't see that bridge device. Hence you have to force the same behavior by a (DomU) kernel command line parameter (which, as much as the workaround, is functional only in recent kernels - both patches were checked in at the same time): iommu=nodac.
updating to latest kernels on both Dom0, uname -ri 2.6.27.21-27-xen x86_64 & DomU (booted w/o pasthrough ...) ... Welcome to openSUSE 11.1 - Kernel 2.6.27.21-27-xen (xvc0). ... uname -ri 2.6.27.21-27-xen x86_64 then, in DomU's .cfg, --- #pci = [ '04:07.0', '04:08.0' ] --- extra = 'textmode=1 xencons=xvc0' +++ pci = [ '04:07.0', '04:08.0' ] +++ extra = 'textmode=1 xencons=xvc0 iommu=nodac' @ DomU reboot --> crash ... Fatal DMA error! Please use 'swiotlb=force' ------------[ cut here ]------------ kernel BUG at arch/x86/kernel/pci-nommu-xen.c:39! invalid opcode: 0000 [1] SMP ... adding in DomU's .cfg, --- extra = 'textmode=1 xencons=xvc0 iommu=nodac' +++ extra = 'textmode=1 xencons=xvc0 iommu=nodac swiotlb=force' then, @ DomU boot, success !! uname -ri 2.6.27.21-27-xen x86_64 lspci 00:00.0 RAID bus controller: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller (rev 02) 00:01.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0) fdisk -l | grep GB Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/sda: 1000.2 GB, 1000204886016 bytes Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes so the external disks, attached at passed-thru SATA card, are now "seen" by DomU (not yet stress-tested ...) questions: is the req't for 'swiotlb=force' simply an expected cmd line addition (as above), or a bug? is 'swiotlb=force' appropriate, or should a specific value (e.g., =128 ...) be used? -- 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.