Hello, I need this feature too, so I made myself the more general solution. Attached patch sets the fourth argument of the hook to 3 differnent values: "migration-target-direct", "migration-target-tunnel" and "restore". On 12/16/2011 02:48 AM, Adam Tilghman wrote:
On Thu, Dec 15, 2011 at 11:32:23PM +0000, Daniel P. Berrange wrote:
Rather, we need to thread something through the call chain so that we can tell whether this code was reached from qemu_migrate.c during an actual migration case.
That information is in fact already passed into qemuProcessStart() via the virDomainRunningReason parameter, one of whose possible values is VIR_DOMAIN_RUNNING_MIGRATED
I'll take a stab at a more general solution and get back to the list.
-- Adam
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- С уважением, Роман Шишнёв, CTO | ActiveCloud | http://www.active.by Т +375 17 2 911 511 доб. 308 | rommer@active.by Облачные решения | Серверы и инфраструктура | IaaS | SaaS | Хостинг