Hi - apologies. Forgot to change the subject line on original reply. GAM
---------- Forwarded message ---------- From: Glen McAllister <[EMAIL PROTECTED]> Date: Sun, Apr 27, 2008 at 9:49 PM Subject: Re: vbox-users Digest, Vol 16, Issue 26 To: [email protected] > Message: 1 > Date: Fri, 25 Apr 2008 12:12:26 +0200 > From: Klaus Espenlaub <[EMAIL PROTECTED]> > Subject: Re: [vbox-users] Importing Fusion .vmdk files to VBox > To: VirtualBox end user list <[email protected]> > .... > Windows is sometimes a real pain to get migrated. I suspect it's some > driver which doesn't serve any purpose inside VirtualBox and blocks > booting. Try booting in safe mode with logging enabled and check what's > failing. In general, all such problems are no VirtualBox bugs, they are > driver bugs which we can't do anything about. > I have done that and it doesn't even get to the stage of writing a log. This happens on booting from disk & the install CD, 'tho I did manage to boot from the CD once and re-disabled the agp440 service. Sometimes it will hang at the initial boot screen, but if I choose the "Enable Logging" option after pressing F8, I always generate a 'Floating Guru' execution failure message within VBox. The original .vdi file boots fine from this VM. Would it do any good/be ok to post the log file and vbox.png as suggested by the Floating Guru? Regards, GAM _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
