search for: cvm1

Migration without --p2p works just fine, ie. the below works: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+ssh://kashyapc@devstack3/system Migration: [100 %] Result: - On the source host, the guest is shut off - On the destination host, the guest is live migratied successfully Migration with "--p2p" fails, a simple test below: First, I should note, I didn't...

Hello, I am very new to R (as my Subject probably indicates). I want to do something that should, I think, be very simple. I have five vectors in a list and I want to construct a covariance matrix out of them. Given a 5X5 matrix cvm1, and the list of vectors, cvm1_list, I thought the following would work (sorry cannot find code tags): for(i in 1:5){ for(j in 1:5){ cvm1[i,j] <- cov(cvm1_list[[i]], cvm1_list[[j]]) } } (PS. I know this is not the var-cov matrix yet but I though it might be a start.) But I get the error:...

Hi, I'm experimenting with the migration function of virsh. I'm doing the migrate with following commands: virsh migrate --life --persistent --copy-storage-all --verbose --abort-on-error domain qemu+ssh://root@destination/system virsh migrate-setmaxdowntime domain 20000 However sometimes at the end of the migration, the guest isn't started on the destination host. So I'm left

...5 at 10:13:38AM +0200, Kashyap Chamarthy wrote: > On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > > Migration without --p2p works just fine, ie. the below works: > > > > > > $ virsh migrate --verbose --copy-storage-all \ > > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > Migration: [100 %] > > > > [. . .] > > > > > (2) Perform peer to peer live migration (as root): > > > > $ virsh migrate --verbose --p2p --copy-storage-all \ > > --live cvm1 qemu+ssh://ka...

...ate answer on why your guest on destination host doesn't start, but I've previously successfully tested wih qemu+tcp URI and these three variants, without shared storage: (1) Native migration, client to two libvirtd servers $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+tcp://kashyapc@desthost/system (2) Native migration, peer2peer between two libvirtd servers: $ virsh migrate --verbose --copy-storage-all \ --p2p --live cvm1 qemu+tcp://kashyapc@desthost/system (3) Tunnelled migration, peer2peer between two libvirtd servers: $ virsh migra...

On Fri, Apr 03, 2015 at 10:08:21AM +0200, Kashyap Chamarthy wrote: > Migration without --p2p works just fine, ie. the below works: > > > $ virsh migrate --verbose --copy-storage-all \ > --live cvm1 qemu+ssh://kashyapc@devstack3/system > Migration: [100 %] > [. . .] > > (2) Perform peer to peer live migration (as root): > > $ virsh migrate --verbose --p2p --copy-storage-all \ > --live cvm1 qemu+ssh://kashyapc@devstack3/system > > error: op...

...ial consoles on L1s. And I can login to the L2 guest on the destination L1 just fine.) Once you have the password-less SSH between source and destination, and a bit of libvirt config setup. I ran the migrate command as following: $ virsh migrate --verbose --copy-storage-all \ --live cvm1 qemu+tcp://root@f26-vm2/system Migration: [100 %] $ echo $? 0 Full details: https://kashyapc.fedorapeople.org/virt/Migrate-a-nested-guest-08Feb2018.txt (At the end of the document above, I also posted the libvirt config and the version details across L0, L1 and L2. So this is a fully...

...; login to the L2 guest on the destination L1 just fine.) > > Once you have the password-less SSH between source and destination, and > a bit of libvirt config setup. I ran the migrate command as following: > > $ virsh migrate --verbose --copy-storage-all \ > --live cvm1 qemu+tcp://root@f26-vm2/system > Migration: [100 %] > $ echo $? > 0 > > Full details: > https://kashyapc.fedorapeople.org/virt/Migrate-a-nested-guest-08Feb2018.txt > > (At the end of the document above, I also posted the libvirt config and > the version deta...

On 07.02.2018 16:31, Kashyap Chamarthy wrote: > [Cc: KVM upstream list.] > > On Tue, Feb 06, 2018 at 04:11:46PM +0100, Florian Haas wrote: >> Hi everyone, >> >> I hope this is the correct list to discuss this issue; please feel >> free to redirect me otherwise. >> >> I have a nested virtualization setup that looks as follows: >> >> - Host: