Linux openSUSE 11.3 (64Bit) boot - general protection fault

[noteirak]

Could you attach as zip the .vbox of the VM please? It is located in the VM folder.

[helfrw]

I run VB as Administrator and got after start VM:

Code: Select all

Das COM-Objekt für VirtualBox konnte nicht erzeugt werden.
Die Anwendung wird nun beendet.
Callee RC:CO_E_SERVER_EXEC_FAILURE (0x80080005)

[helfrw]

in the LOG file there is only one error at the end:

Code: Select all

00:01:34.231459 /VUSB/0/cUrbsInPool                     0 count
00:01:34.231466 /VUSB/1/cUrbsInPool                     1 count
00:01:34.231473 ********************* End of statistics **********************
00:01:34.274166 Changing the VM state from 'DESTROYING' to 'TERMINATED'.
00:01:34.625977 ERROR [COM]: aRC=E_ACCESSDENIED (0x80070005) aIID={db7ab4ca-2a3f-4183-9243-c1208da92392} aComponent={Console} aText={The virtual machine is not powered up}, preserve=false

[helfrw]

Could you attach as zip the .vbox of the VM please? It is located in the VM folder.

See uploaded file.

[helfrw]

I found some things by comparing the current created VM and its ".vbox" file and an older from a backup from VM same name.

Old one from backup - date 16.09.2012. Name: "openSuSE 11.3 (64Bit) - Gnome.xml"

Code: Select all

<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.10-windows"

<StorageController name="SATA-Controller" 
</StorageControllers>

current .vbox file, Name: "openSuSE 11.3 (64Bit) - Gnome.vbox"

Code: Select all

<VirtualBox xmlns="http://www.innotek.de/VirtualBox-settings" version="1.12-windows"
<StorageController
********************** NO SATA Controller included, but in GUI it is present ************************
</StorageControllers>

If I change in VB GUI name "SATA" to name "SATA-Controller", then the entry for SATA-Controller is written to VMNAME.vbox file, otherwise not.

Code: Select all

<StorageController name="SATA-Controller" type="AHCI" PortCount="1" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice type="HardDisk" port="0" device="0">
          <Image uuid="{ddb4ee56-3a9e-4090-9a24-31eb8485e2d1}"/>
        </AttachedDevice>
      </StorageController>
    </StorageControllers>

So I merged the differences from backup VMNAME.XML file to current GUI settings, but my VM still does not boot: only dump stack with panic (another error Situation than this morning).

[helfrw]

I made some futher checks: I compared the VBox.log from not booting (with dump trace) "openSUSE 11.3 (64Bit) - Gnome" and the fine running VM "openSUSE 11.2 (64Bit) - KDE". Just starting up and shutting down. There are no significant entries in both LOG files, which points to an error, most of compared text is equal, but some values differ.

The second thing I observed, all running VMs have a fixed size hard disk, only the both not running VMs have a dynamic allocated hard disk. These VMs were created in year 2010 with a VirtualBox version 3.x and run until version 4.2.0. I made further VB updates until 4.2.12, but in this time I don't use these two VMs before yesterday.

May be this is the cause, but I have still no solution. I will make a backup of internal VM partitions with True Image and after this I will recover these partitions into a fixed size hard disk. Would this work than and will the Linux VM then boot?

[noteirak]

I hope you have backup of all those modifications, else you gonna be in troubles.

You didn't attach the proper .vbox file. I am expecting openSuSE 11.3 (64Bit) - Gnome - defekt.vbox but you gave me openSuSE 11.3 (64Bit) - Gnome.vbox

[helfrw]

I hope you have backup of all those modifications, else you gonna be in troubles.

You didn't attach the proper .vbox file. I am expecting openSuSE 11.3 (64Bit) - Gnome - defekt.vbox but you gave me openSuSE 11.3 (64Bit) - Gnome.vbox

Backups from my first system hard disk are running each two weeks (image backups) alternate on two external disk and if there are meantime essential changes in user files, I copy them with robocopy /MIR to two another alternate external hard disks. I meanwhile have to manage 35 VMs.

"openSuSE 11.3 (64Bit) - Gnome - defekt.vbox" was previous "openSuSE 11.3 (64Bit) - Gnome.vbox". I renamed it to create a new VM named "openSuSE 11.3 (64Bit) - Gnome.vbox" with a fixed size hard disk and installed openSUSE 11.3 Gnome again from scratch.
It makes no difference - fixed size hard disk or dynamic allocated hard disk - all openSUSE-11.3 Gnome, Gnome - defekt and KDE are not booting, just trace dump. The three VMs can start and boot from LiveCD openSuSE 11.3. If I start installation from openSUSE 11.3 DVD, cancel it and start installed system, I got a prompt for username and password, but login ends with "error in service module" and I cannot login, just Strg-Alt-Entf to reboot. I meanwhile made a new VM "openSuSE 11.3 (64Bit) - Gnome.vbox" merging settings from a backup file of "openSuSE 11.3 (64Bit) - Gnome.vbox". I uploaded the current version of "openSuSE 11.3 (64Bit) - Gnome - defekt.vbox"".

[noteirak]

You have the entry for the disk attachment

Code: Select all

      <StorageController name="SATA-Controller" type="AHCI" PortCount="1" useHostIOCache="false" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice type="HardDisk" port="0" device="0">
          <Image uuid="{ddb4ee56-3a9e-4090-9a24-31eb8485e2d1}"/>
        </AttachedDevice>
      </StorageController>

But you don't have the entry at the top of your control file.

On the other hand, with the previous file you attached, you have both :

Code: Select all

      <StorageController name="SATA" type="AHCI" PortCount="1" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
        <AttachedDevice type="HardDisk" port="0" device="0">
          <Image uuid="{9be5e420-8b35-439e-8c02-77c07d552fda}"/>
        </AttachedDevice>
      </StorageController>

Code: Select all

<HardDisks>
        <HardDisk uuid="{9be5e420-8b35-439e-8c02-77c07d552fda}" location="G:/VirtualBox/HardDisks/openSuSE 11.3 (64Bit) - Gnome -2.vdi" format="VDI" type="Normal"/>
      </HardDisks>

So what you should do with your current broken VM is :
- Remove the attached disk from the VM, using Virtualbox Manager or vboxmanage
- Make sure you remove the possible broken registration of the disk from the Media Registery and remove it by force if required
- Add again the disk to the VM, which will rebuild the .vbox with the appropriate entries.

[helfrw]

thanks, noteirak,

I tried like you described, removed all hard disks (SATA) from VM and VB Manager for "openSUSE 11.3 - Gnome" and "openSUSE 113. - Gnome - defekt", keeping virtual hard disk files .vdi, but there is no change to boot completely from this hard disks (one dynamic size, the other fixed size) with openSUSE 11.3 - fresh installed from scratch, keeping home partition (fsck on home partition is without errors).

So I removed hard disk and added an openSUSE 11.2 hard disk, which boots fine and can be used. So the Settings in the VM openSUSE 11.3 - Gnome are well done, also in .vbox file. It is a problem with openSUSE 11.3 and VB 4.2.12. or with installed grub boot manager on this hard disks. Unfortunately I cannot repair this Linux with Installation DVD by starting installed System, because this fails on login in console with "error in service modul". Any further ideas?

I perhaps will try to install openSUSE 11.2 on this "faultily" hard disks and then, if running, I will make an upgrade to openSUSE 11.3 with openSUSE 11.3 installation DVD or with zypper.

[noteirak]

I am out of ideas to be honest - I never use openSUSE so I cannot really help you further.
To me it all looks like data corruption, either in the VDI or in the FS. So I would run a full check on the hardware, and in the VM from a rescue disk with disk fixing tools.

If this doesn't work, and you don't see any error anywhere, either on the hardware, in the host OS or in the VM, then I don't know. Maybe others will.

[helfrw]

thanks. I already checked all VM partition with LiveCD or rescue console with fsck. All partitions are ok. The host OS Hardware is also ok, because I have several other VMs, which are running fine, i.e openSUSE 11.2, openSUSE 11.4, openSUSE 12.3 and some Windows VMs. Only openSUSE 11.3 makes difficulties, either with KDE or with Gnome Desktop. LiveCD is running, but there came some strange errors, if starting i.e. Firefox or Yast2 on this "problematic" VM. May 1 GB RAM be to less? For Linux normally not.

I googled for some dump trace messages and found some one of them regarding to different kind of problems with openSUSE 11.3. I can investige more time in reseaching about this dump messeage - but could not see all at the beginning of dump, because I am not quick enough to press "pause" for VM.
An example message from dump is: "DWARF2 unwinder stuck at processCDI+0x3d/0x690" followed by "Leftover inexact backtrace:"
Some line before I have "General protection fault: 0000 8] PREEMTP SMP" .... and then "Pid: 305, comm: splash Not tainted 2.6.34-12-desktop #1 VirtualBox/VirtualBox"

I think at this time it is not a problem of VM Settings or virtual hard disks. I will either install openSUSE 11.2 and upgrade then to 11.3, or if this doesn't work, I let this VM die and use the user data (some documents, music and picture files) in another VM, which works.

[helfrw]

I might found the cause: I installed openSUSE from images and not from rpm packets during Installation ("from images" is default and faster). Might be these images from openSUSE 11.3 does not run with virtualbox hardware. But meanwhile I could install in the VM "openSuSE 11.3 - Gnome" openSUSE 11.2 - Gnome (one distribution number lower), which boots successfully, and next I try to make a distribution upgrade http://de.opensuse.org/SDB:Distribution-Upgrade from repository to 11.3.

[helfrw]

openSUSE 11.3 VM will not let me in peace, but now I could timely press "pause" (Ctrl-P) to see what happens at the beginning of boot sequence. There is printed after "Copying static /dev content" "BUG: unable to handle kernel paging request at ffffffff6208ed56". This seems to be a point for a Linux expert.

[helfrw]

openSUSE 11.3 (64Bit) does not boot with VirtualBox 4.2.12 on my Windows 7 64Bit host. I installed first openSUSE 11.2, made an update from repository 11.2-update, reboot, and than I made a distribution upgrade to 11.3. The same as days before: trace dump on boot. openSUSE 11.2 before distribution upgrade worked fine, but kernel 11.3 - 2.6.34.10-0.6 has difficulties. The pervious kernel 11.2 - 2.6.31.14-0.8 works fine. I didn't understand why. Update and upgrade was done without problems till reboot, and some month ago with a lower VirtualBox version this VM with openSUSE 11.3 still runs. Could there be some Microsoft Updates for host responsible, which are done during last time (I have done no driver updates on host)?