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 ...


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

Yes, it is. What you probably want is multiple "server" stanzas, each with a different port, but possibly (probably?) the same server_name, serving the "different" content appropriately within each one, maybe with a different document root in each server. Full documentation is here: http://nginx.org/en/docs/http/server_names.html Example: server { ...


1

This is absolutely possible. The easiest way to set up nginx to listen on two ports is with a second server block, i.e.: # first server on port 80 serving one set of content server { listen 80; root /one/directory; } # second server on port 82 serving different content server { listen 82; root /some/other/directory; } All of the other ...


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 ...


1

Alexus pointed towards a link with the solution, though for StackOverflow, we should always pull out the salient points and post them here. Delete the old VM, choose to keep the disks. Restart the portal, this is important since the UI controls availability (show|hide) is computed once on load. With the new VM highlighted, from the bottom menu, choose ...



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