1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, I'm trying to figure out how to classify this bug report for QEMU. The user mentioned that when they use the command `lspci`, the IVSHMEM device isn't showing up. They provided their configuration, which includes setting up an IVSHMEM model in their guest VM's XML file.
Looking at the details, the IVSHMEM device is correctly added as a PCI device with specific parameters. The user also ran `ps aux` and saw that QEMU includes the device option, so it seems like QEMU is aware of the device. However, when they run `lspci`, it doesn't appear.
They did check with `lshw` and found the device listed as unclaimed. This suggests that while the device is present in the system, it's not being properly recognized or claimed by the OS.
Considering the categories provided: mistranslation, assembly, other, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The issue is related to a device (IVSHMEM) not being detected by `lspci`. This doesn't seem to be an incorrect translation or assembly lowering. It's more about the device not appearing correctly in the system, so "device" seems appropriate. Alternatively, since it's a hardware-related issue within the VM, maybe "peripherals" could fit, but I think "device" is more specific here.
</think>
The bug report relates to an IVSHMEM device not showing up under `lspci`, which suggests an issue with how the device is being handled or detected by the system. Since the device is present in QEMU's configuration and visible via `lshw` but not through `lspci`, this points towards a problem with device recognition, likely within the device management layer.
**Answer:** device
|