2013 January

apt-get upgrade failing after moving from vmware to virtual box?

Moving to VirtualBox is just a great idea when you’re coming from VMWare Server 2.0 which is no longer supported. VirtualBox is a lot more modern, also allows for a headless setup, and it is a lot faster. The only drawback I saw is that VMWare Server allows for memory overcommitment (though I did have issues with that, see my OOM post) – which means I just had to upgrade my server from 32 GB to 64 GB.

Now some problem that I ran into is this:

when doing the occasional apt-get upgrade. Turns out that when you move to vbox, you’re obviously no longer able to run the vmware tools that you may have installed. Following this post, it is an easy fix:

Hope, this helps someone.

 

By mnott on 2013/01/30 | Computer | A comment?

Pay attention to disk space when you’re running unattended upgrades on your Linux boxes

Today’s one of those days where you start with a clear plan of what you want to do, and then you end up fixing something entirely different. Since I’ve built most of my virtual machines based on a small set of templates, at some point I got bored by having to keep them updated manually (and there’s a lot of them). So one day I switched them all to automatic updates.

Now’s the other day where all of them decided to throw errors. Basically, my boot drive was chosen to small, and the automated update process didn’t remove older kernel images.

Easy to fix, though I’ve to find a way to automate that (you’ve to make sure you’re running on the latest kernel, i.e. a reboot), if you use this script from the command shell (I found it somewhere on the net but have lost track):

Little update here: I just had that again. So instead of using apt-get at the end, I ended up using dpkg -r: