<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 7 Mar 2018, at 14:03, 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="">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>correct on both<br 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>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" class="">spice-devel@lists.freedesktop.org</a>?</div><div><br class=""></div><div>Thanks,</div><div>michal<br class=""><blockquote type="cite" class=""><div class=""><div text="#000000" bgcolor="#FFFFFF" class=""><p class="">Let me know.<br class="">
Thanks</p><p class="">Fernando Frediani<br class="">
</p>
<br class="">
<div class="moz-cite-prefix">On 24/11/2017 20:45, Gianluca Cecchi
wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:CAG2kNCz1eA76NVa38w6ZnQEgV93ZYtWEzK+L+Z0jH-zgeFjegA@mail.gmail.com" class="">
<div dir="ltr" class="">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Nov 24, 2017 at 5:50 PM,
FERNANDO FREDIANI <span dir="ltr" class=""><<a href="mailto:fernando.frediani@upx.com" target="_blank" moz-do-not-send="true" class="">fernando.frediani@upx.com</a>></span>
wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF" class=""><p class="">I have made a Export of the same VM created in oVirt
to a server running pure qemu/KVM and which creates
new VMs profiles with vram 65536 and it turned on the
Windows 10 which run perfectly with that
configuration.</p><p class="">Was reading some documentation that it may be
possible to change the file
/usr/share/ovirt-engine/conf/o<wbr class="">sinfo-defaults.properties
in order to change it for the profile you want but I
am not sure how these changed should be made if
directly in that file, on another one just with custom
configs and also how to apply them immediatelly to any
new or existing VM ? I am pretty confident once vram
is increased that should resolve the issue with not
only Windows 10 VMs, but other as well.</p><p class="">Anyone can give a hint about the correct procedure to
apply this change ?</p><p class="">Thanks in advance.<span class="gmail-m_-601229090134847646gmail-m_-3245813213114366385HOEnZb"><font color="#888888" class=""><br class="">
Fernando<br class="">
</font></span></p>
<br class="">
</div>
<br class="">
</blockquote>
<div class=""><br class="">
</div>
<div class="">Hi Fernando, <br class="">
</div>
<div class="">based on this:</div>
<div class=""> <a href="https://www.ovirt.org/develop/release-management/features/virt/os-info/" target="_blank" moz-do-not-send="true" class="">https://www.ovirt.org/develop/<wbr class="">release-management/features/<wbr class="">virt/os-info/</a></div>
<div class=""><br class="">
</div>
<div class="">you should create a file of kind <br class="">
</div>
<div class="">/etc/ovirt-engine/osinfo.conf.<wbr class="">d/20-overload.properties</div>
<div class="">but I think you can only overwrite the multiplier and
not directly the vgamem (or vgamem_mb in rhel 7) values</div>
<div class=""><br class="">
</div>
<div class="">so that you could put something like this inside it:</div>
<div class=""><br class="">
</div>
<div class="">os.windows_10.devices.display.vramMultiplier.value = 2<br class="">
os.windows_10x64.devices.display.vramMultiplier.value = 2</div>
<div class=""><br class="">
</div>
<div class="">I think there are no values for vgamem_mb<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">I found these two threads in 2016</div>
<div class=""><a href="http://lists.ovirt.org/pipermail/users/2016-June/073692.html" moz-do-not-send="true" class="">http://lists.ovirt.org/pipermail/users/2016-June/073692.html</a></div>
<div class="">that confirms you cannot set vgamem<br class="">
</div>
<div class="">and</div>
<div class=""><a href="http://lists.ovirt.org/pipermail/users/2016-June/073786.html" moz-do-not-send="true" class="">http://lists.ovirt.org/pipermail/users/2016-June/073786.html</a></div>
<div class="">that suggests to create a hook<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">Just a hack that came into mind:</div>
<div class="">in a CentOS vm of mine in a 4.1.5 environment I see
that by default I get this qemu command line<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">-device qxl-vga,id=video0,ram_size=<wbr class="">67108864,vram_size=33554432,<wbr class="">vram64_size_mb=0,vgamem_mb=16,<wbr class="">bus=pci.0,addr=0x2<br class="">
</div>
</div>
</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">Based on this:</div>
<div class="gmail_extra"><a href="https://www.ovirt.org/documentation/draft/video-ram/" target="_blank" moz-do-not-send="true" class="">https://www.ovirt.org/<wbr class="">documentation/draft/video-ram/</a></div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">you have</div>
<div class="gmail_extra">vgamem = 16 MB * number_of_heads</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">I verified that if I edit the vm in the
gui and set Monitors=4 in console section (but with the aim of
using only the first head) and then I power off and power on
the VM, I get now<br class="">
</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">-device qxl-vga,id=video0,ram_size=<wbr class="">268435456,vram_size=134217728,<wbr class="">vram64_size_mb=0,vgamem_mb=64,<wbr class="">bus=pci.0,addr=0x2</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">I have not a client to connect and
verify any improvement: I don't know if you will be able to
use all the new ram in the only first head with a better
experience or if it is partitioned in some way...<br class="">
</div>
<div class="gmail_extra">Could you try eventually?</div>
<div class="gmail_extra"><br class="">
</div>
<div class="gmail_extra">Gianluca<br class="">
</div>
</div>
</blockquote>
<br class="">
</div>
_______________________________________________<br class="">Users mailing list<br class=""><a href="mailto:Users@ovirt.org" class="">Users@ovirt.org</a><br class="">http://lists.ovirt.org/mailman/listinfo/users<br class=""></div></blockquote></div><br class=""></body></html>