virtualbox.org

Hallo,

I have installed VirtualBox 4.2.12 r84980 on Windows 7 . 64Bit with an Intel i7 Core processor and four Linux guests: openSUSE 11.2 - KDE, openSUSE 11.3 - KDE, openSUSE 11.3 - GNOME and openSUSE 11.4 KDE, all 64bit VMs. openSUSE 11.2 and openSUSE 11.4 boot well and can be used, but openSUSE 11.3 - GNOME or KDE boots into trace dump, print several pages of dump info like "General protection fault: 0000 [#5] PREEMPT SMP" is one of the lines printed out.

I wonder why this happens. openSUSE 11.2 and 11.4 with same settings in VirtualBox VM tab "System", "Display", "Audio", "Network", "USB" are running fine, but not openSUSE 11.3. VirtualBox Guest Additions installed in VM has Version 4.2.0 and runs successfully some month ago with a previous VirtualBox Version, Version 4.2.0, where I last could install current Guest Additions. Later I update VirtualBox to 4.2.10, but not the Guest Additions.

I could start VM with openSUSE Gnome LiveCD and checked partitions with fsck. Then I started with openSUSE-11.3-DVD the installation, terminate it and started installed System. There I got a Login prompt, but could not Login, because of "Error in Service modul". I tried a update Installation, but VM does not boot. I tried a new Installation, keeping home Partition: Linux does not boot, same trace dump. I made a new virtual hard disk fixed size 25 GB, installing new and formating all partitions: Linux does not boot.

The difference between running and not running Linux VMs: not running hard disk Images are stored on my second hard disk of my physical Computer, running VMs disk Images are storen on an external hard disk. So I checked permissions of virtual disk image files and granted access to everybody. Makes no effect.

I tried to uncheck Setting "PAE/NX activate", and also checking it again: no effect to faulty boot, just the same. 3D acceleration and 2D Video acceleration are unchecked.

I have upload the VM log file.

helfrw

00:00:03.287625 Host RAM: 5589MB total, 912MB available
00:00:05.162923 RamSize <integer> = 0x0000000040000000 (1 073 741 824, 1 024 MB)
00:00:05.163828 VRamSize <integer> = 0x0000000008000000 (134 217 728, 128 MB)

The total of RAM + VRAM you gave to the VM is bigger than what is have available in the host. You also need to include Virtualization overhead.
Either reduce the amount of memory given to the VM or increase the RAM of your host.

I checked RAM. Available on host 1.342 MB. I reduced memory of VM from 1024MB to 512MB, but same error.

here a screenshot from booting - last page.

I checked PAE/NX and started VM with 512MB RAM, 128MB VRAM. Now I got "kernel Panic"

You say you installed guest additions but they are not detected - are they the matching version of Virtulbox - 4.2.12?

Could you attach as zip the guest config output from vboxmanage? Replace vmname :

I have made for the VM a new openSUSE Installation, but it doesn't boot, so there are no Guest Additions yet installed. I can try to recover the virtual hard disk image for this VM from a backup, which has installed Guest Additions Version 4.2.0. VirtualBox has 4.2.10.

The VM boots with GNOME or KDE LiveCD and same settings.

first try:
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe showvminfo "openSuSE 11.3 (64Bit) - Gnome" --details
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

There are only two VMs affected: openSUSE 11.3 KDE and 11.3 GNOME, all other VM can be started and run.

Looks like something corrupted your installation which could be the reason you fail to run your VM aswell.
My suggestion would be to uninstall, remove every trace of Virtualbox on your system, and reinstall from scratch.

Or maybe Perry has more insight on this.

ok, thank you. You mean uninstall VirtualBox 4.2.10, removing every trace of Virtualbox on my system - which files are this? - and reinstall VB?

see uploaded showvminfo file "ShowVMInfo.zip"

Nothing strikes my eye in your config that could cause problems.
By all files, I meant the general settings file, Virtualbox.xml. The rest is handled by the uninstaller. make sure you reboot before reinstalling.

see uloaded showvminfo --Detail from a running VM "openSUSE 11.2 (64Bit) - KDE" and compare with other one: I cannot recognize significant points, why one VM runs and the other VM not.

thank you. I will try a reinstall of VB.

I have uninstalled VB, rebooted Computer and installed VB 4.2.10. I removed VirtualBox.xml and started VB. It now starts with no VM added - empty. I added the "problem" VM at first and tried to run. Same error as before, many trace dump pages.

But now I have a second Problem: could not add any other VM, because hard disk UUID was not found. What's that now?
"Konnte die virtuelle Maschine in C:/Users/Helmut/.VirtualBox/Machines/openSuSE 11.3 (64Bit) - Gnome - defekt/openSuSE 11.3 (64Bit) - Gnome - defekt.vbox nicht öffnen.

Could not find an open hard disk with UUID {ddb4ee56-3a9e-4090-9a24-31eb8485e2d1}.

Fehlercode:VBOX_E_OBJECT_NOT_FOUND (0x80BB0001)
Komponente:VirtualBox
Interface:IVirtualBox {3b2f08eb-b810-4715-bee0-bb06b9880ad2}