VER_INTERNAL_ERROR

[giggetto]

Hello, I can't speak very good english, I'd prefer speak french or italian. I've installed virtualbox 1.3.6 for two weeks and everything was going on very good, but two days ago i tried to start VB but the only thing i get is this message :Failed to start VM execution (VERR_INTERNAL_ERROR).

Result Code: 0x80004005 Component: Console Interface: IConsole {1dea5c4b-0753-4193-b909-22330f64ec45} I installed VB 1.3.8 and created a new virtual machine, but i get the same thing, i tried to delete the old machine but it was the same thing. My OS is ubuntu edgy and i simulated windows Xp. Could you help me ? Thanks,giggetto

[Frank Mehnert]

Please upload your VBox.log file of your ~/.VirtualBox/Machines/<vm name>/Logs directory.

[Frank Mehnert]

I don't see any unusual so far. VERR_INTERNAL_ERROR means something went wrong and we did not implement a proper error message for this case. Please could you do the following:

VirtualBox shutdown
LD_LIBRARY_PATH=/opt/VirtualBox-1.3.8 strace -f -o ~/VBoxSVC.log -s 1024 /opt/VirtualBox-1.3.8/VBoxSVC &
LD_LIBRARY_PATH=/opt/VirtualBox-1.3.8 strace -f -o ~/VBoxSDL.log -s 1024 /opt/VirtualBox-1.3.8/VBoxSDL -vm machine

and add the resulting files (VBoxSVC.log and VBoxSDL.log) here as attachments (see the "Attach File" button)? Thank you.

[KhaoticMind]

The exact same thing happened to me after upgrading from 1.3.6 to 1.3.8 on Edgy. I solved the issue by doing a "sudo /etc/init.d/vboxdrv restart".

I guess the driver wasn't properly unloaded/loaded during the upgrade.

Hope this works for you.

Cheers, KM

[Frank Mehnert]

Did you use the Edgy package provided by InnoTek? Then this is very unlikely. The prerm script of the 1.3.6 package does '/etc/init.d/vboxdrv stop' and the postinst script of the 1.3.8 package does '/etc/init.d/vboxdrv start'.

[KhaoticMind]

Yeap, Innotek package. And it really happened :)

But comme to think of it, i might have used 1.3.8, downgrade to 1.3.6 and the issue happened when going back to 1.3.8 ... Not sure thou.

[giggetto]

Replying to frank:

I don't see any unusual so far. VERR_INTERNAL_ERROR means something went wrong and we did not implement a proper error message for this case. Please could you do the following:

VirtualBox shutdown
LD_LIBRARY_PATH=/opt/VirtualBox-1.3.8 strace -f -o ~/VBoxSVC.log -s 1024 /opt/VirtualBox-1.3.8/VBoxSVC &
LD_LIBRARY_PATH=/opt/VirtualBox-1.3.8 strace -f -o ~/VBoxSDL.log -s 1024 /opt/VirtualBox-1.3.8/VBoxSDL -vm machine

and add the resulting files (VBoxSVC.log and VBoxSDL.log) here as attachments (see the "Attach File" button)? Thank you.

Hello, i tried to do what you said : so, here's the VBoxSVC.log file, as attachments, but for the second line that's what i get : :~$ LD_LIBRARY_PATH=/opt/VirtualBox-1.3.8 strace -f -o ~/VBoxSDL.log -s 1024 /opt/VirtualBox-1.3.8/VBoxSDL -vm machine VirtualBox SDL GUI 1.3.8 built Mar 13 2007 19:25:21 SDL Error: 'No available video device' Thanks to you again Giggetto

[Frank Mehnert]

You should have send me the second log file anywhere, even if VBoxSDL fails. And the first log file is most likely not the output of strace. Anyway, it seems that exactly the problem 'No available video device' is the problem with your setup. I know that VirtualBox dies with an VERR_INTERNAL_ERROR if the video mode could not be initialized (VirtualBox uses the SDL library for video output). So the question is why SDL could not initialize the video mode on your system.

Are you able to start an xterm from the command line? If so, are you able to start other known SDL applications from you command line (e.g. a game linked against the SDL library)? Do you have any environment variables set starting with SDL_ in their name?

[giggetto]

Hello, I don't have VBoxSDL.log file, I've search it with locate. I can start xterm from the command line, but none of the game(like anagramarama) that use SDl library can be start (I always get : "error: No available video device". I don't understand what means : "Do you have any environment variables set starting with SDL_ in their name?". Thanks, giggetto

[Frank Mehnert]

So this is definitely a problem of the SDL installation of your distribution. We should provide a better error message if VirtualBox fails to initialize the video mode of course.

Please could you provide some more information: the output of

set|grep SDL_

Furthermode your /etc/X11/xorg.conf and your currently running window manager.

[giggetto]

Hello, Ihave notjing with "set|grep SDL_". I attache the xorg.conf file

[Frank Mehnert]

Thank you. What is your window manager? beryl, kwin or metacity? Or any other window manager?

[giggetto]

Replying to frank:

Thank you. What is your window manager? beryl, kwin or metacity? Or any other window manager?

Sorry, I forgot it : my window manager is nautilus. Thank you, giggetto

[Frank Mehnert]

That is very unlikely. nautilus is a file browser not a window manager. Please would you enter

/bin/ps aux > ~/PSAUX

and add the resulting file ~/PSAUX here as an attachment? Thx.

[Frank Mehnert]

Ok, your window manager is metacity. I don't expect any harm from this.
You said that you are not able to start any SDL application. As logging VirtualBox seems a bit difficult, please could you select an arbitrary SDL application and strace it? First make sure that strace is installed on your system:

sudo apt-get install strace

Then do

strace -f -s 1024 -o ~/SDL.log <SDL application>

And add the resulting ~/SDL.log as attachment. Perhaps we can track down what is the problem with your SDL setup.

Thx.

[giggetto]

Replying to frank:

Ok, your window manager is metacity. I don't expect any harm from this.
You said that you are not able to start any SDL application. As logging VirtualBox seems a bit difficult, please could you select an arbitrary SDL application and strace it? First make sure that strace is installed on your system:

sudo apt-get install strace

Then do

strace -f -s 1024 -o ~/SDL.log <SDL application>

And add the resulting ~/SDL.log as attachment. Perhaps we can track down what is the problem with your SDL setup.

Thx.

That's what I get :"Unable to init SDL: No available video device"

[Frank Mehnert]

The application does not try to open any X11-related stuff. Did you start it from an xterm or something like that? What is the output of

sudo apt-get install binutils
objdump -p /usr/lib/libSDL-1.2.so.0

[giggetto]

No, I don't start it from xterm, and here's what I get: ~$ sudo apt-get install binutils Password: Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Reading state information... Fait binutils est déjà la plus récente version disponible. The following packages were automatically installed and are no longer required:

libgnucrypto-java fillets-ng-data libcairo-java-gcj libevent-execflow-perl libbcprov-java-gcj pinball-data libfame-0.9 libglib-java-gcj armagetron-common libintl-perl libpvm3 libtext-glob-perl liblog4j1.2-java libnspr4-0d libswt3.2-gtk-java mencoder libseda-java libgtk-java-gcj libcommons-cli-java libgtk-jni dvdauthor libcairo-java libggi2 libbcprov-java libevent-rpc-perl libgii1 gtk2-ex-formfactory-perl lsdvd stellarium-data libglib-java neverdata squid-common libgii1-target-x libgdk-pixbuf2 ftplib3 frozen-bubble-data anyevent-perl libfluidsynth1 libfile-find-rule-perl libcrypto++5.2c2a libmozjs0d libevent-perl libgtk-java amule-common fb-music-high libswt3.2-gtk-jni ladcca2 gl-117-data libnumber-compare-perl

Use 'apt-get autoremove' to remove them. 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. giggetto@lec67-4-82-230-52-18:~$ objdump -p /usr/lib/libSDL-1.2.so.0

/usr/lib/libSDL-1.2.so.0: file format elf32-i386

Program Header:

LOAD off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 212

filesz 0x0004678c memsz 0x0004678c flags r-x

LOAD off 0x0004678c vaddr 0x0004778c paddr 0x0004778c align 212

filesz 0x00001014 memsz 0x000265bc flags rw-

DYNAMIC off 0x00046ad4 vaddr 0x00047ad4 paddr 0x00047ad4 align 22

filesz 0x000000e0 memsz 0x000000e0 flags rw-

EH_FRAME off 0x000466c4 vaddr 0x000466c4 paddr 0x000466c4 align 22

filesz 0x0000002c memsz 0x0000002c flags r--

STACK off 0x00000000 vaddr 0x00000000 paddr 0x00000000 align 22

filesz 0x00000000 memsz 0x00000000 flags rw-

Dynamic Section:

NEEDED libm.so.6 NEEDED libdl.so.2 NEEDED libpthread.so.0 NEEDED libc.so.6 SONAME libSDL-1.2.so.0 INIT 0x3ce4 FINI 0x41774 HASH 0xd4 STRTAB 0x1e34 SYMTAB 0xa04 STRSZ 0x1102 SYMENT 0x10 PLTGOT 0x47c10 PLTRELSZ 0x5f0 PLTREL 0x11 JMPREL 0x36f4 REL 0x32ac RELSZ 0x448 RELENT 0x8 VERNEED 0x31bc VERNEEDNUM 0x4 VERSYM 0x2f36 RELCOUNT 0x85

Version References:

required from libm.so.6:

0x0d696910 0x00 09 GLIBC_2.0

required from libdl.so.2:

0x0d696911 0x00 12 GLIBC_2.1 0x0d696910 0x00 07 GLIBC_2.0

required from libc.so.6:

0x09691f73 0x00 11 GLIBC_2.1.3 0x0d696914 0x00 10 GLIBC_2.4 0x0d696911 0x00 08 GLIBC_2.1 0x0d696913 0x00 06 GLIBC_2.3 0x0d696910 0x00 05 GLIBC_2.0

required from libpthread.so.0:

0x0d696910 0x00 04 GLIBC_2.0 0x0d696911 0x00 03 GLIBC_2.1 0x09691972 0x00 02 GLIBC_2.3.2

[Frank Mehnert]

Then, how did you start the SDL application?

Please would you execute

sudo apt-get install dlocate
dlocate /usr/lib/libSDL-1.2.so.0

then take the Debian package which is printed out and do

dpkg -s <the package name which was printed out before>

and post the ouput.

Thx.

[giggetto]

I started the SDL application from "terminal", in french we call it "console". Here's what I get : ~$ dlocate /usr/lib/libSDL-1.2.so.0 libsdl1.2debian-alsa: /usr/lib/libSDL-1.2.so.0.7.3 libsdl1.2debian-alsa: /usr/lib/libSDL-1.2.so.0 I don't understand what I should do now

[Frank Mehnert]

Ok. What is the output of

dpkg -l libxrandr2 libxrender1 libxext6 libx11-6

?

[giggetto]

Here it is : ~$ dpkg -l libxrandr2 libxrender1 libxext6 libx11-6 Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais)

/ Nom Version Description

+++-==============-==============-============================================ ii libx11-6 1.0.3-0ubuntu4 X11 client-side library ii libxext6 1.0.1-1ubuntu1 X11 miscellaneous extension library ii libxrandr2 1.1.1-0ubuntu1 X11 RandR extension library ii libxrender1 0.9.1-0ubuntu1 X Rendering Extension client library

[giggetto]

Here it is : ~$ dpkg -l libxrandr2 libxrender1 libxext6 libx11-6 Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé |/ Err?=(aucune)/H=à garder/besoin Réinstallation/X=les deux (État,Err: majuscule=mauvais)

Nom	Version	Description
ii libx11-6	1.0.3-0ubuntu4	X11 client-side library
ii libxext6	1.0.1-1ubuntu1	X11 miscellaneous extension library
ii libxrandr2	1.1.1-0ubuntu1	X11 RandR extension library
ii libxrender1	0.9.1-0ubuntu1	X Rendering Extension client library

[Frank Mehnert]

I'm running out of ideas. Your X11 libraries are correct. VirtualBox does not start because your SDL installation does not work for some reason. We will fix the misleading error message but you have to get your SDL installation working. Perhaps you might ask on www.ubuntuforums.org for some help.

[giggetto]

OK, thank you for your help

[stefan]

Hi, i've had the same error ("Failed to start VM execution (VERR_INTERNAL_ERROR) ... rc=0x80004005") on Gentoo. The problem was that libsdl was not compiled with the X use flag.

[Frank Mehnert]

gigetto, any news?