Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I keep trying to add a *.vbox file packaged with a *.vmdk virtual machine. When I add to add that VM to my VirtualBox, I get the error:
Code:
Trying to open a VM config '/Users/jrsharp3/Documents/vm_share/WISP_1.3.0/WISP_1.3.0.vbox' which has the same UUID as an existing virtual machine.
p, li { white-space: pre-wrap; }
even if I run the command
Code:
VBoxManage internalcommands sethduuid
on it.
How can I fix this? I added a version of the machine in already, but modified it. I want to have both the modified and unmodified version in VirtualBox
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by wagscat123
Hi all,
I keep trying to add a *.vbox file packaged with a *.vmdk virtual machine. When I add to add that VM to my VirtualBox, I get the error:
Code:
Trying to open a VM config '/Users/jrsharp3/Documents/vm_share/WISP_1.3.0/WISP_1.3.0.vbox' which has the same UUID as an existing virtual machine.
p, li { white-space: pre-wrap; }
even if I run the command
Code:
VBoxManage internalcommands sethduuid
on it.
How can I fix this? I added a version of the machine in already, but modified it. I want to have both the modified and unmodified version in VirtualBox
Maybe machine was registered (partially successful). Try first:
Quote:
vboxmanage list hdds
if you will see your machine listed, remove UUID first:
Quote:
vboxmanage closemedium disk uuid_of_your_machine --delete
Have you seen like https://superuser.com/questions/4681...virtual-machin
? "Trying to open a VM config" "which has the same UUID as an existing virtual machine" web-search finds some ...
The VirtualBox.org forums seem to get good&prompt replies VB experts', esp. to sophisticated (='good') questions like this (but their first response is often: "log?"?)
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008
Rep:
Quote:
Originally Posted by GentleThotSeaMonkey
Have you seen like https://superuser.com/questions/4681...virtual-machin
? "Trying to open a VM config" "which has the same UUID as an existing virtual machine" web-search finds some ...
The VirtualBox.org forums seem to get good&prompt replies VB experts', esp. to sophisticated (='good') questions like this (but their first response is often: "log?"?)
link(S) refers to cloned machines, in OP case something happened and installation was incomplete leaving traces in the form of UUID. Just remove offending UUID. This does not solve a reason why VM machine could not be installed in the first place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.