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 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
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
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.
