I am running VMWare Workstation 10 on Windows 8.1 Pro
I have installed a Guest OS and when I run the Guest OS for the first time, I get the following error message and my Virtual Machine will Crash.
For some reason, the Virtual Machine is having a hard time trying to configure its network card.
Every time I try to configure the network card in the virtual machine, I get the following error.
Some times, the virtual machine will just crash during boot up.
2014-02-08T18:33:48.658+08:00| vmx| I120: USBGW: Write arbitrator op:13 len:32
2014-02-08T18:33:49.302+08:00| vcpu-2| I120: E1000: Unsupported Tx buffer length: 16548
2014-02-08T18:33:49.302+08:00| vcpu-2| I120: E1000: Unsupported Tx buffer length: 24885
2014-02-08T18:33:49.909+08:00| vcpu-2| I120: E1000: Unsupported Tx buffer length: 55107
2014-02-08T18:33:49.909+08:00| vcpu-2| I120: E1000: Unsupported Tx buffer length: 14169
2014-02-08T18:33:50.254+08:00| vcpu-1| I120: E1000: Unsupported Tx buffer length: 2431
2014-02-08T18:33:50.505+08:00| vcpu-0| I120: E1000: Unsupported Tx buffer length: 47775
2014-02-08T18:33:50.795+08:00| vcpu-2| I120: NOT_IMPLEMENTED d:/build/ob/bora-1379776/bora/devices/e1000/e1000Hosted.c:1829
2014-02-08T18:33:50.795+08:00| vcpu-2| W110: Win32 object usage: GDI 13, USER 23
2014-02-08T18:33:50.795+08:00| vcpu-2| I120: CoreDump_CoreDump: faking exception to get context
Interesting. We've had a few reports similar failures lately.
What's the guest OS (and its version) you are running there? It would seem that the guest is doing something to its virtual network card that we aren't expecting.
Thanks,
--
Darius
guest os is OS X Mavericks 10.9.1
![]()
VMware does not support the running of OS X under VMware Player/Workstation! Also, running legally virtualizable versions of OS X in a Virtual Machine may only be done when done on Apple-branded hardware and when done while running under OS X and for that you need VMware Fusion not VMware Player/Workstation, otherwise you're violating the Apple SLA for that product. Therefore no help can be provided to you for OS X in this use case scenario as it would violate VMware Community Terms of Use to do so.
