i want to know the 'network-vif-plugged' signal which was waiting for source node should be trigger by what or where? I think the signal was trigger by the linuxbridge-agent of destination node, after the vif tap device was scan by the linuxbridge-agent of dest node, the linuxbridge agent can send 'network-vif-plugged' by method notify_port_active_direct(). but how the linuxbridge agent can scan the new tap device in dest node? I found the source node should have received the signal of 'network-vif-plugged', and run guest.migration(), the VM started in dest, and NOW the tap device can be created. I found this is a dead circle. I think there is any problem in proccess of live migration,thx.
Hi Sean,
i want to know the 'network- vif-plugged' signal which was waiting for source node should be trigger by what or where? I think the signal was trigger by the linuxbridge-agent of destination node, after the vif tap device was scan by the linuxbridge-agent of dest node, the linuxbridge agent can send 'network- vif-plugged' by method notify_ port_active_ direct( ). but how the linuxbridge agent can scan the new tap device in dest node? I found the source node should have received the signal of 'network- vif-plugged' , and run guest.migration(), the VM started in dest, and NOW the tap device can be created. I found this is a dead circle. I think there is any problem in proccess of live migration,thx.