pabloMVM
join:2003-06-23
kudos:1 | reply to JTC
Re: Virtualbox, vmware server 2.x, same machine said by JTC:...unless it takes down the VM subsystem, taking out a subversion server that is used by multiple community run coding projects that has devs across the globe... Hi,
Paranoid is a Good Thing [tm] when dealing with a Production(-like) environment. In this situation, I'd copy the VDI('s) and try them with VirtualBox as well. Depending on which VM you start first, you may not get hardware-level optimization (e.g. VT-x/AMD-V and/or Nested Paging) but you should get a pretty good idea of how things work (or not!  with VBox.
Cheers,
-pablo
--
openSUSE 11.1/.2;KDE/Xfce
ISP: TekSavvy DSL; backhauled via a 6KM wireless link |
|
 JTCAlways Mount A Scratch Monkey
join:2002-01-09
USA | said by pablo:Depending on which VM you start first, you may not get hardware-level optimization (e.g. VT-x/AMD-V and/or Nested Paging) but you should get a pretty good idea of how things work (or not! with VBox. Right, but will running VBox at the same time as VMWare server 2.x on the same machine cause problems with either one, that's my question.
--
All hardware sucks, all software sucks, some just suck more than others |
|
pabloMVM
join:2003-06-23
kudos:1 | said by JTC:Right, but will running VBox at the same time as VMWare server 2.x on the same machine cause problems with either one, that's my question. As long as there is no resource contention, there shouldn't be a problem. For example, suppose you were trying to share a serial port, there'd be a problem. Bridging should handle NIC requirements.
You probably already know this, do not over-subscribe your RAM. 
Cheers,
-pablo
--
openSUSE 11.1/.2;KDE/Xfce
ISP: TekSavvy DSL; backhauled via a 6KM wireless link |
|
|
|
