Содержание
- «VMware Workstation unrecoverable error: (mks) ISBRendererComm: Lost connection to mksSandbox (2878)» at end of disk shrink on Windows 10 host Fedora guest #561
- Comments
- Vmware workstation unrecoverable error mks isbrenderercomm lost connection to mkssandbox
«VMware Workstation unrecoverable error: (mks) ISBRendererComm: Lost connection to mksSandbox (2878)» at end of disk shrink on Windows 10 host Fedora guest #561
I believe since VMware Workstation 16.2 or a recent Windows 10 update (host) that disk shrinking, in my case on a Fedora 34 or 35 guest, causes an mksSandbox core dump at the end of the process on the VMware Windows application side. It didn’t used to ever do this.
As per usual within the guest I run:
The Linux side completes successfully to 99% and then the Windows popup to shrink the vmdk comes up and that progress bar goes to the end. It stays open at 100% progress for a long while because looks like the Windows Security antimalware needs to scan the resized vmdk in full again and it takes some time as it’s doing it using a single thread. (this is a separate issue that’s been happening since the last couple versions of VMware Workstation on Windows 10 host and it didn’t used to, but wasn’t a big deal to me as it did always eventually finish)
But now instead of eventually finishing and renaming the shrunken tmp vmdk back to it’s original name I get a Windows popup from the VMware application:
This crashes the running VM and the VMware Windows app. Since it happens right at the end I tried manually renaming the tmp vmdk to original after the crash and it comes back up. Seem like no damage is done other than the crash.
FYI my Fedora VMs are always standard partitions using ext4
The text was updated successfully, but these errors were encountered:
Источник
Vmware workstation unrecoverable error mks isbrenderercomm lost connection to mkssandbox
How can I solve the following problem? I have attached the relevant files below. Thanks for your help.
Moderator edit by wila: Moved thread from Technical Community Resources to Workstation Pro discussions and put the log snippet in a spoiler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any clues as to which Workstation version you are using?
And what guest OS you are running in the VM?
And what you were doing when it happened?
And any changes you made since it last worked?
And any troubleshooting steps you’ve already taken?
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Windows 7 x64 — 4 GB Ram
hangs when opening the game. last time i encountered the same error 4 minutes ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And any changes you made since it last worked?
And any troubleshooting steps you’ve already taken?
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I haven’t made any changes. I can’t fix the problem as I also don’t know how to fix it. My English is a little bad. Sorry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One thing to try is to disable 3D hardware acceleration on the VM.
If that doesn’t help then please attach a full vmware.log file, not just a few lines so that we don’t have to ask 20 questions.
PS: You probably have to zip/compress the log file for being able to attach it here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have disabled 3D hardware acceleration in the virtual machine. But the game seems to be opening but does not appear on the screen. I’m just waiting.
I have shared the log file and the picture of the error below. Can you help me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have shared the log file and the picture of the error below. Can you help me?
I looked at your log and don’t see anything out of the ordinary.
If there’s somebody else who can help, then they still need that same log file though.
There’s a chance that the mkssandbox.log has some additional information as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have shared the log file and the picture of the error below. Can you help me?
I looked at your log and don’t see anything out of the ordinary.
If there’s somebody else who can help, then they still need that same log file though.
There’s a chance that the mkssandbox.log has some additional information as well.
Yes, having mksSandbox.log would be helpful. It should tell us more about the reason for the crash and why Workstation is picking up Intel integrated GPU over NVIDIA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have disabled 3D hardware acceleration in the virtual machine. But the game seems to be opening but does not appear on the screen. I’m just waiting.
You need to keep 3D hardware acceleration enabled to run 3D games in the VM.
On dual-GPU systems like yours, you need to make sure Workstation is picking the High performance GPU (NVIDIA GeForce GTX 1060 in your case) over the Power saving GPU. This should give you better performance, but more importantly, potentially fix the crash.
On your host OS, go to Settings -> Display settings -> scroll down to reveal Graphic settings.
Источник
«VMware Workstation unrecoverable error: (mks) ISBRendererComm: Lost connection to mksSandbox (2878)» at end of disk shrink on Windows 10 host Fedora guest #561
Comments
hermidalc commented Dec 10, 2021
I believe since VMware Workstation 16.2 or a recent Windows 10 update (host) that disk shrinking, in my case on a Fedora 34 or 35 guest, causes an mksSandbox core dump at the end of the process on the VMware Windows application side. It didn’t used to ever do this.
As per usual within the guest I run:
The Linux side completes successfully to 99% and then the Windows popup to shrink the vmdk comes up and that progress bar goes to the end. It stays open at 100% progress for a long while because looks like the Windows Security antimalware needs to scan the resized vmdk in full again and it takes some time as it’s doing it using a single thread. (this is a separate issue that’s been happening since the last couple versions of VMware Workstation on Windows 10 host and it didn’t used to, but wasn’t a big deal to me as it did always eventually finish)
But now instead of eventually finishing and renaming the shrunken tmp vmdk back to it’s original name I get a Windows popup from the VMware application:
This crashes the running VM and the VMware Windows app. Since it happens right at the end I tried manually renaming the tmp vmdk to original after the crash and it comes back up. Seem like no damage is done other than the crash.
FYI my Fedora VMs are always standard partitions using ext4
The text was updated successfully, but these errors were encountered:
Источник
Vmware workstation unrecoverable error mks isbrenderercomm lost connection to mkssandbox
How can I solve the following problem? I have attached the relevant files below. Thanks for your help.
Moderator edit by wila: Moved thread from Technical Community Resources to Workstation Pro discussions and put the log snippet in a spoiler
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any clues as to which Workstation version you are using?
And what guest OS you are running in the VM?
And what you were doing when it happened?
And any changes you made since it last worked?
And any troubleshooting steps you’ve already taken?
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Windows 7 x64 — 4 GB Ram
hangs when opening the game. last time i encountered the same error 4 minutes ago
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
And any changes you made since it last worked?
And any troubleshooting steps you’ve already taken?
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I haven’t made any changes. I can’t fix the problem as I also don’t know how to fix it. My English is a little bad. Sorry
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One thing to try is to disable 3D hardware acceleration on the VM.
If that doesn’t help then please attach a full vmware.log file, not just a few lines so that we don’t have to ask 20 questions.
PS: You probably have to zip/compress the log file for being able to attach it here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have disabled 3D hardware acceleration in the virtual machine. But the game seems to be opening but does not appear on the screen. I’m just waiting.
I have shared the log file and the picture of the error below. Can you help me?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have shared the log file and the picture of the error below. Can you help me?
I looked at your log and don’t see anything out of the ordinary.
If there’s somebody else who can help, then they still need that same log file though.
There’s a chance that the mkssandbox.log has some additional information as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have shared the log file and the picture of the error below. Can you help me?
I looked at your log and don’t see anything out of the ordinary.
If there’s somebody else who can help, then they still need that same log file though.
There’s a chance that the mkssandbox.log has some additional information as well.
Yes, having mksSandbox.log would be helpful. It should tell us more about the reason for the crash and why Workstation is picking up Intel integrated GPU over NVIDIA.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have disabled 3D hardware acceleration in the virtual machine. But the game seems to be opening but does not appear on the screen. I’m just waiting.
You need to keep 3D hardware acceleration enabled to run 3D games in the VM.
On dual-GPU systems like yours, you need to make sure Workstation is picking the High performance GPU (NVIDIA GeForce GTX 1060 in your case) over the Power saving GPU. This should give you better performance, but more importantly, potentially fix the crash.
On your host OS, go to Settings -> Display settings -> scroll down to reveal Graphic settings.
Источник
Vmware workstation unrecoverable error mks isbrenderercomm lost connection to mkssandbox
My host computer runs Windows 10 Professional
I am trying to connect my Kingston USB Flash Drive to access files on it from my Windows XP setup within VMware version 16.2.0
When I open VMware Player, it shows this choice to be available.
1. When I try connecting the Kingston USB Flash Drive, the following message is being displayed, with an OK button:-
«The device Kingston ‘USB Flash Drive’ was unable to connect to its ideal host controller.
An attempt will be made to connect this device to the best available host controller. This might result in unpredictable behaviour for this device.»
2. When I then click the «OK» button , the following message displays along with an «OK» button and a «Cancel» button:-
«A USB device is about to be unplugged from the host and connected to this virtual machine.
It will first be stopped to enable safe removal. With some devices, the host may display the message «The device can now safely be removed.»»
3. When I then click this (second) «OK» button, the following error message appears:-
«VMware Player unrecoverable error: (mks)
ISBRendererComm: Lost connection to mksSandbox (2878)
A log file is available in «C:UserschishDocumentsVirtual MachinesWindows XP Professionalvmware.log».
You can request support.
To collect data to submit to VMware technical support, run «vm-support».
We will respond on the basis of your support entitlement.»
4. When I then click this (third) «OK» button, the following message appears, along with an «OK» button:-
«The following devices can be connected to this virtual machine using the status bar or choosing VM > Removeable Devices: Kingston USB Flash Drive»
5. When I then click this (fourth) «OK» button, VMWare Player shuts down without warning.
6. I also have trouble when I try connecting my «Seagate RSS BUP Slim» external hard drive. This starts with the following error message, along with an «OK» button:-
«The device ‘Seagate RSS BUP Slim’ was unable to connect to its ideal host controller.
An attempt will be made to connect this device to the best available host controller. This might result in unpredictable behaviour for this device.»
7. When I then click this (fifth) «OK» button, the following message appears along with an «OK» button:-
«A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message «The device can now safely be removed.»
8. When I then click this (sixth) «OK» button, the following error message appears, along with an «OK» button:-
«VMware Player unrecoverable error: (mks)
ISBRendererComm: Lost connection to mksSandbox (2878)
A log file is available in «C:UserschishDocumentsVirtual MachinesWindows XP Professionalvmware.log».
You can request support.
To collect data to submit to VMware technical support, run «vm-support».
We will respond on the basis of your support entitlement.»
9. When I then click this (seventh) «OK» button, VMWare Player shuts down without warning.
Note the similarities between points 1 to 5 above and points 6 to 9 — except that nothing equivlent to point 2 comes up (along with points 6 to 9) when I try connecting my ‘Seagate RSS BUP Slim’.
The above difficulties are preventing me from swapping any files between my host computer with its Windows 10 Professional operating system and my VMware virtual machine with its Windows XP Service Pack 3 operating system.
Источник
Vmware workstation unrecoverable error mks isbrenderercomm lost connection to mkssandbox
My host computer runs Windows 10 Professional
I am trying to connect my Kingston USB Flash Drive to access files on it from my Windows XP setup within VMware version 16.2.0
When I open VMware Player, it shows this choice to be available.
1. When I try connecting the Kingston USB Flash Drive, the following message is being displayed, with an OK button:-
«The device Kingston ‘USB Flash Drive’ was unable to connect to its ideal host controller.
An attempt will be made to connect this device to the best available host controller. This might result in unpredictable behaviour for this device.»
2. When I then click the «OK» button , the following message displays along with an «OK» button and a «Cancel» button:-
«A USB device is about to be unplugged from the host and connected to this virtual machine.
It will first be stopped to enable safe removal. With some devices, the host may display the message «The device can now safely be removed.»»
3. When I then click this (second) «OK» button, the following error message appears:-
«VMware Player unrecoverable error: (mks)
ISBRendererComm: Lost connection to mksSandbox (2878)
A log file is available in «C:UserschishDocumentsVirtual MachinesWindows XP Professionalvmware.log».
You can request support.
To collect data to submit to VMware technical support, run «vm-support».
We will respond on the basis of your support entitlement.»
4. When I then click this (third) «OK» button, the following message appears, along with an «OK» button:-
«The following devices can be connected to this virtual machine using the status bar or choosing VM > Removeable Devices: Kingston USB Flash Drive»
5. When I then click this (fourth) «OK» button, VMWare Player shuts down without warning.
6. I also have trouble when I try connecting my «Seagate RSS BUP Slim» external hard drive. This starts with the following error message, along with an «OK» button:-
«The device ‘Seagate RSS BUP Slim’ was unable to connect to its ideal host controller.
An attempt will be made to connect this device to the best available host controller. This might result in unpredictable behaviour for this device.»
7. When I then click this (fifth) «OK» button, the following message appears along with an «OK» button:-
«A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message «The device can now safely be removed.»
8. When I then click this (sixth) «OK» button, the following error message appears, along with an «OK» button:-
«VMware Player unrecoverable error: (mks)
ISBRendererComm: Lost connection to mksSandbox (2878)
A log file is available in «C:UserschishDocumentsVirtual MachinesWindows XP Professionalvmware.log».
You can request support.
To collect data to submit to VMware technical support, run «vm-support».
We will respond on the basis of your support entitlement.»
9. When I then click this (seventh) «OK» button, VMWare Player shuts down without warning.
Note the similarities between points 1 to 5 above and points 6 to 9 — except that nothing equivlent to point 2 comes up (along with points 6 to 9) when I try connecting my ‘Seagate RSS BUP Slim’.
The above difficulties are preventing me from swapping any files between my host computer with its Windows 10 Professional operating system and my VMware virtual machine with its Windows XP Service Pack 3 operating system.
Источник
When was the last time you tried to remote console to a VM only to be greeted with the annoying Unable to connect to the MKS or similar message? Some of the causes leading to this issue range from firewalls blocking the required ports, badly configured DNS, and ESXi services in need of a restart. Today’s post explores a number of ways you can use to remote console to a VMware virtual machine and what you can do when remote connections fail, and you are unable to connect to the MSK.
Speaking of firewalls, adding a persistent firewall rule to ESXi can be daunting. I discuss how to do this in How to create persistent firewall rules on ESXi.
What is MKS?
MKS stands for Mouse, Keyboard and Screen. In vSphere, you can remote console to VMs using the standard vSphere clients and products such as VMware Workstation.
In pre-6.5 vSphere releases, you can use the legacy vSphere client which has now been deprecated for a long time. As shown next, just highlight the virtual machine you want to connect to and click on the Console tab. Alternatively, right-click on the VM and select Open Console. The latter method opens a stand-alone console window for you.
Remote console using the vSphere Client
If you have vCenter installed, the vSphere Web Client provides you with two remote console options, these being VMRC (the standalone VMware Remote Console) and the Web Console.
You can change the default virtual console by clicking on your user in the top right corner > My Preferences > Default Console > You can then select the web or vmrc as your default console.
You also get both options directly underneath the preview of the VM screen in the VM view. VMRC is installed by following the link given in vSphere client or by downloading it from here.
NOTE: Users who have VMware Workstation installed will have noticed that selecting Launch Remote Console brings up Workstation’s VMRC instead of the standalone one. To override this behavior, uninstall the standalone VMRC and reinstall it back.
Back to vSphere Web Client, clicking on the VM’s console screen or selecting Open Console from the VM’s context menu will launch the default remote console.
Choose between the web console and VMRC.
Remote console using the host client (ESXi embedded)
Interestingly, you can configure a virtual machine such that you connect to it using a remote client such as tightVNC. To do this, add the following lines to the VM’s configuration (Edit Settings -> VM Options tab -> Advanced Settings -> Edit Configuration). You must disable the ESXi firewall for this to work or add a rule to allow 5900 through, this being the default VNC port. If memory serves me right, this worked with ESXi 5.x versions but to be honest, I had little time to try it out on 6.x. With ESXi 6.5, I manage to establish a connection but it keeps asking for a password regardless of the one specified in the VM’s configuration.
Configuring a VM to accept remote connections from VNC
What can go wrong and how to fix it
Some of the MKS errors (for instance, vmware unable to connect to the mks internal error) you might see are as follows:
-
- Error connecting: Host address lookup for server <SERVER> failed: The requested name is valid and was found in the database, but it does not have the correct associated data being resolved for.
-
- Error connecting: cannot connect to host <host>: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because the connected host has failed to respond.
-
- Error connecting: You need to execute access in order to connect with the VMware console. Access denied for config file.
-
- Unable to connect to MKS: Failed to connect to server IP:903.
1. Firewalls
Depending on the version of ESXi / vCenter Server installed, TCP ports 902, 903, 443 and 9443 need to be reachable when using the web based and standalone remote consoles. With vSphere 6.5, I managed to replicate a common problem where a personal firewall, or one sitting between the client computer and ESXi networks, is blocking one or more ports especially 902. To do this, I enabled the Windows firewall and created an outbound rule blocking 902 as shown.
Managing Microsoft Windows firewall rules
When the firewall rule is enabled, the following is what you get when trying to remote console to a virtual machine. The error message might differ slightly depending at which point the connection is dropped.
Remote console connection errors due to a firewall blocking ports 902 and 9443
Changing the firewall rule to Allow from Block fixes the “unable to connect to the mks” issue. Often, the lost ability to remote console occurs right after someone installs or rolls out security software incorporating a personal firewall. From my experience, other primary suspects include updates to group policies governing the Windows firewall and unannounced changes to ACLs on switches / routers. If you’re not the one administering the latter, talk to your colleagues to try and narrow down the source of the problem.
You can use netstat to verify that connections on port 902 are being established when you remote console to a VM. If you don’t see any entries, the issue is definitely firewall / network related. Another trick you can use is to telnet <ESXi IP> 902 from a command prompt or terminal. If you get a reply, it means that ESXi is listening on the port and ready for connections.
Using netstat to inspect network connections
If you’re not running a personal firewall, SSH to ESXi and temporarily disable the ESXi firewall by running esxcli network firewall set –enabled false. Verify that you can connect. If not, it’s a firewall sitting in between the management station and ESXi that’s dropping the connection.
If the problem persists after having ruled out firewalling as a problem source, move on to the next check.
2. DNS
Connection to remote console can also be impeded if ESXi and vCenter Server hostnames do not resolve correctly. To determine correct DNS resolution, use ping <ESXi hostname> or nslookup to verify that your ESXi and vCenter Server hostnames are resolving to the correct IP addresses and, likewise, to the correct hostnames. If the issues persists, try adding your ESXi hosts and IP addresses to windowssystem32driversetchosts, run ipconfig /flushdns and retry.
192.168.10.10 ESX65-a.lab.local
192.168.10.11 ESX65-b.lab.local
192.168.10.12 ESX65-c.lab.local
3. Free Disk Space
If firewalling and DNS are not the culprit, verify that the partition where /var lives has enough free disk space. To do this, run df -h from an SSH session on the ESXi hosting the VM you’re trying to remote console to. Make sure that the partition where /var is located is not full.
Checking for free disk space on ESXi
Another command you could use is vdh -h.
Making sure /var has free disk space using the vdf -h command
4. Permissions
Verify that the permissions set on the VM’s VMX file are set correctly (755). To check the permissions, run the command:
ls -l *.vmx
-rwxr-xr-x 1 root root 3995 Aug 18 10:00 Windows 7.vmx
We can see that the permissions are correctly set for the VMX file of a VM called Window 7.
-
- rwx = 111 = 7
-
- r-x = 101 = 5
-
- r-x = 101 = 5
If the VMX file permissions are not set to 755, run the following command:
chmod 755 ‘Windows 7.vmx’
Note: On ESXi 6.5, setting the permissions to read only had no effect so the permissions issues might only apply to older versions of ESXi.
5. If nothing else works!
If none of the above worked, try doing the following:
-
- Check that the time on ESXi is set correctly and in sync with the rest of the infrastructure.
-
- vMotion the VM you’re unable to remote console to, to another ESXi host and retry.
-
- Restart the management agents on ESXi as per the following KB.
-
- Reboot the VM.
-
- Reboot ESXi.
Note: Sometimes to fix if vmware remote console is unable to connect to the mks is as trivial as pressing a key while the focus is given to the console window. This was common with older versions of the legacy client and vSphere releases where nothing is displayed in the VM’s console window. Hitting Enter or another key usually brings the console back to life. An alternative fix is to launch the console in its own window by right-clicking on it and selecting Open Console.
Conclusion
Being able to remote console to a virtual machine is, of course, an integral part of any admin’s job. Seeing the dreaded “Unable to connect to the MKS” message and being able to console can be highly frustrating more so when you need to fix something fast. In most cases, the problem lies with a firewall blocking one or more required ports and missing or bad DNS entries. For the rest, it’s usually enough to vMotion a VM to another host or restart the management agent on ESXi.
If you enjoyed reading this post, why not have a look at The Complete List of VMware Articles.