Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Recent distros will include the appropriate drivers. VMWare tools is only needed if you want extended functionality between the host and the guest OS such as shared folders, copy/paste, time synchronization, etc.
  • I'm a bit surprised that the Xorg autoconfiguration script didn't get it right. Recent releases of it are pretty slick; you can totally remove your configuration and it'll reconfigure everything the next time you try to use X.
    • Well, I'm not sure what part of Xorg to blame. The config actually looks fine - just one mouse configured to use the VMWare driver. But when I start X it finds the mouse twice. Some kind of conflict between the config and the auto-probe code perhaps.

      Ultimately it comes down to the fact that Fedora 8 isn't actually supported by VMWare. It's reasonable to expect a bit of pain when playing outside the lines. I was mostly surprised I couldn't find a solution after a lot of searching - most VMWare bugs a

      • I've installed unsupported OSes in VMWare in the past with no problems. Perhaps there's something new in Fedora 8 that is interfering somehow.

        This is probably a stupid question but here goes anyway. Did you enable Desktop Effects in Fedora 8? I can see how that might cause problems.

        I suppose the new virtualization features in Fedora 8 could be wrecking havok with VMWare.

        • No, no desktop effects. I know it sounds like a rendering problem but I'm sure it wasn't. The rest of the display was snappy, the mouse pointer was just shaking!

          -sam

  • Just starting using FC8 on VMWare and I know exactly what you are talking about :)