Very Slow Console Performance - Windows 10
This is a multi-part message in MIME format. --------------C64C2289E18148FC52BD4390 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hello Has anyone installed a Windows 10 Virtual Machine ? I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO. Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ? <video> <model type='qxl' ram='131072' vram='131072' vgamem='65536' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> Thanks Fernando --------------C64C2289E18148FC52BD4390 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <font face="arial, helvetica, sans-serif">Hello<br> <br> Has anyone installed a Windows 10 Virtual Machine ? <br> <br> I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO.<br> Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ?</font><br> <br> <video><br> <model type='qxl' ram='131072' vram='131072' vgamem='<ins>65536</ins>' heads='1'/><br> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/><br> </video><br> <br> Thanks<br> Fernando<br> </body> </html> --------------C64C2289E18148FC52BD4390--
This is a multi-part message in MIME format. --------------DD3210C84327688149B6FCAD Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 On 23/11/2017 10:46, FERNANDO FREDIANI wrote:
Hello
Has anyone installed a Windows 10 Virtual Machine ?
I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO. Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ?
<video> <model type='qxl' ram='131072' vram='131072' vgamem='65536' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video>
Thanks Fernando
--------------DD3210C84327688149B6FCAD Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> </head> <body bgcolor="#FFFFFF" text="#000000"> <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/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.</p> <p>Anyone can give a hint about the correct procedure to apply this change ?</p> <p>Thanks in advance.<br> Fernando<br> </p> <br> <div class="moz-cite-prefix">On 23/11/2017 10:46, FERNANDO FREDIANI wrote:<br> </div> <blockquote type="cite" cite="mid:781778b2-1d81-4a55-2060-ea570e83fbd1@upx.com"> <meta http-equiv="content-type" content="text/html; charset=utf-8"> <font face="arial, helvetica, sans-serif">Hello<br> <br> Has anyone installed a Windows 10 Virtual Machine ? <br> <br> I am having serious Console Performance issues even after installing the Ted Hat QXL controller from the virtio-win ISO.<br> Someone informed in a forum having similar issues and have resolved by increasing the graphics card memory to 65536 by editing the XML (example below), but how is that possible in oVirt permanently ?</font><br> <br> <video><br> <model type='qxl' ram='131072' vram='131072' vgamem='<ins>65536</ins>' heads='1'/><br> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/><br> </video><br> <br> Thanks<br> Fernando<br> </blockquote> <br> </body> </html> --------------DD3210C84327688149B6FCAD--
On Fri, Nov 24, 2017 at 5:50 PM, FERNANDO FREDIANI < 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/ 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/ 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
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--
On 7 Mar 2018, at 14:03, FERNANDO FREDIANI <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 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
Let me know. Thanks =20 Fernando Frediani =20 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. =20 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 =
=20 Anyone can give a hint about the correct procedure to apply this = change ? =20 Thanks in advance. Fernando =20 =20 =20 =20 Hi Fernando,=20 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/> =20 you should create a file of kind=20 /etc/ovirt-engine/osinfo.conf.d/20-overload.properties but I think you can only overwrite the multiplier and not directly =
--Apple-Mail=_AD8EF33F-AD8D-4221-B00E-6EEC1C75E08B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii 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? Thanks, michal the issue with not only Windows 10 VMs, but other as well. the vgamem (or vgamem_mb in rhel 7) values
=20 so that you could put something like this inside it: =20 os.windows_10.devices.display.vramMultiplier.value =3D 2 os.windows_10x64.devices.display.vramMultiplier.value =3D 2 =20 I think there are no values for vgamem_mb =20 I found these two threads in 2016 http://lists.ovirt.org/pipermail/users/2016-June/073692.html = <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 = <http://lists.ovirt.org/pipermail/users/2016-June/073786.html> that suggests to create a hook =20 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 =20 -device = qxl-vga,id=3Dvideo0,ram_size=3D67108864,vram_size=3D33554432,vram64_size_m= b=3D0,vgamem_mb=3D16,bus=3Dpci.0,addr=3D0x2 =20 Based on this: https://www.ovirt.org/documentation/draft/video-ram/ = <https://www.ovirt.org/documentation/draft/video-ram/> =20 you have vgamem =3D 16 MB * number_of_heads =20 I verified that if I edit the vm in the gui and set Monitors=3D4 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 =20 -device = qxl-vga,id=3Dvideo0,ram_size=3D268435456,vram_size=3D134217728,vram64_size= _mb=3D0,vgamem_mb=3D64,bus=3Dpci.0,addr=3D0x2 =20 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? =20 Gianluca =20
Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--Apple-Mail=_AD8EF33F-AD8D-4221-B00E-6EEC1C75E08B 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 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> --Apple-Mail=_AD8EF33F-AD8D-4221-B00E-6EEC1C75E08B--
This is a multi-part message in MIME format. --------------F0A33FA7845CA9C6A0F4EC16 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Hi I don't think these issue have much to do with Spice, but with the amount of memory oVirt sets to VMs by default, which in some cases for desktop usage seems too little. A field where that could be adjusted without having to edit files in the Engine would probably resolve this issue, or am I missing anything ? Fernando On 07/03/2018 15:43, Michal Skrivanek wrote:
On 7 Mar 2018, at 14:03, FERNANDO FREDIANI <fernando.frediani@upx.com <mailto:fernando.frediani@upx.com>> wrote:
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 ?
correct on both
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.
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>?
Thanks, michal
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
_______________________________________________ Users mailing list Users@ovirt.org <mailto:Users@ovirt.org> http://lists.ovirt.org/mailman/listinfo/users
--------------F0A33FA7845CA9C6A0F4EC16 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>Hi</p> <p>I don't think these issue have much to do with Spice, but with the amount of memory oVirt sets to VMs by default, which in some cases for desktop usage seems too little. A field where that could be adjusted without having to edit files in the Engine would probably resolve this issue, or am I missing anything ?</p> <p>Fernando<br> </p> <br> <div class="moz-cite-prefix">On 07/03/2018 15:43, Michal Skrivanek wrote:<br> </div> <blockquote type="cite" cite="mid:536C27CE-F311-4344-8067-20D217FC6D79@redhat.com"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <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="" moz-do-not-send="true">fernando.frediani@upx.com</a>> wrote:</div> <br class="Apple-interchange-newline"> <div class=""> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252" 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="" moz-do-not-send="true">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 class="" color="#888888"><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="" moz-do-not-send="true">Users@ovirt.org</a><br class=""> <a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><br class=""> </div> </blockquote> </div> <br class=""> </blockquote> <br> </body> </html> --------------F0A33FA7845CA9C6A0F4EC16--
On Wed, Mar 7, 2018 at 7:43 PM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
On 7 Mar 2018, at 14:03, FERNANDO FREDIANI <fernando.frediani@upx.com> wrote:
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 ?
correct on both
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 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.
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?
This could be very useful too Cheers, Gianluca
This is a multi-part message in MIME format. --------------E2B121412E141ED3C402FA64 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Hello Gianluca. 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. Fernando 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:
On 7 Mar 2018, at 14:03, FERNANDO FREDIANI <fernando.frediani@upx.com <mailto:fernando.frediani@upx.com>> wrote:
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 ?
correct on both
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 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.
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>?
This could be very useful too
Cheers, Gianluca
--------------E2B121412E141ED3C402FA64 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <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> --------------E2B121412E141ED3C402FA64--
--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--
participants (3)
-
FERNANDO FREDIANI -
Gianluca Cecchi -
Michal Skrivanek