http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c2 --- Comment #2 from Werner Flamme --- Well, for me "keeping the KMP related logic in the .spec file" does not mean that the KMP is dropped. Isn't the KMP built from the main spec file anyway? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c4 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #4 from Dominique Leuenberger --- (In reply to Werner Flamme from comment #2)

Well, for me "keeping the KMP related logic in the .spec file" does not mean that the KMP is dropped. Isn't the KMP built from the main spec file anyway?

no - the KMP is/was built by open-vm-tools-KMP. The current problem faced is that modern kernels no longer need the KMPs (there is only one module missing in the mainline kernel, vmhgfs, which is no longer supported by vmware, in favor of a still to be written fuse implementation) - and building an empty KMP package does not work, so it needed to be removed completely. What I CAN offer is to re-enable the KMP building for SLE11... any newer, still supported version should not rely on the kernel modules package anymore. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c6 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(werner.flamme@ufz | |.de) | --- Comment #6 from Dominique Leuenberger --- ok, found why it no longer built: # The vmhgfs module is currently built for all versions # (Shared Folders are not supported under ESX/ESXi, so this driver is not necessary for SLES11/12) %define vmhgfs vmhgfs # exclude AMD PCnet32 LANCE pci.id from Supplements list [bnc#397554] %define __find_supplements sh -c '/usr/lib/rpm/find-supplements %{name} | grep -v pci:v00001022d00002000' # Modules to be built up to openSUSE 12.3 (excluding SLES11), possibly not building on newer versions. %if 0%{?suse_version} <= 1230 && 0%{?suse_version} != 1110 %define vm_modules1230 vmci vsock %endif %if 0%{?suse_version} <= 1220 && 0%{?suse_version} != 1110 # Modules to be built up to openSUSE 12.1 (excluding SLES11), possibly not building on newer versions. %define vm_modules1220 vmsync %endif %if 0%{?suse_version} <= 1210 && 0%{?suse_version} != 1110 # Modules to be built up to openSUSE 12.1 (excluding SLES11), possibly not building on newer versions. %define vm_modules1210 vmxnet %endif the vmhgfs had been disabled in a first attempt completely - which again resulted in an empty KMP package... but this also means, that there actually were NO modules provided for SLE11, except the vmhgfs module. As such, if this worked feature wise before the change, it works afterwards without the KMP module as well) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c8 --- Comment #8 from Werner Flamme --- (In reply to Dominique Leuenberger from comment #6)

ok, found why it no longer built:

# The vmhgfs module is currently built for all versions # (Shared Folders are not supported under ESX/ESXi, so this driver is not necessary for SLES11/12) %define vmhgfs vmhgfs

# exclude AMD PCnet32 LANCE pci.id from Supplements list [bnc#397554] %define __find_supplements sh -c '/usr/lib/rpm/find-supplements %{name} | grep -v pci:v00001022d00002000'

[...]

the vmhgfs had been disabled in a first attempt completely - which again resulted in an empty KMP package...

but this also means, that there actually were NO modules provided for SLE11, except the vmhgfs module. As such, if this worked feature wise before the change, it works afterwards without the KMP module as well)

OK, so that means, that everything that once was provided by the KMP is either deprecated or superfluous :). Nobody needs the KMP any more, even not on a SLE 11 with its prehistoric kernel ;). Am I right here? SLE 12 does not need the KMP right from the start, so I just want to make sure I can delete the KMP packages on my 20+ SLE 11 SP3 hosts, when the current open-vm-tools package is installed (and working). -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c10 --- Comment #10 from Dominique Leuenberger --- (In reply to Werner Flamme from comment #8)

...

the vmhgfs had been disabled in a first attempt completely - which again resulted in an empty KMP package...

but this also means, that there actually were NO modules provided for SLE11, except the vmhgfs module. As such, if this worked feature wise before the change, it works afterwards without the KMP module as well)

OK, so that means, that everything that once was provided by the KMP is either deprecated or superfluous :). Nobody needs the KMP any more, even not on a SLE 11 with its prehistoric kernel ;). Am I right here? SLE 12 does not need the KMP right from the start, so I just want to make sure I can delete the KMP packages on my 20+ SLE 11 SP3 hosts, when the current open-vm-tools package is installed (and working).

If you check the content of your installed KMPs, there is only vmhgfs module in it. And as you run a larger scale setup, you likely run this on ESX, where that module is useless anyway (it's the host/guest file sharing module for VMWare Workstation) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c12 --- Comment #12 from Dominique Leuenberger --- (In reply to Werner Flamme from comment #11)

Strange things happen...

Today I found a new package of open-vm-tools, open-vm-tools-10.0.0-183.1. I updated...

# rpm -qa 'open-vm*' | sort open-vm-tools-10.0.0-183.1 open-vm-tools-desktop-10.0.0-183.1

# rpm -qa '*-kmp-*' vmware-guest-kmp-default-9.10.2_3.0.76_0.11-168.1 vmware-guest-kmp-default-9.10.2_3.0.76_0.11-176.1

# rpm -e vmware-guest-kmp-default-9.10.2_3.0.76_0.11-168.1 vmware-guest-kmp-default-9.10.2_3.0.76_0.11-176.1 error: Failed dependencies: vmware-guest-kmp is needed by (installed) open-vm-tools-10.0.0-183.1.x86_64

Pardon? Why is there a dependency in package open-vm-tools into a package that is not even built in the proper version?

So why don't you update the KMP as well, that exists in the same repository at http://download.opensuse.org/repositories/Virtualization:/VMware/SLE_11_SP3/... ? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=941384 http://bugzilla.novell.com/show_bug.cgi?id=941384#c14 --- Comment #14 from Werner Flamme --- Dear maintainers, today I found the repo for SLE_11_SP4. That's nice. And there is no kernel module. I learnt that this is not needed any more. But why has the package open-vm-tools still the requirement for the kmp package? That is something I am too dumb to understand. === snip === # LANG=C zypper in open-vm-tools Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides vmware-guest-kmp needed by open-vm-tools-10.0.0-190.1.x86_64 Solution 1: do not install open-vm-tools-10.0.0-190.1.x86_64 Solution 2: break open-vm-tools-10.0.0-190.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): === pins === Of course I can break the dependencies, but why do they exist at all? Regards, Werner -- You are receiving this mail because: You are on the CC list for the bug.