Well for me the problem is that if I open vbox with w7, then SM, and try to open the AOO, on a few occasions I get an error SYS0147 that is correct. But in other cases it hangs system without giving me any error, and that is worse. Of approximately 10 attempts, such only twice has the SYS0147 come out.
VBox uses huge amounts of shared memory space (mostly low shared space, from what I have seen). If you load something, and it runs out of shared memory space, the system needs to be able to get enough shared memory to be able to tell you about it (SYS0147). If it can't get enough shared memory space, it hangs, waiting for it to become available, and that rarely happens.
The only known answer, is to load as much as possible into high shared memory, leaving more room in lower shared memory, so you don't run into the problem. AOO can be set to load code, and data, in high shared memory, but it still uses some lower shared memory, and you do need to prevent it from unloading, to avoid the kernel problems when you do unload it. QuickStart does that. FF, SM, and TB, now have the firefox-highmem package, that sets FF to use high memory (I expect that also helps with SM and TB). Now, we also have MOZTURBO, to keep those things from unloading, and triggering the kernel problem. You probably also need to expand the amount of upper shared memory space, that is available. Use VIRTUALADDRESSLIMIT=2560, in CONFIG.SYS, to do that. The max is 3072, but I find that many systems have problems using the max, so 2560 is a good compromise.
Unfortunately, those things only help, they don't fix the problems, so eventually you will have problems.