VB crashes Windows Server 2008 during guest OS install

[mgengokalzalski]

Hello,

I am trying to install Windows XP on my VirtualBox 4.3.6, which is installed on my machine which I connect to via remote desktop, which is running Windows Server 2008 r2.
VirtualBox seems to install and run just fine, but when it comes to actually installing XP the entire system crashes - not just VB - and restarts...
I am using an ISO disk image not a CD for the install, which I have successfully installed on a previous iteration of VB on my Windows 8 machine - I know it is not the XP iso as I tried it with my Vista iso too and this too also crashed the WS2008r2 OS.
It seems to always happen when XP is on "FAT File system..." stage, however I then tried using VB 3.2.22 and it got slightly further to "CD settings" before the same result!

Any help is greatly appreciated!

Thanks!

[loukingjr]

Minimum information needed for assistance

[mpack]

It seems to always happen when XP is on "FAT File system..." stage

I'm not familiar with that stage of an XP install. The default filesystem in XP is NTFS, not FAT, which should only be used for removable media.

I suggest doing memory and disk tests on the host.

[mgengokalzalski]

Minimum information needed for assistance

Apologies, I have attached the log...
The host has 8GB ram and 1gb on c drive but 35gb hdd space left on the b drive which is where this is installed and vdi located. It is running WS2008 r2 standard 64bit
I have given the vm allocation of 10gb dynamic hdd and 1gb RAM and am trying to install xp 32bit

any more information required?

I'm not familiar with that stage of an XP install. The default filesystem in XP is NTFS, not FAT, which should only be used for removable media.

I suggest doing memory and disk tests on the host.

I would take a screen shot - but as I said the whole host crashes and so I lose any clipboard data.

Thanks

update:
I have tried installing this now using "Qemu Manager" (not something I wanted to do) and it seems to be working so far...it got past the stage VitrualBox crashes at (the aforementioned FAT file system) as it turns out the next stage is "installing windows" where you can actually start to edit ANYTHING in the set-up (i.e. partition the drive etc)
So why is VB not letting me do this?

[noteirak]

00:00:13.568820 Hypervisor Present (we're a guest) = 0 (1)
00:00:13.568844 Full Name: QEMU Virtual CPU version 0.10.50

Your log shows you're running your VM inside another VM. Either you got the wrong log (the one inside QEMU you mention), or your "host" is actually a VM.

[mgengokalzalski]

00:00:13.568820 Hypervisor Present (we're a guest) = 0 (1)
00:00:13.568844 Full Name: QEMU Virtual CPU version 0.10.50

Your log shows you're running your VM inside another VM. Either you got the wrong log (the one inside QEMU you mention), or your "host" is actually a VM.

Apologies, I re-read my first post again, I did say I was connecting via Remote Desktop but obviously didn't put it was to a VM...
but according to VB documentation this is more than possible to do, no?
The vm is an instance in it's own right.

This log was taken before installing Qemu Manager

[loukingjr]

This log was taken before installing Qemu Manager

I'm not sure what you mean by "this log" but the one you posted couldn't possibly mention QEMU before you install it.

[mgengokalzalski]

This log was taken before installing Qemu Manager

I'm not sure what you mean by "this log" but the one you posted couldn't possibly mention QEMU before you install it.

yes it can...
"This log" is the log that is attached above, and it was taken before Qemu Manager was installed on THIS host machine, from which the log which is attached above was taking.
The host machine is obviously being run via qemu on a linux host itself - I did not create this machine, hence why I am connecting via remote desktop.

[loukingjr]

yes it can...
"This log" is the log that is attached above, and it was taken before Qemu Manager was installed on THIS host machine, from which the log which is attached above was taking.
The host machine is obviously being run via qemu on a linux host itself - I did not create this machine, hence why I am connecting via remote desktop.

first of all, there is no way to know which machine you were referring to when you said "before QEUM" was installed. It also doesn't help that you are calling a guest VM running in QEUM a "host".

the bottom line as was mentioned is you can't run a VM inside another VM.

[mgengokalzalski]

yes it can...
"This log" is the log that is attached above, and it was taken before Qemu Manager was installed on THIS host machine, from which the log which is attached above was taking.
The host machine is obviously being run via qemu on a linux host itself - I did not create this machine, hence why I am connecting via remote desktop.

first of all, there is no way to know which machine you were referring to when you said "before QEUM" was installed. It also doesn't help that you are calling a guest VM running in QEUM a "host".

the bottom line as was mentioned is you can't run a VM inside another VM.

apologies, I thought I was being clear as I had only uploaded one log, and had only mentioned about installing qemu MANAGER (which is a windows gui for qemu) after attaching the log from the virtualbox instance.

I am referring to the WS2008r2 machine as the host, as having read the documentation, I couldn't find anywhere that stated a VM could not be run in a VM, and therefore assumed that the as this instance of WS2008r2 would have VB installed on it and then have XP installed into that, that the original machine was the "host" regardless of whether it was a VM itself or not. - so again, my mistake, and apologies.

I have obviously misread the documentation and even though VB will run it won't let OS's be installed...

update:
thank you for everyone's help though - forgot to put that in the post!