Convert the file to zerothick type.
vmkfstools -i uda20.vmdk -d zeroedthick uda20z.vmdk
nJoy;-)
Convert the file to zerothick type.
vmkfstools -i uda20.vmdk -d zeroedthick uda20z.vmdk
nJoy;-)
This is a hint from Andrew Thanks..
C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe -i yes -s 10.21.68.8 -u root -p password
Works !
In a batch:
start “VMLauncher” /D”C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\” VpxClient.exe -i yes -s 10.21.68.8 -u root -p password”
Thanks nJoy 😉
Virtual machines and NTP do not go easily well together. Machines paused for extended periods tend to loose the ntp sync since the difference grows too much.
Also from VMware Docs the following info might be clarificatory:
And :
In ESX, the ESX NTP daemon runs in the service console. Because the service console is partially virtualized, with the VMkernel in direct control of the hardware, NTP running on the service console provides less precise time than in configurations where it runs directly on a host operating system. Therefore, if you are using native synchronization software in your virtual machines, it is somewhat preferable to synchronize them over the network from an NTP server that is running directly on its host kernel, not to the NTP server in the service console. In ESXi, there is no service console and the NTP daemon runs directly on the VMkernel, so it works well as a NTP server for virtual machines.
Quoted from : http://www.vmware.com/files/pdf/techpaper/Timekeeping-In-VirtualMachines.pdf
Easy way (And I think best solution is)
To force a sync run hwclock command.
nJoy 🙂 !
kickstart postinstall, you can read how to do this on the internet.
wget http://foo/tools.tar.gz
tar xzvf *.tar.gz
cd directory-where-you-untarred
vmware-tools-install.pl -d
BINGO !
Giggidi Giggidi