Discuss the 4.3.0 Release

This is for discussing general topics about how to use VirtualBox.
gpaCook
Posts: 15
Joined: 7. Jul 2013, 16:56
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: MS Windows 8, Ubuntu Studio

Re: Discuss the 4.3.0 Release

Post by gpaCook »

Error when starting VB Manager

Host: OSX Mavericks
4.3 Extensions and Guest Additions installed successfully

Since installing v. 4.3.0, when I start the VB Manager, I get the following error pop up:
Screen Shot 2013-10-29 at 12.08.36 PM.png
Screen Shot 2013-10-29 at 12.08.36 PM.png (119.19 KiB) Viewed 1750 times
[/i]

Upon clicking the check button, I get the following:
Screen Shot 2013-10-29 at 12.04.13 PM.png
Screen Shot 2013-10-29 at 12.04.13 PM.png (122.36 KiB) Viewed 1750 times
If I ignore or close out that error, things seem to work ok, except for the full screen on the windows 8 guest that I posted separately.

Thanks
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Discuss the 4.3.0 Release

Post by mpack »

Note the red icon marking the "Optical Disks" tab. Maybe that's the tab you should select if you want to see what the problem is...

Most likely you've made a common mistake: you upgraded VirtualBox while one or more VMs still had the old VBoxGuestAdditions.iso mounted, therefore the old file has been overwritten and therefore lost.
gpaCook
Posts: 15
Joined: 7. Jul 2013, 16:56
Primary OS: Mac OS X other
VBox Version: OSE other
Guest OSses: MS Windows 8, Ubuntu Studio

Re: Discuss the 4.3.0 Release

Post by gpaCook »

Well, you got my head straighter. Yes [duh!] I should have selected the tab with the exclamation point. :oops:

Now having done that, the error is on an ISO file on an external usb hard drive that was not connected. The ISO file is HRM_CCSA_X64FRE_EN-US_DV5.ISO - the file I burned to install MS Windows 8 guest. Apparently VBOX remembers that volume as something that supports it's environment, so reports when it can't find it?

Anyway, I have a copy of that file on my internal HD, so removed that copy from VBOX's list (an option it provided in the error window), and all is good.

Thank you very much :D
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Discuss the 4.3.0 Release

Post by mpack »

VirtualBox stores the path to all media in its Virtual Media Register, where it persists, and that includes removable media such as CD/DVD and floppy. I have to admit that it's a feature I don't like. Removeable media paths should I think be recorded in the recent files list, and (when in use) should be recorded in the global (non-persistent) media register, but it should be forgotten as soon as it's ejected from the drive - just as happens in the physical world. The problem with this is that if you suspend or snapshot a VM then the media path must be recorded somewhere... perhaps move the registration of removable media it to the controller element of the xml, to indicate that removing the media also implies unregistering.
cac
Posts: 18
Joined: 5. Feb 2008, 17:38
Contact:

Re: Discuss the 4.3.0 Release

Post by cac »

Hello.
I updated from 4.2 to 4.3, all VM running guest Windows Xp crash.
To run my guest Windows XP Os, i must disable VTx-AMDv, biut these guest Os runnning very slow.
My configuration Ubuntu 13.10, AMD 64(Phonon 4 core)

Last weekend, i updated to 4.3.2, i had the same problems, now i can't restore machine virtual state :
I get this error message below :

Échec de l'ouverture de session pour la machine virtuelle Xp.
Failed to load unit 'PATM' (VERR_SSM_LOADED_TOO_MUCH).

Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : Console
Interface : IConsole {8ab7c520-2442-4b66-8d74-4ff1e195d2b6}



Best Regards.
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: Discuss the 4.3.0 Release

Post by mpack »

Try upgrading to VirtualBox v4.3.2.
Post Reply