Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #1822
| From | Tim Watts <tw@dionic.net> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Best practice Linux support vendors? |
| Followup-To | comp.os.linux.misc |
| Date | 2011-07-16 07:49 +0100 |
| Organization | A noiseless patient Spider |
| Message-ID | <tso7f8-5j8.ln1@squidward.dionic.net> (permalink) |
| References | <39f71fac-d3bf-4144-a7ee-5d71ebd9c08f@c29g2000yqd.googlegroups.com> <oti2f8-0lg.ln1@squidward.dionic.net> <f51dbf4e-9beb-4e76-8b6d-cfeddd7f223b@fq4g2000vbb.googlegroups.com> <98bl3nFcglU6@mid.individual.net> |
Followups directed to: comp.os.linux.misc
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. -- Tim Watts
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Best practice Linux support vendors? snorble <snorble@hotmail.com> - 2011-07-13 19:12 -0700
Re: Best practice Linux support vendors? Tim Watts <tw@dionic.net> - 2011-07-14 08:36 +0100
Re: Best practice Linux support vendors? snorble <snorble@hotmail.com> - 2011-07-15 10:17 -0700
Re: Best practice Linux support vendors? The Natural Philosopher <tnp@invalid.invalid> - 2011-07-15 18:35 +0100
Re: Best practice Linux support vendors? General Schvantzkoph <schvantzkoph@yahoo.com> - 2011-07-15 20:09 +0000
Re: Best practice Linux support vendors? Tim Watts <tw@dionic.net> - 2011-07-16 07:49 +0100
Re: Best practice Linux support vendors? General Schvantzkoph <schvantzkoph@yahoo.com> - 2011-07-16 13:40 +0000
Re: Best practice Linux support vendors? Tim Watts <tw@dionic.net> - 2011-07-16 18:19 +0100
Re: Best practice Linux support vendors? Aragorn <stryder@telenet.be.invalid> - 2011-07-17 03:44 +0200
Re: Best practice Linux support vendors? aw@anhrefn.saar.de - 2011-07-14 15:25 +0200
Re: Best practice Linux support vendors? notbob <notbob@notbob.invalid> - 2011-07-14 14:13 +0000
Re: Best practice Linux support vendors? The Natural Philosopher <tnp@invalid.invalid> - 2011-07-14 19:01 +0100
Re: Best practice Linux support vendors? ray <ray@zianet.com> - 2011-07-14 14:51 +0000
Re: Best practice Linux support vendors? JeffM <jeffm_@email.com> - 2011-07-14 14:34 -0700
Re: Best practice Linux support vendors? John Hasler <jhasler@newsguy.com> - 2011-07-14 17:32 -0500
Re: Best practice Linux support vendors? Tim Watts <tw@dionic.net> - 2011-07-15 06:59 +0100
Re: Best practice Linux support vendors? Tim Watts <tw@dionic.net> - 2011-07-15 06:57 +0100
csiph-web