We have some isolated clusters. I needed to move a VM from one isolated cluster to another and chose to export and import an OVF template of the VM. During the OVF deployment in the new cluster I made a point to not select "power on after deployment". When the deployment completed, it appears that DRS powered the VM on. This was not a critical issue but, I'm wanting to understand this behavior. I didn't expect that and don't recall DRS ever powering on a deployed OVF like that. I've included the pertinent events read from bottom to top.
Has anyone had a similar experience or an explanation?
DRS powered On the virtual machine on
ESXI-Host-Y
info
10/30/2013 12:39:37 PM
Power On virtual machine
OVF-DEPLOYED-VM
Resource allocation changed
info
10/30/2013 12:39:37 PM
OVF-DEPLOYED-VM
Warning message from hfesxinf27ph.hilton.com:
Insufficient video RAM. The maximum resolution
of the virtual machine will be limited to 1176x885
. To use the configured maximum resolution of
2560x1600, increase the amount of video RAM
allocated to this virtual machine by setting
svga.vramSize="16384000" in the virtual machine
's configuration file.
warning
10/30/2013 12:39:36 PM
OVF-DEPLOYED-VM
vpxuser
Failed to retrieve OVF environment sections from
extension vService Manager
error
10/30/2013 12:39:35 PM
Power On virtual machine
OVF-DEPLOYED-VM
Virtual machine is starting
info
10/30/2013 12:39:34 PM
Power On virtual machine
OVF-DEPLOYED-VM
Completed the relocation of the virtual machine
info
10/30/2013 12:39:34 PM
Power On virtual machine
Relocating from ESXi-Host-X,
to ESXi-Host-Y
info
10/30/2013 12:39:32 PM
Power On virtual machine
Task: Power On virtual machine
info
10/30/2013 12:39:31 PM
Power On virtual machine
OVF-DEPLOYED-VM
Virtual machine created
info
10/30/2013 12:14:06 PM
OVF-DEPLOYED-VM
Domain\UserX
Hello,
Have you checked if the VM monitoring was enabled on the DRS cluster by any chance.? which could power on the VM.
Thanks,
Avinash
Thank you for the suggestion. I have it disabled on all clusters and did check HA and DRS settings when initially investigating.
this event also happend in our environment,:(
I want to know why?????
In fact,we didn't enable the"VM Monitoring"
I never did find root cause for this. We are going through maintenance upgrades but I wanted to include the version levels when this behavior was witnessed:
vCenter 5.0.0 Build 913577
ESXi 5.0.0 Build 1254542