1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
|
<think>
Alright, let's try to classify this bug report. The user is experiencing an issue where attaching WinDbg to a Windows guest on a Windows host causes QEMU to hang when using real serial ports.
First, I need to understand what each category means. Looking at the list provided: categories include things like mistranslation, assembly lowering, device, graphic, socket, network, KVM, boot, vnc, debug, files, permissions, performance, kernel, peripherals, hypervisor.
The problem here is about attaching a debugger (WinDbg) to a guest VM running Windows on a Windows host. When they do this using real serial ports, QEMU hangs.
Let's break down the steps provided:
1. Enable debug in the Windows guest: This probably involves enabling some debugging features within the VM.
2. Create a DB9 connection between two COM ports: So, setting up serial ports for communication.
3. Power on the guest and attach WinDbg to the second COM port not used by the guest.
The issue is that when they perform this setup, QEMU locks up.
Looking at the possible categories:
- **debug**: This seems related since it's about attaching a debugger (WinDbg) to the VM.
- **network**: Could be involved if there was a network-related hang, but in this case, it's using serial ports, so probably not.
- **device** or **peripherals**: Serial ports are devices, so that could be relevant too.
But since the primary action is attaching a debugger and the problem occurs during that process, I think 'debug' is the most fitting category. The issue might be related to how QEMU handles debugging sessions, possibly leading to a deadlock or hang when using serial COM ports for debugging.
</think>
debug
|