Obscure xinetd tip

If you have a "wait=yes" server bound to 127.0.0.1, you can get a syslog full of messages like this:

xinetd[25741]: warning: can't get client address: Transport endpoint is not connected

The trick is to add "flags=NOLIBWRAP".

THis bug report gives a clue as to the underlying cause: https://bugzilla.redhat.com/show_bug.cgi?id=108583

Migrating a guest VM with Xen 3.2

'xen migrate' didn't work - it hung, as others have reported.

It turned out to be as simple as:

1. Stop the original guest.
2. Copy the disk image and the config files ( in /etc/xen/vm) to the new host.
3. Execute 'xm create guest-name' on the new host.
4. Done!