From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 23 14:46:24 2014 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B02CED78 for ; Sun, 23 Feb 2014 14:46:24 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6B5731308 for ; Sun, 23 Feb 2014 14:46:20 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 0F0C41534ED for ; Sun, 23 Feb 2014 15:46:19 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JUXd7299qMVg; Sun, 23 Feb 2014 15:46:16 +0100 (CET) Received: from [192.168.10.9] (vaio [192.168.10.9]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 8CDE6153448 for ; Sun, 23 Feb 2014 15:46:16 +0100 (CET) Message-ID: <530A09B7.2030505@digiware.nl> Date: Sun, 23 Feb 2014 15:46:15 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: bhyve FreeBSD 10.0 VM crashed Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Feb 2014 14:46:24 -0000 Hi, I've kicked off 3 2G vm's which do a continous while(1) { make -j 4 buidlworld } And one of those VM's just crashed with the message below. Observation: The VM is clearly not able to recover from this. And probably needs to be destroyed and restarted... Don't know it it got as far as vmrun.sh restarting it. Question: 1) I expect this to be due to 3 VM's running in parallel with quite some load. But is this something that needs to be reported to stable@? Or does this belong here on this list. 2) Killing the VM and restarting probably also kills the memory but not the swap? And thus would allow to extract a core? I'll see when I reboot. --WjW ==== spin lock 0xffffffff814fa030 (smp rendezvous) held by 0xfffff80079e8d490 (tid 100097) too long timeout stopping cpus panic: spin lock held too long cpuid = 3 KDB: stack backtrace: #0 0xffffffff808e7dd0 at kdb_backtrace+0x60 #1 0xffffffff808af8b5 at panic+0x155 #2 0xffffffff8089cb71 at _mtx_lock_spin_cookie+0x241 #3 0xffffffff80c7ec7a at smp_tlb_shootdown+0x8a #4 0xffffffff80c8066c at pmap_invalidate_range+0x2fc #5 0xffffffff80932f6d at allocbuf+0x55d #6 0xffffffff809317cf at brelse+0x14f #7 0xffffffff80934b18 at bufdone+0x78 #8 0xffffffff809346c2 at biodone+0xe2 #9 0xffffffff8081c561 at g_io_schedule_up+0x1b1 #10 0xffffffff8081ca5d at g_up_procbody+0x6d #11 0xffffffff8088198a at fork_exit+0x9a #12 0xffffffff80c758ce at fork_trampoline+0xe Uptime: 1h21m3s Dumping 183 out of 2025 MB:..9%..18%..27%..35%..44%..53%..62%..79%..88%..97% Dump complete Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset: Stopping other CPUs timeout stopping cpus cpu_reset: Restarting BSP cpu_reset: Failed to restart BSP ====