dominic.giles
Bit poster
Hi.
Most VMWare disk images will come on a number of disks... and feature a VMX file as well.
The transporter client seems designed only to "transport" a single vmdk file. Does this mean that this process needs to be restarted for each vmdk device....
Does the transporter ignore all of the seetings in the VMX file, I realise many of them are specific to a VM setup, but some are not (disk caching etc).
Im afraid I cant test this since Transporter fails straight away after selecting the first of several vmdk files. It does work selecting the second etc.
And finally why do I need a Boot disk.. This is impracticle in many situations... I realise the licensing issues (Windows?) but I use it for Linux images where I know longer have a boot disk.
Thanks
Dom.
Most VMWare disk images will come on a number of disks... and feature a VMX file as well.
The transporter client seems designed only to "transport" a single vmdk file. Does this mean that this process needs to be restarted for each vmdk device....
Does the transporter ignore all of the seetings in the VMX file, I realise many of them are specific to a VM setup, but some are not (disk caching etc).
Im afraid I cant test this since Transporter fails straight away after selecting the first of several vmdk files. It does work selecting the second etc.
And finally why do I need a Boot disk.. This is impracticle in many situations... I realise the licensing issues (Windows?) but I use it for Linux images where I know longer have a boot disk.
Thanks
Dom.
