blob: cc2d18cd42a523d7db2484815ad8182c84d2213f (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
|
<think>
Alright, let's figure out which category this bug report falls into. The user is experiencing a "Connection reset by peer" when using port forwarding with QEMU. They provided the command line arguments and the output from an SSH attempt.
First, looking at the commands, they're using `qemu-system-ppc64` with various devices and network configurations. Specifically, there's `-netdev user,id=netdev0,hostfwd=tcp:127.0.0.1:2222-:22`, which sets up port forwarding from the host's 2222 to the guest's 22 (SSH). Then they're trying to connect via SSH but getting a reset.
The error message mentions "Connection reset by peer," which typically points to an issue with how connections are being handled, possibly at the network level. Since it's related to port forwarding and networking in QEMU, I should consider categories like 'network' or maybe even 'device' if it's hardware-related.
Looking at the possible categories: network is a direct fit here because the problem occurs during network communication between the host and guest. Other possibilities could be 'device' if it's a specific device issue, but since it's about port forwarding and SSH connectivity, 'network' seems more accurate.
</think>
The bug report involves an issue with port forwarding in QEMU, specifically related to network connections being reset. This points directly to a problem within the networking component of QEMU.
**network**
|