I submitted a question earlier as I had rebooted my host and got stuck at 'Loading initial ramdisk'. Annoyingly I had two problems, causing me to get lost in unnecessary troubleshooting.
My problem is that earlier today, in an attempt to fix problems with the Bluetooth on my Windows 11 VM, I ran the command
My host is now working and all VMs seem to be running correctly, but I'm struggling to get the passthrough working again. I have gone back through passthrough guides in the past to ensure all my settings are correct, which they appear to be.
Help me understand what I might be missing? I've attached a copy of my /etc/default/grub and the most recent logs.
My problem is that earlier today, in an attempt to fix problems with the Bluetooth on my Windows 11 VM, I ran the command
update-initramfs -u -k all, following a guide. This appears to be the reason that my monitor plugged into the GPU (which usually passes through the VM image) is just showing 'Loading initial ramdisk'.My host is now working and all VMs seem to be running correctly, but I'm struggling to get the passthrough working again. I have gone back through passthrough guides in the past to ensure all my settings are correct, which they appear to be.
Help me understand what I might be missing? I've attached a copy of my /etc/default/grub and the most recent logs.
Code:
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on amd_iommu=on modprobe.blacklist=xhci_hcd modprobe.blacklist=nvidia-gpu modprobe.blacklist=nouveau modprobe.blacklist=n>
GRUB_CMDLINE_LINUX="intel_iommu=on amd_iommu=on iommu=pt rd.driver.pre=vfio-pci video=efifb:off kvm.ignore_msrs=1 kvm.allow_unsafe_assigned_interrupts=1 pcie_acs_overr>
Code:
[ 0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
[ 0.000000] Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
[ 0.000000] secureboot: Secure boot could not be determined (mode 0)
[ 0.010426] secureboot: Secure boot could not be determined (mode 0)
[ 0.087934] Booted with the nomodeset parameter. Only the system framebuffer will be available
[ 0.088035] Booted with the nomodeset parameter. Only the system framebuffer will be available
[ 0.232689] x86/cpu: SGX disabled by BIOS.
[ 0.253189] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[ 0.253189] #9 #10 #11 #12 #13 #14 #15
[ 0.433039] Driver imsttfb not loading because of nomodeset parameter
[ 0.433040] Driver asiliantfb not loading because of nomodeset parameter
[ 0.470318] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 0.470366] platform eisa.0: EISA: Cannot allocate resource for mainboard
[ 0.470367] platform eisa.0: Cannot allocate resource for EISA slot 1
[ 0.470368] platform eisa.0: Cannot allocate resource for EISA slot 2
[ 0.470368] platform eisa.0: Cannot allocate resource for EISA slot 3
[ 0.470369] platform eisa.0: Cannot allocate resource for EISA slot 4
[ 0.470370] platform eisa.0: Cannot allocate resource for EISA slot 5
[ 0.470370] platform eisa.0: Cannot allocate resource for EISA slot 6
[ 0.470371] platform eisa.0: Cannot allocate resource for EISA slot 7
[ 0.470371] platform eisa.0: Cannot allocate resource for EISA slot 8
[ 0.652416] blacklist: Problem blacklisting hash (-13)
[ 0.652420] blacklist: Problem blacklisting hash (-13)
[ 0.652443] blacklist: Problem blacklisting hash (-13)
[ 0.652462] blacklist: Problem blacklisting hash (-13)
[ 0.652485] blacklist: Problem blacklisting hash (-13)
[ 0.652501] blacklist: Problem blacklisting hash (-13)
[ 4.020672] spl: loading out-of-tree module taints kernel.
[ 4.024232] znvpair: module license 'CDDL' taints kernel.
[ 4.024233] Disabling lock debugging due to kernel taint
[ 4.199970] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 4.430336] iwlwifi 0000:07:00.0: api flags index 2 larger than supported by driver
[ 4.441818] Bluetooth: hci0: FW download error recovery failed (-19)
[ 4.441882] Bluetooth: hci0: sending frame failed (-19)
[ 4.441959] Bluetooth: hci0: Failed to read MSFT supported features (-19)
[ 4.475187] kvm: unknown parameter 'allow_unsafe_assigned_interrupts' ignored
[ 4.475189] kvm: unknown parameter 'allow_unsafe_assigned_interrupts' ignored
[ 4.522397] thermal thermal_zone1: failed to read out thermal zone (-61)
[ 6.358308] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 39.817745] kauditd_printk_skb: 13 callbacks suppressed
[ 44.468205] kvm [2733]: ignored rdmsr: 0xc0011029 data 0x0
[ 70.890007] overlayfs: upper fs does not support RENAME_WHITEOUT.
[ 70.890028] overlayfs: fs on '/var/lib/docker/overlay2/check-overlayfs-support2605339747/lower2' does not support file handles, falling back to xino=off.
[ 76.453436] overlayfs: upper fs does not support RENAME_WHITEOUT.
[ 76.453455] overlayfs: fs on '/var/lib/docker/overlay2/metacopy-check959366092/l1' does not support file handles, falling back to xino=off.
[ 85.375168] overlayfs: upper fs does not support RENAME_WHITEOUT.
[ 85.394901] overlayfs: upper fs does not support RENAME_WHITEOUT.
[ 85.496511] overlayfs: fs on '/var/lib/docker/overlay2/l/OADGQT76PNUUPVRXRU6MAAX2KY' does not support file handles, falling back to xino=off.
[ 85.530205] overlayfs: fs on '/var/lib/docker/overlay2/l/PDZN3YMQMRSIY2W2Y6SW64VXXG' does not support file handles, falling back to xino=off.