blob: 375e636f2a7c202eb50c14201fc23b19af3b4bf2 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
|
<think>
Alright, let's try to figure out which category this bug report falls into. The user is experiencing an issue with their QEMU setup where the secondary VM can't receive any packets during a migration. They provided some code snippets from 'colo.c' and 'kvm.c' that seem to be related.
First, looking at the problem description: the secondary VM isn't receiving packets because the filter-redirector's queue isn't being flushed when the secondary is in the RUN_STATE_INMIGRATE state. The function qemu_can_send_packet() returns 0 on the secondary VM since runstate_is_running() is false there. This means that network packets aren't being sent out as expected.
The user also mentioned that they're confused about how outbound packets are produced in the secondary VM when it's in migrate mode, citing the kvm_cpu_exec() function which might not be running on the secondary.
So, considering the categories provided: 'device', 'graphic', 'network', etc. The issue revolves around network packet handling during migration, specifically related to the filter-redirector and net client states. This points towards a networking problem within QEMU.
The functions involved are part of the network stack (NetClientState) and relate to whether packets can be sent or not. Since the secondary VM is in a migrate state, it's likely that the network handling during this state isn't correctly flushed or processed, leading to no packets being received.
Thus, the most fitting category here would be 'network' because the bug is directly affecting packet reception and involves network-related functions in QEMU.
</think>
network
|