Andreas, for such problems better open a bug report at www.virtualbox.org because you can attach statistics results better to a bug report than sending it to a mailing list. And it is easier for us to track the status. Perhaps you still want to do this (please only one problem per report).
On Sunday 04 January 2009, Andreas Höschler wrote: > A few days ago I started to experiment with VirtualBox 2.1.0 and was > amazed again, since no tun/tap stuff was needed anymore. Host Interface > Networking worked just out of the box. Unfortunately cloning virtual > machines did/does not work with this release!? The generated duplicates > are not bootable (PBR Signal)! We will fix this with the next release. > I therefore downgraded to VirtualBox 2.0.6 and gave this a try on a > X2200 with 8GB RAM. This worked and still works like a charm!! I have a > handfull on Solaris instances running now, all with Host Interface > Networking, so they are reachable from the outside and can offer The question is still if 2.1.0 changed something that you are no longer able to run several VM's at once. Or was it indeed a memory problem with your other box? > services. Dulicating virtual images works with this release. I will > never touch the snapshot feature again though, since I lost important > data during my tests and moving virtual machines from one host to > another. I later learned that this is not really supported yet. I never Moving a VM to another host is a feature we will support in med-term. > got the snapshots integrated again. :-( But I can live without > snapshots as long as duplicating images works reliably. Actually snapshots should work well with 2.0.6. Not sure about 2.1.0 though. > This is fabulous technology! Thanks Sun!!! > > My last unsolved problem is realizing a reasonable backup scheme for > the images. I am wondering whether pausing the virtual machine, copying > the vdi file to another host and then resuming the machine will do the > trick!? This could be done by a cron job at midnight. We could live > with a downtime of 15 minutes per day (required for copying the image). > If machine A dies all we had to do would be to fire up the vms on > machine B. What are you guys doing to do backups? The suggested backup scheme are snapshots. You can perform a snapshot using 'VBoxManage snapshot' with a cron job or somethink like that. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
