Date: Sat, 31 Mar 2012 03:07:09 -0500 From: Mark Felder <feld@feld.me> To: freebsd-hackers@freebsd.org Cc: Adrian Chadd <adrian@freebsd.org>, Dieter BSD <dieterbsd@engineer.com> Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <op.wb0zh7a234t2sn@tech304> In-Reply-To: <CAJ-Vmok9UxrpK30Hh1p5UXj4=9V0eCpSo2Wz%2B5fFJj5-yiSrOA@mail.gmail.com> References: <20120330211819.155070@gmx.com> <CAJ-Vmok9UxrpK30Hh1p5UXj4=9V0eCpSo2Wz%2B5fFJj5-yiSrOA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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. :(
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.wb0zh7a234t2sn>