Hi,

no, not really - but meanwhile I found out that it is not really a perl issue. I ran a valgrind on it, and I got a message like "the impossible happened". And I can reproduce the error on the Xen host itself.

Anyway, if I let the VM run alone on the Xen host, everything is fine and the error is gone. But as soon as a second VM is running in parallel on the same host, the error is there again. So I guess it's more a Xen issue, and I'll do a follow-up with the Xen guys as soon as I have enough evidence :)

Thanks for all your suggestions!

Thomas