Currently, we support virtio-net, and not support all vhost-xxx.
On Fri, Jul 27, 2018 at 6:41 PM WANG Chao
wrote:
> Yes, ide works.
>
> And by the way, how about other virtio devices or vhost-xxx? Are they
> supported by COLO?
>
> Do you know the working set of devices? My preliminary test show
Hi, Zhang Chen
It seems virtio blk isn't working.
I test coloft against https://github.com/zhangckid/qemu/tree/qemu-colo-
18jul22, got the following error on very early stage:
On primary:
qemu-system-x86_64: Can't receive COLO message: Input/output error
On secondary:
qemu-system-x86_64: block.
Yes, ide works.
And by the way, how about other virtio devices or vhost-xxx? Are they
supported by COLO?
Do you know the working set of devices? My preliminary test shows ide,
e1000, rtl8139 work.
Thanks
WANG Chao
--
You received this bug notification because you are a member of qemu-
devel-ml
Hi Chao,
Yes, virtio blk isn't supported by current COLO, you can try the "-drive
if=ide ".
Thanks
Zhang Chen
On Fri, Jul 27, 2018 at 12:53 PM, WANG Chao
wrote:
> Hi, Zhang Chen
>
> It seems virtio blk isn't working.
>
> I test coloft against https://github.com/zhangckid/qemu/tree/qemu
Hi Suiheng,
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
--
You received this bug notification because you are a member of qemu-
Thanks zhijian.
On Fri, Mar 23, 2018 at 4:34 PM, Li Zhijian
wrote:
> Just noticed that's a little old, you may need to rebase it
>
>
> Thanks
>
>
> On 03/23/2018 11:51 AM, Li Zhijian wrote:
>
>>
>>
>> On 03/21/2018 02:04 PM, Zhang Chen wrote:
>>
>>> Hi Suiheng,
>>>
>>> I made a new guest image a
Just noticed that's a little old, you may need to rebase it
Thanks
On 03/23/2018 11:51 AM, Li Zhijian wrote:
On 03/21/2018 02:04 PM, Zhang Chen wrote:
Hi Suiheng,
I made a new guest image and retest it, and got the same bug from latest branch.
I found that after the COLO checkpoint begin,
On 03/21/2018 02:04 PM, Zhang Chen wrote:
Hi Suiheng,
I made a new guest image and retest it, and got the same bug from latest branch.
I found that after the COLO checkpoint begin, the secondary guest always send
reset request to Qemu like someone still push the reset button in the guest.
And
SVM error photo
** Attachment removed: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
** Attachment added: "SVM.err.jpg"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086654/+files/SVM.err.jpg
--
You received this bug
I took a photo when SVM print reset.
It seems like kernel panic.
I hope this will help.
** Attachment added: "SVM_error.HEIC"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5086650/+files/SVM_error.HEIC
--
You received this bug notification because you are a member of qemu-
devel-
Hi Suiheng,
I made a new guest image and retest it, and got the same bug from latest
branch.
I found that after the COLO checkpoint begin, the secondary guest always
send
reset request to Qemu like someone still push the reset button in the guest.
And this bug occurred in COLO frame related codes.
It is svn trace even
** Attachment added: "trace-svm.log"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5084771/+files/trace-svm.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/17545
It is my trace event file.
I read it many times, but still can't find the cause of the error.
I just found after colo_vm_state_change ide_reset and ps2_kbd_reset ...
** Attachment added: "trace-pvm.log"
https://bugs.launchpad.net/qemu/+bug/1754542/+attachment/5084770/+files/trace-pvm.log
--
Hi Zhang Chen，
I follow the https://wiki.qemu.org/Features/COLO, And Vm no crash.
But SVM rebooting constantly after print RESET, PVM normal startup.
Secondary:
{"timestamp": {"seconds": 1521421788, "microseconds": 541058}, "event":
"RESUME"}
{"timestamp": {"seconds": 1521421808, "microseconds":
** Description changed:
I use Arch Linux x86_64
Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run this command
Primary:
- sudo qemu-system-x86_64 -boot c -enable-kvm -m 2048 -smp 2 -qmp s
** Description changed:
I use Arch Linux x86_64
- Zhang
Chen's(https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10)
+ Zhang Chen's(https://github.com/zhangckid/qemu/tree/qemu-colo-18mar10)
Following document 'COLO-FT.txt',
I test colo feature on my hosts
I run
** Summary changed:
- colo: secondary vm crash when execute x-colo-lost-heartbeat
+ colo: vm crash with segmentation fault
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1754542
Title:
colo: vm c
17 matches
Mail list logo
