search for: virdomainmigratetouri

Hello I am working with 3 host machines each running xen with shared NFS storage. I am working on automatic load balancing if one host is over utilized and another is under utilized by measuring the utilization from xentop. I am facing a problem after migration of VM. I am setting the flags ( 1| 8| 16) in order to do live migration, persist VM on destination, undefine host from source. After

...i did it with "virsh --live migrate <Domain> xen+ssh://root at Destination", it failed and told me something like "Error Domain not found:xenUnifiedDomainLookupByName". The same thing happened when i tried to do the same thing with libvirt API like virDomainMigrate & virDomainMigrateToURI. i am confused about this. So can anybody can tell me why?Thanks a lot. BTW ,my OS is CentOS 5.4 and my hypervisor is xen3.1.2 which is installed with the OS.And the libvirt version is 0.7.7. THANKS A LOT AGAIN. _________________________________________________________________ ????????...

Hi, After recently upgrading to 0.9.11 (as shipped with Fedora 17), I was just trying to migrate a qemu domain from one host to another (using virDomainMigrateToURI()), when I got this error message: Unsafe migration: Migration may lead to data corruption if disks use cache != none Okay, this is explainable (if a bit disappointing - I would have hoped that qemu would be able to disable disk caches before migration and then reenable them afterwards...). Ho...

Hi, is there a reliable way to find out to what kind of job does the information returned from virDomainGetJobStats or provided in VIR_DOMAIN_EVENT_ID_JOB_COMPLETED event callback belong to? I'm specifically interested in distinguishing host-to-host migration jobs (e.g. those started by virDomainMigrateToUri* functions) from other jobs. If there is no better way, I'm thinking about examining presence or values of certain fields in the stats. I'd be fine with that as long as I can be sure it's a reliable way to identify the job kind. Thanks, Milan

...xen4.5. I can creat instance successfully , but live migration is always failed. Error report like this: 2015-05-07 10:47:22.135 1331 ERROR nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Live Migration failure: this function is not supported by the connection driver: virDomainMigrateToURI2 2015-05-07 10:47:22.246 1331 WARNING nova.virt.libvirt.driver [-] [instance: b1081b86-fdce-4fcc-82c4-51896de4418c] Error monitoring migration: this function is not supported by the connection driver: virDomainGetJobInfo 2015-05-07 10:47:22.246 1331 TRACE nova.virt.libvirt.driver [instance: b1081b8...