Errors Hardware Linux Software VM

Wheezy Xen Dom0 & RAM

Note to self: <1Gb of RAM on a Dom0 Wheezy server causes kernel panics.

Using 2Gb of RAM seems to do the trick.

Errors Linux Software VM

Hint of the day: run-parts and not executing files

If you have a rc.local looking like this:

/bin/run-parts /etc/rc.local.d

and files in /etc/rc.local.d looking like this

it’s not going to work.

Why, you ask, after cursing and shouting for the past hour?

because run-parts ignores files with dots (“.”) and/or .sh files.

Yes. True story.

rename all the files to:

hostname sshkeys firstboot

and your problem will be solved (and of course chmod +x them).

Linux Networking Software VM

Hint of the day: @digitalocean and not mounting sshfs at boot

In /etc/fstab, be sure to add the option:


As it will attempt to start the network mounted sshfs before networking has been started.

The entire line looks like this:

[email protected]:/some/dir /local/path fuse.sshfs defaults,idmap=user,_netdev  0 0

From the man pages:


The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system).

Misc VM www

Blog’s back

Yay, after some hardware issues my blog’s back.

Zero had a corrupt reiserfs. Decommissioned the old P4 and replaced by a brand new dual Xeon. Running Xen and Debian instead of Gentoo.

And shortly there after Four (the server that hosts this VM), the Ubuntu host with Xen refused to start its networking, so I decided to start a fresh install (Debian as well this time).

One, who also had a broken hard disk (an old P3) got decommed as well.

Long story short, it’s back!

Linux Software VM

Xen: iptables issue

vm3:/# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j DNAT --to-destination
WARNING: Could not open 'kernel/net/netfilter/x_tables.ko': No such file or directory
FATAL: Could not open 'kernel/net/ipv4/netfilter/ip_tables.ko': No such file or directory
iptables v1.4.2: can't initialize iptables table `filter': iptables who? (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.


vm3:/# depmod
vm3:/# iptables -t nat -A PREROUTING -p tcp -m tcp --dport 80 -j DNAT --to-destination

All ok 🙂