similar to: Should domain be undefined after migration, or not?

On Sun, Jan 19, 2014 at 10:03:36PM +0600, Brian Candler wrote: > I have been running a lab using libvirt under Debian Wheezy (libvirt > 0.9.12.3-1, qemu-kvm 1.1.2+dfsg-6, virt-manager 0.9.1-4). There are > a number of machines as front-end servers and an nbd shared storage > backend. > > When I live-migrate a domain from one machine to another, normally I > observe that

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

Hi libvirt support, Can you please give me some example of how to use "virsh migrate --live" with p2p option 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]

Hi, I've recently been working on setting up a set of libvirt compute nodes that will be using a ceph rbd pool for storing vm disk image files. I've got a couple of issues I've run into. First, per the standard ceph documentation examples [1], the way to add a disk is to create a block in the VM definition XML that looks something like this: <disk type='network'

TLDR: Why is virsh migrate --persistent --live domain qemu+ssh://root@host/system --xml domain.ceph.xml not persistent and what could i do about it? Hi, after years of beeing pleased with local storage and migrating the complete storage from one host to another, it was time for ceph. After setting up a cluster and testing it, its time now for moving a lot of VMs on that type of storage, without

On 04/24/2015 02:02 PM, mimicafe@gmail.com wrote: > On Centos 6.5 both packages cannot be identified. any idea? > > Yes. CentS 6 uses libvirt-0.10.2 + a ton of backported patches. The splitting of libvirt into a bunch of smaller subpackages so that admins could more easily tailor what was installed on their systems happened [sometime after that, not motivated to look up the exact version

Il 25-08-2017 08:32 Gionatan Danti ha scritto: > Hi all, > any other advice from who use (or do not use) Gluster as a replicated > VM backend? > > Thanks. Sorry, I was not seeing messages because I was not subscribed on the list; I read it from the web. So it seems that Pavel and WK have vastly different experience with Gluster. Any plausible cause for that difference? > WK

Hello, I configured libvirtd with the sanlock lock manager plugin: # rpm -qa | egrep "libvirt-0|sanlock-[01]" libvirt-lock-sanlock-0.9.4-23.el6_2.4.x86_64 sanlock-1.8-2.el6.x86_64 libvirt-0.9.4-23.el6_2.4.x86_64 # egrep -v "^#|^$" /etc/libvirt/qemu-sanlock.conf auto_disk_leases = 1 disk_lease_dir = "/var/lib/libvirt/sanlock" host_id = 4 # mount | grep sanlock

On 02/19/2014 10:01 AM, Niccolo Rigacci wrote: > On Tue, Feb 18, 2014 at 09:49:06AM -0500, Cole Robinson wrote: >> >> What libvirt and qemu version are you using? > > I'm on a Debian 7.4 Wheezy (Stable): > > libvirt: 0.9.12.3-1 > qemu: 1.1.2+dfsg-6a > > It seems that Debian has more recent versions, via the backports > repository. I will test them

I am trying to work out what all the options 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

Il 23-08-2017 18:51 Gionatan Danti ha scritto: > Il 23-08-2017 18:14 Pavel Szalbot ha scritto: >> Hi, after many VM crashes during upgrades of Gluster, losing network >> connectivity on one node etc. I would advise running replica 2 with >> arbiter. > > Hi Pavel, this is bad news :( > So, in your case at least, Gluster was not stable? Something as simple > as an

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

Hello, I wonder what the "open error -1" / "release open_disk error" messages in sanlock.log actually mean. I saw these messages in the log on a KVM host that rebooted, and after running "/usr/sbin/virt-sanlock-cleanup" on that host. The resources where disks from 2 guests running on another KVM host. So in fact the disks are still in use, bot got cleaned up by

Hi libvirt team, I was trying to migrate an OpenVZ domain 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://

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

Hello, I'm using libvirt and sanlock on qemu-kvm guests. Each guest has it's own Logical Volume for it's root filesystem. Sanlock is configured and working and prevents me from starting the same VM twice on multiple nodes and corrupting it's root filesystem. Each VM's domain XML resides on 2 servers that share the LVM volume group over fiber channel. In testing, I noticed

Dear All, I have upgrade my hypervisors: qemu-kvm 0.12.5 => 1.1.2 libvirt-bin 0.8.3-5 => 0.9.12.3 (debian6 to debian7) After that upgrade, i noticed that live migration was most of the time failing (freeze) (not always) I also noticed that creating a machine with the updated hypervisor was always working. After some days of

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