gbohn's Posts

Hi;    I just upgraded from VMware Workstation 7.1.5 to 8.0.1 on a Windows 7 SP1 64-Bit Host.    I did a test trying transferring a single large 4 GB file from a USB drive (a Patriot Supers... See more...
Hi;    I just upgraded from VMware Workstation 7.1.5 to 8.0.1 on a Windows 7 SP1 64-Bit Host.    I did a test trying transferring a single large 4 GB file from a USB drive (a Patriot Supersonic 32 GB USB 3.0 drive plugged into a USB 2.0 port on my Intel X58 / ICHR10 system).    Using a Windows 7 64-bit or 32-Bit guest, I only see about a 1.4 MB/second transfer rate. Natively on the Host, the same file transfer runs about 34 MB/second.   Is this the expected performance? I don't have the 7.1.5 setup to compare this against, but I don't think it was previously that slow (although I could be wrong ).    I also tried this using the motherboards built-in NEC/Renesas USB 3.0 Port of course (and it works fine in the Host environment).    But Workstation pops up with a message saying that the ideal driver wasn't found (This is using the Renesas 2.1.27.0 drivers, if that makes a difference) and it doesn't work in the guest. I am under the impression that USB 3.0 is still not supported for VMware guests with a Windows 7 Host.   Thanks;       -Greg
Hi;    I just upgraded to VMware Workstation 8.0.1 on a Windows 7 SP1 64-Bit host (from 7.1.5)    Whenever I start a particular Windows XP Guest I see the message      "There is at least... See more...
Hi;    I just upgraded to VMware Workstation 8.0.1 on a Windows 7 SP1 64-Bit host (from 7.1.5)    Whenever I start a particular Windows XP Guest I see the message      "There is at least one Virtual SCSI device installed on the Windows XP virtual machine". See the attached image.    I have an LSI SCSI device configured and the driver installed, so this actually works o.k.    This is probably a silly question, but how do I get it to stop popping up a warning every time I start the Guest? This didn't happen with the prior 7.1.5 installation.    Thanks;        -Greg
Hi;    I just upgraded to Workstation 8.0.1 (from 7.1.5) with Windows 7 64-Bit as the Host. I am experiencing some quirks that I didn't see with Workstation 7.1.5.    When I boot a Windows ... See more...
Hi;    I just upgraded to Workstation 8.0.1 (from 7.1.5) with Windows 7 64-Bit as the Host. I am experiencing some quirks that I didn't see with Workstation 7.1.5.    When I boot a Windows 7 32-Bit or Windows 7 64-Bit Aero Guest, I get a mostly black/unpainted guest desktop right after I log-in (the log-on panel comes up fine). See the attachment picture.    This is for a Guest that has my prior VMware 7 hardware setup, and either the 7.1.5 or 8.0.1 tools. (So far, my Windows XP (32-Bit) guest doesn't show the same problem.)    After about 30 seconds, the guest desktop seems to finally refresh itself correctly. Other than some momentary garbage when switching back and forth between Full screen and Windowed mode, the video seems to work otherwise.    If I bring up a guest VM application during the time it's not painted properly, the application seems to come up fine. But, if I minimize the app, the guest desktop area behind it is painted, but incorrectly. (It looks like maybe something left over from the logon panel). See the second picture.    If I upgrade the Guest to the VMware 8 hardware compatibility, I don't see this. (And, I don't remember ever seeing this using Workstation 7.1.5).    Does anyone else have this issue?    This is on a Windows 7 SP1 Host system with an AMD/ATI Radeon HD 5870 video card and Catalyst 11.11 drivers.   Thanks;       -Greg
Just a quick update. It looks like I've found a problem with the solution I used.   Using the 'fixed' VMware tools vmxnet module seems to work o.k. except for hibernate.   It looks like I ... See more...
Just a quick update. It looks like I've found a problem with the solution I used.   Using the 'fixed' VMware tools vmxnet module seems to work o.k. except for hibernate.   It looks like I can select 'hibernate' from the Fedora Guest o.k. But, the bridged network (eth0 in the guest) is missing after I power the hibernated guest system back on (even after waiting a while).   (I would have used 'sleep', but this choice was not presented by Fedora).   Going back to the 'original' 7.1.4 tools (where vmxnet gets a compiler error) and the Guest network appears to come back after I power back on.    -Greg
> If you install Fedora thru VMWare "easy install", it will install Tools automagically.   I don't think I used the 'Easy' install. (I once made the mistake of using 'easy install' for Windows... See more...
> If you install Fedora thru VMWare "easy install", it will install Tools automagically.   I don't think I used the 'Easy' install. (I once made the mistake of using 'easy install' for Windows. I found it made the 'wrong' decisions for what I wanted... Maybe I just need to find out more about how to control what it does, but ever since then I've shyed away from using it)     -Greg
> After you got these errors in buiding  vmxnet, have you experienced any problems > with guest network, or it worked fine?   I wasn't sure if I was getting slower performance or not. I had s... See more...
> After you got these errors in buiding  vmxnet, have you experienced any problems > with guest network, or it worked fine?   I wasn't sure if I was getting slower performance or not. I had some 'slow' responses (in certain operations) over a VPN and was hoping the tools update would improve things.   Since 'fixing' the compiler error, things are either the same or a little faster. > Fedora already contains its own device drivers for Vmware,   So I shouldn't install the VMWare tools at all then (for Fedora 13)?       -Greg
I solved my vmxnet.c problem. I searched for (and found) the magic incantations to extract and rebuild the vmxnet.c source. In the vmxnet_load_multicast function, I altered the two conditional... See more...
I solved my vmxnet.c problem. I searched for (and found) the magic incantations to extract and rebuild the vmxnet.c source. In the vmxnet_load_multicast function, I altered the two conditional compiles of    #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 34)         to     #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 35) and recompiled with      vmware-config-tools.pl -c I can't say if that is actually the correct fix, but it had the effect of allowing vmxnet.c to be compiled without error on my system. (This is using the current FC 13 32-bit kernel 2.6.34.8-68.fc13.i686.PAE).    -Greg
Hi;   I am trying to install VMWare Tools (from 7.1.4) on a Fedora 13 Guest image (with the 2.6.34.8-68.fc13.i686.PAE kernel).  This is on a Windows 7 SP1 Host.   This seems to mostly work,... See more...
Hi;   I am trying to install VMWare Tools (from 7.1.4) on a Fedora 13 Guest image (with the 2.6.34.8-68.fc13.i686.PAE kernel).  This is on a Windows 7 SP1 Host.   This seems to mostly work, but I get an error and a few other seemingly unusual things.   The first error I see is: "Using 2.6.x kernel build system. make: Entering directory `/tmp/vmware-root/modules/vmxnet-only' make -C /lib/modules/2.6.34.8-68.fc13.i686.PAE/build/include/.. SUBDIRS=$PWD SRCROOT=$PWD/. \           MODULEBUILDDIR= modules make[1]: Entering directory `/usr/src/kernels/2.6.34.8-68.fc13.i686.PAE'   CC [M]  /tmp/vmware-root/modules/vmxnet-only/vmxnet.o /tmp/vmware-root/modules/vmxnet-only/vmxnet.c: In function ‘vmxnet_load_multicast’: /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2810: warning: assignment from incompatible pointer type /tmp/vmware-root/modules/vmxnet-only/vmxnet.c:2810: error: ‘struct netdev_hw_addr’ has no member named ‘next’ make[2]: *** [/tmp/vmware-root/modules/vmxnet-only/vmxnet.o] Error 1 make[1]: *** [_module_/tmp/vmware-root/modules/vmxnet-only] Error 2 make[1]: Leaving directory `/usr/src/kernels/2.6.34.8-68.fc13.i686.PAE' make: *** [vmxnet.ko] Error 2 make: Leaving directory `/tmp/vmware-root/modules/vmxnet-only' The fast network device driver (vmxnet module) is used only for our fast networking interface. The rest of the software provided by VMware Tools is "    This is followed later with "The module vmxnet3 has already been installed on this system by another installer or package and will not be modified by this installer.  Use the flag --clobber-kernel-modules=vmxnet3 to override. The module pvscsi has already been installed on this system by another installer or package and will not be modified by this installer.  Use the flag --clobber-kernel-modules=pvscsi to override."   I'm thinking the error is most likely something going wrong.  Is there a way to fix this?   Also, should I be concerned about the vmxnet3 messages?   I'm attaching a section of most of the install messages.   Thanks;       -Greg