Hi,

On Mon, Jan 07, 2019 at 07:00:04PM +0200, Leo David wrote:
> Thank you very much !
>
> I have modified /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties file
> and added the last line
>
> # Windows10x64
> os.windows_10x64.id.value = 27
> os.windows_10x64.name.value = Windows 10 x64
> os.windows_10x64.derivedFrom.value = windows_8x64
> os.windows_10x64.productKey.value =
> os.windows_10x64.resources.maximum.ram.value = 2097152
> os.windows_10x64.cpu.unsupported.value = conroe, opteron_g1
> os.windows_10x64.sysprepPath.value =
> ${ENGINE_USR}/conf/sysprep/sysprep.w10x64
> *os.windows_10x64.devices.display.vramMultiplier.value = 2*
>
> The vm has the "Windows10x64" profile configured
>
> Restarted the ovirt-engine vm, powered on the Windows 10 vm. Not any
> difference...The console is very slow, almost unusable.
>
> Also, tried to upgrade spice-server on the node, but it seems that there
> aeno updates available. At the moment, it is installed:
>  spice-server.x86_64                           0.14.0-2.el7_5.3

Just for reference, the patch in spice-server that should help is
from the mail thread

    https://lists.freedesktop.org/archives/spice-devel/2018-June/044237.html

Merged as

    https://gitlab.freedesktop.org/spice/spice/commit/ca4984570f425e87e92abe5f62f9687bb55c1e14

Looking at the repo with git tag --contains ca4984570f425e87e92
it shows v0.14.1.

0.14.0-2 probably does not contain that. Either update to 0.14.1
or backport the patch. It does need to shutdown and start the VM
again.

> Any thoughts ?
>
> Thank you !

I hope it helps ;)

Cheers,