From owner-freebsd-hackers@FreeBSD.ORG  Sat Mar 31 08:07:17 2012
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 688131065676;
	Sat, 31 Mar 2012 08:07:17 +0000 (UTC) (envelope-from feld@feld.me)
Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 2C5BA8FC12;
	Sat, 31 Mar 2012 08:07:17 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me;
	s=blargle; 
	h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type;
	bh=dH8nxfWkodNxnIFa1kUYxWrA6L94W+nwEJSj6eYB6PA=; 
	b=cxe/3w1OaiHXxRiMnQxWlE0ncQwx/TYsFzQsimDuc4aQAsvzNhe5uAMinePHvVUMsF9QidCH1egW9/GiQueZwhut/4cQsrKhF5OasRRYZHA85dfqRIteBlJUFDq/8KsP;
Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org)
	by feld.me with esmtp (Exim 4.77 (FreeBSD))
	(envelope-from <feld@feld.me>)
	id 1SDtL9-0006cG-Hr; Sat, 31 Mar 2012 03:07:16 -0500
Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4)
	with esmtpa id 1333181229-20726-20725/5/39; Sat, 31 Mar 2012 08:07:09
	+0000
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
To: freebsd-hackers@freebsd.org
References: <20120330211819.155070@gmx.com>
	<CAJ-Vmok9UxrpK30Hh1p5UXj4=9V0eCpSo2Wz+5fFJj5-yiSrOA@mail.gmail.com>
Date: Sat, 31 Mar 2012 03:07:09 -0500
Mime-Version: 1.0
From: Mark Felder <feld@feld.me>
Message-Id: <op.wb0zh7a234t2sn@tech304>
In-Reply-To: <CAJ-Vmok9UxrpK30Hh1p5UXj4=9V0eCpSo2Wz+5fFJj5-yiSrOA@mail.gmail.com>
User-Agent: Opera Mail/11.62 (FreeBSD)
X-SA-Score: -1.5
Cc: Adrian Chadd <adrian@freebsd.org>, Dieter BSD <dieterbsd@engineer.com>
Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Mar 2012 08:07:17 -0000

On Fri, 30 Mar 2012 19:49:54 -0500, Adrian Chadd <adrian@freebsd.org>  
wrote:

> There's no guarantee that upgarding a VM or rebooting it won't change
> the config of said VM. Don't forget to diff the vm config file..

I'm not sure how this would be accomplished.... Am I supposed to be  
running backup software (rsync, etc?) on my ESX nodes now so I can capture  
these VM config files? How would I ever know what changed the VM files  
when? I'm sure if I called up VMWare and said "HEY YOU GUYS YOU BROKE THIS  
BY CHANGING THESE FILES" and then when they asked how I figured it out I  
told them I installed software that is definitely unsupported on their  
ESXi server to track it that they would certainly tell me to go pound sand.

Working in a black box environment is never fun. :(