|
From: Heiko Z. <he...@zu...> - 2006-04-13 18:14:29
|
On Thu, April 13, 2006 13:05, Kari Mattsson wrote: > > We (actually our customer) have been running 1.2.6 as a firewall in ESX > 2.5.2 (2 different update levels) since it came out. It is rock solid. > 1 CPU, 128 MB RAM, 4 NICs. Best uptime 3+ months. The only time DL is > booted, is when the whole system is upgraded. > > 1.2.6 (i686 server version) is the stock one, no vmware tools. Good to know, thanks for the infos. > I presume you guys are talking about the free VMware Server? I think it > might be a good thing to mention. Yes it's the free one. If I get approval, I only want to add the vmxnet and the vmmemctl (memory management for ESX server) modules. They seem to be the same between the various versions. If they deny the request, you will still be able to use a DL version with VMWare support, but you'll have to compile it yourself. I will leave the scripts and the only thing you'd have to do is copy the source files over. > One interesting side note: DL virtual machine is still not working in > proxy-arped DMZ. I've been forced to use Gentoo and Debian instead. I've > boiled down the problem to the pcnet32.o in DL - it doesn't like the > virtual switch or something. If/when we can change to vmxnet or even the > vlance driver in VMware Tools, I think the problem will vanish. Since you have ESX, try the e1000 drivers. I heard they behave better. > By the way, on VMware ESX, when I launch 10 DL VMs of same version, it > first takes up quite a lot of memory. After a while ESX finds identical > 4K block in memory and collapses each block in to one. It save *a lot* > memory :-) Wow that's pretty cool ! -- Regards Heiko Zuerker http://www.devil-linux.org |