1:32 p.m.
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(a)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(a)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(a)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(a)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(a)upx.com</a>&gt;
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(a)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(a)upx.com</a>&gt;</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...
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&q...
moz-do-not-send="true"
class="">http://lists.ovirt.org/pipermail/users/2016-June/07...
<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&q...
moz-do-not-send="true"
class="">http://lists.ovirt.org/pipermail/users/2016-June/07...
<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(a)ovirt.org</a><br
class="">
<a class="moz-txt-link-freetext"
href="http://lists.ovirt.org/mailman/listinfo/users">http://...
class="">
</div>
</blockquote>
</div>
<br class="">
</blockquote>
<br>
</body>
</html>
--------------F0A33FA7845CA9C6A0F4EC16--