Archive for the tag 'virtualization'

Why I prefer Gentoo

When talking about Linux, most people really mean that-Linux-Kernel-with-userland-tools. And there are a lot of flavours of that as distrowatch shows. As being asked a lot what and why I use [it], here is the answer: Gentoo. And that’s why: Read more »

cross-compiling under i686 Gentoo for x86_64 AMD64 Hyper-V

After moving my old Pentium 4 server into Hyper-V I’ve had some problems compiling a new kernel for the 64bit Hyper-V VM. The server itself had been moved by simple tar/netcat pipes into its new destination. (Thank you Alex, for the assistance!)

I had to emerge crossdev, then let crossdev compile Binutils, GCC etc. for the new enivronment by invoking crossdev -t amd64.

Having that done I configured the kernel as usual (don’t forget to activate IA32 emulation!) and compiled it by make ARCH=x86_64 CROSS_COMPILE=x86_64-pc-linux-gnu- bzImage. If you happen to compile modules simply append corresponding arguments.

After a restart everything will work fine.
Just remember to add a “legacy network card” (100 MBit –> tulip/DECnet 21140 in the kernel) to your VM and check whether it has changed from eth0 to something other! (See /proc/sys/net/ipv4/neigh/eth*)
Plus, try to compile the kernel as XEN guest (more) – Hyper-V is said to share interfaces with it (and more).

Snapshot trees in Hyper-V and automated backup

One important feature is missing from VMware Server 2 – the ability to make multiple snapshots. And I did not discover how to make snapshot hierarchies with it. (Although it is possible with Workstation 6 – screenshots here.)

That is something you can easily do with Hyper-V. On installing Exchange? Ever tried with/without DC? Forefront? Spamassassin? Combinations? Now it is possible. I have installed a Windows Server 2008, activated it and run a snapshot with Visual Studio installed, another without etc.

You can always revert your VM to a snapshot (in German horribly translated as “Snapshot anwenden”) and, in case you don’t need it anymore, safely delete it. The next time you power off/shutdown your VM the delta will get integrated. Plus, you can assign a different drive for your snapshots. Handy!

Tore Lervik, the programmer behind the sidebar widget, has written a script which utilizes snapshot functionality for backups. But beware: There is no data de-duplication, therefore your backup space will get filled very vigorously:

Hyper-V to replace VMWare Server

Some weeks ago I have deployed two virtual machines to run my Windows Homeserver and an Exchange Server 2007 SP1. Well, VMware was the first option to do so, and I installed version 2.

VMware Server 2 build 8xxxx has not started my VMs after host’s reboots and repeatedly asked whether I copied the machines or moved it. There was no default in order to avoid these silly questions as I did neither. Obviously this must be something with my second harddrive containing the VMs. Then, build 101586 crashed my host every time a VM started…

A nice thing has been the web access for administration and the option to utilize VMware’s Virtual Infrastructure [Client], but in summa these demanded quite a big portion of my RAM (about 500 MB). The fact that 2 GB of guest RAM grew to an usage of about 3.5 GB host’s RAM usage made me move to Hyper-V.

The latter consumes only about 2.5 GB RAM and network performance increased significantly! Where VMware limits the guests’ network speed to the one the host is connected (say 100 MBit), Hyper-V creates a virtual net “above” your host’s networking device, with 10 GBit. Therefore I can transfer data from/to my Homeserver with full speed. Excellent!

I/O-Performance is quite good, and for computing performance I do not have the tools to measure it. Honestly spoken, it is not that relevant as I run an fileserver and a mailserver for definitely under 25 users.

But, there is still some bugs in Hyper-V. I could not manage to copy VMs and trivial importing/exporting did not work.

On moving to Hyper-V? Make sure you check these out: