On Wed, 2009-09-30 at 15:51 +0200, Maciek Kaliszewski wrote: > Brian J. Murrell wrote: > > > > Hiper-complicated machine?
To be clear, my emphasis on your nomenclature here was on that hiper-complicated machines (supercomputers) are not so complicated in that they are just farms of PCs. > AFAIK VMDK is proprietary VMware(Never used :-) file format not fully > supported by VBox . VBox most certainly uses VMDK. I don't what's not "fully supported" about it. Maybe something esoteric like snapshots or something. But for the "shared disk" case, snapshots are likely not so important. Is VMDK "proprietary"? I guess. So is VDI then. Are you insinuating that "proprietary" means "closed"? VirtualBox certainly seemed to figure out how to use it. > I doubt it is possible to achieve "sharing "physical-virtual" disk" > between few VBox machine instances this way or I'm wrong :-) I'm 99% sure you are wrong. I'm 99% sure I have done it. I have VMware instances right this moment, up and running currently that are doing it. I am 99% sure I have investigated replacing those with VB and tested the shared disk for that. Sadly I have just not gotten around ot actually doing the replacement. But I'm not that motivated anyway given the host that this is running on doesn't support any of the CPU virtualization features that VB could take advantage of. > I bet it is possible via ATA over Ethernet :-) Perhaps. But why make it so complicated? VMDK works just fine. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
