On 5/11/07, Dmitry A. Kuminov <[EMAIL PROTECTED]> wrote: > Hello, Matt! > > Matt Cheddar wrote: > (...) > > > Another thing i tried was adding the .iso again in VirtualBox, but > > the UUID does not match up with the one that VirtualBox is saying is > > not registered. I do not know if the UUID is a function of its path > > but that is the only thing that differs between it being mounted now > > and it being mounted earlier (before deleting it from the hard drive > > i backed it up and MD5ed it so i know this is an exact copy of the > > previously working .iso). > > UUID for .iso images is randomly generated when they are registered, so > every time you register a (even the same) image file, it gets a new > UUID. As opposed, hard disk images (.vdi) store UUIDs inside, so > registering the same image twice will give you the same UUID. >
Why not use the hash of the path to create a UID for a .iso? Or even its md5 (thou it would take to long to compute). It would be very helpful in cases like this :) While we are in the subject... i find the uuid thing quite dumb. Personally i prefer direct referencing path to my files. This second approach is also a lot easier when you want to move VMs from one place to another. It also makes the virtual files self contended. Simply take the whole directory with you, double click the file and BAMN! Instant VM ;) No need to register/unregister stuff here and there (specially when you can't "import" a VM in VirtualBox (the Qt app), but have to create a new one, and reassign the original disk). Any ways... just my opinion :) Cheers, KM -- As coisas são como elas são porque é assim que as fizemos ser. _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
