Thank you very mucjh, and sorry for being so lazy to search
for that rpm by myself. Somehow, fedora rpms missed from my
mind. Oh boy, it requires a lot of packages. Do you think
would it be a good idea to temporarily install fedora repos, do
the yum installation to get the dependencoes too and then
disable the repo ? I am thinking to not break the ovirt node
installation.
The easiest path is to get the source from your current rpm,
apply the patch mentioned in previous email, build, install,
test.
If that does not work you can rollback. If works, you can rethink
what is best.
Cheers,
yum localinstall spice-server-0.14.1-1.fc30.x86_64.rpm
Loaded plugins: enabled_repos_upload, fastestmirror, imgbased-persist,
package_upload, product-id, search-disabled-repos, subscription-manager,
vdsmupgrade
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Examining spice-server-0.14.1-1.fc30.x86_64.rpm:
spice-server-0.14.1-1.fc30.x86_64
Marking spice-server-0.14.1-1.fc30.x86_64.rpm as an update to
spice-server-0.14.0-2.el7_5.3.x86_64
Resolving Dependencies
--> Running transaction check
---> Package spice-server.x86_64 0:0.14.0-2.el7_5.3 will be updated
---> Package spice-server.x86_64 0:0.14.1-1.fc30 will be an update
--> Processing Dependency: libcrypto.so.1.1(OPENSSL_1_1_0)(64bit) for
package: spice-server-0.14.1-1.fc30.x86_64
Loading mirror speeds from cached hostfile
* epel: ftp.nluug.nl
* ovirt-4.2-epel: ftp.nluug.nl
--> Processing Dependency: libssl.so.1.1(OPENSSL_1_1_0)(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libcrypto.so.1.1()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libgstapp-1.0.so.0()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libgstbase-1.0.so.0()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libgstreamer-1.0.so.0()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libgstvideo-1.0.so.0()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: liborc-0.4.so.0()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Processing Dependency: libssl.so.1.1()(64bit) for package:
spice-server-0.14.1-1.fc30.x86_64
--> Finished Dependency Resolution
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libgstvideo-1.0.so.0()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libgstbase-1.0.so.0()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libgstreamer-1.0.so.0()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libcrypto.so.1.1(OPENSSL_1_1_0)(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: liborc-0.4.so.0()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libcrypto.so.1.1()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libssl.so.1.1(OPENSSL_1_1_0)(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libgstapp-1.0.so.0()(64bit)
Error: Package: spice-server-0.14.1-1.fc30.x86_64
(/spice-server-0.14.1-1.fc30.x86_64)
Requires: libssl.so.1.1()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Uploading Enabled Repositories Report
Loaded plugins: fastestmirror, product-id, subscription-manager
This system is not registered with an entitlement server. You can use
subscription-manager to register.
Cannot upload enabled repos report, is this client registered?
Thank you !
Leo
On Tue, Jan 8, 2019 at 10:19 AM Victor Toso <victortoso(a)redhat.com> wrote:
> Hi,
>
> On Mon, Jan 07, 2019 at 07:29:13PM +0200, Leo David wrote:
> > Thank you very much Victor,
> > Is there a rpm that I can easily install on all the nodes, or will I need
> > to build that version from sources ?
>
> You can fetch the release of 0.14.1 version at
>
https://gitlab.freedesktop.org/spice/spice/tags
>
> You can fetch an rpm from Fedora here
>
https://koji.fedoraproject.org/koji/buildinfo?buildID=1138474
>
> Cheers,
>
> > On Mon, Jan 7, 2019, 19:14 Victor Toso <victortoso(a)redhat.com wrote:
> >
> > > 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/ca4984570f425e87e92abe5...
> > >
> > > 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,
> > >
>
--
Best regards, Leo David