virtualbox.org

We install VirtualBox on several different platforms, Windows and Mac included, and have tested different versions over the years. One problem we have encountered with VirtualBox 4.3.28 does not occur in some earlier releases. What we basically do is:

1. We create a Windows Guest and run it ok.
2. We then shut down the virtual machine and change a setting for the guest (e.g. increase the RAM allocated to the VM).
3. Next we restart the virtual machine. At this point we get the error:
FATAL: could not read from the boot medium! System halted.

Examining the .vbox file shows that there is no longer any attached storage device i.e. the DVD and/or the hard drive configuration vanishes from the affected machine. For instance, for the DVD the following lines will vanish from the .vbox file:
<AttachedDevice passthrough="false" type="DVD" port="0" device="1">
<Image uuid="{6e1f371f-7eea-42a8-b398-b0e06233f720}"/>
</AttachedDevice>


On VirtualBox 4.3.20, for instance, we can change settings (RAM, CPUs etc) ok: this problem does not occur.
On VirtualBox 4.3.28 we get the fatal error.

Other users have reported seeing this message but under slightly different scenarios, or on much older releases of VirtualBox (e.g. 4.3.12) So it would seem that there has been a regression in VirtualBox? Any pointers anyone can give us will be greatly appreciated.

I suspect that you are mounting the guest hard disk incorrectly. It needs to be mounted in the Storage section of the VM settings, otherwise it isn't persistent: if you fully shut down the VM then its gone.

And - no previous version behaved any differently.

The hard disk is mounted correctly; it shows up in the <StorageControllers> section of the .vbox file and survives multiple reboots etc. Everything works perfectly until we change a setting using the VirtualBox Manager.

Here is an example of what we have before the problem occurs:

<StorageControllers>
<StorageController name="IDE Controller" type="PIIX4" PortCount="2" useHostIOCache="false" Bootable="true">
<AttachedDevice passthrough="false" type="DVD" port="0" device="1">
<Image uuid="{6e1f371f-7eea-42a8-b398-b0e06233f720}"/>
</AttachedDevice>
</StorageController>
<StorageController name="SATA Controller" type="AHCI" PortCount="30" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice type="HardDisk" port="0" device="0">
<Image uuid="{ac2bdd13-a154-4994-8750-ded7f2159bab}"/>
</AttachedDevice>
</StorageController>
</StorageControllers>


After changing the RAM size, for instance, this is what can happen:

<StorageControllers>
<StorageController name="IDE Controller" type="PIIX4" PortCount="2" useHostIOCache="false" Bootable="true">
<AttachedDevice passthrough="false" type="DVD" port="0" device="1"/>
</StorageController>
<StorageController name="SATA Controller" type="AHCI" PortCount="30" useHostIOCache="false" Bootable="true" IDE0MasterEmulationPort="0" IDE0SlaveEmulationPort="1" IDE1MasterEmulationPort="2" IDE1SlaveEmulationPort="3">
<AttachedDevice type="HardDisk" port="0" device="0">
<Image uuid="{ac2bdd13-a154-4994-8750-ded7f2159bab}"/>
</AttachedDevice>
</StorageController>
</StorageControllers>


In this case we have lost the DVD drive. But the hard disk could also disappear. If we save the .vbox file (and its .vbox-prev counterpart) and restore them after we see the problem it makes no difference.

However version 4.3.20 and I suspect others as well, do not exhibit this behaviour... I haven't had the time to run this test on them all just yet.

If this is repeatable for you then you shoudl describe it in a BugTracker ticket, with a link to this discussion.

Remember to be specific about which VBox versions you tested. And provide a zipped VBox.log file.

Thanks, I have raised a ticket: 14165.

https://www.virtualbox.org/ticket/14165

It would be nice if you provided a link here, or at least quoted the number.