<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hello Gianluca.</p>
<p>As I mentioned previously I am not sure it has anything to do
with SPICE at all, but with the amount of memory the VM has
assigned to it. Proff of it is that when you access with via any
Remote Desktop protocol it remains slow as if the amount of video
memory wasnt being enough and have seen it crashing several times
as well.</p>
<p>Fernando<br>
</p>
<br>
<div class="moz-cite-prefix">On 07/03/2018 16:59, Gianluca Cecchi
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAG2kNCzLa=vvbUxScZe_=wZ0G1OAwF=TZFS8nbOuPXjq6o9CwA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Mar 7, 2018 at 7:43 PM,
Michal Skrivanek <span dir="ltr"><<a
href="mailto:michal.skrivanek@redhat.com"
target="_blank" moz-do-not-send="true">michal.skrivanek@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space"><br>
<div><span class=""><br>
<blockquote type="cite">
<div>On 7 Mar 2018, at 14:03, FERNANDO FREDIANI
<<a href="mailto:fernando.frediani@upx.com"
target="_blank" moz-do-not-send="true">fernando.frediani@upx.com</a>>
wrote:</div>
<br
class="m_-2928413078620554861Apple-interchange-newline">
<div>
<div text="#000000" bgcolor="#FFFFFF">
<p>Hello Gianluca</p>
<p>Resurrecting this topic. I made the changes
as per your instructions below on the Engine
configuration but it had no effect on the VM
graphics memory. Is it necessary to restart
the Engine after adding the
20-overload.properties file ? Also I don't
think is necessary to do any changes on the
hosts right ?</p>
</div>
</div>
</blockquote>
</span>correct on both<span class=""><br>
</span></div>
</div>
</blockquote>
<div><br>
<br>
</div>
<div>Hello Fernando and Michal,<br>
</div>
<div>at that time I was doing some tests both with plain
virt-manager and oVirt for some Windows 10 VMs.<br>
</div>
<div>More recently I haven't done anything in that regard
again, unfortunately.<br>
</div>
<div>After you have done what you did suggest yourself and
Michal confirmed, then you can test powering off and then
on again the VM (so that the new qemu-kvm process starts
with the new parameters) and let us know if you enjoy
better experience, so that we can ask for adoption as a
default (eg for VMs configured as desktops) or as a custom
property to give<br>
</div>
<div> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div
style="word-wrap:break-word;line-break:after-white-space">
<div><span class="">
<blockquote type="cite">
<div>
<div text="#000000" bgcolor="#FFFFFF">
<p>On the recent updates has anything changed
in the terms on how to change the video
memory assigned to any given VM. I guess it
is something that has been forgotten
overtime, specially if you are running a
VDI-like environment whcih depends very much
on the video memory.</p>
</div>
</div>
</blockquote>
</span>there were no changes recently, these are the
most recent guidelines we got from SPICE people. They
might be out of date. Would be good to raise that
specifically (the performance difference for default
sizes) to them, can you narrow it down and post to <a
href="mailto:spice-devel@lists.freedesktop.org"
target="_blank" moz-do-not-send="true">spice-devel@lists.<wbr>freedesktop.org</a>?</div>
</div>
</blockquote>
<div><br>
<br>
</div>
<div>This could be very useful too <br>
</div>
<br>
</div>
Cheers,<br>
</div>
<div class="gmail_extra">Gianluca<br>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>