Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kmod (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned | ||
linux-hwe (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bionic |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Can't Load vfio-pci Module on Ubuntu 18.04 HWE Kernel
```
ubuntu@ubuntu-2:~$ modinfo vfio-pci
modinfo: ERROR: Module vfio-pci not found.
ubuntu@ubuntu-2:~$ uname -a
Linux DL360G9-2 5.4.0-52-generic #57~18.04.1-Ubuntu SMP Thu Oct 15 14:04:49 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
```
But Generic kernel is Working.
```
ubuntu@ubuntu-4:~$ modinfo vfio-pci
filename: /lib/modules/
description: VFIO PCI - User Level meta-driver
author: Alex Williamson <email address hidden>
license: GPL v2
version: 0.2
srcversion: 1E92A800B94EAE7
depends: vfio,irqbypass,
retpoline: Y
intree: Y
name: vfio_pci
vermagic: 4.15.0-122-generic SMP mod_unload
signat: PKCS#7
signer:
sig_key:
sig_hashalgo: md4
parm: ids:Initial PCI IDs to add to the vfio driver, format is "vendor:
parm: nointxmask:Disable support for PCI 2.3 style INTx masking. If this resolves problems for specific devices, report lspci -vvvxxx to <email address hidden> so the device can be fixed automatically via the broken_intx_masking flag. (bool)
parm: disable_vga:Disable VGA resource access through vfio-pci (bool)
parm: disable_
```
How to use vfio-pci module in HWE kernel?
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-52-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.16
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer'
Card0.Amixer.
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-11-09 (0 days ago)
InstallationMedia: Ubuntu-Server 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
MachineType: VMware, Inc. VMware Virtual Platform
Package: linux (not installed)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
linux-firmware 1.173.19
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags: bionic uec-images
Uname: Linux 5.4.0-52-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lxd plugdev sudo
_MarkForUpload: True
dmi.bios.date: 07/22/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VMware Virtual Platform
dmi.product.
dmi.sys.vendor: VMware, Inc.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
affects: | linux (Ubuntu) → linux-hwe (Ubuntu) |
Changed in linux-hwe (Ubuntu Bionic): | |
status: | New → In Progress |
assignee: | nobody → Po-Hsu Lin (cypressyew) |
Changed in linux-hwe (Ubuntu): | |
status: | Incomplete → Confirmed |
Changed in linux-hwe (Ubuntu Bionic): | |
status: | Incomplete → Confirmed |
Changed in kmod (Ubuntu): | |
status: | New → Fix Released |
Changed in kmod (Ubuntu Bionic): | |
status: | New → Confirmed |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1903612
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.