--Apple-Mail=_6472D1DC-E771-418C-A275-8688952B4DA5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii
On 8 Mar 2018, at 14:51, FERNANDO FREDIANI <fernando.frediani@upx.com> = wrote: =20 Hello Gianluca. =20 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. =20 =20
Fernando =20 On 07/03/2018 16:59, Gianluca Cecchi wrote:
On Wed, Mar 7, 2018 at 7:43 PM, Michal Skrivanek = <michal.skrivanek@redhat.com <mailto:michal.skrivanek@redhat.com>> = wrote: =20 =20
On 7 Mar 2018, at 14:03, FERNANDO FREDIANI = <fernando.frediani@upx.com <mailto:fernando.frediani@upx.com>> wrote: =20 Hello Gianluca =20 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 ? =20 correct on both =20 =20 Hello Fernando and Michal, at that time I was doing some tests both with plain virt-manager and = oVirt for some Windows 10 VMs. More recently I haven't done anything in that regard again, = unfortunately. 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 =
It does, because we just follow their recommendations:) 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
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. =20
=20 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 = spice-devel@lists.freedesktop.org = <mailto:spice-devel@lists.freedesktop.org>? =20 =20 This could be very useful too=20 =20 Cheers, Gianluca =20 =20
--Apple-Mail=_6472D1DC-E771-418C-A275-8688952B4DA5 Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=us-ascii <html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Mar 2018, at 14:51, FERNANDO FREDIANI <<a href="mailto:fernando.frediani@upx.com" class="">fernando.frediani@upx.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""> <div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hello Gianluca.</p><p class="">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><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div>It does, because we just follow their recommendations:)</div><div><br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Fernando<br class=""> </p> <br class=""> <div class="moz-cite-prefix">On 07/03/2018 16:59, Gianluca Cecchi wrote:<br class=""> </div> <blockquote type="cite" cite="mid:CAG2kNCzLa=vvbUxScZe_=wZ0G1OAwF=TZFS8nbOuPXjq6o9CwA@mail.gmail.com" class=""> <div dir="ltr" class=""> <div class="gmail_extra"> <div class="gmail_quote">On Wed, Mar 7, 2018 at 7:43 PM, Michal Skrivanek <span dir="ltr" class=""><<a href="mailto:michal.skrivanek@redhat.com" target="_blank" moz-do-not-send="true" class="">michal.skrivanek@redhat.com</a>></span> wrote:<br class=""> <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" class=""><br class=""> <div class=""><span class=""><br class=""> <blockquote type="cite" class=""> <div class="">On 7 Mar 2018, at 14:03, FERNANDO FREDIANI <<a href="mailto:fernando.frediani@upx.com" target="_blank" moz-do-not-send="true" class="">fernando.frediani@upx.com</a>> wrote:</div> <br class="m_-2928413078620554861Apple-interchange-newline"> <div class=""> <div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Hello Gianluca</p><p class="">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 class=""> </span></div> </div> </blockquote> <div class=""><br class=""> <br class=""> </div> <div class="">Hello Fernando and Michal,<br class=""> </div> <div class="">at that time I was doing some tests both with plain virt-manager and oVirt for some Windows 10 VMs.<br class=""> </div> <div class="">More recently I haven't done anything in that regard again, unfortunately.<br class=""> </div> <div class="">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 class=""> </div> <div class=""> <br class=""> </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" class=""> <div class=""><span class=""> <blockquote type="cite" class=""> <div class=""> <div text="#000000" bgcolor="#FFFFFF" class=""><p class="">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" class="">spice-devel@lists.<wbr class="">freedesktop.org</a>?</div> </div> </blockquote> <div class=""><br class=""> <br class=""> </div> <div class="">This could be very useful too <br class=""> </div> <br class=""> </div> Cheers,<br class=""> </div> <div class="gmail_extra">Gianluca<br class=""> <br class=""> </div> </div> </blockquote> <br class=""> </div> </div></blockquote></div><br class=""></body></html> --Apple-Mail=_6472D1DC-E771-418C-A275-8688952B4DA5--