This is a multi-part message in MIME format. --------------CAB4B588B3F22DFB1CAD9670 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello Gianluca 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 ? 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. Let me know. Thanks Fernando Frediani On 24/11/2017 20:45, Gianluca Cecchi wrote:
On Fri, Nov 24, 2017 at 5:50 PM, FERNANDO FREDIANI <fernando.frediani@upx.com <mailto:fernando.frediani@upx.com>> wrote:
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.
Was reading some documentation that it may be possible to change the file /usr/share/ovirt-engine/conf/osinfo-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.
Anyone can give a hint about the correct procedure to apply this change ?
Thanks in advance. Fernando
Hi Fernando, based on this: https://www.ovirt.org/develop/release-management/features/virt/os-info/ <https://www.ovirt.org/develop/release-management/features/virt/os-info/>
you should create a file of kind /etc/ovirt-engine/osinfo.conf.d/20-overload.properties but I think you can only overwrite the multiplier and not directly the vgamem (or vgamem_mb in rhel 7) values
so that you could put something like this inside it:
os.windows_10.devices.display.vramMultiplier.value = 2 os.windows_10x64.devices.display.vramMultiplier.value = 2
I think there are no values for vgamem_mb
I found these two threads in 2016 http://lists.ovirt.org/pipermail/users/2016-June/073692.html that confirms you cannot set vgamem and http://lists.ovirt.org/pipermail/users/2016-June/073786.html that suggests to create a hook
Just a hack that came into mind: in a CentOS vm of mine in a 4.1.5 environment I see that by default I get this qemu command line
-device qxl-vga,id=video0,ram_size=67108864,vram_size=33554432,vram64_size_mb=0,vgamem_mb=16,bus=pci.0,addr=0x2
Based on this: https://www.ovirt.org/documentation/draft/video-ram/ <https://www.ovirt.org/documentation/draft/video-ram/>
you have vgamem = 16 MB * number_of_heads
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
-device qxl-vga,id=video0,ram_size=268435456,vram_size=134217728,vram64_size_mb=0,vgamem_mb=64,bus=pci.0,addr=0x2
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... Could you try eventually?
Gianluca
--------------CAB4B588B3F22DFB1CAD9670 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body 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> <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> <p>Let me know.<br> Thanks</p> <p>Fernando Frediani<br> </p> <br> <div class="moz-cite-prefix">On 24/11/2017 20:45, Gianluca Cecchi wrote:<br> </div> <blockquote type="cite" cite="mid:CAG2kNCz1eA76NVa38w6ZnQEgV93ZYtWEzK+L+Z0jH-zgeFjegA@mail.gmail.com"> <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" moz-do-not-send="true">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" moz-do-not-send="true">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><br> </div> <div>I found these two threads in 2016</div> <div><a href="http://lists.ovirt.org/pipermail/users/2016-June/073692.html" moz-do-not-send="true">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" moz-do-not-send="true">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" moz-do-not-send="true">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> </blockquote> <br> </body> </html> --------------CAB4B588B3F22DFB1CAD9670--