Launching RDM causes VirtualBox instances to become unresponsive
There are times that when I launch RDM in a VirtualBox machine it causes it to become unresponsive, it hangs. I have to pause the machine for a few seconds then unpause it to get it to resume functioning. Sometimes I have to pause/unpause several times, or straight up kill the virtual machine.
Has anyone one else seen this?
My setup:
I use the VirtualBox machines to isolate connectivity to various customer systems, hence running RDM inside of the VM instead at the host level. Sometimes I run multiple VMs, usually 1-2 most at a time.
I haven't dug into the VirtualBox logs yet to find out why this happens. Just want to check to see if anyone else has seen this before I go deeper into this.
Thanks.
Hello,
Thank you for reaching out to us regarding this,
I must say I've not seen this before, could you confirm which version of RDM you are using?
Are there any logs in the Windows Event Viewer of the virtual machine relating to this crash?
Let me know,
Best regards,
Samuel Dery
Thanks for the reply, it's helpful to know that you haven't seen it.
I should have included the version information in my original post. I've updated that and added a couple more points of information.
I've yet to look into event viewer or the virtualbox logs for this. I'll do that when I get some free time. When it happens I'm typically pressed for time.
Thanks again!
Hello Eugene,
Thank you for your reply,
No problem, you could update to the latest version 2024.1.12.0 to see if the problem persists:
https://devolutions.net/remote-desktop-manager/home/thankyou/rdmsetup/
Let me know once you've had the time to look at the event viewer logs,
Best regards,
Samuel Dery
An update on this: It not RDM's fault.
Despite having turned off Hyper-V on my system, Windows 11 still had it enabled for some features. I went through a long game of whack-a-mole to get Hyper-V turned off and finally my VMs and RDM sessions within my VMs reached stability.
RDM just happens to be the most resource intensive application I use in these VMs, so it was the one triggering the problems that Hyper-V was creating.