search for: undefinesource

Hi, We have been trying to get live migration working between two xen boxes running libvirt 1.2.12, However i seem to be getting the following error root@libvirt-xen1:~# virsh migrate --live trusty-image qemu+ssh://192.168.13.9/system --copy-storage-all --verbose --persistent --undefinesource root@192.168.13.9's password: error: unsupported flags (0x48) in function libxlDomainMigrateBegin3Params root@libvirt-xen1:~# virsh migrate --live trusty-image xen+ssh://192.168.13.9/system --copy-storage-all --verbose --persistent --undefinesource root@192.168.13.9's password: error: unsu...

...including both source host and target host? I try to get some info from your website, but no info with migrate. [root at vmoactive02 qemu]# virsh help migrate NAME migrate - migrate domain to another host SYNOPSIS migrate [--live] [--p2p] [--direct] [--tunnelled] [--persistent] [--undefinesource] [--suspend] [--copy-storage-all] [--copy-storage-inc] <domain> <desturi> [<migrateuri>] [<dname>] DESCRIPTION Migrate domain to another host. Add --live for live migration. OPTIONS --live live migration --p2p peer-2-peer migration...

...ptions are for migrating a KVM machine to another KVM machine, without using shared storage. The documentation is not quite verbose and not intuitive, so I'm hoping someone can explain this to me. The man pages show this syntax: migrate optional --live --p2p --direct --tunnelled --persistent --undefinesource --suspend --copy-storage-all --copy-storage-inc domain-id desturi migrateuri dname The 'live' and 'suspend' options are clear. The 'undefinesource' option is straightforward as well. But what does 'persistent' mean? I mean, when transferring a VM to a destination,...

On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: internal error: Failed to reserve port" error is received and migration does not succeed: virsh # migrate cartridge qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose error: internal error: Failed to reserve port 49153 virsh # On target host with debug logs, nothing interesting but the error itself is found in the logs ... 2020-10-12 02:11:33.852+0000: 6871: debug : qemuMonitorJSONIOProcessLine:220 : Line [{"return": {},...

...virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> Now i'm calling: root@host_a:~# virsh migrate --verbose --p2p --copy-storage-all --persistent --change-protection --abort-on-error --undefinesource --live domain qemu+ssh://root@host_b/system --xml domain.ceph.xml This takes its time to copy everything into ceph, but when its over, i never have to migrate Terabytes of Storage again. But its not over. The new domain definition on host_b is not persistent and after a shutdown, local storage is...

Hi, These are my doubts: 1. I tried live migration of Ubuntu 11.04 from the one physical machine to another using the migrate() function. I connected via tcp in the destination URI and migrated successfully(lesser than 2 seconds). I tried running virsh list --all on the destination PM and confirmed that the VM had been migrated successfully. When I tried checking ps aux | grep vmname where

...as well when transferring? Would be useful to be able to migrate big guests using the full capacity of the 10gb nics. Our example command to migrate: # virsh migrate --compressed --comp-methods mt --comp-mt-level 9 --comp-mt-threads 16 --comp-mt-dthreads 16 --verbose --live --copy-storage-all --undefinesource --unsafe --persistent dev-testvm790.mydomain.net qemu+tcp://myhost-10g.mydomain.net/system

On 05/30/2016 09:07 AM, Dominique Ramaekers wrote: >> root@host_a:~# virsh migrate --verbose --p2p --copy-storage-all --persistent -- >> change-protection --abort-on-error --undefinesource --live domain >> qemu+ssh://root@host_b/system --xml domain.ceph.xml > > Weird: The domain should be persistent Well, the domain is persistent. But the changes i did to domain.ceph.xml to migrate the storage to ceph are not. > You can make an transient domain persistent by doing a...

...gt;> On libvirt 6.8.0 and qemu 5.1.0, when trying to live migrate "error: >> internal error: Failed to reserve port" error is received and >> migration does not succeed: >> >> virsh # migrate cartridge qemu+tls://ratchet.lan/system --live >> --persistent --undefinesource --copy-storage-all --verbose >> error: internal error: Failed to reserve port 49153 >> >> virsh # >> > > Sorry for not replying earlier. But this is a clear libvirt bug and I > think it's a regression introduced by the following commit: > > https://gitl...

Hello, I have been trying to migrate a guest from one host to another. But it is showing this error: virsh --connect qemu+ssh://root at host1/system migrate --live --undefinesource testvm3 qemu+ssh://root at host2/system tcp://host2:48160 error: operation failed: failed to retrieve chardev info in qemu with 'info chardev' I have tried this command from the host1 also but it shows the same error. Another thing i would like to ask is the that whats the use of migrateu...

...storage and I also have found some persons give their experiments, for example: （http://blog.allanglesit.com/2011/08/linux-kvm-management-live-migration-without-shared-storage/） # virsh migrate --live vmname qemu+ssh://kvmnode02.allanglesit.net/system --copy-storage-all --verbose --persistent --undefinesource I repeated the above experiment, but I failed. I want to know I need which version of qemu and libvirt and how the progress of the new feature.

...from one host to another host. It seems that the live migration of OpenVZ container is there ( https://openvz.org/Migration_from_one_HN_to_another), but it haven't been integrated to libvirt yet. In particular, I ran the following commands and it failed: $ sudo virsh migrate --live --verbose --undefinesource 101 openvz+ssh:// root@10.12.1.39/system error: this function is not supported by the connection driver: virDomainMigrate3 Could anyone confirm if libvirt supports live migration of OpenVZ domain. If yes, please let me know the correct way to do that. If no, I would like to know if there is a plan...

...all. However, I found that since by default virt-manager leaves the VM defined on both the source and destination, I'm actually able to start the VM in both places. I didn't see an option to disable that, so I just wrote a simple wrapper script to do the right thing via virsh using --undefinesource, but I can't guarantee that some other admin might not skip that and just use the GUI. It appears that libvirt (or is it qemu?) doesn't set rbd locks on the disk image files by default. After running across [2], I had originally thought about writing some hooks to set and release lock...

...log_filters="3:remote 4:event 3:util.json 3:rpc 1:*" log_outputs="1:file:/var/log/libvirt/libvirtd.log" qemu: default_tls_x509_cert_dir = "/etc/ssl/qemu" default_tls_x509_verify = 1 migration with tls: virsh # migrate vm1 qemu+tls://server2.lan/system --persistent --undefinesource --copy-storage-all --verbose --tls never succeeds. Progress stops typically at high progress amounts (95%-98%), and network traffic drastically drops as well (from 1 gbps+ to nothing). domjobinfo progress also stops. Without --tls migrations succeed without issues without any other changes to host...

...bvirt-glib-0.2.3-1.el7.x86_64 libvirt-python-2.0.0-2.el7.x86_64 qemu-img-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-common-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-ev-2.6.0-28.el7_3.6.1.x86_64 qemu-kvm-tools-ev-2.6.0-28.el7_3.6.1.x86_64 My command is: virsh migrate --live --copy-storage-all --persistent --undefinesource --tunnelled --p2p --verbose --xml server.xml server qemu+ssh://xxx at a.b.c.d/system Any help would be greatly appreciated. Thanks, Valentin

...then enlarge the disk using steps in 1). Please refer to the docs of > > live migration. > > I use normally something like this, because in my case every fysical > server has it's own storage: > > virsh migrate --live --p2p --copy-storage-inc --persistent \ > --undefinesource --verbose $vm qemu+ssh://$other/system > > A point is that I have to create disk(s) on the other side with > qemu-img, I did not found a way to do that automatically. My question We are able to pre-create the storage given that a full copy is requested (copy-storage-all, not copy-storage...

...;nee"; then echo "rsync..." rsync /data/$vm.qcow2 $other://data/$vm.qcow2 if test $? = 0; then echo "gelukt"; else echo "niet gelukt"; exit; fi fi # migrate echo "migrate..." virsh migrate --live --p2p --tunnelled --copy-storage-inc --persistent --undefinesource --verbose $vm qemu+ssh://$other/system if test $? = 0; then echo "gelukt"; else echo "niet gelukt"; exit; fi ----------- -- Paul van der Vlis Linux systeembeheer Groningen https://www.vandervlis.nl/

Hi , when i have run virsh migrate command , the migration progress fiailed at [61 %]. command : virsh migrate --live --undefinesource --p2p --copy-storage-inc --verbose --persistent instance-00001959 qemu+tcp://host292/system result : Migration: [ 61 %]error: operation failed: migration job: unexpectedly failed os/kernel version: centos 6.7 / kernel 2.6.32 qemu-kvm version : 0.12.1.2 libvirt version : 0.10.2...

...have a couple of questions. 1) It appears that in some cases modified default_tls_x509_cert_dir from qemu.conf is not respected, seems like virsh always expects a default location and does not check default_tls_x509_cert_dir: virsh # migrate vm1 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --verbose --tls error: internal error: unable to execute QEMU command 'object-add': Unable to access credentials /etc/pki/qemu/ca-cert.pem: No such file or directory It's checking /etc/pki and not the location specified in default_tls_x509_cert_dir. Is this a bug or...

Hey all, With libvirt 6.5.0 and qemu 5.1.0 migration of non shared disks in tunneled mode does not work for me: virsh # migrate alpinelinux3.8 qemu+tls://ratchet.lan/system --live --persistent --undefinesource --copy-storage-all --tunneled --p2p error: internal error: qemu unexpectedly closed the monitor: Receiving block device images Error unknown block device 2020-08-15T21:21:48.995016Z qemu-system-x86_64: error while loading state section id 1(block) 2020-08-15T21:21:48.995193Z qemu-system-x86_64: loa...