Creating Windows 2012 template crash VirtualBox

[Tidji22]

Hello,

I'm using Virtualbox 4.2.4 with Guest Addition for 4.2.4 on Windows XP 32bit.

I use this release everyday creating VM's based on Windows 2003, 2008, Seven, Linux Redhat 5.x and 6.x, Mac OS X templates without any problem.

I decide to create a vm based on Windows 2012 template. So i choose memory size, disk size and type, i have enough space on disk. After un click on "create" button to create the vm windows 2012, Virtualbox crash brutally, and i can't re open it, each time i launch virtualbox, it crash. Only virtualbox application crash, not the host. I need to kill manually the process for virtualbox which stay started, and delete manually the files created for this new vm windows 2012.

Have you ever tested creating a Windows 2012 vm with this release of virtualbox ?

I have tested after that creating a winddows 2008 vm, or windows 8 64bit vm, without any problem, no crash, so the problem is mainly with windows 2012 vm's...


Thanks in advance,

[mpack]

Details please: are you enabling VT-x for this VM, how much RAM does your host have, how much of that is free, and how much are you allocating to the VM (including in the form of VRAM). Are you enabling 2D and 3D acceleration.

A VM log file would be useful - as a .zip attachment.

A screenshot of any error dialog - equally so.

[Tidji22]

No problem. So, here is the answers, you will see most of them attached to this post in the zip file :

- i let the default values, 2048Mo of RAM, and 25Go of disk space
- no, i don't have enabled VT-x (like all my others VM's and like the tests i have done with creating a new vm windows 2008 or Windows
- no, i don't have enable 2D or 3D acceleration, at these screens we don't have the choice to enable or not 2D/3D acceleration, because the issue come up when we first create the vm, not after that, so, i never have acces to the configuration screen of the vm (see screenshots)

i have attached in the zip file all the screenshots including the error message of the creation procedure of the vm. I also have included the files created.


Have you ever tested windows 2012 with virtualbox 4.2.4 ?

[Perryg]

no, i don't have enabled VT-x

No need to go any further. (AFAIK) Without the NX bit enabled this is not going to work. At the present you must have VT-x/AMD-v enabled for the NX bit to work properly in VirtualBox.

[mpack]

Thanks for posting the entire contents of your VM folder (though unfortunately you skipped the log file), however only the screenshot of the error is needed. Since your attachment used excessive space I have deleted it and replaced it with the important screenshot.

I think one of your problems is evident in the background of the error dialog: you have a "path not found" error. Strangely, the path mentioned is nonsensical: VirtualBox does not create the "VirtualBox VMs" folder inside the "Program Files" folder. I assume there has been some manual editing of xmls going on here, or at the very least the Preferences have been inappropriately edited. In any case VirtualBox will be unable to run the VM if it can't access the .vbox file.

[Tidji22]

Ok, can you tell me where to activate this bit ? Is it specific for windows 2012 vm's ? Because, for all others vm's, i never enable this bit and i works perfectly. As i don't have access to the configuration screen of the vm i can't set this bit. in fact, for all my vm's this bit is ever checked, not because i have enable it, but because this bit is checked by default. But in my case of windows 2012, normally if it works like other windows templates, it should be enabled by default, no ?

So i don't know to activate this bit manually as virtualbox crash directly after i have click on "Create" the vm...

[Perryg]

Like I said the NX bit is more than likely set but if you do not have VT-x/AMD-v enabled it will not work. At least with the present versions of VirtualBox. Windows 8, 2012 has made the NX bit mandatory so yes it is only going to show it's nasty head with these version.


Edit: Here is a link to where one of the discussions have taken place: https://www.virtualbox.org/ticket/11159

[Tidji22]

Thanks for posting the entire contents of your VM folder (though unfortunately you skipped the log file), however only the screenshot of the error is needed. Since your attachment used excessive space I have deleted it and replaced it with the important screenshot.

I think one of your problems is evident in the background of the error dialog: you have a "path not found" error. Strangely, the path mentioned is nonsensical: VirtualBox does not create the "VirtualBox VMs" folder inside the "Program Files" folder. I assume there has been some manual editing of xmls going on here, or at the very least the Preferences have been inappropriately edited. In any case VirtualBox will be unable to run the VM if it can't access the .vbox file.

Ok, thank you for your reply. I don't have posted log file because i don"t have one, i have checked before sending the file

Yes, the screenshot with path not found is because, after virtualbox crashing, the only way to have a virtualbox running again is to delete all the files of the vm created (wich has been added to the file sent) and killed all virtualbox process which were stayed alive. So, restarting virtualbox giving the message that path is not found, it's logical because i have deleted the folder... It's not the root of the problem, when i have tested with other vm (windows 2008, windows , it was the same path and i don't had any error.

Yes, i have changed the default folder of the vm's is how it works usually for my laptop, it's not a problem.

[Tidji22]

Like I said the NX bit is more than likely set but if you do not have VT-x/AMD-v enabled it will not work. At least with the present versions of VirtualBox. Windows 8, 2012 has made the NX bit mandatory so yes it is only going to show it's nasty head with these version.

Ok, so, i think this bit is automatically set creating a new vm. I have tested at this time a new vm windows 8 64bit and VT-x/AMD-V has been set automatically (and has not crashed anyway) with same memory size, disk size and same default folders of course, same default configuration.

[BillG]

I think that you failed to understand exactly what you are being told. It is the hardware which must have hardware virtualization enabled and the NX bit set to run Server 2012. (These are set it the computer's BIOS). Windows 8 must have the NX bit set, but would probably run 32-bit Windows 8 without hardware virtualization, but Server 2012 (like 2008R2) is 64-bit only.

And yes, I am running Server 2012 under VirtualBox.

[Tidji22]

My colluegue has tested the same thing on his laptop and same result (host os Windows 7 32bit, virtualization set in bios and same thing, he launch 64bit guest os's (2008, linux, and windows 8 with success).

No no, i don't speak about virtualization in bios, on my case, virtualization has ever been set in bios to be able to launch 64bit guest on 32bit host. In my case, my laptop is windows xp 32bit, and i used virtualbox for my work everyday, launching vm's in 32 AND 64bit, without any issue. I confirm that i launch 64bit guest os's with success, it's not the root of the problem.

The test done on windows 2008 and windows 8 i used are 64 bit profiles.

[smart2128]

I experienced the same behaviour changing a Windows 2008 64bit machine OS type to Windows 2012 64bit.
After that change, VBox exits with a segfault.

VBoxSVC.log content:

Code: Select all

00:00:05.637424 nspr-3   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:05.643774 nspr-3   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for vboxnet0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:05.654097 nspr-4   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for wlan0: VBoxNetAdpCtl: ioctl failed: Operation not supported
00:00:05.660835 nspr-4   NetIfAdpCtlOut: VBoxNetAdpCtl: Error while retrieving link speed for vboxnet0: VBoxNetAdpCtl: ioctl failed: Operation not supported

To get VBox working again, I had to delete .vbox file and rename the .vbox-prev.

[Tidji22]

I have found something strange. As Windows 2012 64bit profile failed to create, i decide to use "Other Windows" profile. So, i have check the box for enabling VT-x is checked. So, i have attached the iso image file for windows Server 2012 (64bit) and starting the vm to install windows Server 2012. After the files are loaded, i had an error message saying that my procesor is not a 64bit processor. I think that the detection of the processor type is different in windows server 2012, beacause the virtualization bit is well set in bios, and all my other vm's 64bit don't have this problem.

I think that, as my host os (windows XP) is only 32bit and in windows Server 2012 process to detect the os type is different, it doesn't work.

For all the user who have successfully installed Windows Server 2012 in guest os using Virtualbox, which are your host os, 32 or 64bit ? I think it works only on 64bit host os, even if virtualization is set in bios. Can you verify this hypothesis ?

Can you confirm me that the detection procedure of the processor type is different in windows 2012 than all others old windows Server Version, for example, with Windows Server 2008 R2 ?

Thanks in advance,

[smart2128]

It worked for me using the VM with Windows 2008 64 bit OS Type previously created. On a 32 bit Linux host system.
VBox crashes only if I choose Windows 2012 as OS Type.

[Tidji22]

So, i think you have the same behavior on 32bit os type (host type), creating template windows 2012!