Hi, Falko
i execute after "rkhunter --update" and i obtain the same result.
My distribution is a debian etch in a container of openvz (with proxmox). Can are this a issue?
PD: the distribution of the fisical server with proxmox is a debian lenny.

You have run the original rkhunter check on a different host then migrated the virtual machine then ran the check on the new system again... and this is the result. Different hardware, different inodes.

It's a good policy to do 'rkhunter --propupd' before and after the migration.