Hi there! I discovered a kind of problem in VirtualBox 2.1... or at least a different behaviour in comparision to 2.0 regarding cloning VDIs.
For my Debian guests, I have a kind of template-VDI which - until now - I always cloned using "VBoxManage clonevdi template.VDI new.vdi" and attached to a new guest afterwards... which worked pretty well up to now. But since my upgrade to 2.1, this approach does not work any more (at least not for me). When trying to boot the new guest, it freezes at "Grub Loading stage 1.5. Please wait..." (or something like that). I also recognized that the new VDI has a different (smaller) size than the template, but I thought that this could eventually be caused by fragmentation of the template... so I didn't pay much attention to this. Maybe I should also point out that Debian doesn't use the UUID within /boot/grub/menu.lst nor in /etc/fstab, so the change of the UUID should not be the problem (and never was in 2.0). In the meantime, I'm using the workaround of simply copying the template using "cp template.vdi new.vdi" and assigning a new UUID using "VBoxManage internalcommands setvdiuuid new.vdi" which seems to work fine for me. Just a few facts to my host system: It's an AMD QuadCore running Debian Lenny/Testing amd64 Does anybody else have similar problems with clonevdi under 2.1? Cheers, Andy _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
