Hi all, Today, my server was rebooted (due to a 17min power interuption), and I was greeted by an email from it saying that it couldn't start up Virtualbox. My server is running Debian's kernel image 2.6.32-5-vserver-amd64. Yes, I AM running two virtualisation solutions on here - I didn't like Xen when I tried it for a couple of months, I just couldn't get the hang of it despite reading heaps of tutorials about it. Linux Vserver provides a very light (in terms of overhead) way of running multiple virtualised Linux "servers" through extensive use of security contexts and the like. But I also wanted to run a single Windows server instance, so hence the use of Virtualbox. The virtualbox email states that I need to ensure I have virtualbox-ose-dkms and the kernel header files installed. I have virtualbox-ose-dkms installed, but somewhere along the way my linux-headers-2.6.32-5-vserver-amd64 package became uninstalled. Instead I have headers for 2.6.37-1, 2.6.37-2, 2.6.38-1, 2.6.38-2, 2.6.39-2 and 3.0.0-1, but none of the corresponding kernel images... Go figure. So I'm thinking I'll upgrade to a newer kernel, but none of the kernel images mention vserver in their name, nor directly indicate that they support it either. I am willing to go down the path of rolling my own, and packaging it up with make-kpkg (from kernel-package) so that I don't break apt's idea of what's installed... Therefore, can anyone confirm for me if I upgrade to 2.6.39 or 3.0.0, will I still be able to use my Linux vservers (I really do NOT want to have to rebuild them all within another virtualisation environment)? Or has Xen become the defacto (and possibly only) virtualisation system that Debian's pre-packaged kernels will support? Cheers, Tim Lyth.