Hi:) I am migrating from Vmware ESXi to XenServer 7.1. In the process I need to move some virtual machines that have special software which is licensed, the license is tied to the 'Bios UUID / Bios serial'. Some of the software is legacy and not possible to acquire new license for. When I migrated from physical servers to VMware this was easy. I just changed the 'uuid.bios' option in the.vmx file and the virtual machine 'thought' it was running on the same HW as before and the license was still valid. However when I imported the VM in XenServer (Through export/import of OVA) there was generated a new bios UUID? With the consequence that the licenses won't activate.

So, is it possible to manually set the bios UUID in XenServer (not randomly generated)? Or option B is it possible to specify a bios UUID when a VM is generated? I want to avoid the 'randomly generated' bios UUID for just five VM's. How To Install Ocarina Cheat Code Manager For Wii. I understand that UUID collisions is really bad, but this is more a edge case where I manually ensure that it won't collide. I assume thats just reading the VM uuid. Thats read only field generated when the VM is created. If you have support contact Citrix, they can likely get it can be modified some way, somehow.

I just don't ever remember seeing/reading anyone changing it. --Alan-- I think so, I do not have access to the system as we speak, but if I remember correctly the licensing software said the bios serial == Xen VM uuid (as shown in the 'xe vm-list' command). Xex Menu Download Usb No Jtag 2013.

Unfortunately I don't have any support contract yet, I currently just are checking if everything will migrate OK before I move all of the servers over to new platform, and glad I did as it don't. So when you initially activated the licences it was tied to the VMs 'Hardware' is that what you mean? We have the option to copy the host BIOS strings to the guest to activate OEM software but changing the VM uuid is not possible without tampering with the DB which is dangerous. No, some history: Pre year 2010, the servers in question did run on dedicated physical hardware. It's this hardware the software is originally licensed on.

In year 2010-2011 this servers were virtualized and moved to a VMWare ESX platform. I did get the same problem (licence won't activate). I then contacted the software company, and after some rounds they told that the easiest way (for both parties) is to change the.vmx bios uuid parameter so that the software will continue to work. This have worked flawlessly since.

So the problem is just that the VM is now seeing a 'randomly' generated bios UUID, I want it to be a predefined one. Am I correct when I say: 'Bios UUID / Bios serial' == Xen VM uuid? And it's no way to change that behaviour so I could specify a predefined UUID so that the OS 'sees' a different UUID than Xen is using?

(I want 'Bios UUID / Bios serial'!= Xen VM uuid, where I manually can specify Bios UUID). If not the above: • Is it possible to change the UUID without any danger? I would not taper with the DB, then I stay with VMware instead. • Is it possible to specify a predefined UUID while creating a new VM (instead of random generation)? Thanks for the answers so far and all help is highly appreciated:). I think it would take Citrix support hacking the state.db file and maybe other files to make it work. They may not even be able to easily.

Client came to me with a need to modify Discovery. All of their ESX Servers had a VMWare serial number (e.g. They want the actual server's hardware manufacturer serial number instead. SSH and SNMP were not an option. So, we did some digging on 'The. I have been smashing my head against this for hours and finally have given up and am asking for help. I have this function below that I found at It works fantastic for one individual VM, however I have a list of 250.

I don't know if thats just a simple single entry of if its scattered and very difficult to manipulate. Hope its not a show stopper for you, but that is a difficult request. --Alan-- Okey, thanks for your answer:D Yeah, it's currently a show stopper then:/ I will try (again, 2017 edition) to contact the sotfware company and check with them if they have any other solution that allows me to get the software up and running on XenServer platform, else I must probably stick with VMware until those servers are completely out of the environment, probably years. I asked around, currently we have no functionality to do this. Altering the DB in this case would be messy and dangerous. There are multiple references spread across the DB. Thank you so much for checking, really appreciate it:D And indeed I do not want to alter the DB.

So to conclude then: It's currently not possible to do what I'm asking. If this changes in the future, and anybody sees this, please leave a reply so I can update the answer! And if this is seen by anybody that is involved in the development, AFIK solution to this problem could be implemented in three possible ways: • Allow separate UUID's for the XenServer VM UUID and the UUID presented to the OS. This is similar to what VMware is doing. • Allow the user to specify a desired UUID in VM creation.

If the UUID is not found elsewhere in the system/pool. The VM is created with the specified UUID. • Use the BIOS UUID from the OVA/OFV importer (if it exist there, I haven't checked) and generate the VM UUID from this (should probably be implemented with a check for existing UUID's in the system/pool).