Bug 1269446
Summary: | unable to detach virtual function from the host | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Siddharth Moghe <smoghe> | ||||||||
Component: | libvirt | Assignee: | Laine Stump <laine> | ||||||||
Status: | CLOSED NOTABUG | QA Contact: | Virtualization Bugs <virt-bugs> | ||||||||
Severity: | high | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 7.1 | CC: | alex.williamson, dyuan, honzhang, rbalakri, smoghe | ||||||||
Target Milestone: | rc | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Linux | ||||||||||
Whiteboard: | |||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2015-10-17 05:13:22 UTC | Type: | Bug | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Siddharth Moghe
2015-10-07 11:31:18 UTC
1) What is the output of these two commands: * "ls -l /dev/vfio/vfio" * "ls -l /sys/kernel/iommu_groups/*" 2) does this change if you run "modprobe -i vfio" ? Bug 1044595, which was resolved in time for RHEL7.0 was supposed to make vfio loaded and available by default, yet the error message you're reporting occurs only if either /sys/kernel/iommu_groups is missing or empty, or /dev/vfio/vfio doesn't exist, which I think shouldn't be the case. Another suggestion from someone with a much better memory than me: check the BIOS configuration of the machine to make sure that VT-d is enabled there. VT-d is enabled by default on the HP gen9 machines [root@rhe7 Desktop]# ls -l /dev/vfio/vfio crw-------. 1 root root 10, 196 Oct 7 21:46 /dev/vfio/vfio [root@rhe7 Desktop]# ls -l /sys/kernel/iommu_groups/ total 0 This is exactly the symptoms displayed when intel_iommu=on is missing from the kernel commandline. In the bug description you say that you've added that to /etc/default/grub, but have you run grub2-mkconfig (setting the appropriate output file) so that it actually gets added to the commandline used by grub during boot, and verified after booting that the commandline used for boot contained the option (this will be in the first several lines of the dmesg output)? no, i had not run grub2-mkconfig but now even after i ran it, i dont see any change. Please attach dmesg from the system Created attachment 1083652 [details]
dmesg
Created attachment 1083653 [details]
/etc/default/grub
Created attachment 1083654 [details]
grub2-mkconifg -o /boot/grub2/grub.cfg
The kernel commandline in dmesg indicates intel_iommu=on is not being enabled: [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-229.el7.x86_64 root=/dev/mapper/rhel-root ro nomodeset crashkernel=auto rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet LANG=en_US.UTF-8 Since your system is using UEFI, the output of grub2-mkconfig should be to /etc/grub2-efi.cfg. Please: 1) Run: grub2-mkconifg -o /etc/grub2-efi.cfg 2) Reboot And let us know if the problem is resolved. wow, did not realize this even when i was seeing the OS not installing in GUI in the first place. I will try that, in addition to also checking if it works on legacy boot mode with the previous configurations. thanks, this is working. Closing the bug. |