>>>>> "s" == Steve  <[EMAIL PROTECTED]> writes:

     s> the use of zfs
     s> clones/snapshots encompasses the entire zfs filesystem

I use one ZFS filesystem per VDI file.  It might be better to use
vmdk's and zvol's, but right now that's not what I do.

I also often copy ExPee VDI's onto physical hardware using xxcopy, the
MS iSCSI initiator, and FreeNAS, so I use the VDI's in ZFS act as
bootable-machine backups for this ghetto-ghosting scheme.  There is
this retarded dance you have to do with WPA.DBL---write me if you ever
need to do this.

     s> virtualbox clone

the ZFS snapshot/clone commands are a lot faster and less
mistake-prone than the virtualbox features, and they support a full
clone tree rather than just a linear progression of snapshots.  And
that ``delete last two snapshots'' button in vbox is idiotic.

After cloning a VDI you need to incant:

VBoxManage internalcommands setvdiuuid <cloned filename>

to mark a new random uuid onto it, then you can add it with the vdi
wizard or whatever you call it.

     s> if I ever add a new 'gold vdi file', it does not effect the
     s> clones, [...] I'll be testing more OS's than the current ones,
     s> so scalability

what?

Attachment: pgpZDAwc928xg.pgp
Description: PGP signature

_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss

Reply via email to