1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
|
<think>
Okay, so I need to classify this bug report according to the given categories for QEMU. Let me start by reading the bug report carefully.
The user is talking about the qom-* scripts (list, tree, get, set) not accepting TCP endpoint arguments correctly. They mention that while the help text says it can take a Unix socket path or a TCP host:port string, only the Unix socket part works. The problem seems to be in how these scripts handle the '-s' argument for TCP connections.
The user points out that QEMUMonitorProtocol accepts either a string (for Unix sockets) or a tuple (host, port), but the qom-* scripts don't process the '-s' into such a tuple. They have a patch to fix this.
Now, looking at 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 how arguments are handled in the scripts. Since it's about parsing and processing command-line arguments for network connections (TCP), this seems more related to networking rather than other categories like graphics or sockets specifically.
Wait, but socket could also be a possibility since TCP endpoints involve sockets. However, the primary function here is about connecting over a network, so 'network' might be more appropriate. Alternatively, it's about handling the argument parsing correctly, which is a script issue, not directly a networking component.
But considering that the scripts are part of the QEMU management and communication, and they're dealing with TCP endpoints for remote connections, the main area affected here is network-related functionality.
So, I think the category should be 'network'.
</think>
network
|