Proxmox 1.1 / KVM-83 and PCI Passthrough

But even with skystar 2 (using the args: option) i can't get any tv channels. Scan does not find anything, the card simply does not get signal, though it is detected correctly:

You previously wrote that it works when you use '-pcidevice host=01:00.0'? So what do you do exactly to
get the cards working?
 
Sorry, maybe i did not describe it correctly.

The passtrough works only with the Skystar 2. The card is detected in the Guest, but it doesn't get signal. I use the -pcidevice host=... option for this.

hostpci does not work completely.
 
If you want to say it so - yes. But i can passtrough a NIC and it works (getting ip etc). So the Passthrough option can work. Plus i have read some postst from guys in a german Ubuntu board, that they have gotten a Signal with qemu + libvirtd.. But they are afk atm :D
 
If you want to say it so - yes. But i can passtrough a NIC and it works (getting ip etc). So the Passthrough option can work.

If you have a working card, use that and test if it work with our 'hostpci' setting. If it does not work, try to debug what we do wrong.

I can't do that, because I never got anything working with passthrough.
 
hi!

i had the same problem on esxi with a different tv card. i enabled passthrough for my guest, but i didn't get a signal.

but there was a option called msiDisabled = true. after that the card was fully working (with signal).
i think it hat something to do with irq sharing or something like that.

is there such a setting in proxmox? if yes, could you try it?
 
There is a kernel option "nomsi" but i dont know if that is the right option.

Searching kvm, qm, qemu man pages, i couldn't find anything about msi..
 
yeah i think thats the right option.
but i think you have to create the vm from scratch after that
 
Last edited by a moderator:
Hm why do you think so? I mean it's "only" a Kernel parameter, or do you mean nomsi at the host?
 
I recently installed Proxmox 1.5 along with the 2.6.32-1-pve kernel planning to use PCI passthrough to my dvb-c tuner.

My findings seem similar to those of jakap.

If I add

Code:
args:  -pcidevice host=03:06.0

to conf the KVM boots up and the device is seen inside. However I have not been able to scan.

If I add
Code:
hostpci: 03:06.0
the KVM doesn't start, nothing special in the logs.


I am not really sure about the host driver unloading bit though. I have no special driver installed for the tuner on the host. By default there is pci-stub driver loaded on host kernel.

I have tried having pci-stub unloaded and loaded using both -pcidevice and hostpci:

With -pcidevice there is no noticeable differnce, KVM boots , still not able to scan.

With hostpci: if pci-stub is unloaded the kvm stops with:

Code:
Apr 4  16:06:37     qm    24143     VM 102 start
Apr 4 16:06:37      kernel         pci-stub 0000:03:06.0: claimed by stub
Apr 4 16:06:37      kernel         pci-stub 0000:03:06.0: claimed by stub
Apr 4  16:06:37     pvedaemon    24142     VM 102 start failed - Transport  endpoint is not connected

and after the failed start of the KVM the host kernel will autoload pci-stub by itself.

I could really need some pointer in how to troubleshoot this further? :cool:
 
I could really need some pointer in how to troubleshoot this further? :cool:

We never got anything working with pci passthrough. But you can join the kvm user list and and try to find out the correct parameters for kvm. If you can get it work with plain kvm, we can try to include it into 'qm'.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!