Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: General Schvantzkoph Newsgroups: comp.os.linux.misc Subject: Re: Best practice Linux support vendors? Date: 16 Jul 2011 13:40:53 GMT Lines: 39 Message-ID: <98din4FcglU7@mid.individual.net> References: <39f71fac-d3bf-4144-a7ee-5d71ebd9c08f@c29g2000yqd.googlegroups.com> <98bl3nFcglU6@mid.individual.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net wLQ7kGHltbt/pkEYYBJkCApZQ7MiK2po7+dcUbOsq8sNtIqpOQ Cancel-Lock: sha1:UxmzeSUAriTpaWl0I5/2/ib6d5c= User-Agent: Pan/0.133 (House of Butterflies) Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:1823 On Sat, 16 Jul 2011 07:49:33 +0100, Tim Watts wrote: > General Schvantzkoph wrote: > > >> KVM is pretty easy to use. I'm using Scientific Linux 6 on my servers >> and KVM VMs for both Windows and Linux. It's trivial to create a VM >> using the virt-manager. After you've created your base VMs you can >> clone them by simply making copies of the virtual disk files. With a >> Linux VM all you have to do is reconfigure the networking for each >> clone and you're done. For a Windows VM you will have to patch the >> registration number to create multiple Windows VMs that can run >> simultaneously (it's exactly the same process as if you were and OEM >> cloning Windows disks). To back up a VM just make copies of your >> working virtual disks. I use SAMBA and NFS for all of my user space on >> the VMs, that way backups can be done on the native Linux systems. >> >> The downside of KVM is that the virtual IO is pretty slow. For CPU >> intensive programs this isn't a problem but of IO intensive programs >> you'll notice it. VMware has much better IO performance but it's not >> free like KVM. > > OpenVZ is also interesting. It's not full virtualisation - rather it's > "containerisaton". Everything runs in it's own space under the same > kernel. > > Bit like a chroot jail, except each jail: > > 1) cannot see processes and other facets in other jails > > 2) each jail is resource limited in several ways at a jail level > > 3) each jail runs its own full userland but shares a common kernel. > > Needless to say, it's a lot more efficient if that model suits you. Is OpenVZ an active project? It doesn't seem to be in the repos for Fedora 14 or SL6 and the OpenVZ wiki only mentions Fedora 5 & 6 and CentOS 4 and 5, no mention of a recent distro.