Bug 436714
| Summary: | F-9 VMWare video driver is broken | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jon Stanley <jonstanley> | ||||||||
| Component: | xorg-x11-drv-vmware | Assignee: | Adam Jackson <ajax> | ||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | low | ||||||||||
| Version: | rawhide | CC: | aa_sb_0, denis, gilboad, jbastian, mgansser, poelstra, xgl-maint | ||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-04-02 20:04:14 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: | |||||||||||
| Bug Depends On: | |||||||||||
| Bug Blocks: | 430962, 436904 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Jon Stanley
2008-03-09 20:44:11 UTC
Created attachment 297378 [details]
XConfig.test from installation
Created attachment 297379 [details]
X.log from installation
I was about ready to reassign when Jeremy did - the installed system has exactly the same symptoms. kvm-63's -vmware-vga which is now default in our kvm package has the same issue with rawhide drivers. same problem on my VMWare Server with fc9 after yum update. I'm also experiencing this with VMware Fusion 1.1.1 under OS X 10.5.2. FWIW, the VESA driver works under VMware Fusion 1.1.1 (although it's not very fast, of course). I currently have: xorg-x11-drv-vesa-1.3.0-13.20071113.fc9.i386 xorg-x11-drv-vmware-10.15.2-100.1.fc9.i386 Sticking on the beta blocker at least for now given the prevalence of using virtualization for testing the betas. not working with i386 20080311 rawhide on VMwareWorkstation-5.5.5-56455 xserver 1.4.99.901-4 will at least start up. There might still be a bug in the cursor code though, in my testing the cursor just shows up black. And this got tagged My naïve hope was that simply flipping to software cursor in the vmware driver would fix things, but instead that actually makes it much worse. The glyph looks correct but mouse events don't happen. Possibly worth flipping qemu back to cirrus for the beta? Not my call. I'll keep looking at the vmware cursor problem but I suspect it's a qemu bug, since "hardware cursor" in vmware hardware means the container draws the cursor. with workstation 6, the driver doesn't work at all, it's not just a cursor problem... (In reply to comment #13) > with workstation 6, the driver doesn't work at all, it's not just a cursor > problem... Can you attach the X log from the failure please? Ajax, apologies. xserver 1.4.99.901-5 works fine here, with no cursor problems. Thanks! (In reply to comment #15) > Ajax, apologies. xserver 1.4.99.901-5 works fine here, with no cursor problems. > Thanks! I'm assuming that means "works fine with vmware as the host". So I think the remaining failure case is just that qemu's vmware emulation doesn't do the cursor glyph right (since clearly it works with vmware vmware). Created attachment 297968 [details]
xorg log file from 1.4.99.901-5.20080310.fc9
It's better with xorg-x11-server-Xorg-1.4.99.901-5.20080310.fc9 under
VMware Fusion 1.1.1 but it's not fully functional yet.
1. The mouse cursor moves, but the buttons don't work. I can't click on
anything. If I can get the focus onto a window, I can use keyboard
shortcuts to do things.
2. I couldn't choose a resolution above 800x600 with s-c-display. This
may be because of the mouse buttons not working, I couldn't pick a
monitor with a supported resolution. I copied my xorg.conf from my
Fedora 8 VMware system and that got me to 1680x1050, but the mouse
buttons were still non-functional.
/var/log/Xorg.0.log is attached
In reply to comment #16) > I'm assuming that means "works fine with vmware as the host". That was F-8 as host, F-9 as guest. I was able to xrandr to a higher resolution in the guest OS too. *** Bug 437403 has been marked as a duplicate of this bug. *** xorg-x11-drv-vmware-10.15.2-100.1.fc9.x86_64 xorg-x11-server-Xorg-1.4.99.901-1.20080307.fc9.x86_64 VMWare Server 1.0.4 under F8 as a host. X dies with a "Mode pool is empty" message and leaves a corrupted text console. P.S. I'm using vesafb on my text consoles. (vga=0x317). - Gilboa *** Bug 437439 has been marked as a duplicate of this bug. *** (In reply to comment #20) > xorg-x11-drv-vmware-10.15.2-100.1.fc9.x86_64 > xorg-x11-server-Xorg-1.4.99.901-1.20080307.fc9.x86_64 Yes, 1.4.99.901-1 is busted. Which is why it's not in the beta: atropine:~% koji latest-pkg --quiet f9-beta xorg-x11-server xorg-x11-server-1.4.99.901-8.20080310.fc9 f9-beta ajax I can confirm that the vmware driver in rawhide / beta now works. appears to be broken again in 2008-04-02 rawhide John, no, that was a different new issue in Bug #440175 (In reply to comment #17) > Created an attachment (id=297968) [edit] > xorg log file from 1.4.99.901-5.20080310.fc9 > > It's better with xorg-x11-server-Xorg-1.4.99.901-5.20080310.fc9 under > VMware Fusion 1.1.1 but it's not fully functional yet. > > 1. The mouse cursor moves, but the buttons don't work. I can't click on > anything. If I can get the focus onto a window, I can use keyboard > shortcuts to do things. > > 2. I couldn't choose a resolution above 800x600 with s-c-display. This > may be because of the mouse buttons not working, I couldn't pick a > monitor with a supported resolution. I copied my xorg.conf from my > Fedora 8 VMware system and that got me to 1680x1050, but the mouse > buttons were still non-functional. > > /var/log/Xorg.0.log is attached I have a feeling the issues described here are related to bug# 439336. Feel free to add yourself to the CC list if it is... (In reply to comment #26) > I have a feeling the issues described here are related to bug# 439336. Feel free > to add yourself to the CC list if it is... Actually, I believe bug 434807 describes the problem. I tried the workaround mentioned in https://bugzilla.redhat.com/show_bug.cgi?sourceid=Mozilla-search&id=434807#c6 and my mouse started acting normally again. I have no problems (mouse, driver,...) with the latest Koji build (xorg-x11-server-1.4.99.901-16.20080401.fc9). |