I tend to check google, then this list or my gmail archive of this list
before I persue support on general products.  Nine times out of ten someone
has already invented the wheel.  For our tax compliance and engagement
software I go to support, though.



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.
>
>  ------------------------------
>  *From:* Don Ely [mailto:[email protected]]
> *Sent:* Wednesday, October 14, 2009 12:07 PM
>
> *To:* NT System Admin Issues
> *Subject:* Re: OT: can't power off a VM on ESX 3.5
>
>   I have vmotion, I have DRS, I have it all, I still wouldn't do that for
> one guest...
>
> On Wed, Oct 14, 2009 at 9:43 AM, N Parr <[email protected]> wrote:
>
>>  That's what vmotion's for.  You should be able to lose a host a keep
>> running.
>>
>>  ------------------------------
>> *From:* Don Ely [mailto:[email protected]]
>> *Sent:* Wednesday, October 14, 2009 11:39 AM
>>
>> *To:* NT System Admin Issues
>> *Subject:* Re: OT: can't power off a VM on ESX 3.5
>>
>>   Probably not an easy thing to do if you have more than one guest...  I
>> have 60 guests across 3 hosts, I wouldn't arbitrarily reboot a single host
>> for a single guest problem...
>>
>> On Wed, Oct 14, 2009 at 9:37 AM, N Parr <[email protected]> wrote:
>>
>>> Could always just reboot the host!
>>>
>>> -----Original Message-----
>>> From: Eldridge, Dave [mailto:[email protected]]
>>> Sent: Wednesday, October 14, 2009 11:32 AM
>>> To: NT System Admin Issues
>>> Subject: RE: OT: can't power off a VM on ESX 3.5
>>>
>>> I agree if it's hung it needs to be nuked anyway.
>>> Let me know if that worked.
>>> dave
>>>
>>> -----Original Message-----
>>> From: Michael Leone [mailto:[email protected]]
>>> Sent: Wednesday, October 14, 2009 10:30 AM
>>> To: NT System Admin Issues
>>> Subject: Re: OT: can't power off a VM on ESX 3.5
>>>
>>> On Wed, Oct 14, 2009 at 12:21 PM, Eldridge, Dave <[email protected]>
>>> wrote:
>>> > Try these two commands. Notice the small x and then a large X.
>>> > Ssh in as root.
>>> >
>>> > vm-support -x
>>> >
>>> > This will give you a list of vm's with a vmid.
>>> > Look for the vmid of the vm that is hung.
>>> >
>>> >
>>> > vm-support -X vmid
>>> >
>>> > this will crash the vm though. I just had to do this last week.
>>>
>>> Don't care about the VM, as I am about to delete it from disk, anyway.
>>>
>>> So it's in the process of slapping it into submission. :-) I told it to
>>> include a snapshot, and to try the NMI and ABORT. And it says it will take
>>> another 5-10 minutes ...
>>>
>>> So we'll see ...
>>>
>>> Thanks so much for that!
>>>
>>> > hth
>>> >
>>> >
>>> > -----Original Message-----
>>> > From: Richard Stovall [mailto:[email protected]]
>>> > Sent: Wednesday, October 14, 2009 10:08 AM
>>> > To: NT System Admin Issues
>>> > Subject: RE: OT: can't power off a VM on ESX 3.5
>>> >
>>> > I'm sure there are appropriate commands to turn off the VM from the
>>> > console, but you might not need to go that way.  Try browsing to the
>>> > ESX host (by ip, if necessary) and logging in to "VMware Virtual
>>> > Infrastructure Web Access".
>>> >
>>> > -----Original Message-----
>>> > From: Michael Leone [mailto:[email protected]]
>>> > Sent: Wednesday, October 14, 2009 12:03 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 11:58 AM, James Rankin <[email protected]>
>>> > wrote:
>>> >> Or alternatively, is a snapshot being removed/still open?
>>> >
>>> > No snapshot. At least, I didn't tell it to take a snapshot, and
>>> > there's nothing that schedules snapshots.
>>> >
>>> > I'm not trying to shut down the ESX server, just one of the VMs. I can
>>> > SSH directly to that ESX server, but what would I do once I got there?
>>> >
>>> > ~ 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/>  ~
>>> >
>>> >
>>> >
>>> > This message contains confidential information and is intended only for
>>> the intended recipient(s). If you are not the named recipient you should not
>>> read, distribute or copy this e-mail. Please notify the sender immediately
>>> via e-mail if you have received this e-mail by mistake; then, delete this
>>> e-mail from your system.
>>> >
>>> > ~ 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/>  ~
>>>
>>>
>>>
>>> This message contains confidential information and is intended only for
>>> the intended recipient(s). If you are not the named recipient you should not
>>> read, distribute or copy this e-mail. Please notify the sender immediately
>>> via e-mail if you have received this e-mail by mistake; then, delete this
>>> e-mail from your system.
>>>
>>> ~ 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/>  ~
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
>
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to