Dear,
In my case, my system hdd is full, so I have to move the "VirtualBox"
directory to data disks.
I just closed VirtualBox, and moved the directory. And vbox could not
find
anything. I registered the VDIs in new directory. Then I registered the
machine.xml, it told me something wrong with vdi (which reminds me the
horrible vbox error messages....). I removed the hdd configuration from the
xml file, then something wrong with snapshots. I removed these, too. Then it
worked, with all my snapshots lost. Luckly, I have backuped all file, so I
tried and tried, till I felt tired and just deleted all snapshots.
I do not think this register thing has the benefits of organization at
all. A
management based on filesystem is more easy and natural.
Look at vmware, reference disk files directly with file path in machine
configuration. So anything is easy to move, and easy to configure.
Thanks.
On Wednesday 12 December 2007 16:40:14 Dmitry A. Kuminov wrote:
> Hello Magicloud Wang,
>
> Magicloud Wang wrote:
> > I think this makes it harder to do things like mounting many isos by
> > command or moving a vm and its vdis to another place.
> > I had just lost a vm's all snapshots, because of this register thing....
>
> Yes, we know that this makes problems for some users. But that depends
> on how you use the product (if you don't need to move the VMs all around
> the current "register" scheme has its benefits since it causes you to
> organize things properly).
>
> Anyway, we are working on an alternative approach of a "portable" VM
> definition that will address the mentioned problem too.
>
> Also, you don't need to lose your snapshots because of the register
> thing, there is always a way to move the definitions (including
> snapshots) but that requires manual corrections to the settings files.
> So, if you describe what happened in detail, I will try to help you.
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
