Strange problem with radiusd

[j0ystick]

I'm trying my first installation of VB on an osx host. It is a current model mac mini (Leopard server version, 8gb ram), last security patches applied. Last VB release for osx, binary version.
As soon as i start any virtual machine, regardless virtual network interface settings, radiusd (running on host) stops working in a weird fashion. Radiusd is the one included with osx server, almost all services are configured from Server Admin GUI tool, almost no custom settings anywhere, radius included.

It authenticates WPA2 Access points as you can imagine. Nothing is visible in any system log: the user gets accepted by the server as normal (or refused if credentials are invalid, obviously), the client's supplicant freezes (tried on osx and windows), after some time, timeout, it popups again the authentication, and GOTO user gets accepted. Never had a problem before with radius. Currently i use vmware fusion (but in headless environment it really is not good), no problem happens with vmware bridged adapter, nor nat, nor host only.

100% reproduced every time, as soon as i stop all VMs, AP/radius auth works again.

All this happens with VMs newly created in VB and converted from VMWare.

What can i look to get/give better debugging info? I know the network system in VB is pretty different from VMWare and i'm not familiar with it and issues, all i can tell is that all interfaces are disabled except for en0, on which i bridge or nat virtual machines.

Is it some kind of incompatibility with vmware? even with those interfaces off, vmware not running, the problem remains.

[j0ystick]

Runtime log of the machine while it is probably blocking radius (tried loggin in my iphone and laptop to wifi, radius auth times out).

Note that If i disable networking completely for the vm by removing all network cards from it, radius works.

I've also tried all the emulated network card types (this one in the log is paravirtualized network card, but it is the same with all card types).