Default SATA port count of 30 is problematic for some users => Fixed in SVN

When creating a CentOS 4.6 VM via in VB 3.2.4 OSE via LibVirt 0.8.1 (modified to handle VB 3.2), the created VM will not start properly. It either freezes during hardware detection (for at least several minutes, possibly forever), or panics. Yet, frustratingly, if you perform *any* edit of the VM configuration -- even a null one where you just bring up the VM settings in the GUI and click "OK" -- the VM will start normally. This is very confusing to the user, since it is easy to believe that whatever random change you might have made is the one that fixed the VM.

Doing a simple "diff" before and after the null edit shows the following:

So there is at least one problem, that the default of 30 causes problems for CentOS 4.6 (and perhaps other Linuxes). Note that LibVirt does not itself provide the max port count -- that is hard-coded into VB 3.2.4 OSE at line 159 of "Main/StorageControllerImpl.cpp". But there also might be a second problem, where the VB GUI silently changes the value of the maximum SATA port count -- why would it do this, and does it silently modify (perhaps just clamp within certain bounds) the values of other fields?

Considering the days of effort I wasted over the past few months due to confusion caused by this subtle, insidious bug, I declare it to be "critical", but of course, feel free to adjust as desired.