ESXi

 View Only
  • 1.  Reload VM Configuration after changing VMX File

    Posted Feb 21, 2014 01:42 AM

    Hello,

    If I make changes to a .vmx file on a VM in vCenter 5.5 does the configuration automatically apply to the powered off vm? I made some changes earlier and it looked like it did, but one of the steps I'm seeing in some documentation is to reload the vm config so it can be used appropriately. So, does this happen automatically or not?



  • 2.  RE: Reload VM Configuration after changing VMX File
    Best Answer

    Posted Feb 21, 2014 02:10 AM

    Hi,

    If it power off VM, then while powering ON , changes will take effect.

    Regards

    Mohammed



  • 3.  RE: Reload VM Configuration after changing VMX File

    Posted Feb 21, 2014 12:48 PM

    Confirmed. I made changes and as soon as it powered up I could see the changes in the details. Thanks.



  • 4.  RE: Reload VM Configuration after changing VMX File

    Posted Jan 31, 2018 03:51 PM
    can these changes be implemented without the virtual machine crashing?



  • 5.  RE: Reload VM Configuration after changing VMX File

    Posted Jan 31, 2018 04:11 PM

    Some vmx-file changes will result in a crash when the VM is powered on next time.
    Example: changing scsi0.virtualDev will probably result in a Windows VM not booting anymore.
    Honestly I assume  I do not understand your question - please explain.



  • 6.  RE: Reload VM Configuration after changing VMX File

    Posted Jan 31, 2018 04:24 PM

    The change I want to make without closing the virtual machine is related to the processor name.

    for example;

    I want to make the changes in Vmx on the following line in the named file without closing the virtual machine.

    cpuid.brandstring = "XXXXXXXXXXXX"

    ie reload.

    Host Machine ; Win 7 64 bit
    Virtual Machine : Win Xp Sp 3 32 Bit

    Thanks



  • 7.  RE: Reload VM Configuration after changing VMX File

    Posted Jan 31, 2018 06:43 PM

    Changing the CPU-parameters for a running VM is expected to crash the VM.
    Did you expect anything else ???