
sudo usermod -aG disk $USER
sudo chown $USER:disk /dev/sda1 [/dev/sda2 ...]
install-mbr --force ~/.VirtualBox/WindowsRAW.mbr
sudo dd if=/dev/sdb of=~/Windows7_sdb.mbr count=1 bs=512
sudo VBoxManage internalcommands createrawvmdk -filename raw7.vmdk -rawdisk /dev/sdb -partitions 1
sudo VBoxManage internalcommands createrawvmdk -filename raw7.vmdk -rawdisk /dev/sdb -partitions 1 -relative
Somehow Windows detects the faked SLIC.bin Dell OEM table and corrupts it so it cannot be used again in the virtual machine.
The dmidecode screenshots in native boot vs virtual boot can be found at: https://forums.virtualbox.org/viewtopic ... 55#p227455.
I can virtualize Windows 7 with activated status only once.
I can then boot into Windows 7 natively, also with activated status.
The problem begins when I try to virtualize again. I cannot reactivate until I recreate the SLIC.bin using "dd if=/sys/firmware/acpi/tables/SLIC of=SLIC.bin" command. Once recreated I can activate the Windws 7 virtual machine once more, until I boot into native Windows again.
Even if I try to restore the Virtual machine license status with the Advanced Token Manager, I get an error.
Lauscher wrote:Somehow Windows detects the faked SLIC.bin Dell OEM table and corrupts it so it cannot be used again in the virtual machine.
This cannot be. How should Windows be able to change the BIOS? The problem must be somewhere else.The dmidecode screenshots in native boot vs virtual boot can be found at: https://forums.virtualbox.org/viewtopic ... 55#p227455.
Do you still have these damaged output? You should get correct output of parameters you set with "setextradata". If not, the problem is here.I can virtualize Windows 7 with activated status only once.
I can then boot into Windows 7 natively, also with activated status.
The problem begins when I try to virtualize again. I cannot reactivate until I recreate the SLIC.bin using "dd if=/sys/firmware/acpi/tables/SLIC of=SLIC.bin" command. Once recreated I can activate the Windws 7 virtual machine once more, until I boot into native Windows again.
Windows 7 is curious with its activation status. Even with changed hardware, it doesn't want to get reactivated immediately.
Edit: if you really think Windows changes the SLIC-table, you could compare an old and a new SLIC.bin, for example using checksum. If you really find a difference, it would be very interesting.Even if I try to restore the Virtual machine license status with the Advanced Token Manager, I get an error.
ok, Advanced Tokens Manager is only successfull whether the hardware is not changed too much.
At first you should have a look to get the right dmidecode outputs. As long as you get the wrong output, Windows won't stay activated. Maybe something goes wrong because of manually editing the win7.vbox file.
I recommend: create a new virtual machine, don't edit the win7.vbox manually, set parameters only with "setextradata". If you want to delete a setextradata parameter, set it again with value ""; then it disappears in the vbox file. You can use the BIOS script in my guidance, so you don't need to set every parameter severally.
After that, look at harddisk parameters, CD/DVD parameters, and MAC-Adresses of network adapters.
Be happy; you only have problems with activation. In this thread some people have problems with a BSOD 0xc000000e, we are searching for a solution since weeks with no success
. Whenever it is solved in virtual boot, it appears in native boot. Whenever it is solved in native boot, it appears in virtual boot.
![]()
All activation problems we have solved, I don't know anyone with no success.
I'm betting if you run dmidecode when you virtualize Windows you also receive the "Invalid entry length, DMI is broken. Stop!" message. Can you check?
Lauscher wrote:I'm betting if you run dmidecode when you virtualize Windows you also receive the "Invalid entry length, DMI is broken. Stop!" message. Can you check?
I don't have this problem, i checked it. The BIOS parameters appear as they should, and there is no error message.
I don't have this problem, i checked it. The BIOS parameters appear as they should, and there is no error message.
Wrong DMI structures length: 608 bytes announced, structures occupy 275 bytes
The "Wrong DMI structures length" can not be avoided currently, because it is a fixed value. But I don't think it harms the system.
I recommend: create a new virtual machine, don't edit the win7.vbox manually, set parameters only with "setextradata". If you want to delete a setextradata parameter, set it again with value ""; then it disappears in the vbox file.
<ExtraDataItem name="VBoxInternal/Devices/pcbios/0/Config/DmiBoardType" value="Motherboard"/>
Another guess is that Windows checks the motherboard information and deactivates if a motherboard isn't reported
Users browsing this forum: No registered users and 16 guests