On Thu, Apr 02, 2009 at 11:30:12AM -0600, Susan Kamm-Worrell wrote: > I've just pushed vdiskadm translate to the 3.3 vdisk repo. > > You can now translate data from one virtual disk data > type to another without creating a virtual disk. > This allows the user to use a vmdk file and directly > translate the data into a zvol without having to import > it first to a vdisk and then export it to the zvol. > > # vdiskadm help translate > > translate - translate virtual disk data to a different type > > USAGE: > vdiskadm translate [-i type[:opt]] -I input_file -x type[:opt] -d > output_file > > TYPES AND OPTIONS SUPPORTED > vmdk:sparse > vmdk:fixed > vdi:sparse > vdi:fixed > vhd:sparse > vhd:fixed > raw > EXAMPLE: > vdiskadm translate -I app.vmdk -x raw -d /dev/zvol/dsk/pool1/t1 > > ------------ > The -i option is only needed if vdiskadm can't detect the type of virtual > disk data. >
out of curiousity, when might vdiskadm fail to properly detect the virtual disk type? ed _______________________________________________ xen-discuss mailing list [email protected]
