jeremym's Posts

<bump> Just a quick reminder I did as asked with the .VMX entry and it worked / didn't crash. What does that tell you / does this help you? And, is it safe to continue to run this way (until perma... See more...
<bump> Just a quick reminder I did as asked with the .VMX entry and it worked / didn't crash. What does that tell you / does this help you? And, is it safe to continue to run this way (until permanent fix comes around?)
Ohhhhkay. Well that made it NOT CRASH. See results below. Also see attached LOG file as requested. Sorry for the little delay. Thanks Team ! PS: Can I keep running like this or is there some reason n... See more...
Ohhhhkay. Well that made it NOT CRASH. See results below. Also see attached LOG file as requested. Sorry for the little delay. Thanks Team ! PS: Can I keep running like this or is there some reason not to / performance impact? I would say coming up / booting appeared slower than usual, but I didn't make any scientific A:B test. LMK. Thx. - Jeremy    
You got it. So add that line to the VMX .. wait for crash again and upload logs? Just making sure I understand the directive. Thx ! PS: I upgraded the machine to VMW17-VM level today just for fun ... See more...
You got it. So add that line to the VMX .. wait for crash again and upload logs? Just making sure I understand the directive. Thx ! PS: I upgraded the machine to VMW17-VM level today just for fun to see if it helped. It didn't -JM
You got it. Steps were: 1. Change processors. 2. Powered on. 3. Wait for Blue screen. 4. Power off. 5. Upload logs. Thanks !
1. Same VM fails even I increase from 4 to 6 total (and not utilize 8 like I desire). (See fail-vm1.png) 2. Different VM succeeds even if I increase from 4 to 8 total. (See success-vm1.png.)    
Host hardware is Lenovo P1. Processor is Intel Core 9 (yes, 9) i9-1088H CPU.  Product sheet says 8 total cores. https://ark.intel.com/content/www/us/en/ark/products/203682/intel-core-i910885h-process... See more...
Host hardware is Lenovo P1. Processor is Intel Core 9 (yes, 9) i9-1088H CPU.  Product sheet says 8 total cores. https://ark.intel.com/content/www/us/en/ark/products/203682/intel-core-i910885h-processor-16m-cache-up-to-5-30-ghz.html 
Lashup of my issue: 1. Host is Windows 10 - latest - all patches, yada yada. Host running VMW 17.0.2. 2. Guest is Server 2022. 3. Guest is running for months perfectly with Processors = 4.  2 Proc... See more...
Lashup of my issue: 1. Host is Windows 10 - latest - all patches, yada yada. Host running VMW 17.0.2. 2. Guest is Server 2022. 3. Guest is running for months perfectly with Processors = 4.  2 Proc 2 Cores = Total Processor Cores = 4. 4. I need a little boost. So I power off the guest machine. Up the processors to 4 / 2 = Total Processor Cores = 8. Start VM. Result = BSOD (see below.) Inaccessible_Boot_Device. 5. Kicker is that it also wrecks the disk chain. See pic 2.  6. No way to recover the guest except from nicely made backup. Zero snapshots work after this. If there are Zero snapshots it doesn't matter, the guest is dead anyway; no recovery. 7. 100% reproducable again and again on this VM.  Reproducable when guest has snapshots OR guest has ZERO snapshots. 7b. Reproducable with ANY change to virtual CPU. Not just the desired increase. 8. Can change memory OK... but not processors. 9. NOTE: I am NOT trying to LIVE change the processors. Guest is nicely DOWN; THEN processors change. Let me know what you'd like me to attach; and I'll do it for analysis. Thanks Team !    
Can anyone tell me if there's some global config.ini setting which would prevent, say, FUTURE VMs from being allowed to perform encryption? Thanks in advance.
Interesting. I will have to give that a try. VERY helpful answer (as usual.) Thanks !
Here's the scenario: 1. I've taken ownership of the VMX file and prevented a standard user on the box from editing it. 2. Now that VM refuses to launch. Basically, it seem that if the VMX ... See more...
Here's the scenario: 1. I've taken ownership of the VMX file and prevented a standard user on the box from editing it. 2. Now that VM refuses to launch. Basically, it seem that if the VMX file isn't WRITE-able by the user, then VMware Workstation falls over and dies. I wouldn't have guessed that. I would have supposed that it would simply: a. Read what it could from the VMX file. b. Launch. c. Write files in the folder if it needed to. But it doesn't. So.. is there some secret way to, say, inside a VMX file.. give it a parameter to say "Launch anyway, even if the VMX file itself is not writeable?" Thanks in advance.
Christian: I wanted to make you aware of this solution (see the video and associated web page): http://www.policypak.com/products/manage-vmware-workstation-using-group-policy-policypak.html ... See more...
Christian: I wanted to make you aware of this solution (see the video and associated web page): http://www.policypak.com/products/manage-vmware-workstation-using-group-policy-policypak.html We can control (and lock down) almost all the "Options" settings within VMware Workstation for deployments just like yours. If you'd like to try it out, we're here for you. -Jeremy Moskowitz
Well, I've already expended it. So, knowing I cannot do it from the GUI.. What is the command line way to expand VMFS ? Thanks !
Okay. So I originally allocated a mere 100GB to my ESXi -GUEST- within VMware Workstation 9. Now I'm using VMware Workstation 9 to expand the ESXi guest's disk. When ESXi starts up.. will i... See more...
Okay. So I originally allocated a mere 100GB to my ESXi -GUEST- within VMware Workstation 9. Now I'm using VMware Workstation 9 to expand the ESXi guest's disk. When ESXi starts up.. will it just magically recognize the change? (ie: Think it has more space now?) Or must I do something to ESXi guest make it realize that more disk space is now available? Thanks in advance.
And 40 minutes later, I have my own answers: 1. My problem was that I hadn't allocated enough memory to the prototype VHD. Apparently it requires 2GB of memory when originally set in Hyper V. ... See more...
And 40 minutes later, I have my own answers: 1. My problem was that I hadn't allocated enough memory to the prototype VHD. Apparently it requires 2GB of memory when originally set in Hyper V. That did the trick. 2. Also, I didn't need the RemoteFX 3D Video Adapter in the prototype VHD. It seems like its a nice to have, not a NEED to have. I'm off and running now.
Hi Gang. I'm trying to do a quick proof of concept of "Windows Server 2012 Hyper-V / VDI within VMW 9.0". So, if you're familiar with WS12, this screen: http://screencast.com/t/7H5eWj6X Every... See more...
Hi Gang. I'm trying to do a quick proof of concept of "Windows Server 2012 Hyper-V / VDI within VMW 9.0". So, if you're familiar with WS12, this screen: http://screencast.com/t/7H5eWj6X Every time I try to perform the work, I fail at the last mile -- creating the "Virtual desktop collection"  based upon the VHD I give WS12. (Here's a seven second video showing the moment of failure: http://screencast.com/t/c8R36ccEfR ) My *WORKING THEORY* is that Hyper V / VDI docs say that the VHD used as the prototype for the pool must have the software-based "RemoteFX 3D Video Adapter" in it. (Screenshot: http://screencast.com/t/cUE8Ee3jVCI So, here's the two part question: 1. Has anyone here .. ever.. gotten WS12 VDI working with Hyper-V running within VMW 9 as a guest? That is, were you able to get VDI quickstart mode to complete on this screen (Creating the "Virtual Desktop collection": http://screencast.com/t/eTQZAxq3 ) 2. If yes (or no) to #1.. Did you need to light up the software-based "RemoteFX 3D Video Adapter" inside the VHD prototype in order to do it? (If yes to this, how did you do that?) For question #2, I have turned on "Accelerate 3D Graphics" in the guest definition, but it doesn't seem to make a difference to the guest either way. Thanks in advance. -Jeremy M
I tried to search my old notes on this one. Item 1: While this official answer from Vmware tech support referres to that article, perhaps having my SR# request can help you, should you call u... See more...
I tried to search my old notes on this one. Item 1: While this official answer from Vmware tech support referres to that article, perhaps having my SR# request can help you, should you call up for tech support.  (see below). Item 2: While I haven't tried it recently, I'm 98% sure you can find it in *OLDER* versions. I checked my notes, and I was specifically using 7.1.3 when I made my support call, so I have to assume it's that version of the tools. -----Original Message----- From: VMware Technical Support [mailto:webform@vmware.com] Sent: Thursday, January 13, 2011 12:57 PM Subject: Re: VMware Support Request SR# 1602555141 ** Please do not change the subject line of this email if you wish to respond. ** KB referral: 000787983 Hello Jeremy, Can you try something for me?  I am attaching a document that will instruct you on how to revert to our VGA driver instead of the WDDM driver.  I want you to try that out and see if you experience the same issue.  You can also take a look at the knowledge base article below for the same instructions. http://kb.vmware.com/kb/1026466 Regards, Kellan Adamson Desktop Technical Support Specialist Global Support Services VMware Inc. Contacting Support: 1-877-4-VMWARE (1-877-486-9273) KB referral: 000787983
Try these steps after mounting the TOOLS CD: Switching from SVGA II to WDDM 1. Click Start. 2. Right-click Computer and click Manage. 3. Click Device Manager in the left pane. 4. Expand Di... See more...
Try these steps after mounting the TOOLS CD: Switching from SVGA II to WDDM 1. Click Start. 2. Right-click Computer and click Manage. 3. Click Device Manager in the left pane. 4. Expand Display Adapters. 5. Right-click VMware SVGA II and click Uninstall. 6. Select Delete the driver software for this device. 7. Reboot the virtual machine. 8. Click Start. 9. Right-click Computer and click Manage. 10. Click Device Manager. 11. Expand Display Adapters. 12. Right-click Standard VGA Graphics Adapter and click Update Driver Software. 13. Select Browse my computer for the driver software. 14. Navigate to and select the folder C:\Program Files\Common Files\VMware\drivers\wddm_video. 15. Reboot the virtual machine.
My only other suggestion would be.. In the guests.. update the VMware tools.. and if that DOESNT work, then un-install the tools and RE-install the tools. That has worked several times for me.... See more...
My only other suggestion would be.. In the guests.. update the VMware tools.. and if that DOESNT work, then un-install the tools and RE-install the tools. That has worked several times for me.
You cannot drag and drop to/from shared guests. Regular guests (not yet shared) should be fine. Sometimes when regular drag-and-drop 'freaks out'..  I hit CTL+ALT+DEL inside the vm..which w... See more...
You cannot drag and drop to/from shared guests. Regular guests (not yet shared) should be fine. Sometimes when regular drag-and-drop 'freaks out'..  I hit CTL+ALT+DEL inside the vm..which wakes up both the guest and host.. and somehow starts to allow drag and drop.
Sorry if I'm not being clear. I have no desire .. ever.. to catch up with the "regular" (real) hardware time. My goal is to be able to: 1. Start up the guest. 2. RTC time is set to <wha... See more...
Sorry if I'm not being clear. I have no desire .. ever.. to catch up with the "regular" (real) hardware time. My goal is to be able to: 1. Start up the guest. 2. RTC time is set to <whatever> 3. I can reboot, restart, power cycle the guest at will. 4. The guest CONTINUES  to accumulate time when restarted and doesn't "reset" back to RTC time when restarted. Thanks.