From owner-freebsd-virtualization@FreeBSD.ORG Thu Jun 26 22:00:12 2014 Return-Path: Delivered-To: freebsd-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 36E1FB06; Thu, 26 Jun 2014 22:00:12 +0000 (UTC) Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) (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 DDED62D65; Thu, 26 Jun 2014 22:00:11 +0000 (UTC) Received: by mail-qc0-f170.google.com with SMTP id l6so3847956qcy.29 for ; Thu, 26 Jun 2014 15:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Tj0Kycr+Gb56CipOtWc4Te4dGW6qjdlXyoRlI8fj5EM=; b=yyDzQl8ZyiRxNFWBexfMX/jXkOxG+Le66UMuSNi64yh864nIRblyRFMDbw2RQH82kE 5/VTs30rkzza9HR6EpsPKJ38lzJg9NTQyD3kh94BBbvtv0EBSU03GKrQjLq4PCE94IDM /YVWllKLmFQg5WX+WDkgQxVfzBUOzVdVCSrfqbigDKgRsAxOdNLkPE4rkvgusb6s073e le7PFY9FB+TI7i9Wu+wFgPx5jOgBrG4AvS+dByuoX+CEV5XmExO8DfBzp7n/joFYG5ip HhW2vDm9cbwxpcevRt13OPkdTBONxmiDq89gyE1DV55wNzoMnzUJwaylRwWRYh7AkWYu swJQ== MIME-Version: 1.0 X-Received: by 10.140.19.21 with SMTP id 21mr25692728qgg.76.1403820011069; Thu, 26 Jun 2014 15:00:11 -0700 (PDT) Received: by 10.140.48.37 with HTTP; Thu, 26 Jun 2014 15:00:11 -0700 (PDT) In-Reply-To: <1403819194.2417.8.camel@bruno> References: <1403818926.2417.6.camel@bruno> <1403819194.2417.8.camel@bruno> Date: Thu, 26 Jun 2014 15:00:11 -0700 Message-ID: Subject: Re: jenkins bhyve vms crashing and burning after several days of use From: Neel Natu To: Sean Bruno Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18 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: Thu, 26 Jun 2014 22:00:12 -0000 Hi Sean, On Thu, Jun 26, 2014 at 2:46 PM, Sean Bruno wrote: > On Thu, 2014-06-26 at 14:42 -0700, Sean Bruno wrote: >> so, we're seeing the bhyve vms running in the freebsd cluster for >> jenkins crashing and burning after a couple of days of use. >> >> vm exit[9] >> reason VMX >> rip 0x0000000029286336 >> inst_length 3 >> status 0 >> exit_reason 49 >> qualification 0x0000000000000000 >> inst_type 0 >> inst_error 0 >> >> >> It looks like we have an active core file on havoc.ysv if you have a >> moment to look at it: >> >> http://people.freebsd.org/~sbruno/bhyve.core >> >> FreeBSD havoc.ysv.freebsd.org 11.0-CURRENT FreeBSD 11.0-CURRENT #2 >> r267362: Wed Jun 11 14:56:34 UTC 2014 >> sbruno@havoc.freebsd.org:/usr/obj/usr/src/sys/HAVOC amd64 >> > > Also, from chaos.ysv > > http://people.freebsd.org/~sbruno/bhyve.core.chaos > > FreeBSD chaos.ysv.freebsd.org 11.0-CURRENT FreeBSD 11.0-CURRENT #1 > r267362: Wed Jun 11 15:50:24 UTC 2014 > sbruno@chaos.ysv.freebsd.org:/usr/obj/usr/src/sys/CHAOS amd64 > Can you tell us the processor and memory configuration on havoc and chaos? Also, could you execute the following commands on havoc: # bhyvectl --vm=vmname --cpu=9 --get-vmcs-guest-physical-address -- this will output the offending guest physical address that triggered the EPT misconfiguration # bhyvectl --vm=vmname --get-gpa-pmap= -- this will output the page table entries in the EPT that map to the offending GPA Hopefully that provides us with something to work with. best Neel > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org"