colo: secondary vm can't receive any packet

Bug #1702798 reported by junchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QEMU
Expired
Undecided
Unassigned

Bug Description

Following document 'COLO-FT.txt', I test colo feature on my hosts. It seems goes well,but I found the secondary vm can't receive any packets. I attached the process and find out the reason as follow, the filter-redirector(red0) didn't flush it's queue because the secondary vm in migrate state(RUN_STATE_INMIGRATE) :
int qemu_can_send_packet(NetClientState *sender)
{
    int vm_running = runstate_is_running():

    if (!vm_running) { // it will return false on the secondary vm
        return 0;
    }
    ------
}

How does it produce outbound packets in the secondary vm as it in migrate state?
static void *qemu_kvm_cpu_thread_fn(void *arg)
{
    ------
    do {
        if (cpu_can_run(cpu)) { // it will return false on the secondary vm
            r = kvm_cpu_exec(cpu);
    ------
}

Revision history for this message
junchi (pork-prince) wrote :

The qemu version is 2.9.0 release.
The secondary vm state make me confused. I tried to add vm_stop and vm_start in colo_process_incoming_thread function, but it crashed.

Revision history for this message
Zhang Chen (zhangckid) wrote :

In qemu upstream COLO project can not fully running, you can test my internal branch.
https://github.com/zhangckid/qemu/commits/colo-with-virtio-net-internal-jul10

Thanks
Zhang Chen

Revision history for this message
Thomas Huth (th-huth) wrote :

The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Thank you and sorry for the inconvenience.

Changed in qemu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for QEMU because there has been no activity for 60 days.]

Changed in qemu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.