Crash in Virtual Disk Manager when adding a new disk/cdrom

I forgot to mention: Problem is reproducible (crashes every time I try to do this), but worked fine before. Problem still persists even after complete reboot.

Ticket #2081 is a duplicate of this one.

Though I don't doubt that this is the same error as described in #2081 I would like to add that I observed the crash in "Virtual Disk Manager", not in the virtual machine "Settings" window as shown in the screenshot attached to #2081.

The bug is only related to the GUI. Adding a disk image from the command line with "VBoxManage registerimage" works fine.

What means adding? Adding a existing one or creating a new one. Some more detailed steps/info to reproduce this? Currently I couldn't reproduce this.

Screenshot of the Virtual Disk Manager just before pressing the highlighted button, which results in crash of the complete GUI.

Replying to poetzsch:

What means adding? Adding a existing one or creating a new one. Some more detailed steps/info to reproduce this? Currently I couldn't reproduce this.

The problems occurs every time I click the toolbar button for registering an existing image with the "Virtual Disk Manager". I attached a screenshot I have taken just before the button click, which causes the crash (see above).

Can you provide a core dump as described in http://www.virtualbox.org/wiki/Core_dump?

Replying to poetzsch:

Can you provide a core dump as described in http://www.virtualbox.org/wiki/Core_dump?

Since the Virtual Disk Manager suddenly works as expected again, I am not able to provide a core dump. All I changed was to remove a hard disk image from the Manager. Now adding new disks also works again. The disk I removed was working correctly in a virtual machine running Solaris 10.

I am able to create virtual disks from either CMD line or via the Virtual Disk Manager.

However, if I try to do it by selecting a guest, clicking Settings, then Hard Disks, I get the Segmentation Fault.

I also get a SegV when I attempt to create a raw image from the cmd line with the following cmd:

$ VBoxManage internalcommands createrawvmdk -filename raw_edrive.vmdk -rawdisk /dev/sda -partitions 6 -relative -register

The WORKAROUND I did to get around this is as follows:

1) Create the image from the cmd line as follows. (With the RAW disk using cmd above, I still get the Segmentation Fault message, but it still creates the image and it APPEARS to be usable. Creating a VDI, I do NOT get a SegV.)

dbreese@dbreese-laptop:~$ VBoxManage createvdi -filename test.vdi -size 10 -register -type normal
VirtualBox Command Line Management Interface Version 2.0.0
(C) 2005-2008 Sun Microsystems, Inc.
All rights reserved.

Disk image created. UUID: de8cfe02-02ee-4d6c-aa10-ac447eaaf837

2) Make a note of the UUID above. In this case it is de8cfe02-02ee-4d6c-aa10-ac447eaaf837.

3) MAKE A BACKUP OF your machines XML configuration file located under ~/.VirtualBox/Machines/MyMachine/MyMachine?.xml

4) Exit the machine's config file and add a reference to the disk.

    <HardDiskAttachments>
      <HardDiskAttachment hardDisk="{68aa5504-bfab-48c8-b861-647b1c69e167}" bus="IDE" channel="0" device="0"/>
      <HardDiskAttachment hardDisk="{de8cfe02-02ee-4d6c-aa10-ac447eaaf837}" bus="IDE" channel="0" device="1"/>
    </HardDiskAttachments>

The CHANNEL is either 0 or 1 and represents the IDE channel. Device 0 or 1 indicates master or slave, respectively. For IDE channel 1, it appears master is reserved (probably for CD Drive), so it must be 1. Therefore, you can have 3 IDE drives attached.

If VirtualBox complains about an invalid disk, then check 2 things:

1) Did you get the UUID correct and/or did you screw up the machine's XML config file?

2) Make sure the new disk really did get registered in ~/.VirtualBox/VirtualBox?.xml as follows:

      <HardDisks>
        <HardDisk uuid="{68aa5504-bfab-48c8-b861-647b1c69e167}" type="normal">
          <VirtualDiskImage filePath="VDI/drive_c.vdi"/>
        </HardDisk>
        <HardDisk uuid="{de8cfe02-02ee-4d6c-aa10-ac447eaaf837}" type="normal">
          <VirtualDiskImage filePath="VDI/test.vdi"/>
        </HardDisk>
      </HardDisks>

NOTE: The link for generating a core dump didn't help me for Ubuntu. To enable core dumps on Ubuntu, you must edit /etc/default/apport and set enabled=1 and set the maxsize value accordingly. Even doing this, for some reason VirtualBox did not dump core. I am suspecting it is something to do with setuid being set perhaps? So, to get a core dump, I ran "sudo gdb /usr/lib/virtualbox/VirtualBox", typed "start" to run the binary and when it crashed, typed "gcore" to create the core dump in the local directory. Not sure if this is ok for someone to use for debugging or not?

My core dump, compressed, is only about 2.5 megs, so will send it to frank _dot_ mehnert at sun _dot_ com as it states in the above Core_dump link.

Hope this helps?

I am having the same issue. Tried to do a core dump to help but I get the following error:

reets@reets-desktop:~$ ulimit -c unlimited reets@reets-desktop:~$ echo -n 1 > /proc/sys/fs/suid_dumpable bash: /proc/sys/fs/suid_dumpable: Permission denied reets@reets-desktop:~$ VirtualBox Qt FATAL: ASSERT failure in QList<T>::at: "index out of range", file ../../include/QtCore/../../src/corelib/tools/qlist.h, line 391 Aborted

I am having the same issue. Tried to do a core dump to help but I get the following error:

reets@reets-desktop:~$ ulimit -c unlimited 
reets@reets-desktop:~$ echo -n 1 > /proc/sys/fs/suid_dumpable 
bash: /proc/sys/fs/suid_dumpable: Permission denied 
reets@reets-desktop:~$ VirtualBox Qt FATAL: ASSERT failure in QList<T>::at: "index out of range", file ../../include/QtCore/../../src/corelib/tools/qlist.h, line 391 Aborted

dbreese: Thx for your dump, but your error is the same as in #2081. So it doesn't belongs to this bug report here where a crash happens when the virtual disk manager is used & not the vm settings.

My report has to do with both. Mine crashes with the same error whether I go through the VM settings to add an ISO or VDM window to add it.

I have the same bug with Virtual Box 2.0.2. When I click on Add the GUI crash. I have generated a core dump and I am sending it to frank _dot_ mehnert at sun _dot_ com. In console I have

VirtualBox 
Qt FATAL: ASSERT failure in QList<T>::at: "index out of range", file ../../include/QtCore/../../src/corelib/tools/qlist.h, line 391
Abandon (core dumped)

Please reopen if this bug is still present in the latest release (2.1.4).

Problem still exists in VirtualBox 3.0.8 (Ubuntu) ...

A core dump would be interesting. If you are willing to provide one, please contact me via private E-mail at frank _dot_ mehnert _at_ sun _dot_ com.