blob: cde106e680189f47ce35b29f7e4ace84c63628e3 (
plain) (
blame)
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
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
KVM: 0.922
graphic: 0.908
device: 0.825
performance: 0.791
virtual: 0.729
network: 0.622
architecture: 0.597
vnc: 0.573
arm: 0.568
semantic: 0.547
socket: 0.474
VMM: 0.471
user-level: 0.451
files: 0.428
hypervisor: 0.417
risc-v: 0.416
boot: 0.381
debug: 0.366
peripherals: 0.360
PID: 0.353
mistranslation: 0.347
ppc: 0.345
i386: 0.345
kernel: 0.342
x86: 0.311
permissions: 0.273
register: 0.240
TCG: 0.160
assembly: 0.036
migrate exec hangs for several minutes if the pipe is closed before all its data is written
Binary package hint: kvm
Using
migrate "exec:true"
in the monitor hangs the VM for several minutes. What I expect is that the VM stops attempting to migrate after the pipe has been closed.
Indicating a background migrate with -d doesn't help. Presumably the migration is not backgrounded until a certain amount of data is written to the pipe, or the migration times out What I expect is that the migration is backgrounded immediately.
I can reproduce this in Lucid. Like the other related bug report, I don't have a strong opinion on the feature request, though it seems reasonable. We will defer to Upstream's decision on this one. Thanks!
|