On Wed, Jan 06, 2021 at 04:36:46PM +0100, Peter Krempa wrote:
> On Wed, Jan 06, 2021 at 17:16:24 +0200, Nir Soffer wrote:
> > On Wed, Dec 2, 2020 at 4:57 PM Joy Li wrote:
>
> [...]
>
> > Comparing to state before reboot:
> >
> > # virsh -r domblklist disk-mapping
> > Target Source
> > --
On Wed, Jan 06, 2021 at 17:16:24 +0200, Nir Soffer wrote:
> On Wed, Dec 2, 2020 at 4:57 PM Joy Li wrote:
[...]
> Comparing to state before reboot:
>
> # virsh -r domblklist disk-mapping
> Target Source
>
On Wed, Dec 2, 2020 at 4:57 PM Joy Li wrote:
>
> Thanks a lot Nir! Good to know that oVirt cannot guarantee the disk names so
> that I don't need to spend more time trying to enable such a feature.
>
> I can always reproduce the problem via my application, basically, the
> procedure is as follow
On Tue, Jan 05, 2021 at 07:39:49PM +0100, Oliver Dzombic wrote:
> Hi Peter,
>
> thank you very much for this hint. Seems to work! :)
>
> But i also tried another switch: no_verify=1
>
> The whole call:
>
> virsh -K0 -k0 migrate --copy-storage-inc --verbose --persistent --live
> testInstance
> q
On Tue, Jan 05, 2021 at 19:39:49 +0100, Oliver Dzombic wrote:
> Hi Peter,
[...]
> So as you can see
>
> no_verify=1
> no_tty=1
>
> has been added.
>
> But still i receive
>
>
> The authenticity of host '[testnode4]:22 ([10.0.1.4]:22)' can't be
> established.
> ECDSA key fingerprint is SHA256
