unsupported configuration: host doesn't support passthrough of host PCI devices
agonzalezrh opened this issue · 5 comments
Version: 4.7.0-202104142050.p0 provided by Red Hat
From inside the baremetal node, the IOMMU is enabled
[root@provision ocpinstall]# oc debug node/worker-3
Starting pod/worker-3-debug ...
To use host binaries, run chroot /host
Pod IP: 10.20.0.203
If you don't see a command prompt, try pressing enter.
sh-4.4# chroot /host
QEMU: Checking for device assignment IOMMU support : PASS
QEMU: Checking if IOMMU is enabled by kernel : PASS
sh-4.4# /root/virt-host-validate |grep IOMMU
The problem is from the pod
sh-4.4# virt-host-validate |grep IOMMU
QEMU: Checking for device assignment IOMMU support : WARN (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)
strace shows is trying to access /sys/firmware
access("/sys/firmware/acpi/tables/DMAR", F_OK) = -1 ENOENT (No such file or directory)
write(1, " QEMU: Checking for device assignment IOMMU support : \33[33mWARN\33[0m (No ACPI DMAR table found, IOMMU either disabled in BIOS or not supported by this hardware platform)\n", 194 QEMU: Checking for device assignment IOMMU support
The title of the issue comes from the pod log
Note: I'm using the unsupported card (Intel Corporation Ethernet Controller 10-Gigabit X540-AT2), but the VFs are created properly, the only issue is running the VM
it works using
deviceType: vfio-pci
can anyone give me more details why netdevice (default) is not working?
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
/remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen.
Mark the issue as fresh by commenting/remove-lifecycle rotten.
Exclude this issue from closing again by commenting/lifecycle frozen./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.