MBybee |
01-19-2010 09:15 AM |
Quote:
Originally Posted by Electro
(Post 3831694)
Virtualbox is not easy to setup because it requires its network to be setup by hand while VMware does not. If I want to setup either a network bridge or NAT in Virtualbox, the setup gets complicated. It requires the kernels virtual network modules to be compiled if it they are compiled. Also the understanding the methods to setup a virtual network that Virtualbox can identify. Using a physical network connection for Virtualbox also have the same problems. Using USB devices with Virtualbox is more complicated than VMware. Other issues that I had with Virtualbox is its reliability and stability is poor compared to a very, very mature program like VMware.
VMware Server (aka GSX) is easy to setup and easy to use. The speed of both VMware and Virtualbox is the same. The only difference is the stability and reliability which VMware has and Virtualbox does not.
|
That's interesting - I've done probably 200 installs of PC-BSD and FreeBSD under Virtual Box (alpha/beta testing installers - gotta love it) without having a single network issue.
I also have Debian Lenny installed under Virtual Box, as well as Windows XP under Virtual Box. Virtual Box itself is under Windows XP in one case and under PC-BSD in the other cases.
Never a single VirtualBox related crash yet, so I guess I can't substantiate your anecdotes with my own lol :D
Sorry it's being a pain for you, though.
Now as for VMware being mature? That I can back up. Last year, I had 31 tickets open with RedHat, SAP, or Oracle related to VMware stability issues. Easy to tell - I just ran a report on my ticket queue :D
Biggest problem I had there was caused by Java or kernel settings on the clients, though.
|