virtualbox.org

From the changelog:

Windows Additions: make image viewer work correctly with Aero enabled (Vista and Windows 7)

It appears this is still broken. Even without Aero or 3D acceleration, PhotoViewer is still throwing an error:



The behavior reported in this thread persists, it would seem.

@steveriley,
Did you also update the guest additions?

Perryg wrote:Did you also update the guest additions?

Yup.

Edit: adding details...

1. Booted VM into safe mode
2. Uninstalled 4.1.2 Guest Additions
3. Shut down VM
4. Uninstalled 4.1.2 Guest Additions extension from VirtualBox
5. Installed 4.1.4 Guest Additions extension into VirtualBox
6. Booted VM into safe mode
7. Installed 4.1.4 Guest Additions in VM
8. Did not select 3D acceleration
9. Rebooted VM

My VM is configured with 2D acceleration on, 3D acceleration off.

You don't need 2D and you should not install the wddm drivers in safe mode. Now if you have installed the d3d drivers this will cause a lot of issues if you want aero.
I updated my guest additions to 4.1.4 and there it is.

Well, I'm not using Aero and didn't install the D3D drivers. As a test I just disabled 2D acceleration and I'm still getting the error. Had the same problem in 4.1.2, as well. Should I remove the Guest Additions from my VM and then reinstall it in "regular mode," as opposed to safe mode? I'll admit that safe mode installs are kind of a habit now, maybe it's time to break that

I don't think it matters that much but that you don't need to install GAs in safe mode if you are going to use the wddm drivers since it does not replace any Windows system files like d3d did. But I do know that if you install the wddm drivers by selecting 3D during the install and selecting no about the d3d drivers you will install the wddm drivers that you need to be able to use the 3D and the image viewer.

selden wrote: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.

I also updated to the latest version and since testing Windows 8x64 Dev I installed the new additions (4.1.4).No problems so far.At first a compatibility prompt will appear just accept and installation will complete.Now mouse can move freely between host and guest screen.

Perryg wrote:I don't think it matters that much but that you don't need to install GAs in safe mode if you are going to use the wddm drivers since it does not replace any Windows system files like d3d did. But I do know that if you install the wddm drivers by selecting 3D during the install and selecting no about the d3d drivers you will install the wddm drivers that you need to be able to use the 3D and the image viewer.

Well, I uninstalled the GAs (from safe mode, just to be sure). Changed the VM's settings to enable 2D acceleration and 3D. Restarted the VM, installed the GAs in "regular" mode, selected D3D, and chose "no" when asked about the D3D drivers. After install I rebooted the VM again. I checked devmgmt.msc and indeed I see "Virtual Box Graphics Adapter (Microsoft Corporation - WDDM)." However, PhotoViewer still throws that blasted error message. Argh! Any other troubleshooting steps?

After upgrading from VirtualBox 4.0.10 to 4.1.4 I cannot change anymore to the virtual consoles of my Linux guest with ALT+CTRL+F[1-6] . The consoles simply remain black. ALT+CTRL+F7 brings me back to my X session. This situation is very annoying because I cannot use any text console anymore e.g. for runlevel changes. Issuing the runlevel change e.g. to 3 from an X session results in a black console.

I am using an openSUSE 11.4 x86_64 guest. The error occurs reproducible both under Windows 7 SP1 x86_64 and openSUSE 11.4 x86_64 host. I've installed the following VirtualBox versions and extension pack without any occuring error:

http://download.virtualbox.org/virtualb ... _amd64.run
http://download.virtualbox.org/virtualb ... 91-Win.exe
http://download.virtualbox.org/virtualb ... ox-extpack

The console framebuffer of the Linux guest uses 1152x864 resolution which by the way is offered by "hwinfo --framebuffer". The X server of this guest uses the same screen resolution. 2D and 3D acceleration is disabled in the virtual machine definition. The resolution is not too exotic has worked for several years through versions 3.0.x, 3.1.x, 3.2.x up to 4.0.10. I don't know, if relevant, but I am using Grub 1.99~rc2 to pass the framebuffer mode to the kernel.

It's interesting to see, that booting the Linux guest directly into runlevel 3 works without problems: All virtual consoles can be used with the desired resolution. As soon as I switch to runlevel 5 the above described problem with the virtual consoles re-appears.

Finally, I have tested to disable console framebuffer on boot with kernel parameter "vga=normal". Booting into runlevel 5 brings me back my virtual consoles but only with the expected 80x25 characters VGA mode.

I figured out that downgrading the Linux Guest Additions to 4.0.10 while keeping VirtualBox 4.1.4 provides a workaround.

I have searched the forums but cannot find any topic on it. Only thread viewtopic.php?f=3&t=43817 seems to give hints to a similar problem.

Should I open a bug report or could it be an installation/configuration issue?

I just upgraded to 4.1.4 from 4.0.12. I can no longer get in to any of my vm's.

I'm running under Windows 7, with Windows XP guest OS.
I tried going back to the Windows restore point just before the upgrade, but still get the same problem.
Most of my vm's are "saved" and one is "powered off". All give the same problem.

The message which comes up is:
= = = = =
VERR_SYMBOL_NOT_FOUND

Result Code:
E_FAIL (0x80004005)
Component:
Console
Interface:
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}
= = = = =

Thanks for your help,

John Paul

Well, I reinstalled the 4.0.12 version, using "repair", rebooted a couple times, and now I am back running, but still on the old version.

Does anyone have any clues about what might have gone wrong on the upgrade?

thanks,

John Paul

jonsof wrote:

selden wrote: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.

I also updated to the latest version and since testing Windows 8x64 Dev I installed the new additions (4.1.4).No problems so far.At first a compatibility prompt will appear just accept and installation will complete.Now mouse can move freely between host and guest screen.

Thanks for letting me know the GA does install!

My mouse moved freely between my host (Win7 Pro x64) and guest OS (Win8 Preview Dev x64) with no Guest Additions installed.

I was able to install the x64 version of v4.1.4 Guest Additions with no need to select Compatibility Mode.

VirtualBox virtual network shares work. (the shared folders feature)
Copy-and-Paste between guest and host works (I used it for the error message below; although I don't know if the Additions were needed for it).

However, the graphics driver cannot be installed.
Win8 Device Manager --> Display Adapters --> VirtualBox Graphics Adapter --> Properties --> General (tab)
reports

Windows cannot initialize the device driver for this hardware. (Code 37)

Win8 Device Manager --> Display Adapters --> VirtualBox Graphics Adapter --> Properties --> Driver (tab) --> Driver Details
reports

Provider: Oracle Corporation
File version: 4.1.4.74291
Copyright: Copyright (C) 2009-2011 Oracle Corporation
Digital Signer: Not digitally signed

That last line explains why the graphics driver cannot be initialized.
Windows 8 x64 requires that all drivers be digitally signed.
Hopefully this can be fixed in the next VirtualBox update.

ingo2 wrote: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.

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

After extensive tests with VBox 4.1.4 all still is fine, so I've marked bug #9427 as fixed in 4.1.4.

However it would be nice to know more details of the root cause or corresponding fix, as 4.1.4 is the first one in which stability is back to 3.2.12 level.

Best regards,
Ingo

Just a little thought.
I noticed these "Discuss the x.x.x release" threads seem to have become less... popular than they used to be.
This one, for example, counts only 27 replies after 8 days.

Maybe VBox new releases have become more reliable and stable (better tested before release) and so most upgraders do not encounter problems.
Or maybe, on the contrary, the number of "early upgraders" is falling?

The number of early adopters would be close to the number of downloads of the release. Is that number available?

The relative quality of the releases probably would be best measured by the number of tracker bug reports.

There are quite a few external effects which would affect the number of posts. For example, I was reluctant to upgrade from a v3 release before Win8 became available, and skipped 4.0 entirely. Also, the beginning of a new school term would reduce the amount of time that people at educational institutions (students as well as faculty and staff) would have available.