Occasionally I test software in a Windows XP virtualization environment and if the software goes bad with an environment, I need a quick way to recover by purging the environment’s drive and replacing it with a copy: probably the quickest way is to duplicate a virtualized environment’s .vdi file and, should testing go awry, replace the compromised .vdi with the pre-compromised original copy.<\/p>\n
Sometimes I simultaneously test two environments or .vdi files. Since the .vdi are copies of each other, VirtualBox sees them with the same UUID and doesn’t allow you to set up the second environment until the .vdi files have differing UUID. To get around this use Terminal.app to change your copied .vdi’s UUID, before you attempt to set up the new\/second environment. To change the UUID, use the following steps:<\/p>\n
After changing the UUID, you can now continue setting up a second virtualized environment that is linked to the .vdi changed above. <\/p>\n","protected":false},"excerpt":{"rendered":" Occasionally I test software in a Windows XP virtualization environment and if the software goes bad with an environment, I need a quick way to recover by purging the environment’s drive and replacing it with a copy: probably the quickest … Continue reading VBoxManage internalcommands sethduuid WinXP_2.vdi<\/code><\/p>\n<\/p>\n<\/li>\n<\/ol>\n