Hi, Zhang:
When I create PVM with:
-drive
if=virtio,id=primary-disk0,driver=quorum,read-pattern=fifo,vote-threshold=1,
children.0.file.filename=...
SVM with:
-drive if=ide,id=secondary-disk0,file.filename=...
I got this ERR: qemu-system-x86_64: block.c:5062: bdrv_detach_aio_context:
A
;
Cc: "qemu-discuss";
Subject: Re: [Qemu-discuss] Latest Qemu-COLO Segfaults
Hello,
Well the "best" version of COLO (that I know of) is
https://github.com/coloft/qemu/tree/colo-v5.1-developing-COLO-frame-v21-with-shared-disk
together with the old Instructions (see
https://wik
Hello,
Well the "best" version of COLO (that I know of) is
https://github.com/coloft/qemu/tree/colo-v5.1-developing-COLO-frame-v21-with-shared-disk
together with the old Instructions (see
https://wiki.qemu.org/index.php?title=Features/COLO&oldid=7150#Test_environment_prepare
for an older Version o
Hello Again,
Any News on the Problems that I had? Have they been fixed or am I just
doing things wrong?
Regards,
Lukas Straub
On Tue, 5 Jun 2018 22:08:09 +0200
Lukas Straub wrote:
> Hi Zhang,
> I have tested Your latest Patch, and the Crash is gone and the
> Secondary now Synchronizes fine. So
Hi Lukas,
This bug have been fixed in my latest patch.
Please retest it.
https://www.mail-archive.com/qemu-devel@nongnu.org/msg538383.html
github:
https://github.com/zhangckid/qemu/tree/qemu-colo-18jun1
Thanks
Zhang Chen
On Sun, Apr 22, 2018 at 5:47 AM, Lukas Straub wrote:
> Hello Mr Che
Hello Mr Chen,
I found some time to play with Qemu-COLO again. I looked at the other
thread below and tried with the
https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10-legacy Branch
You mentioned there. However with that branch the Primary Aborts for
me with "qemu: qemu_thread_join: No such
Hi Lukas.
I got the same results.
And it seems like a bug.
http://qemu.11.n7.nabble.com/Bug-1754542-NEW-colo-secondary-vm-crash-when-execute-x-colo-lost-heartbeat-td557658.html#a560721
--
Sent from: http://qemu.11.n7.nabble.com/Discuss-f31862.html
Hello,
This already works better, but now I get another weird Problem: The
secondary VM would start normally, but then the kernel always complains
that the initrd is corrupt and panics. After that, colo will resync the
VM state, but the Secondary VM then always resets after every RESUME
and will ne
Yes, you can see the Colo wiki, I just updated it.
https://wiki.qemu.org/Features/COLO
Thanks
Zhang Chen
On Sun, Mar 18, 2018, 6:18 AM Lukas Straub wrote:
> Hello Zhang,
> Thanks for your reply. I've thinkered a bit around with the version you
> provided, on two separate Machines this time (ea
Hello Zhang,
Thanks for your reply. I've thinkered a bit around with the version you
provided, on two separate Machines this time (each with the same
configuration), but I still couldn't get it to work. Could You give me
a case that definitely works for You, with qemu command line and qmp
commands
Hi Lukas,
Sorry, I didn't receive the previous email in my gmail.
Currently, COLO not support primary node and secondary node both in one
physical machine.
COLO is a HA solution, in this case can not support physical faults, like
power cuts.
So, you'd better use two physical machine to use COLO, t
Hello Everyone,
Any Status on this?
Kind Regards,
Lukas Straub
On Sat, 17 Feb 2018 17:36:29 +0100
Lukas Straub wrote:
> Hello Mr. Chen,
> I was trying your latest Version of Qemu-COLO
> (https://github.com/zhangckid/qemu/tree/qemu-colo-18jan19) with both
> Qemu Instances running on One Host. Ho
Hello Mr. Chen,
I was trying your latest Version of Qemu-COLO
(https://github.com/zhangckid/qemu/tree/qemu-colo-18jan19)
with both Qemu Instances running on One Host. However the Secondary always
Segfaults after entering the QMP Commands,
and Sometimes even the Primary Segfaults, depending on the
13 matches
Mail list logo
