Now-a-days, we use virtual machines (VMs) a lot, to test operating systems, software, databases etc. as sandboxes - test, play, destroy ... repeat ! I had an interesting learning with Oracle virtualbox (issue & then solution discovery), which I'm sharing here ... it might help someone with similar situation :
I had a VM in virtualbox, which I copied into a separate folder, while it was powered off. Now, after the original VM was gone, I wanted to add it as a separate VM with a different name. However, I was seeing this UUID conflict. (UUID already exists) What I did :
1) Created a new empty VM with the desired NAME.
2) Located the new folder, where copy of the VM was there.
3) Ran the commands to change the UUID for each disk-file (.vmdk or others) I had there : "C:\Program Files\Oracle\VirtualBox\vboxmanage.exe" internalcommands sethduuid disk1.vmdk
(you have to be in the same directory as the disk files, to run this command. Easy, wherever you need the command window, SHIFT+Right-click > open command window here)
4) I ran the above command 4 times for 4 disks I had in the folder. Each disk file got new UUID now.
(make sure to remember / note the sequence of disk file numbering if there are many)
5) Now, go into the settings of the empty VM, storage, add the disks in same sequence under SATA disks one-by-one (the pictures below show it for 1 disk).
6) That's it ! Now I could start my new VM without issues, as all the disks had new UUID without conflicts.
I had a VM in virtualbox, which I copied into a separate folder, while it was powered off. Now, after the original VM was gone, I wanted to add it as a separate VM with a different name. However, I was seeing this UUID conflict. (UUID already exists) What I did :
1) Created a new empty VM with the desired NAME.
2) Located the new folder, where copy of the VM was there.
3) Ran the commands to change the UUID for each disk-file (.vmdk or others) I had there : "C:\Program Files\Oracle\VirtualBox\vboxmanage.exe" internalcommands sethduuid disk1.vmdk(you have to be in the same directory as the disk files, to run this command. Easy, wherever you need the command window, SHIFT+Right-click > open command window here)
4) I ran the above command 4 times for 4 disks I had in the folder. Each disk file got new UUID now.
(make sure to remember / note the sequence of disk file numbering if there are many)
5) Now, go into the settings of the empty VM, storage, add the disks in same sequence under SATA disks one-by-one (the pictures below show it for 1 disk).
6) That's it ! Now I could start my new VM without issues, as all the disks had new UUID without conflicts.
Learned a lot of new things from your post!Good creation ,thanks for good info Oracle SOA Online Training
ReplyDeleteGood content. You write beautiful things.
ReplyDeletesportsbet
taksi
hacklink
mrbahis
vbet
vbet
mrbahis
hacklink
sportsbet
dijital kartvizit
ReplyDeletereferans kimliği nedir
binance referans kodu
referans kimliği nedir
bitcoin nasıl alınır
resimli magnet
2K2FK
hatay
ReplyDeletekars
mardin
samsun
urfa
AZBTM
ds
ReplyDeleteOracle VirtualBox UUID conflicts can be frustrating, causing VM startup issues. This comprehensive guide offers effective solutions, helping users resolve the problem swiftly. Gaming In Lag Invaluable for anyone encountering this issue then need to solve.
ReplyDelete