<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Fri, Nov 24, 2017 at 5:50 PM, FERNANDO FREDIANI <span dir="ltr"><<a href="mailto:fernando.frediani@upx.com" target="_blank">fernando.frediani@upx.com</a>></span> wrote:<br><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">
<p>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>Was reading some documentation that it may be possible to change
the file /usr/share/ovirt-engine/conf/o<wbr>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>Anyone can give a hint about the correct procedure to apply this
change ?</p>
<p>Thanks in advance.<span class="gmail-m_-601229090134847646gmail-m_-3245813213114366385HOEnZb"><font color="#888888"><br>
Fernando<br>
</font></span></p><br></div><br></blockquote><div><br></div><div>Hi Fernando, <br></div><div>based on this:</div><div> <a href="https://www.ovirt.org/develop/release-management/features/virt/os-info/" target="_blank">https://www.ovirt.org/develop/<wbr>release-management/features/<wbr>virt/os-info/</a></div><div><br></div><div>you should create a file of kind <br></div><div>/etc/ovirt-engine/osinfo.conf.<wbr>d/20-overload.properties</div><div>but I think you can only overwrite the multiplier and not directly the vgamem (or vgamem_mb in rhel 7) values</div><div><br></div><div>so that you could put something like this inside it:</div><div><br></div><div>os.windows_10.devices.display.vramMultiplier.value = 2<br>os.windows_10x64.devices.display.vramMultiplier.value = 2</div><div><br></div><div>I think there are no values for vgamem_mb<br></div><div></div><div><br></div><div>I found these two threads in 2016</div><div><a href="http://lists.ovirt.org/pipermail/users/2016-June/073692.html">http://lists.ovirt.org/pipermail/users/2016-June/073692.html</a></div><div>that confirms you cannot set vgamem<br></div><div>and</div><div><a href="http://lists.ovirt.org/pipermail/users/2016-June/073786.html">http://lists.ovirt.org/pipermail/users/2016-June/073786.html</a></div><div>that suggests to create a hook<br></div><div><br></div><div>Just a hack that came into mind:</div><div>in a CentOS vm of mine in a 4.1.5 environment I see that by default I get this qemu command line<br></div><div><br></div><div>-device qxl-vga,id=video0,ram_size=<wbr>67108864,vram_size=33554432,<wbr>vram64_size_mb=0,vgamem_mb=16,<wbr>bus=pci.0,addr=0x2<br></div></div></div><div class="gmail_extra"><br></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">https://www.ovirt.org/<wbr>documentation/draft/video-ram/</a></div><div class="gmail_extra"><br></div><div class="gmail_extra">you have</div><div class="gmail_extra">vgamem = 16 MB * number_of_heads</div><div class="gmail_extra"><br></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></div><div class="gmail_extra"><br></div><div class="gmail_extra">-device qxl-vga,id=video0,ram_size=<wbr>268435456,vram_size=134217728,<wbr>vram64_size_mb=0,vgamem_mb=64,<wbr>bus=pci.0,addr=0x2</div><div class="gmail_extra"><br></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></div><div class="gmail_extra">Could you try eventually?</div><div class="gmail_extra"><br></div><div class="gmail_extra">Gianluca<br></div></div>