![]() ![]() You can clone your template and make a new template VM, and then use VBoxManage modifyvm -hardwareuuid to set the new template's "Hardware UUID" to the original template's "Machine UUID"/"Hardware UUID".(VBoxSVC sometimes lingers on Windows you may have to kill it from the Task Manager.) You probably want to re-initialize the VirtualBox machine database after this, by closing/killing any VirtualBox process you're running. So, copy the /VirtualBox/Machine uuid attribute and add it to the /VirtualBox/Machine/Hardware uuid attribute. The "Hardware UUID" will only transfer to clones if the /VirtualBox/Machine/Hardware has the uuid attribute. ![]() You can edit the template VM Definition file directly.To ensure that the UUID transfers, you can take one of two approaches: So, for my template VM, it did have a "Hardware UUID" that I could use I just had to find how to transfer it to any clones I would make. I ran VBoxManage showvminfo and noticed that the UUID valued matched the Hardware UUID value, leading me to surmise that if any VM Definition didn't have a uuid attribute in the /VirtualBox/Machine/Hardware node, then the VM would use the "Machine UUID" value as the "Hardware UUID" value. Thankfully, I noticed something about all of my Virtual Machines that I hadn't prepared as those guides had outlined.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |