This looks to be much better than VirtualPC, it has full USB support as well. I've already installed it and will try an installation of Windows XP SP3 on my Vista x64 computer. It's always good to have an extra version of XP running somewhere.
I have a deployment using VirtualBox 2.1 with Ubuntu 8.04 as host OS and XP as guest OS, it just runs like a charm, the only problem was with USB, but easy to fix following instructions from VirtualBox website.
Hi All, I know posting this thing in the wrong place The DMI data VirtualBox provides to guests can be changed for a specific VM. Use the following commands to configure the DMI BIOS information: VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" \ "Host BIOS Vendor" VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" \ "Host BIOS Version" VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate" \ "Host BIOS Release Date" VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor" \ 1 VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor" \ 2 VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" \ 3 VBoxManage setextradata "My VM" \ "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" \ 4 If a DMI string is not set, the default value of VirtualBox is used. To set an empty string use “<EMPTY>“. Changing this information can be necessary to provide the DMI information of the host to the guest to prevent Windows from asking for a new product key. On Linux hosts the DMI BIOS information can be obtained with dmidecode -t0 and the DMI system information can be obtained with dmidecode -t1 Will this help in modifying the SLP ID so as to run a OEM install disc