virtualbox.org

I'm having problems when multiple CPUs are enabled in the x64 guest on a x64 windows host. See http://forums.virtualbox.org/viewtopic. ... 07#p103195

Looking over the tickets opened for SMP, it seems that some corrections were made in 3.0.10.

I'd hate to spend the time building it from SVN. Any chance I could get access to the latest 3.0.10 build? I need to do some development in SharePoint on a guest and one CPU isn't enough. I thought about rebuilding the guest using 32 bit OS but it takes time I'd rather not spend.

Thanks.

3.0.10 will only be available as prebuild package. They are currently on 3.0.9 release, which is an odd number used as internal builds. It was, or still is, a rule of thumb that odd numbered releases are unstable releases, but some projects (like the Linux kernel) no longer hold on to that. VB however does.

So, unless you compile it yourself, what you don't want, you have to wait until it's released.

of course if you do build from SVN you get quite a few extra features way past the 3.0.10 release package, but lose some functionality as its the OSE not PUEL release.

Its easy on Linux, probably a total nightmare on Windows - expect you need Visual Studio (non-Express) or some mingw setup?

Thanks Sasquatch, any chance of me getting a build of 3.0.9 to test if my problem goes away? I opened a ticket for my issue: http://www.virtualbox.org/ticket/5262

Thanks SEJ, do you know if the Windows target can be built under Linux? I have VS via MSDN but it's collecting all the dependencies like mingw that's the pain. If it's simplier under Linux and I can build the Windows version under Linux, that might be an option.
Thanks in advance.

See the technical documentation on the main site. There you can find build instructions for either platform. However, you will only build the version for the OS you're compiling it on. So the Linux version when compiling on Linux, Windows version when compiling on Windows.

Keep in mind that compiling from SVN means you are compiling bleeding edge code. Right now we're in a transition phase and I wouldn't recommend compiling the current code.
3.0.10 is built from a separate branch, which is not available to the public. Most likely we'll release it next week.

After looking over the Windows build instructions, I've decided to wait.

So 3.0.10 might be available next week? That's good news. Hopefully, this problem is fixed in it.

Let me know if you need someone to test 3.0.10 to see if this issue is still present.