search for: vir_migrate_l

...7997: error : doPeer2PeerMigrate:2527 : operation failed: Failed to connect to remote libvirt URI qemu+tcp://n12c1/system I execute migration like this: nova live-migration c923af69-4cb3-46dd-8bd2-871812d7d223 n12c1 Nova.conf: live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE Could you please let me know whether nova/libvirt support p2p live migration with sasl and if so point out what might be misconfigured? Disabling sasl solves all my problems but I have to configure some authentication. I would really appreciate your help. regards -- Maciej Ga?kiewicz Shelly...

...), I try find solution on Internet, I find someone say host uuid same, But virsh sysinfo output uuid is different, when I change one host's hostname, migrate success. I wish know why, and Can I solution this problem not change hostname. My program use api virDomainMigrateToURI2, flag arg is VIR_MIGRATE_LIVE | VIR_MIGRATE_PEER2PEER . I use virsh migrate --live --p2p. Thanks

...t;.) Is there anything I can do to prevent this? Is there a fix for this coming? MORE DETAILS: I open a connection to a remote libvirt instance and begin a live-migration using: domain.migrate(remoteCon, flags, None, None, 0) My flags are: flags = libvirt.VIR_MIGRATE_PEER2PEER | libvirt.VIR_MIGRATE_LIVE | libvirt.VIR_MIGRATE_UNDEFINE_SOURCE | libvirt.VIR_MIGRATE_TUNNELLED Thanks, --Igor -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: <http://listman.redhat.com/archi...

...hine #1. I am unable to migrate the VM back to machine #2 using virDomainMigrate(), even if I first migrate the VM from #2 to #1 by hand, using "xm migrate -l <vmname> <ipaddress1>". When I make the call to virDomainMigrate(domain_to_migrate, connection_to_machine_2, VIR_MIGRATE_LIVE, NULL, NULL, 0), I get the following message: libvir: Xen Daemon error : POST operation failed: xend_post: error from xen daemon: (xend.err "can''t connect: Name or service not known") I have tried running my program on both machine #2 (connecting to machine #1 with ssh...

...or: Xen 3.2.0 The goal is to have the migration done in only one call, including a definition in the remote xend and undefinition from the source, which requires the VIR_MIGRATE_PERSIST_DEST and VIR_MIGRATE_UNDEFINE_SOURCE flags. Here's the code doing the migration: ---------- flags = (libvirt.VIR_MIGRATE_LIVE ^ libvirt.VIR_MIGRATE_PERSIST_DEST ^ libvirt.VIR_MIGRATE_UNDEFINE_SOURCE) uri = 'xenmigr://remote.host.com:8002' domain_obj.migrate(con_handle, flags, None, uri, 0) ---------- There are various problems that occur randomly, such as the VM completely disappearing 5 seco...

...> operation failed: Failed to connect to remote libvirt URI > qemu+tcp://n12c1/system > > I execute migration like this: > nova live-migration c923af69-4cb3-46dd-8bd2-871812d7d223 n12c1 > > Nova.conf: > live_migration_flag=VIR_MIGRATE_UNDEFINE_SOURCE,VIR_MIGRATE_PEER2PEER,VIR_MIGRATE_LIVE > > Could you please let me know whether nova/libvirt support p2p live > migration with sasl and if so point out what might be misconfigured? > Disabling sasl solves all my problems but I have to configure some > authentication. > > I would really appreciate your help. &gt...

...eer) connection between nodes (a third connection isn't possible because of firewalls and SSH keys). Is this actually possible? I've been playing with the API and reading docs, and it seems like "direct managed" migration is simply not possible :-( dom.migrate (dconn, libvirt.VIR_MIGRATE_LIVE|libvirt.VIR_MIGRATE_TUNNELLED) libvirt.libvirtError: Requested operation is not valid: cannot perform tunnelled migration without using peer2peer flag Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://r...

...s migration speed. The code is: def virt_migrate(domain): conn = libvirt.open('qemu:///system') domain_obj = conn.lookupByName(domain) dst='qemu+ssh://root@%s/system' % args.remote domain_obj.migrateSetMaxSpeed(40,0) new_dom = domain_obj.migrateToURI(dst,libvirt.VIR_MIGRATE_LIVE | libvirt.VIR_MIGRATE_PEER2PEER | libvirt.VIR_MIGRATE_NON_SHARED_INC | libvirt.VIR_MIGRATE_PERSIST_DEST | libvirt.VIR_MIGRATE_UNDEFINE_SOURCE, None, 0) conn.close() Also tried to specify bandwidth at migrateToUri- I still get 10 mib/s at any value... Thanks in advance!

...it as: dom.migrateToURI2(duri, muri, xml_str, logical_sum, None, CONF.live_migration_bandwidth) Here are the supplied arguments: duri = u'qemu+tcp://compute-0/system' muri = u'tcp://compute-0' flaglist = ['VIR_MIGRATE_UNDEFINE_SOURCE', 'VIR_MIGRATE_PEER2PEER', 'VIR_MIGRATE_LIVE'] logical_sum = 19, (logical OR of flaglist) CONF.live_migration_bandwidth = 0 Grabbing original XML prior to migration: dom_xml = etree.fromstring(dom.XMLDesc(0)) xml_str = etree.tostring(dom_xml) xml_str (BEFORE) = <domain type="qemu" id="2"> <name>ins...

...domain.undefine() + def migrate_domain(self, name, target): + '''Migrates the specified domain to the target machine.''' + target_conn = libvirt.open(target) + virtmachine = self.get_domain(name) + virtmachine.migrate(target_conn, libvirt.VIR_MIGRATE_LIVE, None, None, 0) + def list_networks(self, defined = True, started = True): '''Lists all networks.''' result = [] diff --git a/nodeadmin/migratedomain.py b/nodeadmin/migratedomain.py new file mode 100644 index 0000000..8c8c268 --- /dev/null +++ b/nod...

Hi, We've run into a problem with libvirt 1.1.2 and are looking for some comments on whether this is a bug or design intent. We're trying to use migrateToURI() but we're using a few things (numatune, vcpu mask, etc.) that may need adjustment during the migration. We found that migrateToURI2() mostly works if we use XML created by copying the domain XML from the running instance

The previous patch set had an error and one development branch's changes showed up twice, and two different change sets. So it was missing the bulk of the configuration work. This patch set fixes that.

..._val (optdnamev); + const char *uri = Optstring_val (opturiv); + unsigned long bandwidth; + virDomainPtr r; + + /* Iterate over the list of flags. */ + for (; flagsv != Val_int (0); flagsv = Field (flagsv, 1)) + { + flagv = Field (flagsv, 0); + if (flagv == Val_int (0)) + flags |= VIR_MIGRATE_LIVE; + } + + if (optbandwidthv == Val_int (0)) /* None */ + bandwidth = 0; + else /* Some bandwidth */ + bandwidth = Int_val (Field (optbandwidthv, 0)); + + NONBLOCKING (r = virDomainMigrate (dom, dconn, flags, dname, uri, bandwidth)); + CHECK_ERROR (!r, "virDomainMigrate")...

libvirt-ocaml is used only by virt-v2v, so move it to this repository, instead of having it around in the common submodule. The removal from common will happen later. Pino Toscano (2): common: Bundle the libvirt-ocaml library for use by virt-v2v build: switch embedded copy of libvirt-ocaml .gitignore | 2 + 3rdparty/libvirt-ocaml/Makefile.am |

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this is a mostly done attempt to switch to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all

Hi, this series switches virt-2v to ocaml-libvirt, embedding the latest version of it from git. This way, it is possible to improve the way v2v connects to libvirt for both input, and output modules, and interacts with libvirt (e.g. no more virsh calls needed in virt-v2v). As side effect, virt-v2v now requires libvirt, as keeping it optional would create too much burden. I could not test all