Dear Libvirt Developers,
I'm working to implement feature request [1]. The feature request proposes
to enhance `libvirt' code so the API caller can specify which block devices
are to be migrated using e.g. parameters in the `virDomainMigrateToURI3'
call.
There is the following issues:
1. It
On 26.03.2015 15:48, Pavel Boldin wrote:
> Dear Libvirt Developers,
>
>
> I'm working to implement feature request [1]. The feature request proposes
> to enhance `libvirt' code so the API caller can specify which block devices
> are to be migrated using e.g. parameters in the `virDomainMigrateToU
Michal,
On Wed, Apr 15, 2015 at 10:54 AM, Michal Privoznik
wrote:
> On 26.03.2015 15:48, Pavel Boldin wrote:
> > Dear Libvirt Developers,
> >
> >
> > I'm working to implement feature request [1]. The feature request
> proposes
> > to enhance `libvirt' code so the API caller can specify which blo
On 15.04.2015 16:38, Pavel Boldin wrote:
> Michal,
>
> On Wed, Apr 15, 2015 at 10:54 AM, Michal Privoznik
> wrote:
>
>> On 26.03.2015 15:48, Pavel Boldin wrote:
>>> Dear Libvirt Developers,
>>>
>>>
>>> I'm working to implement feature request [1]. The feature request
>> proposes
>>> to enhance `
On Wed, Apr 15, 2015 at 6:43 PM, Michal Privoznik
wrote:
> On 15.04.2015 16:38, Pavel Boldin wrote:
> > Michal,
> >
> > On Wed, Apr 15, 2015 at 10:54 AM, Michal Privoznik
> > wrote:
> >
> >> On 26.03.2015 15:48, Pavel Boldin wrote:
> >>> Dear Libvirt Developers,
> >>>
> >>>
> >>> I'm working to
> That's why I've chosen to work purely with disk target at NBD level. We
> have strong rules what characters can occur there. Moreover, it's fairly
> easy to derive qemu disk ID from the target. Oh, and we require targets
> to be unique throughout the domain. So I think it's the best option for
>
