These hosts are in the QA lab, and only accessible via a SSH proxy. Firewalls are certainly in place, but no custom libvirt customisation to my knowledge. We can get you access if you need.
Interestingly, via the proxy I get this:
[cerdea-aws]cerdea@xango3:~$ virsh -c qemu+ssh://aldebaran/system list --all
error: packet 1550146349 bytes received from server too large, want 262144
error: failed to connect to the hypervisor
[cerdea-aws]cerdea@xango3:~$
And, if I am local at aldebaran:
cerdea@aldebaran~:$ virsh -c qemu+ssh://aldebaran/system list --all
cerdea@aldebaran's password:
Id Name State
----------------------------------
1058 8913cfbf-4757-491f-b8c5-02df75d18f6e running
Hi Serge,
These hosts are in the QA lab, and only accessible via a SSH proxy. Firewalls are certainly in place, but no custom libvirt customisation to my knowledge. We can get you access if you need.
Interestingly, via the proxy I get this:
[cerdea- aws]cerdea@ xango3: ~$ virsh -c qemu+ssh: //aldebaran/ system list --all aws]cerdea@ xango3: ~$
error: packet 1550146349 bytes received from server too large, want 262144
error: failed to connect to the hypervisor
[cerdea-
And, if I am local at aldebaran:
cerdea@aldebaran~:$ virsh -c qemu+ssh: //aldebaran/ system list --all ------- ------- ------- ------ 4757-491f- b8c5-02df75d18f 6e running
cerdea@aldebaran's password:
Id Name State
-------
1058 8913cfbf-
cerdea@aldebaran:~$