I've installed F43 in a QEMU/KVM VM and managed to get the 6.18
kernel installed and active, and also seem to have gotten the
akmods nvidia driver compiled as well, although the nvidia server
doesn't seem to be able to communicate. I can't check whether the
kernel has an MT7927 driver embedded in it because the VM can't
detect the wifi device so it doesn't offer me the opportunity to
try to connect via wifi.
Did you give the device to the VM?
I did try to replace the ethernet driver first with MT7927 but that
errored at VM start and secondly I specified MT7925 which I know is
in the host kernel and that failed with the same errors.
How do I give the device to the VM?
In the VM configuration, add hardware, host pci device, pick the wifi
device.
The other issue I have with this is, I have two ethernet controllers
on my motherboard which run at different speeds, both of which,
according to INXI, use different kernel drivers, and the ethernet
driver passed in to the VM seems to be the driver that INXI says is
being used for the ethernet controller I believe I am not actually
using.
By default, the VM will have a virtual ethernet device, not one of
the real ones. If you really want to give the VM a physical ethernet
device, then follow the same steps as above, but that's unusual.
Thanks Samuel, I tried adding the only device that appeared to be
Mediatek and the start of the VM image failed, but I will need to do
some investigation.
regards,
I have selected "Add Hardware->PCI Host Device" and then selected the
only device that is identified as being a Mediatek device and clicked
"Finish". When I then started the VM the start failed with the following
messages:
Error starting domain: internal error: QEMU unexpectedly closed the monitor
(vm='fedora'):2025-12-31T21:41:39.9034658Z qemu-system-x86_64: -device
{"driver":"vfio-pci","host":"0000:08:00.0","id":"hostdev0","bus":"pci.7","addr":"0x0"}:vfio
0000:08:00.0: group 15 is not viable
Please ensure all devices within the iommu_group are bound to their vfio
bus driver.
Having never used QEMU before as a VM Manager I'm at a loss to
understand what this means.
Without that device the VM boots quite happily, and from what George was
showing, the second version of the 6.18 kernel doesn't appear to have
support for the chipset that I read was supposed to be being provided in
the 6.18 kernel. It may be too early in the kernel release.
I've checked the host system and the device that I think is the wifi
device, as shown by INXI has bus-ID 08:00.0 which is the bus address
shown in the message above, so I believe I have selected the correct
device. The only thing I can think of is QEMU is expecting the host to
have provided a driver for that device which in the current kernels
doesn't exist, and, if that is the case that defeats the purpose of the
test I'm trying to do which is check if the 6.18 kernel is going to
provide a driver. Am I looking at things incorrectly?
regards,
BEGIN:VCARD
VERSION:4.0
N:Morris;Stephen;;;
FN:Stephen Morris
EMAIL;PREF=1;TYPE=home:[email protected]
END:VCARD
--
_______________________________________________
users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
