Weird problem: unable to start vm using gui but ok with cmd?
Posted: 6. Apr 2014, 15:38
Hi guys,
Just recently, i faced a really strange problem. All of a sudden, without changing any settings to my vm, I found out that i cant start my vm via the VirtualBox Manager GUI. It gave the error:
A copy of the screenshot can be found in the attachment error1.jpg
On closer inspection, I found that the Manager claimed that I had "an invalid setting" with my vhd file, pointing to some UUID that does not match. Screenshot can be found in attachment as error2.jpg
But the strange thing is, despite failing to start vm via GUI interface, I was able to start vm via VBoxManage command in headless mode: VBoxManage startvm <name> --type headless
But this starts the vm without an interface. Luckily i've enabled remote desktop connection on that vm (since its running windows 7) and managed to recover most of the files.
Nonetheless, Im still curious to know a fix for this problem and any possible causes (though I'm sure I didnt fiddle with the settings before this problem came). Hopefully a reinstall is not required...
Thanks guys
Just recently, i faced a really strange problem. All of a sudden, without changing any settings to my vm, I found out that i cant start my vm via the VirtualBox Manager GUI. It gave the error:
Code: Select all
Failed to open a session for the virtual machine MyVirtualPC.
No error info.
Result Code: E_FAIL (0x80004005)
Component: ProgressProxy
Interface: IProgress {c20238e4-3221-4d3f-8891-81ce92d9f913}On closer inspection, I found that the Manager claimed that I had "an invalid setting" with my vhd file, pointing to some UUID that does not match. Screenshot can be found in attachment as error2.jpg
But the strange thing is, despite failing to start vm via GUI interface, I was able to start vm via VBoxManage command in headless mode: VBoxManage startvm <name> --type headless
But this starts the vm without an interface. Luckily i've enabled remote desktop connection on that vm (since its running windows 7) and managed to recover most of the files.
Nonetheless, Im still curious to know a fix for this problem and any possible causes (though I'm sure I didnt fiddle with the settings before this problem came). Hopefully a reinstall is not required...
Thanks guys