blob: d7dea667d2d912c4cbab3751846d713ac02dd284 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Okay, I need to classify this bug report into one of the given categories. The problem is about QEMU failing to assign a PCI device behind a bridge. Let me read through the details carefully.
The user describes an error where QEMU can't bind a PCI device because there's no such device. They provided strace output showing that the device is behind aPCI bridge. The issue arises because the bridge isn't bound to vfio-pci, causing the failure.
From the steps, I see that manually unbinding the bridge and binding it to vfio-pci fixes the problem. The user also mentions that QEMU should automatically handle this but isn't doing so.
Looking at the categories: Mistranslation is about incorrect mapping in user-mode, which doesn't fit here. Assembly lowering is unrelated. Other might be a possibility, but I see specific issues with PCI devices and vfio binding.
The problem relates to device management—specifically, how QEMU handles devices behind bridges. The error occurs during device assignment, pointing towards a hardware or device-related issue rather than something like graphics or network.
So the most fitting category is 'device' because it's about handling PCI devices and their bindings.
</think>
device
|