Opened 15 years ago
Closed 15 years ago
#6977 closed defect (fixed)
Unable to boot into offline Ubuntu guest snapshot on Ubuntu host
Reported by: | aWak3N | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 3.2.4 |
Keywords: | unable, boot, vtx | Cc: | |
Guest type: | Linux | Host type: | other |
Description
Hello,
I am unable to boot from a clean shut down (=offline) Virtualbox snapshot since yesterday. The sceen simply remains black after going through BIOS. Booting from online snapshots works flawlessly. Booting from older offline snapshots does also work. If I have VT-x enabled, I get no error or progress message at all. Disabling VT-x shows the Guru Meditation message saying a critical error had occured.
Thank you!
Attachments (2)
Change History (12)
by , 15 years ago
comment:1 by , 15 years ago
Additionally it is not even possible to just normally _reboot_ my host system. It always gets stuck after the BIOS. Help please!
comment:3 by , 15 years ago
Yes, they are indeed located on an ext4 drive as this is the default filesystem of my Ubuntu 10.04 host installation. I, however, have no problems booting "older" offline snapshots which are also located on this ext4 partition. Could it be a problem introduced by an updated Virtualbox version?
comment:4 by , 15 years ago
Yes, probably. There is an ext4 bug which is triggered by the way how VirtualBox 3.2.x is accessing virtual disk images. Starting with VBox 3.2.x, host disk caching is disabled for virtual disk images attached to a SATA or SCSI controller. The work around is to enable this cache in the VM settings or to put the files on an ext3 partition. Unfortunately we were not aware of the bug at the time we released VirtualBox 3.2.4.
comment:5 by , 15 years ago
I enabled Host disk caching in the options, but it didnt affect the erroneous behaviour: I'm still unable to boot off an offline image or simple reboot my vm. Unfortunately I can't test the vdi file on an ext3 partition. I am pretty positive this bug was not present on the previous version of VBox 3.2.x (I think it was 3.2.3).
comment:6 by , 15 years ago
I fear your snapshot is already corrupted by this bug, therefore you have probably remove this snapshot.
comment:7 by , 15 years ago
I tried it with an older offline snapshot (which was not corrupted) and enabled host disk caching and i could reboot that system without a problem. I guess the filesystem might get corrupted upon shutdown, that's why i've been having no problem resuming online snapshots. Is it somehow possible to activate host disk caching on a runnning vm, because otherwise i would lose a lot of work and data...
comment:8 by , 15 years ago
Enabling the host cache wouldn't solve your problem as the data in the snapshot is most probably already corrupted.
comment:9 by , 15 years ago
Ok i backed up all my files and reverted to a working snapshot. One last question: Is activating disk host caching affecting a system's performance?
comment:10 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
I believe you will not note a difference, only under certain circumstances. Note that VBox 3.2.6 will show a warning and will automatically enable the host cache if the disk image is located on an ext4 partition.
Booting from an offline snapshot without VT-x