Virtual Box damages Vmware Server 2.0.2
Posted: 18. May 2010, 18:58
Hello,
I have a physical server with Windows 2008 x64 R2 SP2 Enterprise. I installed VMWare Server 2.0.2 (latest) to run some Virtual Machines. On that same system I installed, for my first time, Virtualbox just to see how it worked. Later realized that VBox was not a Server virtual program (Meaning it cannot natively run as a service) I decided it wasn't for me and uninstalled it. I rebooted my server and now Vmware Server 2.0.2 runs extremely poor network wise and disk wise. There was a noticeable slow down, copying say a 10mb file would normally take 1 milisecond now took 14 minutes! The virtual machines on VMware Server were rendered useless.
I had uninstalled, rebooted, reinstalled VMware Server 2.0.2 and the same results were happening.
I then re-installed Virtual Box and rebooted. Now Vmware Server 2.0.2 runs perfectly fine.
I am wondering what seems to have caused the permanent error, was it a driver, and why it cannot be fixed/corrected. I do have a workaround as mentioned above by leaving VBox installed but should this even happen?
Thanks for any suggestions!
I have a physical server with Windows 2008 x64 R2 SP2 Enterprise. I installed VMWare Server 2.0.2 (latest) to run some Virtual Machines. On that same system I installed, for my first time, Virtualbox just to see how it worked. Later realized that VBox was not a Server virtual program (Meaning it cannot natively run as a service) I decided it wasn't for me and uninstalled it. I rebooted my server and now Vmware Server 2.0.2 runs extremely poor network wise and disk wise. There was a noticeable slow down, copying say a 10mb file would normally take 1 milisecond now took 14 minutes! The virtual machines on VMware Server were rendered useless.
I had uninstalled, rebooted, reinstalled VMware Server 2.0.2 and the same results were happening.
I then re-installed Virtual Box and rebooted. Now Vmware Server 2.0.2 runs perfectly fine.
I am wondering what seems to have caused the permanent error, was it a driver, and why it cannot be fixed/corrected. I do have a workaround as mentioned above by leaving VBox installed but should this even happen?
Thanks for any suggestions!