+Spice devel mailing list.
On Thu, Jun 21, 2018, 11:57 PM John Florian wrote:
>
> On 2018-06-21 08:20, Michal Skrivanek wrote:
> > Any connectivity issue should no really be dependent on what you do in
> guest
> Agreed
> > Still, please bring that up to SPICE team -
> https://www.spice-space.org
On 2018-06-21 08:20, Michal Skrivanek wrote:
Any connectivity issue should no really be dependent on what you do in guest
Agreed
Still, please bring that up to SPICE team
-https://www.spice-space.org/support.html
I was just trying to do so myself. If I do a Simple Search at
https://bugs.f
> On 21 Jun 2018, at 14:20, Michal Skrivanek
> wrote:
>
>
>
>> On 19 Jun 2018, at 14:17, Hendrik Peyerl wrote:
>>
>> I have found a temporary? solution that seems to be working for us.
>>
>> As I predicted it is indeed the lockscreen that leads to the problem. Per
>> default the VMs will
> On 19 Jun 2018, at 14:17, Hendrik Peyerl wrote:
>
> I have found a temporary? solution that seems to be working for us.
>
> As I predicted it is indeed the lockscreen that leads to the problem. Per
> default the VMs will lock the screen after 10 minutes at which time I was not
> able to co
I have found a temporary? solution that seems to be working for us.
As I predicted it is indeed the lockscreen that leads to the problem. Per
default the VMs will lock the screen after 10 minutes at which time I was not
able to connect to it anymore. Here is how i disabled the lockscreen:
Set i
That is infact a very interesting Information as we basically only run CentOS
VMs, I have tried to connect to our CentOS 7.4 VMs and that actually worked
everytime. I did manage to get an error from the debug output of my
RemoteViewer.app:
GSpice-CRITICAL **: display_handle_monitors_config: ass
Count me affected too, but like others here, only started having
problems after upgrading from 4.1.8 to 4.2.3 . I've also noticed the it
seems to affect mostly/only my CentOS (all 7.5) VMs, but only after
they've been up for a while. I also have several Fedora 27/28 VMs and
those don't seem to be
I've been seeing similar behavior but when running virt-viewer on
windows. I only noticed it after updating to 4.2 but for me it seems to
only happen with guests running CentOS 7.5 and then only after a while
like it's related to the console going blank from being idle. Using
aspice from movi
On 2018-06-18 08:11, Christophe TREFOIS wrote:
We have the same issue potentially.
In fact, for some VMs, we get even an error now (even though it works
from Windows).
In the error log on the hypervisor, we get a “SSL error”. This is in
libvirtd logs.
@Hendrik, do you have perhaps same error?
We have the same issue potentially.
In fact, for some VMs, we get even an error now (even though it works from
Windows).
In the error log on the hypervisor, we get a “SSL error”. This is in libvirtd
logs.
@Hendrik, do you have perhaps same error?
140085012483328:error:140760FC:SSL routines:SS
> you need something like [1]. It was always the case with spice’s client on mac
> If it is only occasionally used on mac, alternatively you can use SPICE+VNC
> and connect to
> VNC on mac an SPICE on linux/windows
>
> Thanks,
> michal
>
> [1] https://github.com/juhoffma/rhev-console-launcher
H
> On 18 Jun 2018, at 11:09, hpey...@plusline.net wrote:
>
> Hi all,
>
> we are currently experiencing a weird problem with oVirt and the spice
> console on MacOS:
> Occasionally when our Mac Users are connecting to a Spice Console of any
> oVirt VM it opens the usual window but just displays
12 matches
Mail list logo