blob: 0a253863e93bdc931aa4e8983120cf848a1570c7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, so I need to classify this bug report from QEMU. The user provided some logs and details about the problem they're encountering.
First, looking at the messages, it says "VFIO passthrough spits out thousands of messages." VFIO is related to device assignment in QEMU, specifically for passing through hardware devices to a virtual machine. So this is likely a problem with how the device is being handled by the hypervisor or the IOMMU (Input/Output Memory Management Unit).
The error messages mention "iommu has granularity incompatible with target AS" and "iommu map to non memory area." These errors relate to issues in mapping the device's memory, which suggests a problem during the setup of the VFIO passthrough. The IOMMU is responsible for handling DMA (Direct Memory Access) from devices, so any incompatibility here could cause repeated errors.
Looking at the possible categories: hypervisor, kernel, device, etc. Since VFIO is part of the KVM hypervisor and deals with hardware pass-through, the issue seems to be related to how QEMU/KVM interacts with the IOMMU during device assignment.
The user mentioned they're running a Sparc64 system and provided details about the pci device being passed through. The kernel driver in use is vfio-pci, which aligns with the hypervisor's role in managing these devices.
Considering all this, the most appropriate category would be 'hypervisor' because the problem is related to how QEMU/KVM handles the VFIO passthrough and interacts with the IOMMU during device setup.
</think>
hypervisor
|