Migration via qemu+ssh using a given private ssh key possible ?
Oliver Dzombic
info at layer7.net
Tue Jan 5 18:39:49 UTC 2021
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
qemu+ssh://testnode4:22/system?keyfile=/tmp/key-5ff4b02ca966c?no_verify=1?no_tty=1
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:tcF31bWN6Gg8O5bMTkkusbcariPBWjGdLAP7WnfdqsM.
Are you sure you want to continue connecting (yes/no/[fingerprint])?
Should it not accept automatically this unknown fingerprint ?
--
Mit freundlichen Gruessen / Best regards
Oliver Dzombic
Layer7 Networks
mailto:info at layer7.net
Anschrift:
Layer7 Networks GmbH
Zum Sonnenberg 1-3
63571 Gelnhausen
HRB 96293 beim Amtsgericht Hanau
Geschäftsführung: Oliver Dzombic
UST ID: DE259845632
Am 03.01.21 um 13:33 schrieb Peter Krempa:
> On Sat, Jan 02, 2021 at 14:25:32 +0100, Oliver Dzombic wrote:
>> Hi,
>>
>> happy new year!
>>
>> Is there a way to tell libvirt to migrate an instance via qemu+ssh using
>> a specific ssh key ?
>>
>> It seems libvirt will always try to use the .ssh/id_rsa private key.
>>
>> But i would like to somehow tell libvirt to use a specific private ssh
>> key. ( At best via command line argument ).
>
> This can be achieved via the 'keyfile' URI parameter.
>
> See: https://libvirt.org/uri.html#Remote_URI_parameters
>
More information about the libvirt-users
mailing list