My question from yesterday got buried under a few pages full of new threads and it's still unanswered. So reposting in
hopes of catching the eyes of someone knowledgeable who might be lurking today:
-
I recently upgraded to fusion 2.01 on my MacBook Pro running OSX 10.5.5. Before the "upgrade", I was pretty
happy with the way my virtual machine was working (except the high CPU consumption even while the VM was
"at rest").
I thought the upgrade to version 2 was worth a try. The upgrade seemed to go smoothly except for a little
trouble with the vmware-tools in the guest machine for which I had to manually uninstall the existing version
and then install the new version (using the install vmware tools menu item). But I immediately noticed that
the nice automatic resizing behaviour in X windows (either in Full screen mode or in window mode. I'm not
fond of the "unity" mode). Eerlier (i.e. with 1.x versions of Fusion), I was able to resize the window, make it
go full screen(1440x900), put it on an external display (24 inch LCD, 1920x1200 max) and make it go fullscreen
on the external display etc... .all would work beautifull upto version 1.2 of the Fusion software.
after upgrade to 2.01 though, it's a hit or miss proposition. The resizing works as expected a few times, but
at some point, my guest machine gets "stuck" in a particular resolution (I haven't been able to pin down the trigger
for this event) After that, any resizing of the window, full-screening etc. only results in the external frame of the window
being resized but the resolution of the X sever running in side stays the same. If the window is too small for the X server,
I start seeing scroll bars on the edgess, and if the window is too large, the extra space is just filled with black.
Here's the top part from Xorg.0.log:
Build Operating System: Linux Ubuntu (xorg-server 2:1.3.0.0.dfsg-12ubuntu8)
Current Operating System: Linux Ubuntu-VM1 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64
Build Date: 29 September 2007
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jan 26 14:59:17 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Default Layout"
(**) |-->Screen "Default Screen" (0)
(**) | |-->Monitor "vmware"
(**) | |-->Device "VMware SVGA"
(**) |-->Input Device "XWorkAround"
(**) |-->Input Device "VMware Keyboard"
(**) |-->Input Device "VMware Mouse"
(WW) The directory "/usr/share/fonts/X1
and here's some relevant looking VMware related lines from the same log:
**) | |-->Monitor "vmware"
(**) | |-->Device "VMware SVGA"
(**) |-->Input Device "VMware Keyboard"
(**) |-->Input Device "VMware Mouse"
(--) PCI:*(0:15:0) VMware Inc PCI Display Adapter rev 0, Mem @ 0xd0000000/27, 0xd8000000/23, I/O @ 0x10d0/4
(II) LoadModule: "vmware"
(II) Loading /usr/lib/xorg/modules/drivers//vmware_drv.so
(II) Module vmware: vendor="X.Org Foundation"
(II) VMWARE(0): VMMOUSE module was loaded
(II) VMWARE: driver for VMware SVGA: vmware0405, vmware0710
(--) Chipset vmware0405 found
(--) VMWARE(0): VMware SVGA regs at (0x10d0, 0x10d1)
(--) VMWARE(0): caps: 0x003F83E2
(--) VMWARE(0): depth: 24
(--) VMWARE(0): bpp: 32
(--) VMWARE(0): vram: 65536000
(--) VMWARE(0): pbase: 0xd0000000
(--) VMWARE(0): mwidt: 5120
(--) VMWARE(0): mheig: 3200
(--) VMWARE(0): depth: 24
(--) VMWARE(0): bpp: 32
(--) VMWARE(0): w.red: 8
(--) VMWARE(0): w.grn: 8
(--) VMWARE(0): w.blu: 8
(--) VMWARE(0): vis: 4
(==) VMWARE(0): Depth 24, (==) framebuffer bpp 32
(==) VMWARE(0): RGB weight 888
(==) VMWARE(0): Default visual is TrueColor
(==) VMWARE(0): Using HW cursor
(==) VMWARE(0): Using gamma correction (1.0, 1.0, 1.0)
(II) VMWARE(0): vmware: Using hsync range of 1.00-10000.00 kHz
(II) VMWARE(0): vmware: Using vrefresh range of 1.00-10000.00 Hz
(II) VMWARE(0): Clock range: 0.00 to 400000.00 MHz
And here are some error'ish looking lines:
(II) VMWARE(0): Not using default mode "800x512" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "840x525" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "960x600" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "960x720" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "1024x768" (bad mode clock/interlace/doublescan)
(II) VMWARE(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VMWARE(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VMWARE(0): Not using default mode "2048x1536" (width too large for virtual size)
(II) VMWARE(0): Not using default mode "1920x1440" (width too large for virtual size)
(II) VMWARE(0): Not using default mode "1920x1440" (width too large for virtual size)
I'm attaching the entire recent Xorg.0.log file with this posting too. I'd be happy to provide more
information as required to diagnose this issue.
Thanks
grepya
I'm having the same problem under Ubuntu 8.10; It doesn't seem to understand I have a widescreen monitor attached. It defaults to a 4:3 resolution leaving black bars at the sides (typical center cutting). If i set the resolution to a widescreen one (ie, 1920x1080), it letterboxes as if it thinks my monitor is 4:3. I had no problems at all until I went to a widescreen monitor -- a normal 4:3 LCD works flawlessly under vmware and any version of Ubuntu I've tried.
With the new widescreen monitor, though, I can only change resolution once. After that I have to log out then back in. One time I got it some how to autofit my screen (it scaled everything up) after entering/leaving unity a few times.
I've been trying various things with Ubuntu thiking some mode-lines were whacky. I have vmware tools installed, but that doesn't fix the problem. I had originally thought it was specific to Ubuntu 8.10, but seeing you having problems on 7.x makes me wonder.
Under that version of Ubuntu, I believe a utilty is available named "displayconfig-gtk" that will let you tweak things. You can set the monitor hardware there (can't under 8.10) via the hardware tab. Try setting it to Generic LCD and it might work for you. This utility does not exist in 8.10, and 8.1 relies solely on autodetect it seems. Curious that that this is behaving the same though across both versions. Again, moving to a widescreen monitor kicked this problem off.
Deleted duplicate post.