Custom Query (16611 matches)
Results (10 - 12 of 16611)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #11561 | fixed | "<HardDisks>" and section gets removed with data only leaving the closing tag "</HardDisks>" | ||
| Description |
The VM config .vbox file somehow got corrupted. The machine was in "Saved" state, when I started VirtualBox I saw that it failed to start. I do not know whether it happened before I closed VirtualBox, or when I started it later (which is when I noticed it). I did not reboot the machine and there were no unusual problems with anything on the day. Upon comparing a copy of the config I had, "<HardDisks>" section was removed, with data (there should be just 1 vdi attached), for some reason it left the closing tag "</HardDisks>" of the section. I attach the log of when I last closed the VM (saved state). Also attached 2 vbox files, one what it should be and the other with corrupted XML bit. |
|||
| #21693 | invalid | "A critical error" during macos Leopard install on M2 mac | ||
| Description |
First, it's Apple software on Apple hardware, second, it's experimental and third, old OSX errors are common. It halted during the iso installer loading Extensions.mkext followed by dots, similar to when I tried 10.6, but there it froze and didn't gave the error screen. This is about 10.5 and the vm halted due to a critical error. Since it booted fine, I don't think EFI is to blame anymore, if it is, then it isn't solved as of 7.0.8_BETA4 r156879 (Qt6.3.0). I don't se VT-d, I don't know about T2, but enabling TPM makes the vm fail, some SATA options like ICH6 are disabled and everything I tried, including vbox-extpack had no effect. |
|||
| #9623 | fixed | "A disk read error occured - Press Ctrl+Alt+Del to restart" | ||
| Description |
I recently got this error when I want to start my XP SP3 virtual machine in Ubuntu 11.04. I checked and it did not come after an upgrade (because it last upgraded on July 31st and I got the error about two week ago, but now need to use XP) and no settings was changed recently. I tried upgrading from version 4.0.4 to 4.1.2 and to clone the virtual machine to fix the problem, but it did not work. I also read the old bugs about this error, but they all seemed to be related to a version upgrade that took place. |
|||

