Wow what a pain. I purchased through Dell and I don't have to call them first. I go straight to Vmware.
-----Original Message----- From: Michael Leone [mailto:[email protected]] Sent: Wednesday, October 14, 2009 1:49 PM To: NT System Admin Issues Subject: Re: OT: can't power off a VM on ESX 3.5 On Wed, Oct 14, 2009 at 2:22 PM, N Parr <[email protected]> wrote: > Neither would I other than a last resort, I had this same issue with a > guest not shutting down a couple weeks ago and called tech support to > resolve the problem. That's the first solution, but I'm assuming he > doesn't have support or he wouldn't have been asking here. No, I have support. :-) But since we bought our VMware through HP, I have to call HP support, and go to their VMware support desk. That can be ... convoluted ... If it was an actual emergency, I would have done that. But since it wasn't critical, I figured I'd ask here. (and I knew it wasn't critical since no alarms triggered; no other hosts complained; no users complained they couldn't access various hosts; and the responses here weren't along the lines of "Wow, that's serious .."). :-) I wouldn't bounce an ESX host unless I had to, but in this case, this ESX hosts is (mostly) used by my private testing domain/subnet. So if I bounced this one particular host, it would be no big deal. I would just migrate any production VMs onto one of the other ESX hosts, and go on from there. I'm lucky, in that I have that capability. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
