Creating Windows 2012 template crash VirtualBox

[smart2128]

Yes, I can install Windows 2012 with Windows 2008 OS Type, but it crashes using the Windows 2012 OS Type on a 32bit host

[Stefanus]

Hi Tidji22,

I reported the same issue here:

viewtopic.php?f=6&t=51612

Unfortunately I got no response. This seems to be an issue with XP hosts only.

[Tidji22]

Hello Stefanus,

It seems that this problem is not a windows XP specific problem (because we have tested on windows 7 host), but on 32bit host platforms.

If you have a solution, i will be happy to know how to solve it Maybe in a next release...

[MrFurious]

I have the same problem. WinXP Pro SP3 32-bit host (Intel Core 2 Duo Mobile T9400), HP EliteBook 8730w. 3GB RAM (about 2GB free plus cache). Yes, "Virtualization" is ENABLED in the BIOS. As soon as I try to create a 2012 template, VirtualBox crashes (and continues to crash on VBox startup until I delete the new template and kill the VBoxSvc.exe process). To be clear, haven't even installed the OS yet or attempted to start the image (because I can't). VIRTUALBOX IS CRASHING, not the guest. I'm using the default settings for the template (2GB RAM, and I also tried 1GB). It's an Access Violation inside VirtualBox.exe. Log file:

Code: Select all

VirtualBox COM Server 4.2.4 r81684 win.x86 (Oct 26 2012 19:58:19) release log
00:00:00.047000 main     Log opened 2012-11-23T00:05:17.984375000Z
00:00:00.047000 main     OS Product: Windows XP Professional
00:00:00.047000 main     OS Release: 5.1.2600
00:00:00.047000 main     OS Service Pack: 3
00:00:00.219000 main     DMI Product Name: HP EliteBook 8730w
00:00:00.250000 main     DMI Product Version: F.0A
00:00:00.250000 main     Host RAM: 3067MB total, 2166MB available
00:00:00.250000 main     Executable: C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe
00:00:00.250000 main     Process ID: 2788
00:00:00.250000 main     Package type: WINDOWS_32BITS_GENERIC
00:00:00.250000          Loading settings file "C:\Documents and Settings\foobar/.VirtualBox\VirtualBox.xml" with version "1.12-windows"
00:00:00.672000          usbLibDevCfgDrGet: DeviceIoControl 2 fail winEr (170)
00:00:01.328000          failed to get the sun_VBoxNetFlt component, error (0x1)VDInit finished
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\W8_32\Windows 8 (32).vbox" with version "1.13-windows"
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\W8_64\Windows 8 (64).vbox" with version "1.13-windows"
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\W7_32\Windows 7 (32).vbox" with version "1.13-windows"
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\W7_64\Windows 7 (64).vbox" with version "1.13-windows"
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\W2008R2\Windows 2008 R2 (64).vbox" with version "1.13-windows"
00:00:03.375000          Loading settings file "G:\work\vmbox\Clean\WXP\Windows XP (32).vbox" with version "1.13-windows"
00:00:03.391000          Loading settings file "G:\work\vmbox\Clean\W2003R2\Windows 2003 R2 (32).vbox" with version "1.13-windows"

(on second attempt, you see it try to load the broken template:)

00:00:03.032000          Loading settings file "G:\work\vmbox\CLEAN\Test 2012\Test 2012.vbox" with version "1.13-windows"

I actually work at Oracle (sorry)... if there's some way I can escalate this, I'll try to find out. Right up there with "drag-n-drop" support for Windows!

[Perryg]

@MrFurious.

It would really help to see the guests log file instead of the VBoxSVC.log

[MrFurious]

Hi, I don't see any guest logs for the 2012 image... just the 3 files: .vbox, .vbox-prev and .vdi. I assume the access violation takes out the process before any logging is written. FYI, it crashes when you create the template as soon as you fill out all the info and hit the Create button. Are there debug symbols available? I assume I can get source somewhere and compile it... I'm willing to attempt that if it would help. Or I could provide a crash dump if there's a way to generate one. Without symbols, this is what the stack trace claims to look like if I debug in VS2010:

Code: Select all

>	QtCoreVBox4.dll!670fee33() 	
 	[Frames below may be incorrect and/or missing, no symbols loaded for QtCoreVBox4.dll]	
 	VirtualBox.exe!0053e4ed() 	
 	user32.dll!_NtUserCallNoParam@4()  + 0xc bytes	
 	user32.dll!_RealMsgWaitForMultipleObjectsEx@20()  + 0xe2 bytes	
 	90909090()

Thanks

[Perryg]

Sorry to say I can not reproduce this. You can get the source and compile your own from the link below:
https://www.virtualbox.org/wiki/Downloads

And you can raise a ticket at bugtracker

[MrFurious]

Some folks mentioned on this forum it wasn't limited to XP host. I searched for "Windows 2012" and "crash", etc and this sounds familiar:

VirtualBox crashes (SEGV) creating Windows 2012 guest => Fixed in SVN - Ticket # 11206
www . virtualbox . org / ticket / 11206

Unable to create Windows Server 2012 - Ticket # 11090
www . virtualbox . org / ticket / 11090

I take it "Fixed in SVN" implies it is fixed in the latest source? If I have time I can try to compile the latest and see if it fixes my issue. Thanks

[Perryg]

Actually fixed in SVN means that the source code is available from the subversion server is fixed but not in the public available builds. See https://www.virtualbox.org/wiki/Build_instructions on how to build against SVN.

[MrFurious]

I made some progress. So, after creating a template and it crashing, I tried running the command-line "VBoxManage startvm xyz", and it will start the 2012 image. But the first attempt with 2GB RAM... halts the guest shortly after boot, with an "out of memory" error in the log. On XP-32 host, I have about 3GB (really 4GB but this is XP-32 so there's a limit). So, clearly trying to use 2GB guest on a 32-bit Window host is a bad idea. So I tried again, creating a template with 1GB RAM, and... the first time I started it, my 2012 DVD ISO did something weird, like the setup couldn't read the "DVD" (there were "read errors" in the log). Maybe I have a corrupt ISO? Anyway, I powered it off and started it again from the command-line, and this time the 2012 setup starts to run fine... and is now apparently installing 2012. My VBox management GUI still crashes, so this is less-than-ideal... but it seems like you may be able to work around the issue in the short term, using the command-line or alternative UI, if the bug is limited to the default GUI.