search for: mirror_run

Displaying 9 results from an estimated 9 matches for "mirror_run".

Did you mean: mirror_num
2014 Feb 24
2
Re: [Qemu-devel] Adjust disk image migration (NBD)
...uot;:{"detach":true,"blk":false,"inc":false,"uri":"fd:migrate"},"id":"libvirt-223"} > > > However I observe what you do - disk migration is not shaped, while internal state is. Thanks for raising this. I noticed that mirror_run() does not throttle the first loop where it populates the dirty bitmap using bdrv_is_allocated_above(). The main copy loop does take the speed limit into account but perhaps that's broken too. Paolo, Jeff: Any ideas? Stefan
2019 Jun 04
2
blockcommit of domain not successfull
...================================== and "cannot parse process status data" continuously until the end of the logfile. The syslog from the domain itself didn't reveal anything, it just continues to run. The libvirt log from the domains just says: qemu-system-x86_64: block/mirror.c:864: mirror_run: Assertion `((&bs->tracked_requests)->lh_first == ((void *)0))' failed. Hosts are SLES 12 SP4 with libvirt-daemon-4.0.0-8.9.1.x86_64. Bernd -- Bernd Lentes Systemadministration Institut für Entwicklungsgenetik Gebäude 35.34 - Raum 208 HelmholtzZentrum münchen bernd.lente...
2014 Feb 24
0
Re: [Qemu-devel] Adjust disk image migration (NBD)
> Thanks for raising this. > > I noticed that mirror_run() does not throttle the first loop where it > populates the dirty bitmap using bdrv_is_allocated_above(). This is on purpose. Does it causes a noticeable stall in the guest? > The main > copy loop does take the speed limit into account but perhaps that's > broken too. Yeah, it l...
2014 Feb 28
2
Re: [Qemu-devel] Adjust disk image migration (NBD)
On 24/02/14 23:26, Paolo Bonzini wrote: >> Thanks for raising this. >> >> I noticed that mirror_run() does not throttle the first loop where it >> populates the dirty bitmap using bdrv_is_allocated_above(). > This is on purpose. Does it causes a noticeable stall in the guest? > >> The main >> copy loop does take the speed limit into account but perhaps that's >>...
2019 Jun 05
0
Re: blockcommit of domain not successfull
...========= > and "cannot parse process status data" continuously until the end of the logfile. > > The syslog from the domain itself didn't reveal anything, it just continues to run. > The libvirt log from the domains just says: > qemu-system-x86_64: block/mirror.c:864: mirror_run: Assertion `((&bs->tracked_requests)->lh_first == ((void *)0))' failed. So that's interresting. Usually assertion failure in qemu leads to calling abort() and thus the vm would have crashed. Didn't you HA solution restart it? At any rate it would be really beneficial if you...
2014 Feb 14
2
Adjust disk image migration (NBD)
Hi all, As I am doing some tests with qemu, I realized that the way it does 'migrate -i tcp:DEST:444' is not the same as 'libvirt migrate --copy-storage-inc'. Basically qemu uses the same stream as RAM migration and libvirt takes advantage of NBD transfer. With virsh migrate-setspeed I observed that one can only control the transfer throughput of RAM, but not disk
2019 Jun 13
2
Re: blockcommit of domain not successfull
...30299: error : qemuMonitorIO:719 : internal error: >> End of file from qemu monitor > > So this looks like qemu crashed. Or at least it's the usual symptom we > get. Is there anything in /var/log/libvirt/qemu/$VMNAME.log? That's all: qemu-system-x86_64: block/mirror.c:864: mirror_run: Assertion `((&bs->tracked_requests)->lh_first == ((void *)0))' failed. > >> 2019-06-08 03:59:26.145+0000: 30300: warning : qemuGetProcessInfo:1461 : cannot >> parse process status data >> 2019-06-08 03:59:26.191+0000: 30303: warning : qemuGetProcessInfo:1461 :...
2019 Jun 11
2
Re: blockcommit of domain not successfull
----- On Jun 5, 2019, at 4:49 PM, Peter Krempa pkrempa@redhat.com wrote: > On Wed, Jun 05, 2019 at 13:33:49 +0200, Lentes, Bernd wrote: >> Hi Peter, >> >> thanks for your help. >> >> ----- On Jun 5, 2019, at 9:27 AM, Peter Krempa pkrempa@redhat.com wrote: > > [...] > >> >> > >> > So that's interresting. Usually assertion
2019 Jun 05
3
Re: blockcommit of domain not successfull
...(81+18:44) reboot system boot 2.6.4-52-smp Wed Feb 27 20:29 (15+21:04) >> The syslog from the domain itself didn't reveal anything, it just continues to >> run. >> The libvirt log from the domains just says: >> qemu-system-x86_64: block/mirror.c:864: mirror_run: Assertion >> `((&bs->tracked_requests)->lh_first == ((void *)0))' failed. > > So that's interresting. Usually assertion failure in qemu leads to > calling abort() and thus the vm would have crashed. Didn't you HA > solution restart it? No. As said the VM d...