virtualbox.org

This topic is for discussion of the 4.1.4 release.
You may download it from here.

Hi I just upgraded from 4.1.2 to 4.1.4. I use to have a MacOSX VM, after 4.1.4 was installed and I launched the Mac VM a dialog window appeared saying "OrcaleVM Virutalbox manager has stopped working". I ditched the MacOS VM which was working under 4.1.2 and started fresh and got the same error message when I started the brand new VM.

Any ideas?

Thanks
Andrew

PS. I forgot to mention. I running on Windows 7 Pro x64, 12GB of RAM, 512MB Nvidia video, 2TB HD. It's an HP 6200 Pro machine.

Maybe because you're not running it on a Mac, like you should?

@xbasetech,

What Sas was getting at is VirtualBox is not designed to run a MAC guest an anything but a MAC host & MAC hardware. Anything else is a violation of the apple sla.
Please read http://forums.virtualbox.org/viewtopic.php?f=22&t=31104
The complaint that you lodged was merit-less and has been canceled.

In other words, you're actually trying to drive a Ferrari, while you only have the budget for a Fiat. Spend some money and get a Mac or just don't try to run it at all.

Looks like the mouse problem was indeed fixed. I no longer need to use mouse trails to keep the cursor from jumping all over the place.

Don't see the qcow v1 storage changes in the list of changes. Is that included? John

4.1.4 can not full screen or seamless a VM to monitor #2, if you have 2 or more monitors. But vmware can. And 3.x virtualbox can do this.
You should bring this feature back.

I was very pleased to see the appearance of Windows 8 and Windows 8 x64 as options for the type of system to install.
I installed a Win8 Dev Preview x64 guest on a Win7 Pro x64 host with no problems.
I did not try to install Guest Additions, since that already has been reported not to work yet.

p.s. the Win7 Ult x64 guest continues to work fine with the new Guest Additions, too. I still have a problem with the mouse with Celestia (a realtime 3D OpenGL program) in the Win7 guest which I already have reported to the bug tracker. At least one other realtime 3D OpenGL program (Cosmographia) has no mouse problems in the Win7 guest. I've reported this information to the author of the programs.

I use a very, very old version of AutoCad LT (probably the first release of LT for Win 3.1, thats how old I am ), managed to get it up and running on an XP guest but since the release of 4.0.0 the mouse would behaive really strange at times especially when using zoom. I'm glad to report that with this release all is back to normal.
Well done team, your work is most appreciated.

johnelee wrote:Don't see the qcow v1 storage changes in the list of changes. Is that included? John

No, this is a new feature targeted for the next major release.

nobook wrote:4.1.4 can not full screen or seamless a VM to monitor #2, if you have 2 or more monitors. But vmware can. And 3.x virtualbox can do this.
You should bring this feature back.

You can, just bring up the mini-toolbar in fullscreen (or press HOST+Home if you have disabled the toolbar) and assign the guest screens to the respective host screens via the View menu.

I did dare another time to upgrade from VBox 4.0.4 to 4.1.4.
Up to now all versions inbetween had severe mouse problems ending in (or caused by) *.vdi problems after resume from s2ram (VM up and running), see this bug report: https://www.virtualbox.org/ticket/9427.

It appears that finally with VBox 4.1.4 the problem has been fixed. Unfortunately I was never able to collect sufficient information to pin the problem down. Maybe it relates to bug #8532 which was first reported with 4.0.4 and has been fixed now?

I'll keep you updated because I still have to test with several snapshots, s2ram and saved state of all VM's.

I just started VirtualBox and was offered an opportunity to upgrade to 4.1.4. I accepted and the install went smoothly until I got the the dialog that says "Please wait while the Setup Wizard Installs Oracle VM VirtualBox 4.1.4. This may take several minutes." The progress bar is now all the way to the right but the only highlighted button is "Cancel" indicating that it isn't done with the installation. If I cancel at this point will I be able to run VirtualBox 4.1.4? Also, my network connections are no longer working on this machine. I assume this has to do with configuring the network interfaces during VirtualBox installation but I had to go to another computer to post this message.

Can I safely cancel out of the installer? If I do, will I be left with my old verion of VirtualBox or the new 4.1.4? Should I try the install again?

My system is running Windows XP SP3 on an AMD Athlon 64 X2 Dual Core processor 4200+ 2.2ghz, 3gb of RAM.

I turns out that I was unable to even cancel out of the installer. I ended up having to kill it and reboot. Now I find that the old version of VirtualBox (4.1.2) is no longer installed. I tried doing the 4.1.4 install a second time and it hangs in the same place. Is there a way to resolve this problem? I need access to the virtual machines I was running under VirtualBox and now I don't seem to be able to get it installed at all. I guess I'll try to install the old version again after rebooting.