[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-discuss] Latest Qemu-COLO Segfaults

From: Lukas Straub
Subject: Re: [Qemu-discuss] Latest Qemu-COLO Segfaults
Date: Fri, 17 Aug 2018 10:51:23 +0200

Hello Again,
Any News on the Problems that I had? Have they been fixed or am I just
doing things wrong?

Lukas Straub

On Tue, 5 Jun 2018 22:08:09 +0200
Lukas Straub <address@hidden> wrote:

> Hi Zhang,
> I have tested Your latest Patch, and the Crash is gone and the
> Secondary now Synchronizes fine. So far so good. :)
> However sadly, I found more Problems:
> First it seems like COLO has problems comparing Packets send by the
> VMs as it's doing a lot of Checkpoints when doing even simple network
> operations. ping to local LAN for example is around ~200-4000ms and
> ssh is unusable, because input lags almost 10 Seconds behind. Also I
> get lots of messages on the primary qemu, see the log attached.
> Secondly, I couldn't really Failover. While the Secondary VM continues
> to run when the Primary Fails, it's unable to send/receive network
> packets. Also when executing { "execute": "x-colo-lost-heartbeat" }
> (is this still needed for Failover?), the Secondary Aborts:
> qemu-system-x86_64: Can't receive COLO message: Input/output error
> {"timestamp": {"seconds": 1528226730, "microseconds": 287902},
> "event": "COLO_EXIT", "data": {"mode": "secondary", "reason":
> "error"}} qemu-system-x86_64: Unable to connect character device
> red0: Failed to connect socket: Connection refused
> { "execute": "x-colo-lost-heartbeat" }
> {"return": {}}
> {"timestamp": {"seconds": 1528226733, "microseconds": 218936},
> "event": "STOP"}
> qemu-system-x86_64: Conflicts with use by a block device as 'root',
> which does not allow 'resize' on node0
> qemu-system-x86_64: 
> free(): invalid size
> Third, Periodic mode (Remus-like without all the
> comparing/filters/rewriters) doesn't seem to work , the primary
> crashes at the first STOP:
> {"timestamp": {"seconds": 1528228672, "microseconds": 407981},
> "event": "RESUME"}
> {"timestamp": {"seconds": 1528228690, "microseconds": 230970},
> "event": "STOP"}
> qemu-system-x86_64: util/qemu-thread-posix.c:64: qemu_mutex_lock_impl:
> Assertion `mutex->initialized' failed.
> I use the scripts attached to test qemu-COLO (simply copying-pasting
> the echo output to the qmp monitor).
> I'm very glad that you work on Qemu-COLO.
> Many Thanks,
> Lukas Straub

reply via email to

[Prev in Thread] Current Thread [Next in Thread]