Upgrade from Proxmox VE 3.3 to VE 3.4 -> Win7 VM deactivated

R

Ralf

New Member
Mar 30, 2014
18
0
1
Germany
Hello,

after some investigation I am pretty sure, that upgrading from Proxmox VE 3.3 to VE 3.4 deactivated the licence of my Windows 7 VM. Using the recent backup and a test server, I am able to reproduce the fact, that it stays activated on Proxmox 3.3 and loses activation on Proxmox 3.4. Sure I can contact MS for reactivation, but now I doubt wether it was a good idea to start working with a Win7 VM instead of a real hardware. Is there any explanation for that behaviour?

Kind regards,
Ralf
 
Hi,
This is because the Hardware changes where MS is very picky.
and this occurs sometime when you upgrade qemu.

To be clear HW changes is for MS when you change the rang order of device or change Ids.

But reactivation is no problem.
 
Hello Wolfgang,

thank you for your hints. I am a little bit confused about hardware changes, since did not change anything concerning the VM (Mac address, HDD configuration, number of virtual cores, etc.). What exactly do you mean with "rang order of devices"?

To be more specific, the procedure was
1.) backup of the Win7 VM, which generates a vzdump-qemu-531-....vma.lzo file, on server (called Server1).
2.) Copy the vzdump-qemu-531-....vma.lzo, the X17-24289.iso and the virtio-win-0.1-74.iso to a server (called Server2) with a fresh installation of proxmox (3.3 or 3.4 respectively).
3.) Restore the Win7 VM with exactly the same VM ID (= 531) as on Server1.
4.) Start the Win7 VM. At this time (due to the network configuration) the VM was not connected to the internet.
5.) Receiving the message that 3 days left to activate Windows in case that Server2 runs Proxmox VE 3.4. No message appears (and Windows stays activated) if Server2 runs Proxmox VE 3.3.

I just do not feel well if things happen that I cannot understand and repair. Since my plan is/was to install MS Office on this VM and transfer all my office documents from real hardware to virtual hardware, the risk of random deactivation (e.g. during a proxmox update) would be a big problem. Therefore I would also be interested if other users have made same experiences.

Kind regards and thanks for your help,
Ralf
 
As I said MS is picky.

here an example.
you change the Mac address of the Gui. -> Ms oh new HW. (this is not a real new HW but for MS is this a HW change).

Microsoft has a scoring, I don't know how it works in detail exactly.
But if you have reached a score limit then you have to renew your license.

The change events like i describe before has a little score.
changing the UUID of the disk has a big score.

If you update qemu then it could happen that they change some things.
Example: init order of HDD.

this is normally no problem because this kind or changes have little source.
but if you have already a high score then this changes could be enough.
 
You must log in or register to reply here.
Top Bottom