1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
|
<think>
Alright, let's try to figure out how to classify this bug report for QEMU. The user is encountering a "Permission denied" error when trying to mount a USB device using QEMU. They mentioned that they're on Debian with KDE and using QEMU version 14.0.
Looking at the command line arguments they provided, I see options like `-enable-kvm`, which suggests they're using KVM for virtualization. The error message is about accessing `/dev/bus/usb/000/001`, so it's related to USB device access in QEMU.
They mentioned that changing permissions to 777 isn't a good solution because the changes are lost upon restart. Also, they're part of the plugdev group, which typically has permission to access USB devices. So why is QEMU still denying access?
I remember that when using KVM/QEMU with USB devices, there's an interaction between user-mode and kernel drivers. Maybe QEMU isn't properly handling the permissions or the way it accesses the USB device. It could be a problem in how QEMU requests access to the USB bus.
The error seems related to device access during runtime rather than static file permissions. Since they're using KVM, perhaps there's an issue with the hypervisor or how the host OS handles device pass-through to the VM. Alternatively, it might be a bug in QEMU's USB device handling code.
Looking at the possible categories: 'device' and 'permissions' are both relevant, but the root cause seems more tied to how devices are managed during VM setup, which might fall under 'hypervisor' or 'device'. However, since it's about access rights when using KVM, I think 'hypervisor' is a better fit because it relates to how QEMU/KVM interacts with host resources.
Alternatively, maybe it's more about the USB device handling within the VM setup, which would be 'device'. But considering the context of KVM and permissions in that environment, 'hypervisor' makes sense.
</think>
hypervisor
|