Tag Info

Hot answers tagged

4

You are much better off tracking changes inside the machine, as git etc. won't work very well with a large binary blob like a VM disk image. To be able to roll back to another state, snapshots are an excellent solution, but they have a performance impact. The best method (IMHO) is to use a configuration management tool (e.g. Puppet) and track the changes ...


4

That's not the best way to migrate from W10 to ESXi, export the VM as an OVF/OVA and import it - basically, as I'm sure you've figured out, the file paths are wrong doing it the way you have. Alternatively just edit the .vmx file but to be honest it's just quicker to export/import.


4

In short, you are wanting to build a template. On your maintenance schedule, convert it to a virtual machine, boot the new virtual machine, run sudo yum -y update ; sudo shutdown -h now. Once it is down, convert back to a template from a live VM. Since you have configuration management already in-place, you would simply build a new VM matching the ...


3

Yes, you can move the virtual machine from one host to the other. It's less than ideal, since your VM will be scheduled across two physical CPUs, but it will definitely work.


2

The reason you need to rebind the server to the domain is most likely related to the 30 day password for computers. When you restore a machine from snapshot, you're also reverting the password that machine knows and uses to authenticate to the domain. The domain will then refuse to service your computer. Re-adding it to the domain resets the password, and ...


2

VMware vCenter Converter sounds like the best tool for the job.


1

I think you're on the right track in with writing the time to a log file every second, but for the reasons you pointed out that may not be reliable. In addition to writing the time to a local disk, why not have your cron process reach out to a known stable system over the network and have that system log the request to disk? Something as simple as wget ...


1

Check VMFS for metadata inconsistency, it's done with VMware Ondisk Metadata Analyser Before you start VOMA from the CLI of your ESXi host, take care of the following guidelines: Shut down all virtual machines running on the VMFS datastore make sure that the VMFS volume is not in use by other hosts (best practice: unmount the datastore on the other ...



Only top voted, non community-wiki answers of a minimum length are eligible