Thanks for sharing the link. That is what I was trying to post. I tried it in 4.2.6, and it appears to work fine for the XP Mode activation. One benefit that using this method rather than patching is that it should technically carry over with an update. Downside I see is that you aren't using the newest BIOS revision. Is that correct to assume?
XP mode 64 bit patch works for XP mode in VBox 4.2.6, but it causes my Linux VMs not to shutdown completely. Had to use previous version, FYI.
Skyforger if you use the pre-patched 64bit vboxdd2.dll do you get same thing happening with the linux Vms
Went back to original un-patched 64 bit version. XP mode requires activation, but Linux VM shuts down correctly. Tried latest 64 bit patch (already edited version) and XP mode works, but Linux VM doesn't shutdown completely. Went to XP mode patch 64 bit, previous version (from post 386), and everything works fine. Do you have to do anything else except apply the patch, like SLIC codes? I've just been using the patch by itself and everything works (for the next to last patch).
I'm using the latest XP Mode patched version of VBoxDD2.dll (provided by Amiga) but I'm not experiencing the shut down problems you describe. Windows 7 x64 host Linux Mint 13 Cinnamon x64 guest
I reinstalled VBox 4.2.6 and tried latest patch. Same problem. Windows 7 HP SP1 64 bit host. Guests that experience the problems are Linux Mint 14 Cinnamon & XFCE, both 32 bit. I'll install a Linux Mint Cinnamon 13 32 bit guest to try to reproduce the problem with that. Will report back.
I installed a Linux Mint 13 Cinnamon 64 bit guest and the problem did not happen. It only seems to happen on the 32 bit Linux guests. @Sope: can you install a 32 bit Linux guest and see if you get the problem? Or can anyone with a 32 bit Linux guest comment on this?
I have tryed myself with ubuntu 12.10 and 12.04lts and get the same results no full shutdown everything gets stopped and saved but the apm doesn`t switch off virtual computer but just closing works fine. i have tried the xpmode slp in multiple positions in the correct range in the vboxdd2.dll and doesn`t seem to change outcome. i think they changed something from 4.2 to 4.2.6 some fix maybe and the guest (32bit linux) maybe is using that range for a save state or something, i dont really know but i`ll keep looking into it.
Thanks for looking into it. The next to last patch woks fine for me, even with VBox 4.2.6. I'm sure that might change with the next VBox release, though. Let me know if you need me to test a new patch if you make one. If all else fails I guess I'll just use a 64 bit Linux virtual machine when the patch I'm using won't work with a new VBox release. Thanks again.
Only just got around to installing a 32 bit Linux (Xubuntu 12.10) to test this on my setup. Not surprisingly I get the same results. I probably wouldn't have noticed as I usually go with x64 Linux VM's. Useful to be aware of though.
I think i have a solution, just installing mint cinnamon and xfce to check. Its already working on ubuntu 12.04, i`ve been doing a lot of reading on linux forums seems its to do with bios structure and slp that linux 32bit doesn`t like. (effects alot of dell/box shifter machines with slp) so vb bios structure must have changed between 4.2 and 4.2.6, will post as soon as i have finished checking.
OK i have now tested with mint 14 cinammon 32bit ( i gave up trying to install mint and in the end went with a ready made image) ok steps to get shutdown to work properly in most linux i would think. Load your vm Then in a terminal type: 1. sudo gedit /etc/default/grub 2. Find the line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" 3. Change this to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" 4. Save the file and close the file. 5. Finally, in terminal: sudo update-grub now shutdown it will hang again just close from machine menu. from now on it should shutdown ok. This is a oracleVb / linux problem i`m sure they will patch soon (might also explain why vmlite dont use a 4.2.6 bios yet due to compatibility) (This effects x86, x64 hosts with 32bit linux guests.)
Another alternative some might like to use is the 4.2.6 bios file patched and unpatched so you can set for each individual VM Add to your .vbox file <ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/BiosRom" value="<bios.bin>"/> or using VBoxmange from command line: VBoxManage setextradata "<vm_name>" "VBoxInternal/Devices/pcbios/0/Config/BiosRom" "<bios.bin>" Be sure to substitute your Virtual Machine name for <vm_name> and use the full path and file name for <bios.bin>. 7z containing patched xpmode and unpatched View attachment 20479
And for those wanting to get the bios direct from Virtualbox: Dump the VirtualBox BIOS to a file In VirtualBox, boot to Windows xp VM 1) Get to a command prompt and run these commands in the VM to capture the VirtualBox BIOS: C:\>debug r cs eff0 r bx 1 n bios.bin w q Here they are again with comments: C:\>debug [This runs debug.exe, a primitive MS supplied debugger.] r cs [This command says Let me set the CS register, debug.exe will display the current CS and then a ':' prompt] eff0 [This sets the CS register to hex EFF0, which is hex 100 bytes before the BIOS at F000] r bx [This command says let me set the BX register, debug.exe will display the current BX and then a ':' prompt] 1 [This sets the BX register to 1 (digit ONE)] n bios.bin [This says set the fileName to "bios.bin"] w [This writes BX:CX bytes (hex 10000 = dec 65536 bytes), starting at EFF0:100] q [Quit] You should now have a file c:\bios.bin - which is the VirtualBox bios dumped. Now you can transfer in to your main system using shared folders or usb device. (derived from a posting at vbox-dev by Mark Cranness)
I've deleted that VM but when I get the chance I'll recreate it and get the log file for you. EDIT: PM sent