blob: 9613b3b8b84c9585c3c5658a8709c6ad0df21b4c (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Okay, let's try to figure out which category this bug report falls into. The user is reporting an issue with QEMU where VirtIO-Serial-Bus reports an error, causing the Windows vdagent to not start. They mentioned that using qemu-kvm-0.15.0-rc1 causes the problem, but qemu-0.15.0 behaves correctly.
Looking at the configuration, they've enabled several features like VNC threads and Spice. The commands show they're using VirtIO devices, specifically VirtIO-Serial-PCI with max_ports=16, and a VirtSerialPort connected to vdagent via SpiceVMC. They tried different configurations but faced the same issue.
The error message is about an unexpected port ID in VirtIO-Serial-Bus. This suggests that there's a problem with how ports are being handled in the VirtIO-serial implementation. The VirtIO-serial is part of the device emulation, specifically for serial devices in virtual machines.
Since the problem occurs when using KVM (as indicated by -enable-kvm), it relates to hardware acceleration but more so to the device handling within QEMU. The category options include 'device', which seems appropriate because the issue pertains to VirtIO-serial bus ports not being handled correctly during device setup or communication.
Other categories like 'graphic' or 'network' don't fit here, and 'hypervisor' is more about KVM itself rather than specific devices. So, I think the bug is related to a device issue.
</think>
device
|