Hi. I wanted to boot up my MS-DOS virtual machine and this greeted me:
What happened here? What is VERIFY D:\build\bora-16894299\bora\vmcore\monitor\ulm\platform\windows\ulm.c:967? I do not have 😧 drive in my system, nor do I have any sort of source code it tries to verify? What's going on?
This is contents of the log file:
[log dump removed by moderator]
Moderator: Please use the Attach function in the bottom-right of the post creator to add logs, rather than doing a copy/paste of thousands of lines of text.
Regardless MSDOS VM is supported or not in version 16.0, it looks like there is a problem of the ULM crashing with the Windows 10 insider preview.
This thread has
2020-10-28T10:52:03.615+01:00| vmx| I005: Host is Windows 10 Home, 64-bit (Build 20241.1005)
and other thread https://communities.vmware.com/message/2993299#2993299
2020-10-27T01:38:34.103-07:00| vmx| I005: Host is Windows 10 Pro, 64-bit (Build 20241.1005)
Both crashes on the same line of code
2020-10-27T01:38:42.942-07:00| vcpu-1| E001: PANIC: VERIFY D:\build\ob\bora-16894299\bora\vmcore\monitor\ulm\platform\windows\ulm.c:967
2020-10-28T10:52:06.740+01:00| vcpu-0| E001: PANIC: VERIFY D:\build\ob\bora-16894299\bora\vmcore\monitor\ulm\platform\windows\ulm.c:967
Eventually this insider preview will become Windows 10 21H1 (or whatever MSFT will call it); so this ULM crash should be looked into.
My MS-DOS machine works just fine under Workstation 16.0. And it's the first production release with dariusd's fix for the CGA mode 6 in the video graphics adapter... so it darn well BETTER be supported!
So it hasn't been addressed yet. I'll try out my Linux guest and if it fails to boot, too, due to the same error, then I guess we need to report it to Microsoft as well...
You might be better posting this on a Microsoft forum than here.
I did just that, waiting for a response therefore: VMware and Hyper-V compatibility - Microsoft Community
Let's see what Microsoft devs has to say about that...
So it has been addressed and fixed in build 20251, and I can confirm that it works in my current build 20251.1
Isak Pao wrote:
> Seems like it has been fixed in Build 20251, VMWare running on the Hyper-V enabled Host able to functional again.
Thank you 🙂