SASL(-1): generic failure: All-whitespace username - from HA/pacemaker

2020-12-15 Thread lejeczek
Hi guys, I have a HA/pacemaker cluster with VirtualDomain and it all seems to work fine, VMs start & stop, except for live migration. So I thought I'd start here with errors I see, from 'pacemaker': ... All-whitespace username.  notice: vpn1_migrate_to_0[977276] error output [ error:

Re: live migration with authentication - how?

2020-12-15 Thread lejeczek
On 15/12/2020 12:44, Daniel P. Berrangé wrote: On Tue, Dec 15, 2020 at 12:38:39PM +, lejeczek wrote: Hi guys. I'm trying I assumed something very crude, logic suggested I should try it first: $ virsh migrate reactos

live migration with authentication - how?

2020-12-15 Thread lejeczek
Hi guys. I'm trying I assumed something very crude, logic suggested I should try it first: $ virsh migrate reactos qemu+ssh://dzien/system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf Please enter your authentication name: vdsm@ovirt Please enter your password: As you can see I still

Re: live migration with authentication - how?

2020-12-15 Thread Daniel P . Berrangé
On Tue, Dec 15, 2020 at 12:38:39PM +, lejeczek wrote: > Hi guys. > > I'm trying I assumed something very crude, logic suggested I should try it > first: > > $ virsh migrate reactos > qemu+ssh://dzien/system?authfile=/etc/ovirt-hosted-engine/virsh_auth.conf > Please enter your authentication

Re: Libvirt-lxc: iptables not working in containers

2020-12-15 Thread Michal Privoznik
On 12/14/20 12:05 AM, John Hurnett wrote: Hi, I can't get iptables to work in libvirt-lxc containers. "iptables -L" command shows empty chains. However I tested the same scenario with pure lxc and iptables works as it should. Has anyone experienced that? It seems like a bug, but maybe there is

Libvirt-lxc: iptables not working in containers

2020-12-15 Thread John Hurnett
Hi, I can't get iptables to work in libvirt-lxc containers. "iptables -L" command shows empty chains. However I tested the same scenario with pure lxc and iptables works as it should. Has anyone experienced that? It seems like a bug, but maybe there is some libvirt xml parameter I am missing? BR