OZO
Premium
join:2003-01-17
| reply to chachazz
Re: [Free] VirtualBox 3.0.0 final - major update
It's good to know, but I'm not interested in VirtualBox. Thanks you.
Since v.2.0 they've made some changes in VB memory management resulting in permanent crashes of all my VMs in my computer. Additionally now it begins to require considerably more physical memory (RAM) to run those virtual machines. So, my computer with WXP Pro, 512 MiB max becomes obsolete (from their perspective). The only suggestion was to buy a new one (which I will, of cause, but not for VB only). I've gladly returned back to VMware that handles it very well. So, see ya later, VirtualBox...
--
Keep it simple, it'll become complex by itself... |
|
B
Premium,MVM
join:2000-10-28
| said by OZO  :It's good to know, but I'm not interested in VirtualBox. Thanks you. Since v.2.0 they've made some changes in VB memory management resulting in permanent crashes of all my VMs in my computer. Additionally now it begins to require considerably more physical memory (RAM) to run those virtual machines. So, my computer with WXP Pro, 512 MiB max becomes obsolete (from their perspective). The only suggestion was to buy a new one (which I will, of cause, but not for VB only). I've gladly returned back to VMware that handles it very well. So, see ya later, VirtualBox... Which style and version of VMWare? Have you given Xen a shot?
-- B
--
In a realm outside causality and function |
|
OZO
Premium
join:2003-01-17
| I'm running VMware Workstation 6.5.2. There is no any problem with it at all. It certainty has a superior memory management comparing to VB. If VM requires an extra RAM, it simply asks Windows to allocate it (Windows swaps it with paging file, as usual). Latest versions of VB may simply crash in this case.
It's pity that I wasted all my time with VB. I was successfully running multiple VM's in VB until v.2.1.2 was released and installed. Then I started to have problems with memory allocations. I've reported it in VB forum, waited for new releases and saw it again and again. That problem was never being fixed. I've tried v.2.1.2, 2.1.4, 2.2.0 - all ended up with reliable crashes. Finally, instead of fixing this new and obvious VB problem, they have suggested to buy a new computer... Thanks. Now 512 MiB in host computer is not enough for VB to run any guest VM, except DOS. With this attitude in development I hesitate to try v.3.0. May be I'll try it again when they make v.5.0 and at that time I'll have a supercomputer to satisfy its increasing demand for computer resources...
I have not tried Xen yet. My computers have processors that are not in the list of supported CPU's. But as soon as I get one - I certainly will.
--
Keep it simple, it'll become complex by itself... |
|
B
Premium,MVM
join:2000-10-28 | Thanks for the reply!
-- B |
|
chachazz
Premium
join:2003-12-14 | quote:
Have you given Xen a shot?
not yet  ; Thanks B. |
|
