From owner-freebsd-stable@FreeBSD.ORG Tue Sep 9 22:22:13 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A7FF3E0 for ; Tue, 9 Sep 2014 22:22:13 +0000 (UTC) Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D760D110 for ; Tue, 9 Sep 2014 22:22:12 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id c9so18276874qcz.39 for ; Tue, 09 Sep 2014 15:22:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=1Gv9fitv/hz9e6DIlO4EbIN+w587M2GSMJgDejMWFfY=; b=c14q+AMiA9q8tpuyezkNGxlJXMPHyUs8bhwXE/3Q9bxPGvjq1MPPdJjh1hpPKrFyHy eVq/Krk0/+2bi1Q+F2BPPr0HxZiWUVAyP5X/x+s3Ej7HW1Pk5rUpKQFA8A1MV5rxD9Yg 0/PlJgqoYXTJvhrnbd2mqK6SsO5YokjcWEmoylN7X/5R/VPbzkWcroPO1gE7UQRieUey xOWKXuMHGK2BPIQQQssMpKm4//U1X9W+YftBkrQ6xRNULOqm0dca93BK3kfPDKOJPpdW jLyBWEqFzaqsJp1zmMP4Ai5nPV+0kYIylHtue6at+hBi+oCo7Pj7QlRqKb5EYsBz46OZ CSmw== X-Gm-Message-State: ALoCoQm6P3Bqs+oYmvM4WNqG5FyvyGnVPZdOP8xBvRtoyCDopAmofrgb70W5WWQ6A6dSZJqGky0g X-Received: by 10.224.92.83 with SMTP id q19mr53533995qam.29.1410301324670; Tue, 09 Sep 2014 15:22:04 -0700 (PDT) Received: from [97.62.85.214] (214.sub-97-62-85.myvzw.com. [97.62.85.214]) by mx.google.com with ESMTPSA id i110sm10907244qgf.29.2014.09.09.15.21.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 09 Sep 2014 15:22:03 -0700 (PDT) References: Mime-Version: 1.0 (1.0) In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-Id: X-Mailer: iPhone Mail (11D257) From: Mark Saad Subject: Re: VMware and 8.4 known issues? Date: Tue, 9 Sep 2014 18:12:50 -0400 To: Charles Sprickman Cc: freebsd-stable Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 22:22:13 -0000 > On Sep 9, 2014, at 2:56 PM, Charles Sprickman wrote: >=20 > Hello, >=20 > I have about a dozen FreeBSD 8.4 VMs running on a pair of ESXi > (5.0.0, build 469512) boxes. Generally, I have not had any problems > with this configuration. However one particular VM, which is > running the same kernel and same VMware settings as the other VMs > has paniced twice in the past few months. >=20 > I do not have a core dump, but both times a message regading the > CD-ROM device was logged shortly before the panic: >=20 > Sep 9 08:50:56 shellvm kernel: ata1: WARNING - READ_TOC read data > overrun 18>12 >=20 > Prior to the panic, the only thing Ive observed via my normal nagios > checks was that snmp and other network services became unavailable > and ping times to the host became very erratic, jumping from a few > ms to 800ms+. After the panic, the VM is locked up hard and > consuming copious amounts of CPU. >=20 > Looking around I see two things of note: >=20 > https://communities.vmware.com/message/1876880 (suggests it=E2=80=99s an > issue with FreeBSDs CD-ROM handling) >=20 > http://freebsd.1045724.n5.nabble.com/Re-kern-150186-parallels-panic-Parall= els-Desktop-CDROM-disconnected-leads-to-panic-eventually-td4114484.html > (also suggests CD issues) >=20 I dropped the CDROM as it's also caused a weird issues were sysinstall would= not find any daN devices if both were present . This was only an issue when= using sysinstall to jumpstart a box.=20 > This thread also ends with Ivan Voras stating "I'd say it's 'well > known' - at least the panic also happens on VMWare, and has been > happening for many years. >=20 > Ill try the suggested fix of completely removing the CD-ROM device > (its currently in the device list, but is not connected), but Im > curious if theres any reference Ive missed regarding known VMware > issues and/or best practices. Ill be sure to grab a console > screenshot if it happens again, I have little hope of getting a dump > though, as it seems the whole IO system is locked up. >=20 > Thanks, >=20 > Charles >=20 Also try to set the event timer to acpi-fast or acpi-safe . It's a sysctl na= med something like kern.timecounter.choice . There is a buggy emulated hpet i= n some versions on esxi that kill the clock on FreeBSD and Linux . There is a= kb on how to fix the issue dr Linux boxes circa 2011 .=20 =20 -- Mark saad | mark.saad@longcount.org=20 > -- Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best > Internet www.bway.net spork@bway.net - 212.982.9800 >=20