virtualbox.org

Thanks for the help. In the end I went through and tried every disk controller in turn. Despite the vmx file stating that the VM had an IDE drive, it was when I used the VBox SCSI controller that I managed to boot it. Now it's the usual fiddling to install the right drivers and so on, but for now it...

I have, and I've tried all three types. The furthest I've got is the splash screen, the option to boot into safe/safe with prompt/normal modes and then the blue screen. As I said, I've not had the problem with 32bit machines, only 64bit.

I did say in the previous message that I had virtualised an existing system - in this case to short circuit the build process in the hope of isolating the problem. The blue screen is giving a stop error of: 0x0000007B. This is inaccessible boot device. The system was virtualised with an IDE hard dri...

Thanks. The host did have XP mode installed - but I uninstalled that so as far as I know there's no other virtualisation platform or layer active. The right templates are offered. I virtualised a working 64-bit machine and tried to open that in VBox but that blue screens as well.

Log file attached.

mpack wrote:Your CPU appears to support it, so you just need to ensure that it's available: enabled in the BIOS, enabled in the VM settings, and not already in use by something else.

It's enabled in the BIOS and the VM settings. How do I check if it's in use by something else?

Host is Windows 7 64-bit with 8 GB of RAM on a Lenovo with an i7-3520 CPU. No problem with 32-bit Windows (XP, Vista and W7) or Linux guests. But I've tried 64-bit W7 and Vista guests and get a blue screen every time. I've checked the BIOS of the host system and the virtualisation options are all se...

Quick instructions on how to virtualise a machine to a VBox virtual using third party tools:

http://www.techbookreport.com/tutorials/vbox_p2v.html

Hope it's useful as I can see that the issue crops up here periodically...