 jdongEat A Beaver, Save A Tree.Premium
join:2002-07-09
Rochester, MI
kudos:1 | reply to JTC
Re: Virtualbox, vmware server 2.x, same machine »www.virtualbox.org/ticket/894
I'm not quite interested in playing the workaround game. All I'm saying is a heads-up that with the same set of virtual machine guests, similar workloads in the guests in my experience have translated to higher CPU usage on the host in VirtualBox compared to VMWare Server. I didn't investigate too much into possible workarounds, I'm not saying that this is a flaw of virtualbox with any level of confidence.
--
Ubuntu MOTU Developer and Forums Council |
|
|
|
 JTCAlways Mount A Scratch Monkey
join:2002-01-09
USA | Hmm, this looks similar to the vmware server 2.x problem in a way. The difference is that under VMWare the CPU usage on the host grows to crazy levels over time, vs VBox it's high to begin with, but doesn't seem to grow.
However, there does seem to be activity on fixing the issue vs vmware apparently ignoring their issue.
Damned if I do and damned if I don't, eh?
--
All hardware sucks, all software sucks, some just suck more than others |
|
jdongEat A Beaver, Save A Tree.Premium
join:2002-07-09
Rochester, MI
kudos:1 | Heh "activity" "fixing" and "ignoring" are all perceived effects, IMO.
--
Ubuntu MOTU Developer and Forums Council |
|
pabloMVM
join:2003-06-23
kudos:1 | reply to JTC
Plus that ticket is on a VirtualBox 1.5.[246], is closed and the current version of VBox is 3.1.4
I'd say give it a shot and see what happens. No sense in being a `nervous nelly' ... no harm no foul really to simply give it a shot.
Cheers,
-pablo
--
openSUSE 11.1/.2;KDE/Xfce
ISP: TekSavvy DSL; backhauled via a 6KM wireless link |
|
jdongEat A Beaver, Save A Tree.Premium
join:2002-07-09
Rochester, MI
kudos:1 | said by pablo:I'd say give it a shot and see what happens. No sense in being a `nervous nelly' ... no harm no foul really to simply give it a shot. Completely agreed.
--
Ubuntu MOTU Developer and Forums Council |
|
JTCAlways Mount A Scratch Monkey
join:2002-01-09
USA | said by jdong:said by pablo:I'd say give it a shot and see what happens. No sense in being a `nervous nelly' ... no harm no foul really to simply give it a shot. Completely agreed. ...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...
which is what I have. Granted, I'm providing it free of charge, but still, I don't want to take a chance with data that isn't mine. So, I'm being paranoid about the whole thing. 
--
All hardware sucks, all software sucks, some just suck more than others |
|
pabloMVM
join:2003-06-23
kudos:1 | 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 |
|
