virtualbox.org

Hello,

I run Virtual Box under Ubuntu 12.10 and just upgraded from 4.2.8 r83877 to 4.2.10 r84104

My Win7 VM worked fine at 1st boot. I was invited to upgrade guest additions, which I did.
But after reboot, I have no display, just a black screen. But my VM seems to be started correctly.

Then, I rebooted in safe mode and uninstalled guest additions.
After reboot, I got my display back, but without full screen mode (which is normal, as guest additions were removed).

I then re-installed guest additions and got black screen again after reboot...

Any idea ?

winsnomore wrote:All day wasted with this "release"

I recovered by ssh'ing to the VM, upgrading the distro .. that removes the dkms modules installed by new release.
-- I then reran the install of linuxadditions .. that seems to put my humpty dumpty back.
I had work to do today and I spent 5 hours recovering from this fiasco.

Your problem description is very imprecise. So far, the only problem we are aware of is the broken image of the 4.2.10 Guest Additions in the Windows package. That's unfortunate but was fixed with the 84105 upload (yes, the version will still report as 4.2.10 r84104).

winsnomore wrote: In short 4.2.10 seems to be a disaster created by whatever was in 84104 load .. it seems not be there any more so others may not suffer but I have!

Tell us exactly what your problems are (preferably by open a ticket at our public bugtracker) and we will try to help you. The 4.2.10 release is an update to 4.2.8 which contains only a few changes and no changes we made sound related to the problems you described.

winsnomore wrote: My suggestion to VBox maintainers . please
DON'T PUT UP THE MESSAGE ABOUT NEW VERSION EVERY TIME ONE STARTS THE PGM.
DO IT ONCE .. OR ONCE A WEEK but not on EVERY PGM START.

I only installed the new version because I was getting annoyed having to click that off every time.
You are putting out release every few weeks and wasting people's time won't win you friends.

There is no reason to shout. Just go to the global settings and adapt the notification interval to your needs.

will7991 wrote:Hello,

I run Virtual Box under Ubuntu 12.10 and just upgraded from 4.2.8 r83877 to 4.2.10 r84104

My Win7 VM worked fine at 1st boot. I was invited to upgrade guest additions, which I did.
But after reboot, I have no display, just a black screen. But my VM seems to be started correctly.

Then, I rebooted in safe mode and uninstalled guest additions.
After reboot, I got my display back, but without full screen mode (which is normal, as guest additions were removed).

I then re-installed guest additions and got black screen again after reboot...

Any idea ?

This sounds like the Guest Additions installer was not able to compile the guest kernel modules for your guest kernel. Have a look at /var/log/vboxadd-install.log and you should find the reason for the problem. To me this doesn't sound like a 4.2.10 regression.

Is anybody else having problems with a broken Guest Additions .iso image? I saw here reports for Mac OS X as well but we verified and found that the correct image is included. And there was another report for Linux hosts: Which package (exact package name please) did you install?

Frank Mehnert wrote: This sounds like the Guest Additions installer was not able to compile the guest kernel modules for your guest kernel. Have a look at /var/log/vboxadd-install.log and you should find the reason for the problem. To me this doesn't sound like a 4.2.10 regression.

Hello Frank,

I didn't see anything strange in the log file.

I have finally tried to run Virtual Box under Gnome3 instead of Unity. And it works fine.
So, I think the latest release of guest additions may have troubles with Unity...

On the other hand, I don't have Aero Effect anymore (previously with 4.2.8, I did). I'm going to check why...

Hmm, we didn't change anything in the Linux Guest Additions between 4.2.8 and 4.2.10 which could give a hint to your problem.

Unsure what's happened but appears bridged networking was compromised?

I hate to post, as I'm unsure if it's the build or me specifically yet, however upgraded to 4.2.10 this morning as well the additions and guest won't boot up as it has for the past 9 months.

00:00:01.428689 IntNet#0: szNetwork={HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205} enmTrunkType=3 szTrunk={\DEVICE\{0800B98F-AC15-46D4-89B4-311A5ACF31A1}} fFlags=0x8001 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:01.428736 VMSetError: D:\tinderbox\win-4.2\src\VBox\Devices\Network\DrvIntNet.cpp(1718) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_SUPDRV_COMPONENT_NOT_FOUND
00:00:01.428747 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205'
00:00:01.428834 PDM: Failed to construct 'pcnet'/0! VERR_SUPDRV_COMPONENT_NOT_FOUND (-3700) - The component factory was not found.
00:00:01.458340 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Intel(R) Centrino(R) Advanced-N 6205' (VERR_SUPDRV_COMPONENT_NOT_FOUND)}, preserve=false
00:00:01.469452 Power up failed (vrc=VERR_SUPDRV_COMPONENT_NOT_FOUND, rc=E_FAIL (0X80004005))

This seems strange and I've done the typical expansion of the NetFilters registry key as well cleared any possible INFCACHE corruption but still selecting 'Bridged' networking dissallows the VM to boot. Choosing NAT, as others had done in the past, gets it online but working with smartcards and various VPN/Tunnels it may not work for me well. I'm testing now.

Frank, could this have been an introduction on this build as I had seen in earlier posts/release/builds this error crops up and is relatively fixed fast in a new release/build?

Thanks!
~Richard Berg

Richard, this looks more like the VBox VBoxNetFlt host driver was not properly installed. We didn't change anything there. If this is a Windows host, try to completely uninstall VBox and then do a re-install (your VMs will not be harmed). If this is a Linux host, make sure all the VBox kernel modules are compiled by doing /etc/init.d/vboxdrv setup.

Frank Mehnert wrote:Richard, this looks more like the VBox VBoxNetFlt host driver was not properly installed. We didn't change anything there. If this is a Windows host, try to completely uninstall VBox and then do a re-install (your VMs will not be harmed). If this is a Linux host, make sure all the VBox kernel modules are compiled by doing /etc/init.d/vboxdrv setup.

Frank,

I will try again but have uninstalled and re-installed VBox several times and as well tried to rollback to the prior 4.2.8 version without success. It seems at this time I'm unable to get bridged networking to work as it had but I will continue to dig into this. For now NAT works in my environment albeit not as 'clean' as I had it before with bridged.

Thanks for your reply!
~Richard

Really nice to see how quickly this got remedied. Just an FYI, using the "check for updates" mechanism doesn't trigger on the new 84105 build. I had to manually download and install it, but guest additions works now.

Hi,

I'm running Lubuntu 12.10 as a host machine. My VirtualBox instance was automatically updated via Lubuntu's software updater few days ago. After that, one of the guest machines, also running Lubuntu 12.10, doesn't work properly any more - it won't capture mouse, full screen is not in correct resolution, can't install guest add-ons and so on.
On the other hand, guest machine with Windows 7 Pro runs just fine.
Any ideas?

Frank,

Wanted to touch base with you again on the issues I'm having with the Bridged Network drivers.

While I show them installed and enabled within the adapter specific properties I still find issues running VBox in bridged mode to said adapter. I've un-installed, re-installed several times and cleaned various temp paths, registry and everything else I could think of in my 20+ years of Windows development and most recently enabled MSI and Driver Installation logging. In doing so I've found this error and wondered if you might have an idea or rectification path?

>>> [Build Driver List - ROOT\SUN_VBOXNETFLT\0000]
>>> Section start 2012/03/14 13:49:43.512
cmd: C:\Windows\system32\MsiExec.exe -Embedding 38E12786AADD972DCD4030DD5B5CEC34 M Global\MSI0000
cpy: Policy is set to make all digital signatures equal.
! sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
! sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
<<< Section end 2012/03/14 13:49:45.368
<<< [Exit status: SUCCESS]

>>> [SetupScanFileQueue]
>>> Section start 2012/03/14 13:49:45.368
cmd: C:\Windows\system32\MsiExec.exe -Embedding 38E12786AADD972DCD4030DD5B5CEC34 M Global\MSI0000
! sig: Verifying file against catalog 'vboxnetflt.cat' failed.
! sig: Error 2: The system cannot find the file specified.
! sig: Verifying file against catalog 'vboxnetflt.cat' failed.
! sig: Error 2: The system cannot find the file specified.
<<< Section end 2012/03/14 13:49:45.384
<<< [Exit status: SUCCESS]

There are of course additional failures within the log but I as surprised to find the drivers having cert issues and will see if I trusted signed drivers by Oracle automatically which may be causing this. Anything you could recommend or comment against would be great.

Thanks!
~Richard

@rberg: unless you are claiming this is a 4.2.10 regression, i.e. that reverting to 4.2.8 fixes it, then this issue doesn't seem to belong in this topic. Frank has said that no work has been done in this area for v4.2.10.

mpack wrote:@rberg: unless you are claiming this is a 4.2.10 regression, i.e. that reverting to 4.2.8 fixes it, then this issue doesn't seem to belong in this topic. Frank has said that no work has been done in this area for v4.2.10.

mpack,

Thanks for the heads up but no regression has fixed this for me personally. I was running 4.2.8 bridged 100% and after updating to 4.2.10 I now cannot run bridged. Uninstalls and re-installs of 4.2.10 or any other version does not seem to fix the issue I'm having. I find it odd that myself and that all version to-date have worked flawlessly, however, upon installation of 4.2.10 it's stopped allowing me to run as I had in bridged mode.

If you feel this is something non-specific to the 4.2.10 edition then please let me apologize but again I find it odd based on the events I've experienced. If this is something else or you wish for me to post in a new or other thread please let me know. I use VBox for development against older 32bit XP clients and VBox has been crucial in my development and deployment. As my installation stands today I may not be able, less a fresh install of Win7, to get this to work.

Thanks again and forgive my ignorance as I have never had a single issue with VBox until yesterday.

Cheers,
~Richard

I have downloaded 4.2.10.84104 from filehippo yesterday (btw, someone should inform them and other software hosting sites about newer build, or you will get many more annoyed users here, they are still hosting older build). I have tried installing it, it finished, but Windows (7 x64) reported that it didn't installed correctly. Never saw such message with older VirtualBox installers. And it still showed 4.2.8 in the about box. So i have donwloaded 84105 from your site and tried installing it again (i always install on top of the older version). It was loger than usually, installer stayed for a few minutes on Publishing product information. Then again it showed me that installation wasn't correct. But now it shows 4.2.10 version in the about box. Though it still shows 84104 build. VMs are working, so i guess it is only the build number not updated in the box.

And i still have the issue i have reported in the 4.2.8 thread. Unnormal Scrollbox in the VMs list..
download/file.php?id=8818

P.S. i'm using filehippo as it is easier to monitor for new versions.

virtualbox.org

Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release

Re: Discuss the 4.2.10 release