Chris, Thanks for the reply. > what memory state do you refer to exactly? What I meant by the memory state is the traffic being transferred through the vNIC when VM migration is triggered. If this memory state (or traffic) is not copied and moved to the destination vNIC how the smooth communication, which is guaranteed on VM migration, is achieved? Thanks Jagath > > If you refer to port profile info, then there is no copying involved: > the source host disassociates the vnic port profile and > the destination host re-associates the port profile on the new vnic. > > /Chris > >> -----Original Message----- >> From: libvir-list-bounces@xxxxxxxxxx > [mailto:libvir-list-bounces@xxxxxxxxxx] On Behalf Of Jagath >> Weerasinghe >> Sent: Friday, April 13, 2012 9:16 AM >> To: libvir-list@xxxxxxxxxx >> Subject: VN-Link vNIC memory state copying on VM Migration >> >> Hi All, >> >> I am new to libvirt. And want to know how the VM migration >> occurs in VN-Link (IEEE802.1Qbh). As far as I know, >> the memory state of vNICs in M81KR VIC has to be copied >> and moved to the destination vNIC on VM migration. >> Is that correct? If so, could you please tell me how this >> has been implemented in libvirt? >> >> Thanks >> Jagath >> >> -- >> libvir-list mailing list >> libvir-list@xxxxxxxxxx >> https://www.redhat.com/mailman/listinfo/libvir-list -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list