https://bugzilla.novell.com/show_bug.cgi?id=386778 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c2 --- Comment #2 from Mike Fabian 2008-05-05 10:54:15 MST ---

From “dmesg”:

vmmon: Unknown symbol VMCIContext_ReleaseContext vmmon: Unknown symbol VMCIProcess_Create vmmon: Unknown symbol VMCIDatagram_AddContext vmmon: Unknown symbol VMCISharedMem_AddContext vmmon: Unknown symbol driverCallHandler vmmon: Unknown symbol VMCIDs_AddContext vmmon: Unknown symbol VMCIContext_InitContext vmmon: Unknown symbol VMCIPublicGroup_RemoveContext vmmon: Unknown symbol VMCIProcess_Destroy vmmon: Unknown symbol VMCIDs_RemoveContext vmmon: Unknown symbol VMCIDatagramProcess_Destroy vmmon: Unknown symbol VMCISharedMem_RemoveContext vmmon: Unknown symbol VMCIContext_GetId vmmon: Unknown symbol VMCI_Init vmmon: Unknown symbol Panic vmmon: Unknown symbol vmciVector vmmon: Unknown symbol VMCIDatagramProcess_Create vmmon: Unknown symbol VMCIPublicGroup_AddContext vmmon: Unknown symbol VMCIContext_ReadCall vmmon: Unknown symbol Warning vmmon: Unknown symbol VMCIDatagramProcess_ReadCall vmmon: Unknown symbol VMCISharedMem_IOCTLHandler vmmon: Unknown symbol VMCIDatagram_RemoveContext vmmon: Unknown symbol VMCI_Cleanup vmmon: Unknown symbol Log vmmon: Unknown symbol VMCIContext_ReleaseContext vmmon: Unknown symbol VMCIProcess_Create vmmon: Unknown symbol VMCIDatagram_AddContext vmmon: Unknown symbol VMCISharedMem_AddContext vmmon: Unknown symbol driverCallHandler vmmon: Unknown symbol VMCIDs_AddContext vmmon: Unknown symbol VMCIContext_InitContext vmmon: Unknown symbol VMCIPublicGroup_RemoveContext vmmon: Unknown symbol VMCIProcess_Destroy vmmon: Unknown symbol VMCIDs_RemoveContext vmmon: Unknown symbol VMCIDatagramProcess_Destroy vmmon: Unknown symbol VMCISharedMem_RemoveContext vmmon: Unknown symbol VMCIContext_GetId vmmon: Unknown symbol VMCI_Init vmmon: Unknown symbol Panic vmmon: Unknown symbol vmciVector vmmon: Unknown symbol VMCIDatagramProcess_Create vmmon: Unknown symbol VMCIPublicGroup_AddContext vmmon: Unknown symbol VMCIContext_ReadCall vmmon: Unknown symbol Warning vmmon: Unknown symbol VMCIDatagramProcess_ReadCall vmmon: Unknown symbol VMCISharedMem_IOCTLHandler vmmon: Unknown symbol VMCIDatagram_RemoveContext vmmon: Unknown symbol VMCI_Cleanup vmmon: Unknown symbol Log -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c4 Greg Kroah-Hartman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #4 from Greg Kroah-Hartman 2008-05-05 11:18:24 MST --- Go talk to vmware, there is nothing that we can do about their closed source, copyright infringing code. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW Component|Kernel |Other QAContact|kernel-maintainers@forge.provo.novell.com |qa@suse.de -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 User gregkh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c7 --- Comment #7 from Greg Kroah-Hartman 2008-05-05 12:03:07 MST --- What? we can't 'package' vmmon, it's closed source, not for distribution. If you are talking about some internal package, then please, assign it to the owner of that package when creating the bug, not the kernel developers who have been objecting to this module for years. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c11 --- Comment #11 from Mike Fabian 2008-05-05 15:18:57 MST --- I only wanted to use vmware to look into bug #381779 where I received a vmware image to reproduce the bug. So I downloaded the VMware-player-2.0.2-59824.x86_64.rpm package from the VMware site and installed it. When trying to start it, it says that it has not been configured yet and I need to run /usr/bin/vmware-config.pl. When I do this, it wants to compile the Kernel modules which fails because some conflicts in header files. Maybe this works on 10.3, but apparently not on Factory-x86_64 (which is what I have on my workstation). Then I found that we had packages for these modules and thought that maybe I need to use these but it didn’t work either. So if these packages don’t work and are not needed anymore, I think it is indeed better to delete them from autobuild. I hope I can find some other machine where I can get vmware to work to look at the image I received in bug #381779. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 User ro@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c13 --- Comment #13 from Ruediger Oertel 2008-05-05 16:18:36 MST --- since I'm the one that kept the module in STABLE trying to update it from time to time so it keeps compiling. you could just assign the bug to me. The whole idea behind having this module internally is having one person spend his time (if there is a bit left over ...) trying to get this running instead of each and everyone that just happens to try to run vmware. of course we are trying this on the latest kernel, with old kernels vmware usually keeps up to date ... and yes, I'm definitely happy that there finally is an effort to make the vmware modules open-source, but as of now, the old vmware does not work with these modules. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=386778 User mfabian@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=386778#c20 --- Comment #20 from Mike Fabian 2008-05-06 10:01:57 MST --- Now I tried with Rudi’s hacked sources on Stefan Dirsch’s machine shannon (which is newer intel hardware). vmmon module can be loaded, vmplayer starts but tells me that the image was created for hardware of a different vendor. I could proceed but the results may be undefined. I clicked on “proceed” and the restore of the vmware image hanged at 99%. And shannon is apparently not usable anymore, I cannot get a new shell anymore to kill the vmware process. Looks like I need to give up here. I have a AMD x86_64 machine at home but this also has old hardware and thus will most likely not work. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.