2010/3/30 Chris Wright <chrisw@xxxxxxxxxx>: > * Alexander Graf (agraf@xxxxxxx) wrote: >> On 30.03.2010, at 01:00, Kenni Lund wrote: >> >> > 2010/3/29 Alexander Graf <agraf@xxxxxxx>: >> >> >> >> On 29.03.2010, at 19:23, Kenni Lund wrote: >> >> >> >>>>> 2010/1/9 Alexander Graf <agraf@xxxxxxx>: >> >>>>>> >> >>>>>> On 09.01.2010, at 03:45, Ryan C. Underwood wrote: >> >>>>>> >> >>>>>>> >> >>>>>>> I have a multifunction PCI device that I'd like to pass through to KVM. >> >>>>>>> In order to do that, I'm reading that the PCI memory region must be >> >>>>>>> 4K-page >> >>>>>>> aligned and the PCI memory resources itself must also be exact multiples >> >>>>>>> of 4K pages. >> >>>>>>> >> >>>>>>> I have added the following on my kernel command line: >> >>>>>>> reassign_resources reassigndev=08:09.0,08:09.1,08:09.2,08:09.3,08:09.4 >> >>>>>>> >> >>>>>>> But I don't know if it has any effect. The resources are still not >> >>>>>>> sized in 4K pages. Also, this seems to screw up the last device. >> >>>>>> >> >>>>>> I submitted a patch to qemu-kvm recently that got rid of that limitation. >> >>>>>> Please try out if the current git head works for you. >> >>>>>> >> >>>>>> Alex-- >> >>>>> >> >>>>> I just upgraded to kernel 2.6.32.10 with qemu-kvm 0.12.3 and I still >> >>>>> get the following error when trying to pass through a dedicated PCI >> >>>>> USB card: >> >>>>> >> >>>>> "Unable to assign device: PCI region 0 at address 0xe9403000 has size >> >>>>> 0x100, which is not a multiple of 4K >> >>>>> Error initializing device pci-assign" >> >>>>> >> >>>>> Didn't the above patch make it into qemu-kvm? I don't know why, but I >> >>>>> was under the impression that this was fixed when I upgraded to >> >>>>> qemu-kvm 0.12.3. >> >>>>> >> >>>> It's only in qemu-kvm.git. Maybe it should go into qemu-kvm-0.12.4 if there >> >>>> is one >> >>> >> >>> That would be highly appriciated...with the current USB support in >> >>> QEMU, PCI passthrough is the only way to get USB 2.0 support. I've >> >>> bought two dedicated PCI USB cards for this, but none of them works >> >>> due to the above limitation. >> >>> >> >>> Perhaps a developer can comment on this? Are there any plans on >> >>> including this patch in the stable releases in the near future? >> >> >> >> Please first try out to build the current git snapshot of qemu-kvm. If it works properly for you then I agree that we should take this into 0.12-stable. >> >> >> >> I wrote the support for a card that still didn't work even with this patch. So having someone say it makes things work for him is definitely a must :-). >> > >> > Sure, I have compiled the current git snapshot and performed some >> > tests...It's at least mostly working, so I'm a bit unsure if this is a >> > bug related to this or to something else. >> >> Chris, any idea on this? Looks like something's going wrong with function assignment. > > Hmm, one thing that sticks out to me is the debug port. Kenni, can you > post full dmesg on both host and guest, nothing is obviously broken (and > in fact the guest should never "see" the debug port). > Uploaded here: Client dmesg: http://pastebin.com/uNG4QK5j Host dmesg: http://pastebin.com/jZu3WKZW I just verified it and I do get the call trace in the host (which disables IRQ 19, used by the PCI USB card), exactly at the same second I ask the DVB-T tuner to view a channel in the guest. Thanks.. Best Regards Kenni Lund -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
