Bug 432964

Summary:	vmware will not start on kernel kernel-2.6.23.15-137.fc8
Product:	[Fedora] Fedora	Reporter:	Kevin DeKorte <kdekorte>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	8
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-02-18 14:40:15 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kevin DeKorte 2008-02-15 14:04:49 UTC

Description of problem:
I upgraded from kernel-2.6.23.14-115.fc8 to kernel-2.6.23.15-137.fc8 to close
the security problem with vmsplice. However, after doing this vmware will not
start with the error that it is unable to remove a callback handler from dbus
and then it give an error from dbus that the debug info is not installed. The
vmware-config.pl function works fine and the modules load. 

Reverting back to kernel-2.6.23.14-115.fc8 allows vmware to work again.

Version-Release number of selected component (if applicable):
kernel-2.6.23.15-137.fc8
VMwareWorkstation-6.0.2-59824
How reproducible:
100%

Steps to Reproduce:
1. Upgrade kernel
2. run vmware
3.
  
Actual results:
vmware will not start

Expected results:
vmware should start

Additional info:
Tried with vmware 6.0.0 and 6.0.2, and got same results.

Marked as security sensitive since vmware doesn't run with the security fixed
kernel (vm-splice)

Comment 1 Tomas Hoger 2008-02-15 14:24:05 UTC

Kevin, marking bug as security sensitive means that it will be accessible to
very small group of people (assignee and security team) and this should only be
used for bugs describing new security vulnerabilities.  Are you ok with me
unrestricting this bug so that it has better changed to get further feedback
from other users?

Additionally, I've not seen similar issues on x86_64 with updated kernel.

Comment 2 Kevin DeKorte 2008-02-15 14:53:53 UTC

I am fine with unrestricting the bug.

Can you please test with the i386 version of the kernel. I was able to duplicate
it after two reboots.

Comment 3 Tomas Hoger 2008-02-15 15:22:34 UTC

(In reply to comment #2)
> Can you please test with the i386 version of the kernel. I was able to duplicate
> it after two reboots.

Sorry, I not have i386 system available to test this quickly.  Maybe some other
user may be experiencing similar issues...

Comment 4 Kevin DeKorte 2008-02-15 15:44:10 UTC

Well crud, I rebooted again into 137 and vmware works fine now... maybe the
machine just needed anther kick... please close the ticket.