virtualbox.org

I am trying to install a Windows XP x64 guest on Windows XP SP3 x32 host (v3.2.8 r64453) by means of RIS. I manage to boot up the guest, using the Intel Pro/1000 MT or Intel Pro/1000 T NICs, but the Windows XP x64 setup program stops @ the first screen with a "Please wait..." status text:
I can install the x32 version on the Windows XP SP3 as guest using the PCNet NICs. I cannot install the Windows XP SP3 as guest using any of the Intel cards though, because of the same issue: the Windows setup program freezes in the first screen. To be honest I'm not sure it is a freeze... it might be a deadlock!?

Does anyone have an idea what am I doing wrong?

as far as im aware you need a 64bit host to run a 64bit guest and you wont be able to run a 64bit guest ontop of a 32bit host

I'm sure you can, as I do so. In fact I'm doing it right on the same VM that I'm trying to install from RIS:
... and not only on the machine with problems; I do run XP x64 on top of XP x32 elsewhere too.
As far as I understand as long as the architecture supports VT-x or AMD-V one is good to go.

From the FAQ:

Q: Does VB support 64 bit guests?
A: Support for 64 bit guests was introduced at version 2.0.0. If you wish to create 64 bit guests then we recommend that you upgrade to the latest version. Note that VirtualBox also supports 64-bit guest operating systems, under the following conditions:

• 1. You need a 64-bit processor with hardware virtualization support (see User Manual chapter 1.2, Software vs. hardware virtualization (VT-x and AMD-V), page 10) and a 64-bit host operating system.
  NOTE: Since version 2.1.0, you can run 64 bit Guests while running a 32 bit Host. The prior requirement for Operating System is only for version 2.0.x. You still need the proper hardware.
• 2. You must enable hardware virtualization through your BIOS; software virtualization is not supported for 64-bit VMs.
  Note: some HP BIOSES have a glitch, When You ENABLE VT-X/AMD-V, You DISABLE it, so do try both ways.

Are you sure the proper intel drivers can be found by the installation?

I think yes, but I can't be sure.
I have copied the RIS inf file (e1G5132e.INF) downloaded from Intel with version 08/20/2008,8.10.3.0 to the amd64 folder along with the driver file (e1G5132e.sys) with version 8.10.3.0.
I did this while selecting the "Intel Pro 1000/MT Server (82545EM)" option as NIC for the VM.

Ok, apart from bad drivers is can also be that the driver can't find the (emulated)hardware for some reason, disable the nic or try some other to see if it continues.

I have removed all drivers (*.cat (not sure they are needed anyway), *.inf, *.pnf, *.sys files) from the amd64 folder, added latest versions of all kind of Intel drivers I could put my hands on, restarted the RIS service and now at the stage where it used to "freeze" it tells me that it cannot find a suitable driver for the NIC of the VM.
I wonder what exactly do the xVM Intel cards emulate and what are the right x64 textmode drivers for them?

If I install Windows XP 64-bit (from CD) and use the NIC named "Intel PRO/1000 MT Desktop (82540EM)" windows will use the Intel driver file called "e1G5132e.sys" file. On the RIS server, in the amd64 folder I do have this "sys" file and the corresponding RIS "inf" file. Might the fact that even despite this in text-mode the hardware is not correctly detected a bug in xVM VB?

Emulation is not an exact science, you might have to force a selection or remove it and 'detect' it after its finished with the main OS.

Per request, with emulation you don't have direct access to the original resource, this can cause some strange effects as the driver detection routines expect certain results which can not be guarenteed to be what is expected, thus leading to a possible incorrect driver. Which is why I said attempt to (pre)select the right one.