![]() ![]() – Create a new snapshots in the menu, call it “Test” – Browsing the Datastore there are many active snapshots. in the “Snapshot Manager” I d idn ’t see the active snapshots and my options were grayed out. – You can “Revert to Current Snapshot” via menu. But while browsing the Datastore I saw many active snapshots. When I went into the “Snapshot Manager” there were no active snapshots and I couldn’t delete the files. Trying to remove the snapshots was a little bit different. I was looking what was going wrong after a few failures. Vmware-iso (vsphere): Uploading output\windows-base-2012.Today I got some problems with backing up one of my VM’s using VMware Data Recovery. => vmware-iso: Running post-processor: vsphere SXi and the format needs to be specified). => vmware-iso: Skipping export of virtual machine (export is allowed only for Vmware-iso: Detaching ISO from CD-ROM device. => vmware-iso: Cleaning VMX prior to finishing up. => vmware-iso: Deleting unnecessary VMware files. Vmware-iso: Waiting for VMware to clean up after itself. => vmware-iso: Gracefully halting virtual machine. => vmware-iso: Uploading D:\packer2\vmware\windows\dependencies\puppet-agent-1ġ0.1-圆4.msi => C:\Windows\Temp\puppet-agent-install.msi => vmware-iso: Machine successfully restarted, moving on ![]() Vmware-iso: A system shutdown is in progress.(1115) => vmware-iso: Waiting for machine to restart. I am having same error - I tried with PP: vsphere and pp: vsphere-template I get the following error Looking at the vsphere-template post-processor code, I noticed a 10 seconds delay when starting the post processor “vsphere-template”. vmx file, and reappear with different values some seconds later (about 10 seconds on the faster hardware and about 15 seconds on the slower hardware). Backtracking to the Packer script revealed that sometime around the end of the builder “vmware-iso” and the start of the post processor “vsphere-template”, those entries disappear from the. After some investigation, the root cause was identified as being two entries uuid.bios and vc.uuid that were missing from the. This problem always happened on a test ESXi/vCenter 6.5 running on a slower hardware, while it did not happen all the time on a faster hardware running ESXi 6.0/vCenter 6.5.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |