From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 12 13:56:51 2010 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7BACD106566B for ; Fri, 12 Feb 2010 13:56:51 +0000 (UTC) (envelope-from freebsd-hardware@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 351808FC15 for ; Fri, 12 Feb 2010 13:56:51 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Nfw0o-0002CP-3r for freebsd-hardware@freebsd.org; Fri, 12 Feb 2010 14:56:50 +0100 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Feb 2010 14:56:50 +0100 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 12 Feb 2010 14:56:50 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-hardware@freebsd.org From: Ivan Voras Date: Fri, 12 Feb 2010 14:56:43 +0100 Lines: 25 Message-ID: References: <4B7484D8.2080406@greatbaysoftware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20100118 Thunderbird/3.0 In-Reply-To: <4B7484D8.2080406@greatbaysoftware.com> Sender: news Subject: Re: mptutil(8) causes VMware VM to crash hard X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Feb 2010 13:56:51 -0000 On 02/11/10 23:29, Charles Owens wrote: > Hello, > > We've been doing some work with mpt(4) and mptutil(8). We noticed that > in VMware (both Workstation and ESX) the SCSI controller is showing up > as mpt0... so it seemed only natural to probe it with mptutil. For Which is probably useless as you can't exactly diagnose a virtual drive :) > about 1 second, it looks ok (see below)... but what happened, in fact, > is that the VM went down pretty much instantly (nothing on console... no > panic, nothing). For what it's worth this is the usual response of VMWare to any situation it can't handle - instant VM kill. To its credit, it doesn't appear to affect the host / hypervisor itself. > Behavior confirmed in both ESX and Workstation. Any help with this > would be appreciated. I'd be glad to test patches or whatever. What are you expecting to do with mptutil? Hardware diagnostics itself should be done on the VMWare host side.