Introducing TermBuilder – a Linux command line generator
Posted by James B. in Technology on February 1, 2010
If you’re a Linux newbie who wants to learn a bit more about the command line, or if you want to chain a few commands together to get some special output, we have a new tool for you to try. It is called TermBuilder, and it’s a web-based command-line generator for Linux and other compatible Unixes. All you have to do is click buttons and choose options and it will generate commands for you to copy and paste into your terminal.
Now, this is just the first release of TermBuilder, and that means you should expect some bugs. Plus, it only supports a handful of commands right now – if there are things you’d like to see it do, post a comment on the TermBuilder page and we’ll see what we can do. In the meantime, give it a try and let us know what you think!
TermBuilder: a graphical Linux command line generator
Microsoft to Revise VDI Licensing
Posted by James B. in Technology on January 31, 2010
Microsoft plans to modify its software licensing program to be more amenable to Windows shops that are interested in virtualization but that hold off because Microsoft’s per-device licensing makes it too expensive.
One executive responsible for Windows licensing, the Software Assurance (SA) maintenance agreement and Virtual Enterprise Centralized Desktop (VECD) said Microsoft will revitalize its licensing program later this year to lift some of the restrictions of today’s per-device model.
“We will see incremental changes on product use rights, on product use types and on requirements customers can meet to enable more types of users,” said Amilcar Alfaro, senior product manager of worldwide licensing and pricing at Microsoft. Read the rest of this entry »
Memory Overcommit Uncovered
Posted by James B. in Technology on January 29, 2010
There was a good discussion on twitter on memory overcommit and the value of memory overcommit and whether you should or should not use it in production. What struck me in this was that on a subject like this, there is so much misunderstanding although there is a lot of documentation available that can explain the subtle difference between good and bad overcommit of memory.
Memory overcommit, the basics.
In short: When you assign more RAM to your VMs than available in your host.
Good memory overcommit: When you assign more RAM to your VMs than available in your host BUT never cross the line where the amount of RAM that is USED by your VMs is more than available in your host.
Bad memory overcommit: When you assign more RAM to your VMs than available in your host AND cross the line where the amount of RAM that is USED by your VMs is more than available in your host.
A simple example:
Host has 48GB of RAM and just for the sake of argument we’ll pretend the hypervisor doesn’t use any RAM and we don’t have memory overhead per VM. I now start loading it with VMs that have 4GB RAM assigned. Without any memory overcommit I can load this host with 12 VMs of each 4GB.
Now let’s say, these VMs normally use only 2.5GB of RAM but sometimes they peak to 4GB. With memory overcommit I could now load the host with 19 VMs of 4GB RAM assigning a total of 76GB RAM and demanding 19 x 2.5GB = 47.5GB of physical memory. Even to me this is a bit on the edge, so I’d reserve some RAM for spikes and would go back to 17 VMs, which would leave me with 17 x 2.5GB = 42.5GB of actively used physical RAM, 17 x 4GB = 68GB of RAM assigned and therefore 68GB-48GB = 20GB of overcommitted RAM. So, 20GB of RAM I didn’t have to pay for. This is a good use of memory overcommit.
Bad use of memory overcommit is when in the previous example I would place more VMs on this host, to the point where the use of physical RAM is higher than the amount of physical RAM present in the host. ESX will start some memory optimization and reclaim techniques, but in the end it will swap host memory to disk, which is bad. It is essential to carefully monitor your hosts to see if you’re moving from good memory overcommit to bad memory overcommit. Read the rest of this entry »
Cloning Hyper-V Virtual Machines – Part 3
Posted by James B. in Technology on January 25, 2010
Although Microsoft’s System Center Virtual Machine Manager automates the process of cloning a virtual machine, you can perform the cloning process manually without the aid of additional software. This article starts with the explanation of the manual cloning process.
In my previous article in this series, I showed you how you could use SYSPREP to prepare a virtual machine for cloning. Once we prepared the system image, we used System Center Virtual Machine Manager to perform the actual cloning process. Although this technique works really well, I realize that not everyone owns a copy of System Center Virtual Machine Manager. That being the case, I want to show you a cloning method that you can perform using only native Windows tools.
Cloning Hyper-V Virtual Machines – Part 2
Posted by James B. in Technology on January 23, 2010
In my previous article in this series, I explained that cloning a virtual machine is not quite as intuitive as you might have been lead to believe. Part of the reason for this is that in order for the cloning process to be successful, you need to use Sysprep to strip certain attributes from the host that is being cloned. In this article, I want to continue the discussion by showing you one method that you can use for cloning virtual machines.
hosted at:
