Hi, all! I've tried reading throuhj the thread and figuring it out, but things are still not clear to me. I've got a Dell laptop with a genuine BIOS naturally accepted by Dell OEM Windows XP, Vista and 7 distributions. The CPU is Intel Core 2 Duo featuring VT-x hardware virtualization facilities. I use Linux (Ununtu 11.10 "Oneiric Ocelot" (planning to upgrade to 12.04 when it gets released) 32-bit x86) as the host OS with VirtualBox 4.1.2 (the about box says "VirtualBox Graphical User Interface Version 4.1.2_Ubuntu r38459", the package version is 4.1.2-dfsg-1ubuntu1) (I don't mind updating to a newer verion if needed). I would like to run 32-bit Windows XP Professional on a VirtualBox machine "without messing with activation" (the same way I run it as a secondary OS on bare hardware). As far as I understand there are 2 ways: emulating a brand BIOS or "XP mode". So, the questions are: 1. Can I copy my actual hardware BIOS identity to a Linux VirtualBox 4.1.2 machine? How? I've seen some XML files mentioned here on the forum, but it seems that's for VirtualBox 3 and there are no such files in VirtualBox 4.1.2. 2. If I patch VirtualBox to emulate "XP mode" (though I don't know how to do it on Lunux) then what a distribution do I install Windows XP from? Is there an ISO image? 4. What are the changes in "VBoxDD.so" found in "VBoxDD_4112_oneiric_i386.tar.bz2"? What am I intended to do after I replace my VBoxDD.so with the patched version?
The VBoxDD.so patched file is a patch to allow OA 2.x installations, XP uses OA 1.0 To install a emulated brand XP, you can use these commands to inject the required OEM SLP strings into the Virtual Box Configuration file, example: Code: "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Windows XP" VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor "Hewlett-Packard" "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" setextradata "Windows XP" VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor "Hewlett-Packard" No XP Mode patch for linus distro's exists (yet)
Obviously for Linux it will not be "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" Then just use OEM media (HP) for install or if not then use Sticky: VLK and OEMBIOS changer... after the install sebus
After reading virtualbox.org/ticket/9231 saying the feature of SLIC Passthrough being already implemented in the SVN I've downloaded and built SVN trunk code and installed Dell OEM Windows XP on it (from the same distro I've successfully used on bare metal)... No luck. The Windows installed was not activated and I could find no SLIC-related settings in the VM properties or VirtualBox configuration dialogues. Then, following FreeStyler's advice I've issued the following commands: Code: VBoxManage setextradata "Windows XP" VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor "Dell Inc." VBoxManage setextradata "Windows XP" VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor "Dell Inc." (I understand "Windows XP" is the VM name here) (I've taken "Dell Inc." from "dmidecode -t0" (for DmiBIOS attributes) and "dmidecode -t1" (for DmiSystem attributes)) No luck. Then I've tried (on the original Ubuntu packaged VirtualBox version, not SVN trunk build of mine) installing Windows from scratch having the setting allready applied... No luck. :-(
You will NOT get it done with Dell, hence Freestyler specified Hewlett-Packard If you do not know what you doing, then at least try to follow the instructions! Then use HP oembios* set SLIC Passthrough might be implememted (nice!), but that has NOTHING to do with XP SLP 1.0 activation! sebus
You're right. It works with "Hewlett-Packard". Thanks a lot. But I am still curious: in this case, how does it come that Dell OEM Windows XP distributions don't require activation (are in the activated state "out of the box") when I indstall them on my laptop (as well as on Dell desktops)? How does a Dell OEM Windows XP distribution recognize a Dell PC?
version 4.1.14-77440 released today h**p://download.virtualbox.org/virtualbox/4.1.14/VirtualBox-4.1.14-77440-Win.exe (replace h**t to http)
version 4.1.16-78094 released today h**p://download.virtualbox.org/virtualbox/4.1.16/VirtualBox-4.1.16-78094-Win.exe (replace h**t to http) Changelog Changes in VirtualBox 4.1.16 (released 2012-05-22): * VMM: fixed a Guru Meditation VERR_ACCESS_DENIED with certain guests (bugs #7589, #8247) * VMM: fixed a Guru Meditation VERR_PAGE_TABLE_NOT_PRESENT with Ubuntu 32-bit guests with nested paging enabled on AMD CPUs (bug #10183) * VMM: preserve segment limits and attributes when switching to unreal mode required for some legacy guests to work properly (VT-x without unrestricted guest execution only; bug #9941) * VMM: fixed a VM hang after a resume from pause / savestate with SMP guests in rare cases * 3D Support: several fixes for the Windows WDDM video driver crash * NAT: fixed a crash on attempt to process ICMP datagram under some circumstances (bug #10527) * Host-only Networking: lifted the maximal number of interfaces to 128 on Linux and Mac OS X hosts (there is no such limitation for Solaris and Windows hosts) * EFI: fixed wrong SEC/PEI Core entry point calculation (bug #10531) * VRDP: fixed a display update problem (bug #10503) * Main: set the proper VM state if savestate failed for some reason (bug #6189) * Main: more useful error message if a medium is inaccessible * VBoxManage: fixed controlvm savestate if the VM is already paused * Mac OS X hosts: addressed issues running on Mountain Lion Preview 3 (bug #10267) * Linux hosts: Linux 3.4 compile fixes * Linux hosts: fixed wrong help path in some rpm-based packages (bug #10418) * Guest Additions: fixed handling of custom environment variables during VBoxManage guestcontrol execute (bug #10581) * Windows Additions: fixed guest driver crash of VBoxSF in certain cases (4.1.10 regression, bug #10408) * Windows Additions: don’t load the WDDM driver if 3D support is not available for Windows 8 guests to keep the guest maintainable in that case (still better to miss some features than providing a blank screen) * Solaris Additions: added support for X.org Server 1.11 and 1.12
@atreyu I noticed in your build script that you're running "kmk" to build the VBoxDD.so module. That takes forever (as you noted). Instead just use Code: kmk VBoxDD This will build only that module and the modules needed to build it. MUCH faster!
oops, the second link works if I'm logged in mediafire, and didn't noticed on the other hand, I've been testing vbox implementation of the SLICTable and it seems great: - it works directly with those 374 bytes binary files that we all know, and a single line in the vm config: Code: <ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/SLICTable" value="/full/path/to/slic_table.bin"/> - accepts any valid slic table ( some Dmi entries do not work with xp ) - is backwards compatible with the patch I provide this direct support is expected in next big realese, that is 4.2.0; unknown schedule
version 4.1.18-78361 released today h**p://download.virtualbox.org/virtualbox/4.1.18/VirtualBox-4.1.18-78361-Win.exe (replace h**t to http) Changelog : VMM: fixed VERR_REM_VIRTUAL_CPU_ERROR under rare conditions after the guest has been reset (bug #5164 and others) VMM: fixed host freezes with 64-bit guests on 32-bit Linux hosts (bug #10528) VRDP: added a workaround for rdesktop clients not properly updating the screen size when minimized AHCI: fixed a rare bug which can cause a guest memory corruption after the guest storage controler has been reset NAT: another attempt to fix crashes under rare conditions (Windows hosts only; bug #10513) Mac OS X hosts: addressed issues running Leopard / Snow Leopard (bug #10631) Linux hosts / Bridged Networking: fixed the problem with device driver unloading on kernels 3.2.18 and newer due to an invalid reference counter (bug #10624) Linux hosts / guests: Linux 3.5-rc1 fixes Linux Additions: the guest content was sometimes not properly updated (bug #9887) Solaris Additions: installer fix for X.org Server 1.11 and 1.12
Sorry if its easy to find, but i couldn't in a quick seach and didnt want to read through all pages - so what exactly does current patch do: add a Slic Table - if so, important to know which one or somehow passes table in client through? Just can test this when PC components arrive and want to be rdy then.