New answers tagged


I have run into this issue in the past. Updating to the patches recommended in the KB fixed the issue. An alternative workaround, which I used until I was able to patch, is to edit /etc/vmware-tools/tools.conf, and add these lines: [vmbackup] enableSyncDriver = false This will cause the snapshot to only run a sync operation before the snapshot, and to ...


May be. Updated VmWare tools - is good practice. Notice, what VmWare recommends use open vm tools from distro. One more check free space on you storage - may be with snapshot or ram image it's exceeded. Check VM from client or cli for lost snapshots, make consolidation, if needed. Check datastore for garbage files


Consider reservation id as a Transactional ID. e.g If you buy a 5 tickets at one time. You have one Transaction ID but Five Booking ID. In the same way, if you launch 1 instance at one time using aws ec2 run-instances, you will have one reservation ID and one Instance ID. But if you launch 10 instance at one time using aws ec2 run-instances, you will have ...


The ResearvationId has nothing to do with Reserved Instances. It is a unique value indicating a request to launch EC2 instances. A launch request may come from the cli, AutoScaling, or the AWS Management Console. Each request to aws ec2 run-instances will return zero or more reservations of instances. Usually, it'll be one if it succeeds, but the docs say ...

Top 50 recent answers are included