mark rumsey wrote:Whilst some of these faults will clearly trash the file, others may simply prevent it being mounted by Virtualbox, and these are the ones that are most annoying.
mark rumsey wrote:One feature that would be useful is the ability to enable the VHD or VDI file to be mounted by virtualbox or the host OS whilst the guest is not running. This feature exists within Windows7/Windows VPC and I found it very useful following a catasrophic VirtualXP crash
I'm guessing here, but I suspect what ProVega is referring to is corruption of the VHD or VDI file itself caused by a problem with the host, which roughly equates to a hardware fault on a physical disk.
sandervl wrote:I hardly ever use VHD images though, so perhaps there's a serious problem in that backend.
mpack wrote:sandervl wrote:I hardly ever use VHD images though, so perhaps there's a serious problem in that backend.
Total guess: perhaps "invalid header" actually refers to an invalid footer, i.e. the idiot decision some developer made to put a "header" at the end of the VHD file, so it has to be moved every time the file grows. Obviously, if the enlarge+newfooter sequence was interrupted that would leave a dead footer.
Pretty close - This happened just again today. I have a base VHD and a snapshot... I tried to mount a USB drive and VirtualBox froze (64-Bit host, 64-bit guest Windows 2008 R2, single CPU). I let VBox "think" at 100% CPU for 5 minutes and then the screen stopped painting and windows asked me to close VirtualBox. I did. My host OS was stable, only VirtualBox "crashed" while it did this, it corrupted the "header" of the snapshot and I could no longer mount it with that wonderful "invalid header" error.
Users browsing this forum: Bing [Bot], Yahoo [Bot] and 4 guests