virtualbox.org

The only thing I can think of is that along the way with upgrades and all, hardware-v got enabled.

I can image that 6 months ago vbox vt-x code was much less critical then today, you might imagine that vt-x=vt-x but thats not the case the more hardware vt-x features you use. The dev's might be able to shed some light on this.

...that might be right cause I never had the problem using VBox 2.2.x but with version 3.x I'm having souch strange problems.

the worst thing is that if you once screw up the system you can't simply go back to VBox 2.x.x and everything ist fine - the image will not be able to run on a CPU which does not support hardware virtualisation.

I installed a new Win XP and if I run it with VBox 2.x.x I can switch harrdware virtualisation on and off and the system is still running. If I do the same with the latest VBox release I can't go back if I swith on hardware virtualisation once...

Have a nice weekend,
Jan

See http://forums.virtualbox.org/viewtopic.php?f=6&t=24504