70tas's Posts

I found an answer at the following blog: Dixin's Blog - Run Hyper-V and VMware virtual machines on Windows 10 Thanks Dixin! Finally, after pulling my hair out, what is left of it, I found a work-around.  When you reboot, it will ask you two security questions, you must respond with F3 for both.  After rebooting Workstations works..  (For some reason, I had to take ownership on one of my VM's, because I couldn't get in to it. TasP

I was running Workstation Pro 12.5.2, on Windows 8.1 Pro x64. I upgraded to 12.5.7 and have the following issues: 1. All of my VMnets reverted to the three default, when installing Workstation as a first time 2. I had five VMs as Shared VMs;  after the upgrade (and reboot) they didn't start up     a.  I tried to see why, and found the server was disabled     b.  Enabled the server and tried rebooting -- same problem, server was disabled     c.  Removed all shared VMs, rebooted, re-enabled server and shared one VM     d.  After a host reboot, I have the same issue;  Edit/Preferences/Shared VMs are disabled. Has anyone else had this issue, and perhaps fixed it?

I'm running Workstation 11 under Windows 7 (Ent). My monitor is a Dell 2560x1440 Machine is a Dell OptiPlex 7010 with AMD 7000 video (also running workstation at home on ASUS server board, dual E5-2520 v2's with AMD R7) I am experiencing the following issues with listed guests: Windows Setting Workstation options for Auto-size/3D, Windows 7 startup is scrunched VGA in middle of the VMware window;  although it says it is the proper resolution, it is zoomed out so small it can hardly be seen.  I tried changing the sizing options in Workstation which only resulted in my resolution changing, and guest window size and placement becoming 640x480, or 800x600, not quite sure which Setting guest to 2560x1440/3D and 1GB Video RAM, Windows 7 and Windows 10 video starts as VGA, with sizing set to centered and guest at 2560x1440, zoomed out;  changing screen sizing to auto-size, again changes my guest resolution to VGA and all my windows are resized.  2560x1440 is not shown in guest available resolutions.  I found the best thing for this is to set display to auto-size/3D and on startup, press Workstation key (ALT-SHFT)-ENTER twice.  That will unzoom the guest to the proper size of the monitor.  Some windows inside the guest are moved around, but not resized. Linux At manual resolution configurations, 2560x1440 is not available.  I created a script to manually add it using 'xrandr' as follows: #!/bin/bash #Set resolution xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync xrandr --addmode Virtual1 2560x1440_60.00 xrandr --output Virtual1 --mode 2560x1440_60.00 With video auto-size on, the above does not matter, however, if I change the auto-size setting the guest windows get all confused FreeBSD based pcBSD 10.14 VMware has not released a guest tool kit for FreeBSD 10.1.  Guys what's up;  that is the primary reason I upgraded to w11.  FreeBSD 11 is around the corner, can you get a move on please Again, same as Linux, except I was not able to use xrandr.  With the guest video at Auto-detect and NO 3D, and openvm tools, it will bring the window up to 2560x1440.  However, the mouse is a problem with the openvm tools;  It is erratic to say the least, and does not work at all from a remote desktop session, or from VMware VNC, nor from client VNC's I've tried.

So I have a machine with a corporate image and was not included in local admins, so could not initially load Workstation 10.  I logged in with an admin account and added myself to the local admins group, but then as I usually do, I thought I'd me smart, and went in and took ownership and or added my previously non-admin account to C:\Users\... When I tried to upgrade to Workstation 11, I kept getting the MSI error.  Checked all of the posts, the only way I could get around it, was by logging in with the original admin account I had installed VMW 10 with, and upgrading.  I ignored the MSI errors that kept popping up.  It worked. The problem is every time I start up a VM it wants to install tools.  It downloads them, then fails saying it could not install them.  Checked forums, didn't like any of the answers, the most basic of which was to re-install Windows. I went to Microsoft and looked for MSI errors, and found a FixIt tool called "Fix problems that programs cannot be installed or uninstalled". I ran this tool, and selected "Detect problems and let me select the fixes to apply".  After thinking for a while, it asked me if the issue was installing or uninstalling;  I selected Uninstalling.  After thinking for a while it came up with a list of programs including tools-freebsd, tools-netware, tools-solaris, tools-windows and tools-pre-winpre2k.  I had to run the tool for each program one at a time, but I selected each one, and in the next screen selected "Yes, try uninstall". This process fixed the issues.  Hope it can help someone else.

I am seeing the following issues since upgrading to Workstation 10 a few days ago: VM stability Windows hosts appear to be running out of memory resources;  several recurring crashes have occurred on Workstation for the particular VM Unfortunately I have not kept track of errors, I will in future Increased memory requirements The VMs I could run in 16GB of RAM, all in memory, minus about 3GBs for the host can no longer run because of insufficient memory Workstation had me decrease the memory reserve for VMs, which in turn meant I had to decrease the memory allocated to each VM to compensate Performance appears slow, almost about 50% of what I was getting prior to the upgrade I am running on a Gigabyte mobo, 6-core AMD with 16GB of RAM. I will post more information as I collect it. Has anyone else seen these kind of issues with Workstation 10?

A long time ago, I read a post in the Communities about backing up Workstation VMs by using snapshots.  I run Workstation 9.02 under Windows 7 x64.  Here is how I do it (via script): suspend less important VMs take a snapshot called BACKUP for VMs which can't be shut down robocopy the VM subdir to an external disc delete the BACKUP snapshot on the running VMs resume the suspended VMs I've been looking through the entire Community and I don't see this method described anywhere.  I'm beginning to wonder if I'm doing it wrong?