VirtualBox 2.2.0 OSE - !!Assertion Failed!!

[es1]

Hi VirtualBox Team, Frank,
I built the VirtualBox 2.2.0 OSE from sources on Fedora 10, the build complete successfully.
When trying to run it from a regular user, it does not start even the basic GUI and exit with:

Code: Select all

$ Type Manifest File: /home/es1/.VirtualBox/xpti.dat
nsNativeComponentLoader: autoregistering begins.
*** Registering VirtualBox_Server_Module components (all right -- a generic module!)
*** Registering VirtualBox_Client_Module components (all right -- a generic module!)
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)

!!Assertion Failed!!
Expression: !mWarningIcon.isNull()
Location  : /data/vbox-2.2.0.src/VirtualBox-2.2.0_OSE/src/VBox/Frontends/VirtualBox/src/VBoxGlobal.cpp(2967) void VBoxGlobal::retranslateUi()

[1]+  Trace/breakpoint trap   (core dumped) VirtualBox

When I run it as root with no valgrind It seems to be working

When I run it as root with valgrind and open the properties of any VM I get a different - !!Assertion Failed!!

Code: Select all

# valgrind -v --leak-check=full --trace-children=yes --log-file=/tmp/vbox.dbg10.valg.%p.txt VirtualBox
Type Manifest File: /root/.VirtualBox/xpti.dat
pr_LoadLibraryByPathname(): Failed to load '/data/vbox-2.2.0.src/VirtualBox-2.2.0_OSE/out/linux.amd64/debug/bin/libpthread.so'
pr_LoadLibraryByPathname(): Failed to load '/data/vbox-2.2.0.src/VirtualBox-2.2.0_OSE/out/linux.amd64/debug/bin/libdl.so'
nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)

!!Assertion Failed!!
Expression: typeIndex != -1
Location  : /data/vbox-2.2.0.src/VirtualBox-2.2.0_OSE/src/VBox/Frontends/VirtualBox/src/VBoxOSTypeSelectorWidget.cpp(106) void VBoxOSTypeSelectorWidget::setType(const CGuestOSType&)
Type ID should be valid: 'Fedora_64'

btw: if I use the Fedora binary version of VirtualBox it is working
Thank you for your help

[es1]

When starting as root a VM (which works with the binary 2.2.0 version) I get with the OSE,

---
00:00:00.918
00:00:00.918
00:00:00.918 ******************** End of CPUID dump **********************
00:00:00.919 Debug: HCPhysInterPD=00000000cf857000 HCPhysInterPaePDPT=000000000519d000 HCPhysInterPaePML4=000000008fd83000
00:00:00.919 Debug: apInterPTs={00000000cf9fe000,00000000cf9f1000} apInterPaePTs={000000013177d000,000000013177e000} apInterPaePDs={000000013177f000,0000000131628000,0000000131629000,000000013162a000} pInterPaePDPT64=0000000005173000
00:00:01.093 TM: GIP - u32Mode=1 (SyncTSC) u32UpdateHz=99
00:00:01.125 TM: cTSCTicksPerSecond=0x9da3bec0 (2644754112) fTSCVirtualized=true fTSCUseRealTSC=false
00:00:01.125 TM: fMaybeUseOffsettedHostTSC=true TSCTiedToExecution=false TSCNotTiedToHalt=false
00:00:01.130 CoreCode: R3=00007fec60157000 R0=ffffc20011adc000 RC=a05ac000 Phys=0000000005166000 cb=0x2000
00:00:01.156
00:00:01.156 !!Assertion Failed!!
00:00:01.156 Expression: pDev
00:00:01.156 Location : /data/vbox-2.2.0.src/VirtualBox-2.2.0_OSE/src/VBox/VMM/PDMDevice.cpp(195) int pdmR3DevInit(VM*)
00:00:01.156 Configuration error: device 'ahci' not found!
---
Please let me know if I missed something in the build

Extra information:

I'm using English (LNAG=en_US.UTF-8) or (LNAG=C) and I tried VirtualBox from few different Desktop environments (GNOME, KDE, IceWM)

Sun - Thanks ! - now it works, details:

1. The first issue in the first post relates to Language settings, somehow there was no definition of default language in the system, I searched thru the menu systems and set them all to US English, and the GUI is working. -- It raise the questions:
A. Why it was working OK with VirtualBox-2.1.4 (both PUEL ans OSE) and 2.2.0_PUEL ?
B. Do we need to update VBox to cope with such cases, instead of crash (change the asserts to note to the user)?
C. What is the specific files that define these system or user language defaults.
D. It seems to be the similar case to: http://forums.virtualbox.org/viewtopic. ... are#p67551

2. The bug in the beginning of this post relates to having the SATA(ahci) device enabled in the PUEL then trying to use the same VM in OSE edition.

Now things are working much better!

Thanks

[frank]

Did you check VirtualBox 2.2.2? AFAIR we fixed some issues there ...