Hi,
I would have suggested the same as dlhotka.
The subject of your topic surprises me a bit though.
Are you really trying to use VMDKMounter? Last I heard about that tool was Fusion 3.
IOW, it's like 10 years old and I'm not surprised that it doesn't work now.
Normally the VM itself should boot. If it doesn't and the top from dlhotka isn't working then do attach a vmware.log file of a failed boot.
--
Wil
What is the Vm3dservice.exe file that Fusion 11.5 loads in the Windows 10 startup folder?
Thanks dlhotka and Wil.
VMWare Support responded to my request and provided instructions that allowed me to boot from the previously existing VMDK, which also solved the VMDK mounting issue. All I had to do was create a new VM and make the old VMDK its boot volume. The process was straightforward, and I should have thought of it myself, only I had become a little reluctant to delve into it because of my uncertainty about how to deal with selecting the boot volume after drilling into the vmwarevm package of the old VM. That and I just jumped from 8 to 11.5, having hardly tried using Fusion during the interim. Anyway, it's solved. Thanks again.
No change. I tried the experiment a couple of times.
Thank you for your attempt to help.
We open a SR with vmware and there workaround was to clone the golden imge, I think the only solution is to first delete the desktop pool, then delete the snapshots and the vmdks will be deleted as well, finally recreate the desktop pool, I will try this and lets see what happens.
Such as??
That did not help either. One thing I noticed the other day, maybe not relevant, is when I tried to import the VM, after navigating to the folder that contains the VM, was empty. I think I then used the open with command.
Hi all,
We noticed with recent Microsoft updates,
VMware Workstation Pro and Player versions 15.0 and earlier can no longer be launched on Windows 10 1903, after these Windows 10 KBs are applied.After investigation we found following entries were added to Windows 10 Application Compatibility Database (shim database), which will block Workstation and Player with the versions less than or equal to 15.0.
We have reported this problem to Microsoft and working with them on a solution.
As a workaround for Workstation 15.0 customers, you can upgrade to the latest Workstation 15.5 which is a free update. For Workstation 15.0 and prior versions, you could uninstall above Microsoft KBs. If you have concerns about uninstalling above KBs, there are couple of workarounds as mentioned in following community threads:
We are sorry for any inconvenience caused by this.
Appreciate your understanding and we will work with Microsoft for a solution as soon as we can.
Thanks,
VMware Workstation Team
Anyone have an old version of io analyzer so I can test it?
Unable to find on the web. Thank you.
If you are ensured about the ESXi host settings (vmhba, Authentication, VMK port, and target address) then it may be related to specifying a method for the iSCSI inititor on the iSCSI target system. (IP, DNS, MAC, IQN). If you assigned IQN name of your vmhba in the iSCSI target, please check it again
Is this possible to do?
I am doing the following.
$TempSource = Get-Template -Name $Temps.Name -Location "SrcTemplates" -Server "vcenter1"
New-VM -Name "template" -Template $TempSource -ResourcePool "cluster" -Datastore "datastore" -Location "templates" -Server "vcenter2" -RunAsync
Whenever I run this, it starts a clone from a running VM that in the destinations vCenter. I'm trying to find a better alternative to syncing templates across locations since the content library isn't working the way it should.
I have a Windows server 2019 machine on Hyper-V, and try to convert it to vCenter (or EXSi host)
VMWare Converter always reports an error: Unable to find the system volume, reconfiguration is not possible.
Check product release note, I found that Windows server 2019 is not in “Supported Guest Operating Systems”.
https://docs.vmware.com/en/vCenter-Converter-Standalone/6.2/rn/conv_sa_62_rel_notes.html#platf
But on the “Known Issues” -> “Windows Source”, it talks about Windows server 2019, like:
“If you convert a Windows Server 2019 machine and you include a ReFS volume that....”
So, I’m a little confused, does Windows server 2019 is supported officially?
Any comment or suggestion is appreciative.
Thank you for your help!
Not too sure I understand what you mean by
it starts a clone from a running VM that in the destinations vCenter.
Hi Ted,
You DM me on twitter @adamgudger to discuss further
Thanks
Yes, you can but first, ensure you have sufficient resources for both desktop infrastructure (servers & desktop pools). Also, you should check the required IOPS on disk/storage before you deploy the VDI desktops. So it's better to dedicate two different Resource Pools for each of desktop pool on each horizon infra.
Hello,
I have registered but so far I have not received any email to activate the account. Is there any way to get the email?
Thanks
Alassani
Hello, respectful official staff, I'm glad to hear from you patiently. Some of your replies are as follows:
1. I have tried to update Win10 to 1903, VM to the latest version 15.5. As you said, 15.5 may have solved this error. The previous "DX11Shimops: 4962" bullet window did not appear again, but the new and more serious problem came. The crash may occur several hours or a day before. In 15.5 version, game pictures will appear one after another in less than 20 minutes. The difference this time is that instead of "DX11Shimops: 4962" bullet window error, it keeps the card dead, which is the most impressive difference I've made in trying different VM versions.
2. My image card model is: Nvidia RTX 20606G
3. I can't disable 3D acceleration, otherwise the game application can't enter at all. I need to use the 3D acceleration function, otherwise it's meaningless.
4. With regard to error-reporting logs, due to my negligence and ignorance, the system and VM clones have been re-installed many times, which may cause the logs to be overwritten and disappeared. I need to re-simulate such problems, and upload the logs to the FTP server after generating the logs.
=========================
Finally, it is worth mentioning that I have now forcibly installed the win7x64 physical machine on the AMD_3 CPU + X470 motherboard (you know the new product officially no longer supports win7) and then the VM continues to use the old version of V10. Magical things happen. Previous errors have not occurred, windows have not been blocked, has been tested for two days, the first day in the evening when the host automatically restarted. What happened once or again? Maybe I'm not sure why some of the physical drivers are not fully installed or incompatible. I'm not sure that there has been any error or crash since the test was run again. (I'm sure that the current situation is different from any previous attempt, and it feels like it's going to be successful.) But I'll keep watching, and I'll keep feeding back the official results. Thank you very much!
That did not work, and now this time once inside the virtual machine the mouse was limited to inside that window even though it wasn't working. Another words, the mouse pointer was trapped inside the fusion window and I couldn't move it outside to close fusion or use the mac side. I had to power off and restart.
Now what?
Hi,
Good to hear that you resolved it. Yes, that's basically what we were saying.
Beware that you check to have the whole VM in one bundle.
If you copied the disk then all should be in the same bundle.
If you used the share disk option then your config is in one bundle and the disk in another ... which might lead to confusion in times of trouble.
Also take a backup You can do so manually or use my Vimalin for that.
A new version of Vimalin that works on macOS Catalina arrives early next week (it's baked, testing time)
--
Wil
I don't have such a list/document, but I suppose all properties of a given managed object can be used, so you can check the official vSphere Web Services API documentation (for latest 6.7U3 and down to 5.5 version it is available at https://code.vmware.com/apis/704/vsphere) for a comprehensive list of all managed objects and their properties in a given vCenter version.
