atxgeek 


just one more geek in a sea of austin techies
Showing posts with label VirtualBox. Show all posts
Showing posts with label VirtualBox. Show all posts

April 5, 2014

TIP: VirtualBox Unresponsive Windows #VirtualGeek

After many years of using VirtualBox as my preferred virtual desktop hosting software for development VMs I ran into a new-for-me issue:  Internet Explorer's page display would become exceedingly slow to respond to changes within a few seconds of loading.  Refreshing the page did not help.  Opening a new tab repeated the process:  slow page response a few seconds after the completion of page load.

A bit of virtual poking and prodding eventually revealed a solution, though not an explanation...
 

July 10, 2013

TIP: RPC issues with VirtualBox #VirtualGeek

I recently had occasion to set up Virtual Machine Management features of a Windows server hosted within a VirtualBox-based VM instance. I'd done this in the past but this time I was connecting to target VMs hosted within a Windows failover cluster. I could see the clustered VMs just fine (via the Failover Cluster Manager) but when selecting a specific VM and clicking "Manage virtual machine" my VMM console spat out a "RPC server unavailable" error.

It turns out that VirtualBox does not pass through the needed RPC traffic when the VirtualBox-hosted machine's NIC is in "NAT" mode.  If you encounter this, switching the NIC from the default "NAT" to "Bridged Adapter" may take care of the problem (as it did for me).

May 7, 2013

TIP: RAM and Virtual Machine Speed #VMGeek

"More is better" as the current pitch line of a certain US cellular carrier says.  For computers the "more" benefits are obvious for things like disk space, memory, CPU cores and network bandwidth.  The same holds true in the virtual world:  virtual PCs like to have more as well.

As a point of interest I recently conducted a very informal speed test between two identical virtual machines.  My only (big) variable?  RAM.  One machine had twice as much RAM as the other.  My goal was to see how much the extra RAM would benefit me during set up of a new virtual machine (even if that machine were destined to be allocated less RAM once it was up and going).  Temporarily adding RAM should translate to a shorter set up time but would it be enough of a difference to bother with?...