Open savingschampion opened 10 years ago
Googled for solution, it states that the Guest additions are too old for my version of virtualbox 4.3.12. r93733
Strange - I'm using the same VBox version and installed the entire suite of IEs without issue this morning. Can you provide more details about your system setup?
I've completely removed the .ievms directory and forcibly deleted all traces of the old VM's. I realised that IEVMS might not be checking for updated VM source from upstream. I will see if this fixes the issue
Same issue, and it's always the IE7 VM it stops on. The IE6 VM installs correctly every time.
I don't know what details you need about my system, if you could provide me with what you need i can furnish you with the information.
VboxManage version:
josh@Thor ~ $ vboxmanage --version
4.3.12r93733
uname -a
Linux Thor 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Error Output
VM "IE7 - WinXP" has been successfully started.
Waiting for IE7 - WinXP to be available for guestcontrol...
Waiting for IE7 - WinXP to be available for guestcontrol...
Waiting for IE7 - WinXP to be available for guestcontrol...
Waiting for IE7 - WinXP to be available for guestcontrol...
Waiting for IE7 - WinXP to be available for guestcontrol...
Waiting for IE7 - WinXP to be available for guestcontrol...
Setting IEUser password
VBoxManage: error: Session is not in started state
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component GuestSession, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: "ProcessCreate(Bstr(strCmd).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aEnv), ComSafeArrayAsInParam(aCreateFlags), ctrlExecGetRemainingTime(u64StartMS, cMsTimeout), pProcess.asOutParam())" at line 1327 of file VBoxManageGuestCtrl.cpp
I have noted this issue, https://github.com/xdissent/ievms/pull/198 and am attempting the fix outlined in it.
Fix worked, It is down to a timing issue, I'm guessing your machine is faster then mine and so your timings are allowing you to continue installation.
Fix is as follows, Upon installation whenever it says about waiting for guestcontrol, press ctrl + z, then once you see the VM is booted, wait like 10 seconds to be sure and then type 'fg' into the console
Hmm, the ctrl+z
trick might work but I was already running this process in the background ( on a very slow machine ) and it kept crashing with VBoxManage: error: Session is not in started state
I edited the value in the script sleep_wait="5" to be higher, I tried "15" which did not work, so then I changed it to 120
(a.k.a. 2 minutes) which is probably overkill but it allowed the provisioning to complete successfully.
ps: I also tried the fix from #198 that that did not work for me. The real problem was that the machine I was running it on was "too slow" for the standard script.
It looks like the function that detects if the machine is ready, fires ~2 seconds before you are able to run the next command. Adding a 3 second wait before the next command should fix this issue no matter how slow your machine is.
So @savingschampion can you submit a PR with your awesome fix? Thanks
Tracking the video memory issue in #266 Are you still experiencing timeouts with the latest version?
@xdissent Yup, even earlier in the chain and on a faster machine, with the latest Virtualbox 5.0.2
I can't even get XP IE6 up before I get kicked out with
Waiting for IE6 - WinXP to be available for guestcontrol...
Setting IEUser password
The command completed successfully.
Setting auto logon password
VBoxManage: error: Session is not in started state
VBoxManage: error: Details: code NS_ERROR_UNEXPECTED (0x8000ffff), component GuestSessionWrap, interface IGuestSession, callee nsISupports
VBoxManage: error: Context: "ProcessCreate(Bstr(pszImage).raw(), ComSafeArrayAsInParam(aArgs), ComSafeArrayAsInParam(aEnv), ComSafeArrayAsInParam(aCreateFlags), gctlRunGetRemainingTime(msStart, cMsTimeout), pProcess.asOutParam())" at line 1510 of file VBoxManageGuestCtrl.cpp
~ ❯❯❯
@xdissent If you add a wait at https://github.com/xdissent/ievms/blob/master/ievms.sh#L280, then it should give virtualbox time to get it's ass in gear.