search for: vir_domain_block_rebase_copi

Hi. I am using openstack, ceph and libvirt now. The live volume migration will call the libvirt rebase function in openstack nova project. https://github.com/openstack/nova/blob/stable/rocky/nova/virt/libvirt/driver.py#L1497 https://github.com/openstack/nova/blob/stable/rocky/nova/virt/libvirt/guest.py#L802 But I use the ceph as the openstack block backend. And the type of

On Fri, Nov 02, 2018 at 13:42:56 +0800, Boxiang Zhu wrote: > > > Hi. > I am using openstack, ceph and libvirt now. > > > The live volume migration will call the libvirt rebase function in openstack nova project. > https://github.com/openstack/nova/blob/stable/rocky/nova/virt/libvirt/driver.py#L1497 >

Thanks for your reply. The nova project uses the virDomainBlockRebase API to finish the rebase operation from the old disk to the new disk not using the virDomainBlockCopy API. I am confused of the difference of virDomainBlockRebase and virDomainBlockCopy. Cheers, Boxiang On 11/5/2018 22:07，Peter Krempa<pkrempa@redhat.com> wrote： On Fri, Nov 02, 2018 at 13:42:56 +0800, Boxiang Zhu wrote:

I'm currently running: virsh --version 1.0.2 libvirtd --version libvirtd (libvirt) 1.0.2 I have a couple questions. 1. Can I upgrade my libvirt.so version to use with an older libvirtd? In other words, does the versions of libvirt and libvirtd need to be in lock step? 2. I'm able to use virsh blockcopy, but I want to do it programmatically via C. I looked through the API and was not

On 12/20/2013 11:45 AM, Mark Trinh wrote: > I'm currently running: > virsh --version > 1.0.2 > > libvirtd --version > libvirtd (libvirt) 1.0.2 > > I have a couple questions. > > 1. Can I upgrade my libvirt.so version to use with an older libvirtd? In > other words, does the versions of libvirt and libvirtd need to be in lock > step? No, they do not have