The only problem with spice certs in oVirt I remember over the last 5
years concerns certificate encoding - which bit only users who used
non-ascii characters in Organization. The bugs (private RHEV
unfortunately) should be fixed for quite some time - and the fix
involved certificate regeneration.
any suggestions on how to get ovirt and spice console keys to work
correctly?
On 03/07/2016 10:09 AM, Bill James wrote:
thanks for the reply.
I tried reinstall of one host. Didn't help.
Also tried removing the host and reinstalling it. Didn't help.
Looks like server cert & key were
thanks for the reply.
I tried reinstall of one host. Didn't help.
Also tried removing the host and reinstalling it. Didn't help.
Looks like server cert & key were regenerated, but not ca-cert.pem.
[root@ovirt2 test ~]# ls -rtl /etc/pki/vdsm/libvirt-spice|grep -v 2016|tail
total 84
-rw-r--r-- 1
Hi,
it looks like you messed up private key location and/or contents. If you
"Reinstall" the host in ovirt engine, the keys/certs should get
regenerated.
David
On Pá, 2016-03-04 at 10:16 -0800, Bill James wrote:
> I needed to bounce libvirtd after changing a config in libvirt/qemu.conf
> so
I needed to bounce libvirtd after changing a config in libvirt/qemu.conf
so import-to-ovirt.pl,
but now my VMs with Spice console complain:
libvirtError: internal error: process exited while connecting to
monitor: ((null):2791): Spice-Warning **: reds.c:3311:reds_init_ssl:
Could not use
5 matches
Mail list logo
