Am 13.11.2010 12:42, Erik Brakkee wrote: > Jan Kiszka wrote: >> >> What IRQ is the sky2 using when assigned to the host? Is it really a >> shared IRQ (I bet not as it should be using MSI)? >> >> Also, check in the libvirt logs what qemu-kvm reports on the console. >> >> Jan >> >> > The output from 'cat /proc/interrupts' directly after boot is in the > sky2.interrupts. > > The relevant line from the output is > 35: 0 0 0 0 1 > 0 0 0 PCI-MSI-edge sky2@pci:0000:04:00.0 > > So it looks like it is using MSI (although I don't have clue what that > means). MSIs are interrupts that, among other things, are not shared. So you can't run into conflicts. > > The log file for my domain (the name is "other") is attached in "other.log" > In the log file I see: > > No IOMMU found. Unable to assign device "hostdev0" > > Does this mean that I don't have IOMMU available on my laptop? The > output from 'dmesg | grep -i IOMMU' showed that Intel-IOMMI was enabled, > but perhaps that means only that the IOMMU option is activated but not > that it is really functioning. > > It must be either (1) Intel VT-d available on my laptop and there is > some configuration/software problem or (2) The output from dmesg is > misleading. What do you think? Strange, should work. I would suggest to post your full kernel log, maybe there is some enlightening message hidden. I don't think it is a problem of your kernel version, but I'm able to pass through devices on OpenSUSE 11.3 with kernel-desktop-2.6.36-90.1.x86_64 from their kernel repository. Jan
Attachment:
signature.asc
Description: OpenPGP digital signature
