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
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
user-level: 0.978
permissions: 0.977
arm: 0.977
assembly: 0.976
register: 0.974
device: 0.972
architecture: 0.972
mistranslation: 0.971
socket: 0.971
semantic: 0.970
debug: 0.970
vnc: 0.969
graphic: 0.968
boot: 0.967
kernel: 0.964
performance: 0.964
PID: 0.963
peripherals: 0.963
virtual: 0.963
ppc: 0.958
files: 0.957
risc-v: 0.950
hypervisor: 0.948
network: 0.948
VMM: 0.947
x86: 0.946
i386: 0.942
TCG: 0.937
KVM: 0.932
qemu hangs on live-migration with storage(virtual machine: windows Server 2008 with only one disk )
Hi,
We are using “Windows Server 2008” with qemu-kvm-2.0.1 (linux kernel:3.10.0) as a host of a VM.
Using drive_mirror to do live-migration on the same host for different disks
Local disk: /sf/data/local/
Shared disk(iscsi): /sf/other/local/ --- the disk is busy, the IO rate is about 30MB/s
qemu-system-x86_64 -k en-us -m 2048 -smp 2 -vnc :3100 -usbdevice tablet -boot c -enable-kvm -drive file=/sf/data/local/vm-disk-1.qcow2,if=none,id=drive-ide0,cache=none,aio=native -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100
Step 1:
Start migration: Drive_mirror -f drive-ide0 /sf/other/local/test.qcow2
Step 2:
When detect the migration has completed, then send cmd: block_job_complete -f drive-ide0
Step 3:
send cmd: info status
What surprised me is that the qemu monitor reports can’t be connected.
Then find bellows:
The qemu process hangs on the mirror_run->bdrv_drain_all->aio_poll->qemu_poll_ns->ppoll (),
None events were received and poll forever. I don’t know why the aio can’t be responsed. This case is hardly to
be generated but it really happens sometimes . I’m looking forward to getting help from you .
The stack capture snapshot:
Thanks
MyAngle
On Sat, Mar 21, 2015 at 07:44:37AM -0000, youyunyehe wrote:
> We are using “Windows Server 2008” with qemu-kvm-2.0.1 (linux kernel:3.10.0) as a host of a VM.
Please give the exact qemu-kvm package version and Linux distro name.
The code in qemu.git/master is slightly different so maybe the issue no
longer happens, but it would be worth looking at the exact source code
your qemu-kvm is built from.
I have CCed Jeff Cody, who maintains drive-mirror.
> Using drive_mirror to do live-migration on the same host for different disks
> Local disk: /sf/data/local/
> Shared disk(iscsi): /sf/other/local/ --- the disk is busy, the IO rate is about 30MB/s
> qemu-system-x86_64 -k en-us -m 2048 -smp 2 -vnc :3100 -usbdevice tablet -boot c -enable-kvm -drive file=/sf/data/local/vm-disk-1.qcow2,if=none,id=drive-ide0,cache=none,aio=native -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100
>
> Step 1:
> Start migration: Drive_mirror -f drive-ide0 /sf/other/local/test.qcow2
>
> Step 2:
> When detect the migration has completed, then send cmd: block_job_complete -f drive-ide0
>
> Step 3:
> send cmd: info status
> What surprised me is that the qemu monitor reports can’t be connected.
>
> Then find bellows:
> The qemu process hangs on the mirror_run->bdrv_drain_all->aio_poll->qemu_poll_ns->ppoll (),
> None events were received and poll forever. I don’t know why the aio can’t be responsed. This case is hardly to
> be generated but it really happens sometimes . I’m looking forward to getting help from you .
> The stack capture snapshot:
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>]
> On Behalf Of Stefan Hajnoczi
> Sent: 2015年3月23日 21:32
> To: Bug 1434779
> Cc: <email address hidden>
> Subject: Re: [Qemu-devel] [Bug 1434779] [NEW] qemu hangs on live-migration with storage(virtual machine: windows Server 2008
> with only one disk )
>
> On Sat, Mar 21, 2015 at 07:44:37AM -0000, youyunyehe wrote:
> > We are using “Windows Server 2008” with qemu-kvm-2.0.1 (linux kernel:3.10.0) as a host of a VM.
>
> Please give the exact qemu-kvm package version and Linux distro name.
> The code in qemu.git/master is slightly different so maybe the issue no longer happens, but it would be worth looking at the exact
> source code your qemu-kvm is built from.
[Halsey] I also recreated this issue today, qemu hangs at bdrv_rw-co() -> bdrv_prwv_co() -> aio_poll(0 -> qemu_poll_ns() -> ppoll(). I'm just call bdrv_write to write data to qcow2 file. My qemu version is qemu-2.2.0.
> I have CCed Jeff Cody, who maintains drive-mirror.
>
> > Using drive_mirror to do live-migration on the same host for
> > different disks Local disk: /sf/data/local/
> > Shared disk(iscsi): /sf/other/local/ --- the disk is busy, the IO rate is about 30MB/s
> > qemu-system-x86_64 -k en-us -m 2048 -smp 2 -vnc :3100 -usbdevice
> > tablet -boot c -enable-kvm -drive
> > file=/sf/data/local/vm-disk-1.qcow2,if=none,id=drive-ide0,cache=none,a
> > io=native -device
> > ide-hd,bus=ide.0,unit=0,drive=drive-ide0,id=ide0,bootindex=100
> >
> > Step 1:
> > Start migration: Drive_mirror -f drive-ide0
> > /sf/other/local/test.qcow2
> >
> > Step 2:
> > When detect the migration has completed, then send cmd:
> > block_job_complete -f drive-ide0
> >
> > Step 3:
> > send cmd: info status
> > What surprised me is that the qemu monitor reports can’t be connected.
> >
> > Then find bellows:
> > The qemu process hangs on the
> > mirror_run->bdrv_drain_all->aio_poll->qemu_poll_ns->ppoll (), None
> > events were received and poll forever. I don’t know why the aio can’t be responsed. This case is hardly to be generated but it really
> happens sometimes . I’m looking forward to getting help from you .
> > The stack capture snapshot:
Looking through old bug tickets... can you still reproduce this issue with the latest version of QEMU? Or could we close this ticket nowadays?
[Expired for QEMU because there has been no activity for 60 days.]
|