Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What I need to do is create a virtual machine template and deploy up to a hundred copies of it at a time. I don't care if this is done in Hyper-V/SCVMM, VMWare ESXi, Xen or VirtualBox, as I can work with any of them. I have yet to find a way to deploy more than one image at a time. Any Suggestions?


migration rejected from Nov 29 '15 at 21:25

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as too broad by Ward, Florin Asăvoaie, womble Nov 29 '15 at 21:25

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

There are about a zillion options here but what is most vendor agnostic is simple PXE + minimalist kickstart + a SCM system like puppet or chef. You can also use a copy on write OS template rather than PXE for the initial setup but past that it's useful to go with a SCM system to handle all your custom configuration instead of constantly dealing with managing disk images.


Learn programming or a scriptable language.

Hyper-V is scriptable. Like totally scriptable. This means anyone worth 10 cents for administration can write scripts to deploy images from a central share and configure the VM and start it, and the result is distributing this script to all the boxes, which - again - any 10 cents worth admin has the tools for in place (some enterprise system control package, like - for Hyper-V - SCCM / SCOM).

It is not that complicated to set up a VM. Copy virtual image file / create delta disc file, then set up VM etc. - for Hyper-V about a page of code, two if you have a lot of complicated settings.


Can the virtual machine's filesystem be read only? If so, in xen/kvm (probably all hypervisors) you can have a base image that all the VMs boot off of with read only access. You just need to create a config file for each host. So for example you have one base image: /mnt/base_hvm/system.img, and a bunch of config files that look like this:

disk = [ 'file:/mnt/base_hvm/system.img,hda,r' ]
vif = [ ' ' ]   #By default no n/w interfaces are configured. E.g:  A default hvm install will have the line as vif=[ 'type=ioemu,bridge=xenbr0' ]
builder = "hvm"
device_model = "/usr/lib/xen/bin/qemu-dm"
serial = "pty" # enable serial console
on_reboot   = 'restart'
on_crash    = 'restart'

Then you can start as many machines on that one image as you want. You could mount some empty file images for each writable /tmp /var/tmp that you want to provide individually to each system for write access as you want.


... I could go on, but ig you could provide more information about budget, etc it would help a lot


Not the answer you're looking for? Browse other questions tagged or ask your own question.