On Wed, 2009-02-04 at 09:11 +0000, Peter Ford wrote: > > I'm currently working on improving my original solution to the problem of > viewing VDIs outside of VBox - I ran a Vbox using a lightweight Linux distro > on > a live disk image (a Damn Small Linux ISO works quite well) and then mounting > the VDI as a hard drive to do maintenance (eg. virus scanning) on it. One > major > drawback is that you can't use the VDI this way if it's still attached to > another VBox...
You know, the VBox source is open. There is no reason someone could not extract the "VDI interpretation" code from it and write a filesystem driver (userspace -- i.e. fuse, or kernel) to interpret and mount it without all of the overhead of a complete virtual machine. Given that VBox reads vmdk files, same thing could be said about that I'd guess. Given that VBox reads vmdk files, I wonder why VDI exists even. It would be nice to see a common standard emerge to describe the format of a virtual hard disk that all VM technology could/should use, so that way virtual disks are portable to different VM technology. Heck, I don't know why everyone isn't just using a flat (i.e. dd'able) image. :-) b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
