Guest Windows 7 activation, is it dependent on the host?

[AntiMatter]

Hi,

Quick description of the issue:
Using Virtualbox 3.02 and now 3.04.

1. I have two VM, Guest 1 = Win7 RTM enterprise 32 bits. Guest 2 = same in 64 bits. These are training VMs. They were activated by our network admin.

2. When I bring home and run them on my home computer (Ubuntu 9.04 x64) then they appears as not activated.

3. I take the same USB drive, plug it to my laptop, open the VM then they are activated.

The difference between the two scenarios is the host OS and the CPU (laptop Core 2 T7200, home: Core2 E8400, both CPU have VTx and VT is enabled in bios). And at home I give these VMs more RAM.

Question: how come the activation status could switch on/off like that? Is it by Windows 7 design or does Virtualbox have anything to do with that? And most importantly, is there any solution to have run thses VM with Win7 activated on my home computer?

Thanks in advance for any help.

[vbox4me2]

Could be the difference in cpu, which would be 'new' for w7.

[Sasquatch]

There are a couple of things that can trigger a reactivation. For one, the MAC address of the NIC(s). If they aren't the same, it's possible that the 'new' hardware change triggers a reactivation. Add the change in processor and you have a recipe for the trigger. RAM should not be a part of it, but with MS, you never know. Bring it down to the original level.

Things you need to change:
- MAC address of the NIC(s), make sure they are the same on each Host.
- Set the RAM level the same, lower or increase on the non-activated host so it's the same as the activated host.

With those things the same, a simple CPU ID difference should not trigger the reactivation.

[AntiMatter]

Things you need to change:
- MAC address of the NIC(s), make sure they are the same on each Host.
- Set the RAM level the same, lower or increase on the non-activated host so it's the same as the activated host.
With those things the same, a simple CPU ID difference should not trigger the reactivation.

Just did this on both VMs. Same problem.

I think that the MAC of NICs is a little bit too constraining. People must be allowed to change a NIC. There are many legitimate reasons, one of it is simply a NIC which is obsolete or fried and must be replace. If the CPU change was the cause, then it's more acceptable, but come on, it's still the same HD. And it's Win7 Enterprise!

My previous VMs with Windows Server 2008 didn't have this kind of activation issue. So either the issue is new from Windows 7 or I wonder if Virtualbox could have something to do (this is just speculation, not accusation). I can fix that easily by bringing my home computer at work to reactivate the VM. But I just feel that is just annoying if I have to do this manipulation frequently. For example, what if I upgrade Ubuntu ?

[vbox4me2]

Keep in mind that once it asks for reactivation any change might not get it out of it until reactivated, so use a fresh activated vdi and set mac and such the same before trying.

[Sasquatch]

A NIC change alone, fine, no reactivation needed. A CPU change alone, fine, same story. Combine these two, and it might as well hit the limit of allowed changes at the same time. Result: reactivation.