https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
h
I'm not certain, but perhaps the device is claimed by the 
qla2xxx
driver, so the 
vfio
driver won't take it over. Perhaps unload the module first?
f
I think the issue may be that Harvester is scheduling based mainly on PCI type/resource pool rather than the exact PCI device. If 2 VMs start at nearly the same time with the same PCI type, Harvester may still see the PCI as available before the first allocation fully syncs, so both can try to claim it. Then one later fails with VFIO 
Device or resource busy
. So this may be a sync/race condition rather than the PCI actually being free. but I would to be sure that the actual behavior of PCI in harvester
t
I have been hunting down other PCI issues. these commands have helped
Copy code
kubectl get <http://pcidevices.devices.harvesterhci.io|pcidevices.devices.harvesterhci.io>
kubectl get <http://pcideviceclaims.devices.harvesterhci.io|pcideviceclaims.devices.harvesterhci.io>
f
the issue is that I want to pin a specific PCI device to a VM. but harvester is using the annotation DeviceAllocationDetails to set the PCI device. even if I select a specific PCI it will change it with another one that match the same PCI type. I would like to know if it exist a way to pin a PCI device and not let him change it overtime
t
harvester should handle that without an issue.
g
that is true.. we have plans to fix this
i will need to find the issue.. but it involves changing the behaviour of the pcidevice controller and how the plugin advertises it
✅ 2
🙏 1
sorry i misread this as related to device allocation
ideally when pcideviceclaim is ready.. the device should be bound to vfio and you should not see the busy message
if there is a support bundle that would help us see what is going on
h
@fierce-zoo-18185 if you have a bundle, it would be great!
f
Thans for the support really appreciate it. @happy-cat-90847 I have sent you the bundle
@great-bear-19718 our actual PCI do not have the SRIOV hardware reference. does getting PCI with it will solve the issue ?
Let me know if you want me to write a ticket about it
33 Views
Open in Slack
PreviousNext
Powered by