Differences

This shows you the differences between two versions of the page.

--- software:virtualbox [2011/12/15 01:01]
cyril [Using same installation for DualBoot and VirtualBoot]
+++ software:virtualbox [2014/11/29 10:03] (current)
cyril
@@ Line 3: / Line 3: @@
 ===== Using same installation for DualBoot and VirtualBoot =====
-First I tried the following tutorial:
+How to boot Windows from its partition with VirtualBox.
-[[http://geekfault.org/2011/10/14/lancer-votre-dual-booting-windows-dans-une-virtualbox/]]
+==== Summary ====
+=== Install Windows ===
+We will assume it is installed on partition 1.
-Don't forget to check "Enable IO APIC" in System tab of Settings for the virtual machine.
+=== Create disk ===
+  * Create the MBR. Two ways, from your disk, but the second one seems better:<code>
+dd if=/dev/sda of=disk.mbr bs=512 count=1
+</code> or from scratch with ''install-mbr'':<code>
+install-mbr -e1 --force ./disk.mbr
+</code>
+  * Create the virtual disk:<code>
+VBoxManage internalcommands createrawvmdk -filename disk.vmdk -rawdisk /dev/sda -partitions 1 -relative -mbr disk.mbr # if single partition for windows
+VBoxManage internalcommands createrawvmdk -filename disk.vmdk -rawdisk /dev/sda -partitions 1,2 -relative -mbr disk.mbr # if boot + system partition for windows
+</code>
+=== Create machine ===
-But I had a problem for booting, and the installation dvd could not repair the install, so I tried this tutorial:
+  * Create the virtual machine in VirtualBox the usual way, with the following settings:
+    * check "Enable IO APIC" in System/Motherboard tab and "Enable PAE/NX" in System/Processor tab
+    * set your real mac address for the Network adapter
+  * Set the DMI BIOS information to avoid activation problems. Execute:<code>
+sudo dmidecode -t0 # provides DmiBIOS* variables
+sudo dmidecode -t1 # provides DmiSystem* variables
+</code>And update the values of the following script that you will then execute (if a value is listed as "Not specified", set it to "<EMPTY>"):<code>
+#! /bin/sh
+VM_NAME="Win7" # Name of your Virtual Machine
+VSETED="VBoxManage setextradata $VM_NAME"
+CFG_PATH="VBoxInternal/Devices/pcbios/0/Config"
+# update the following values:
+$VSETED $CFG_PATH/DmiBIOSVendor       "Dell Inc."
+$VSETED $CFG_PATH/DmiBIOSVersion      "A08"
+$VSETED $CFG_PATH/DmiBIOSReleaseDate  "10/18/2011"
+$VSETED $CFG_PATH/DmiBIOSReleaseMajor  4
+$VSETED $CFG_PATH/DmiBIOSReleaseMinor  6
+$VSETED $CFG_PATH/DmiBIOSFirmwareMajor 2
+$VSETED $CFG_PATH/DmiBIOSFirmwareMinor 6
+$VSETED $CFG_PATH/DmiSystemVendor     "Dell Inc."
+$VSETED $CFG_PATH/DmiSystemProduct    "Precision M4600"
+$VSETED $CFG_PATH/DmiSystemVersion    "string:01"
+$VSETED $CFG_PATH/DmiSystemSerial     "9ZZ99Z9"
+$VSETED $CFG_PATH/DmiSystemUuid       "9Z9Z9999-9999-9999-9999-Z9Z99Z999999"
+$VSETED $CFG_PATH/DmiSystemFamily     "<EMPTY>"
+</code>
-[[https://forums.virtualbox.org/viewtopic.php?f=28&t=33356]]
+=== Fix Windows ===
-But I still had the same problem, a BSOD with error STOP OxOOOOOO7b.
+When you will boot your new virtual machine, it will fail.
+  * If you get an error with grub, because you used the first method to create the MBR, you have to mount the installation or recovery DVD of Windows in your virtual machine, start it, and choose to repair it after the language selection.
-I found on this thread some people having the same problem:
+  * If it fails, you can try to do it manually. Still on the installation DVD, type "ctrl-F10" to open a console, and type:
-[[http://forum.ubuntu-fr.org/viewtopic.php?pid=4062086]]
-Apparently one solved the problem by using an IDE disk instead of SATA in VirtualBox, but it didn't change anything for me. But another user said he followed:
-[[http://support.microsoft.com/?kbid=314082]]
-I did not find the .cab file to extract, but the .sys drivers were already at the right place, so I just merged the .reg file after rebooting to the native Win7, and then it worked also in VirtualBox !
-So basically just merge:
 <code>
+Bootrec.exe /FixMbr
+</code>
+  * You can also try different combinations of partitions you export with VBoxManage (sometimes it can require 1,2,3 which are diagnostic,recovery,windows)
+  * If you get a BSOD "Stop: 0x0000007b" and the installation DVD fails to repair this, reboot natively under Windows, and merge the following registry file merge_ide.reg (you may have to set the main disk as IDE to boot Windows and another useless disk as ATA so that it installs the drivers, and then switch the main disk to ATA):<code>
 Windows Registry Editor Version 5.00
@@ Line 192: / Line 223: @@
 ,2e,00,73,00,79,00,73,00,00,00
 </code>
+==== Sources - Story ====
+First I tried the following tutorial:
+[[http://geekfault.org/2011/10/14/lancer-votre-dual-booting-windows-dans-une-virtualbox/]]
+But I had a problem for booting, and the installation dvd could not repair the install, so I tried this tutorial:
+[[https://forums.virtualbox.org/viewtopic.php?f=28&t=33356]]
+But I still had the same problem, a BSOD with error STOP OxOOOOOO7b.
+Then I found on this thread some people having the same problem:
+[[http://forum.ubuntu-fr.org/viewtopic.php?pid=4062086]]
+Apparently one solved the problem by using an IDE disk instead of SATA in VirtualBox, but it didn't change anything for me. But another user said he followed:
+[[http://support.microsoft.com/?kbid=314082]]
+I did not find the .cab file to extract, but the .sys drivers were already at the right place, so I just merged the .reg file after rebooting to the native Win7, and then it worked also in VirtualBox, even with SATA !
+Several years after I ran into more problems and found this complete tutorial:
+[[https://forums.virtualbox.org/viewtopic.php?t=33356]]