Red Hat Bugzilla – Bug 81982
vmware won't work > 2.4.20-2.13
Last modified: 2015-01-04 17:02:10 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216
Description of problem:
vmware workstation 3.2 (2230) has been working perfectly on recent kernels up to
On 2.4.20-2.15 and 2.4.20-2.18 (current in rawhide as of today) it's broken.
XIO: fatal IO error 0 (Success) on X server ":0.0"
after 3135 requests (3134 known processed) with 8 events remaining.
...or something similar - the exact number of requests varies.
Downgrade to 2.4.20-2.13 makes vmware work again
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Boot kernel 2.4.20-2.15 (or .18) - i686 uniprocessor
Actual Results: Vmware crashed
I upgaded by Redhat 7.2 to kernel 2.4.20-18.7. vmware-config.pl
I upgaded my Redhat 7.2 to kernel 2.4.20-18.7. vmware-config.pl builds the
kernel modules without complaint. But now, when I try to start the Guest OS,
vmware just hangs there for a few minutes. Nothing really happens on the
screen. Then it dies.
I upgraded to this kernel from -13 in order to see if it would fix the USB stuff
that broke in -13. It didn't fix the USB stuff, and broke vmware as my reward.
I'm going back to kernel 2.4.9 for now, where both USB and vmware worked fine.
Hmm. More info. If you let vmware sit for several minutes, it will eventually
start up the guest operating system (tried win 98 and XP). Meanwhile, a check
of dmesg output shows a couple dozem "usb_control/bulk_msg: timeout" messages.
These started right after vmware was launched.
I think the fact that USB is broken in 2.4.20-18.7 (compared to 2.4.9, on this
particular computer, at least) is also what is causing vmware to not work
properly, either. YMMV.