From owner-freebsd-virtualization@freebsd.org Sun Jul 1 08:29:24 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8A2E8FE31A3; Sun, 1 Jul 2018 08:29:24 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c:c09::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB51B85B35; Sun, 1 Jul 2018 08:29:23 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-wm0-x234.google.com with SMTP id u18-v6so5808102wmc.1; Sun, 01 Jul 2018 01:29:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=K0MZjqff1qkliAawhXMFIp6tdjAjg/+ctyBy/ArE+WQ=; b=Jpi8kYLkyP4BlhHWqWebpbfxfhixET08ttbWiX6Rwp+CiHQQtCRjYqLyie+pAgO3O8 nMHRTAz7NeY214IRPChT2mqTf3P1LAL5Gk7Yglaxut1XfW5jpDuakYxxPHE3TiM0duSr GZvYkgbPv6ygbQNd75yxNm+EHb674Vu1KMqlz3OO9fGdPv82k68tYbRP15mje9VdqDAT /weDIHIPVNyFhUV+8jY38Pr6n+3nLqbgcTiZ1v9v7OM4qBeIXyDFVwhVP9jBq1HkKZ6M LRm5RHxWAuooa4rCAYvin9Vow0ReP9Qs1IX1bwt+FdDi6ICrwo9fKmNCHS6YJsC4V61S ha8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=K0MZjqff1qkliAawhXMFIp6tdjAjg/+ctyBy/ArE+WQ=; b=eLWUE2zLhGdGXw4K28J7OHRt3vh2AEhdrYp74XHckjoWwOFCJtUSIJo0iWAKOZBpE/ 8jT072rxtiGPdnLiC6EyfYt+Cc8nhDLiWnY9VyyIFdscHjgjN52ZN1C0JU0IRd4mxFbq urZgsxyG+1qbsyawzauc16jRaqYA5bgx+sFBahmBHysniFRH0DXXIhCBWTuWf5M1hfsI iyCncnCN9q1v8tpamuJwsrZl+Cltdvmw/rFNWa09JeiDEb+9zQki6pXrB5OB3Z8mGfQD C6NIjKqBzfTkexKS1zGZqD7BP7knr/OfekwxQjwtn+fEBOFFztgi0Xroq5cnSlc3hEJT tJ4Q== X-Gm-Message-State: APt69E2IGeG5kDqrXtCk9H0p0w0BOlhivgM0iVtMdYXuPN6RDqkFw/Ih dxc71lG46U3iocSfSdV41w8= X-Google-Smtp-Source: AAOMgpdSojmlJx6AbgpmCqb/qoXHlgAN/FjazD9uXnuPEzZp8Qmt5zv7H1ff4NVDHm19kx89uAsRwg== X-Received: by 2002:a1c:3f56:: with SMTP id m83-v6mr948847wma.37.1530433762673; Sun, 01 Jul 2018 01:29:22 -0700 (PDT) Received: from pesky.lan (93-34-93-211.ip49.fastwebnet.it. [93.34.93.211]) by smtp.gmail.com with ESMTPSA id s184-v6sm5471626wmf.5.2018.07.01.01.29.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 01 Jul 2018 01:29:21 -0700 (PDT) Sender: Mark Johnston Date: Sun, 1 Jul 2018 04:29:19 -0400 From: Mark Johnston To: Konstantin Belousov Cc: Mihai Carabas , freebsd-amd64@freebsd.org, freebsd-virtualization@freebsd.org Subject: Re: Inspect pages created after a vm_object is marked as copy-on-write Message-ID: <20180701082919.GB3926@pesky.lan> References: <20180629225209.GA4238@pesky.lan> <20180630215956.GA1282@pesky.lan> <20180630223401.GW2430@kib.kiev.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180630223401.GW2430@kib.kiev.ua> User-Agent: Mutt/1.10.0 (2018-05-17) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Jul 2018 08:29:24 -0000 On Sun, Jul 01, 2018 at 01:34:01AM +0300, Konstantin Belousov wrote: > On Sat, Jun 30, 2018 at 05:59:56PM -0400, Mark Johnston wrote: > > On Sat, Jun 30, 2018 at 10:38:21AM +0300, Mihai Carabas wrote: > > > On Sat, Jun 30, 2018 at 1:52 AM, Mark Johnston wrote: > > > > On Fri, Jun 29, 2018 at 11:58:31AM +0300, Elena Mihailescu wrote: > > > >> Is there anything I am doing wrong? Maybe I misunderstood something about > > > >> the way the virtual memory works in FreeBSD. > > > > > > > > I'll note that inspecting and manipulating vm_map_entry and vm_object > > > > structures in the bhyve code constitutes something of an abstraction > > > > violation, though it's reasonable to proceed this way while working on a > > > > prototype of the feature. That is, I think you should keep trying your > > > > current approach, but just be aware that you are using the copy-on-write > > > > mechanism in a way that the VM system isn't really expecting. > > > > > > > > > > Can you point out the right approach in our case? > > > > I am merely suggesting that once the required VM interactions are fully > > understood, the mechanism implemented for bhyve should be generalized > > and lifted into the VM code. It's hard to say what the "right" approach > > is, since I don't fully understand the proposed algorithm. It sounds > > like you might be attempting something like: > > > > 1. mark the mappings of to-be-migrated objects as NEEDS_COW, so that a > > subsequent write fault triggers creation of a shadow object > It is actually MAP_ENTRY_COW | MAP_ENTRY_NEEDS_COPY. Indeed. > Note that setting an entry to COW changes the behaviour of mprotect(2), > at least. > > > 2. invalidate all physical mappings of pages in the object to be copied, > > so that subsequent writes trigger a fault > I do not think this is needed to detect writes after the COW is set. > It is enough to remove the write permissions. Same as fork() does, > see the vm_map_copy_entry() code for the handling of MAP_ENTRY_NEEDS_COPY > case. Ah, right. > > 3. copy pages from the backing object to the destination > As I understand, this is done right after the entry is marked > as COW. > > > 4. copy any pages from the shadow object to the desination > And this is done after all backing data is copied and the process is > suspended. Right, I see. Some reading suggests that in general we might perform multiple iterations of this procedure before suspending the process and performing any remaining copies. > > 5. collapse the backing object into the shadow > > 6. if the shadow object exists and was non-empty before the collapse, > > goto 1 > Are you trying to describe how to undo the COW marking ? Marking an > entry as COW really changes its semantic, and we do not need the undo > operation in the base so far. Collapsing the objects would lesser > the pressure on the system pollution with objects, but it does not > change back the meaning of mappings, e.g. their behaviour on inheritance > on fork. I was just thinking about how to avoid creating a long chain of objects if multiple iterations are in fact needed. From owner-freebsd-virtualization@freebsd.org Sun Jul 1 13:34:53 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1CD57FF74AB; Sun, 1 Jul 2018 13:34:53 +0000 (UTC) (envelope-from elenamihailescu22@gmail.com) Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E5F570131; Sun, 1 Jul 2018 13:34:52 +0000 (UTC) (envelope-from elenamihailescu22@gmail.com) Received: by mail-ot0-x22f.google.com with SMTP id l15-v6so14690492oth.6; Sun, 01 Jul 2018 06:34:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=abSFmBRuXW2sVBS1p5Xa8RktRGe540YbZ53HDff2WAM=; b=RNyjmOwIU7cGYaqkimlCclKSiJUdouU1O0YXJzWCydzfJxkFuSjE1EozHOs+7S75KA IytGvIIUoSsOs3tZBgpLRIN+15oNHsU9AxnM3BWcFqESzZiT6QLj/x6yKiL2RlORQR7w HeT1qEqIZ6oZTemMGwqPWDz67ajgmS3Tl+uawe84llLcpFa1cHHN9hY9LGFtrBudLI3U jYTJlTNRpAJC/BvfDFwNztnwa/SgzhPx0xNNrqbjJ40Z6qd86ENIfQU7LAweSBOcxYms Wt0uOwS9efOcfkUCoa547r1F9+juWJFKi1E0PqUFjKr6QepYjyH39/sTq4v5RrIny6vk kpEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=abSFmBRuXW2sVBS1p5Xa8RktRGe540YbZ53HDff2WAM=; b=SNlkGc6cLccs/r2yoiU7j420rt0EASFwM3yjx9NoPSseFfPLF0pnSFEMFr0ddsLAt7 E6N77jjDYAzhGofsyrbnPWW3gftXmnF85uUpw5IakFyOLn+gwER4IuasO9XQwbPs19Z+ s3fVuzwgsG0DnjNS6dzalgYGZHVYUbE7WQiS6V2RlheLxqJAeQHlVM8Dj/mJ33EazAJD X3ZwMmri0qzmV110/3pfErdcJ/ERrZsUm8y/gcIfzkEKTHFRXILPIftIs97yWki4IkeC ivK6nUYxxElRJ3qEWtrejkHpsLxqYGLpqYN2PA4stkUMBdDYc+Njr+kR92TO7JiYs+Wt TaXA== X-Gm-Message-State: APt69E3EbEtgCrbeOnqjjC4pP8OIM1M72VNyINc1YEIzE1oyprIYGbZy VT3Hhioy5IFyJuQpPlDz4MMbDDlFOXKhXwFmW5gm2g== X-Google-Smtp-Source: AAOMgpdWsDTW2nJDo+HHstLWJoQ7jhxPjp3h91tZ6m7CdvXoXoJ3db7cKb3WlmniJ3sU6KFErRv7JirrNzfIP2JEb64= X-Received: by 2002:a9d:5b39:: with SMTP id x54-v6mr10743197oth.106.1530452091396; Sun, 01 Jul 2018 06:34:51 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:3c4e:0:0:0:0:0 with HTTP; Sun, 1 Jul 2018 06:34:20 -0700 (PDT) In-Reply-To: <20180701082919.GB3926@pesky.lan> References: <20180629225209.GA4238@pesky.lan> <20180630215956.GA1282@pesky.lan> <20180630223401.GW2430@kib.kiev.ua> <20180701082919.GB3926@pesky.lan> From: Elena Mihailescu Date: Sun, 1 Jul 2018 16:34:20 +0300 Message-ID: Subject: Re: Inspect pages created after a vm_object is marked as copy-on-write To: Mark Johnston Cc: Konstantin Belousov , Mihai Carabas , freebsd-virtualization@freebsd.org, freebsd-amd64@freebsd.org Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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, 01 Jul 2018 13:34:53 -0000 On 1 July 2018 at 11:29, Mark Johnston wrote: > > On Sun, Jul 01, 2018 at 01:34:01AM +0300, Konstantin Belousov wrote: > > On Sat, Jun 30, 2018 at 05:59:56PM -0400, Mark Johnston wrote: > > > On Sat, Jun 30, 2018 at 10:38:21AM +0300, Mihai Carabas wrote: > > > > On Sat, Jun 30, 2018 at 1:52 AM, Mark Johnston wrote: > > > > > On Fri, Jun 29, 2018 at 11:58:31AM +0300, Elena Mihailescu wrote: > > > > >> Is there anything I am doing wrong? Maybe I misunderstood something about > > > > >> the way the virtual memory works in FreeBSD. > > > > > > > > > > I'll note that inspecting and manipulating vm_map_entry and vm_object > > > > > structures in the bhyve code constitutes something of an abstraction > > > > > violation, though it's reasonable to proceed this way while working on a > > > > > prototype of the feature. That is, I think you should keep trying your > > > > > current approach, but just be aware that you are using the copy-on-write > > > > > mechanism in a way that the VM system isn't really expecting. > > > > > > > > > > > > > Can you point out the right approach in our case? > > > > > > I am merely suggesting that once the required VM interactions are fully > > > understood, the mechanism implemented for bhyve should be generalized > > > and lifted into the VM code. It's hard to say what the "right" approach > > > is, since I don't fully understand the proposed algorithm. It sounds > > > like you might be attempting something like: > > > > > > 1. mark the mappings of to-be-migrated objects as NEEDS_COW, so that a > > > subsequent write fault triggers creation of a shadow object > > It is actually MAP_ENTRY_COW | MAP_ENTRY_NEEDS_COPY. > > Indeed. > > > Note that setting an entry to COW changes the behaviour of mprotect(2), > > at least. > > > > > 2. invalidate all physical mappings of pages in the object to be copied, > > > so that subsequent writes trigger a fault > > I do not think this is needed to detect writes after the COW is set. > > It is enough to remove the write permissions. Same as fork() does, > > see the vm_map_copy_entry() code for the handling of MAP_ENTRY_NEEDS_COPY > > case. > > Ah, right. > > > > 3. copy pages from the backing object to the destination > > As I understand, this is done right after the entry is marked > > as COW. > > > > > 4. copy any pages from the shadow object to the desination > > And this is done after all backing data is copied and the process is > > suspended. > > Right, I see. Some reading suggests that in general we might perform > multiple iterations of this procedure before suspending the process and > performing any remaining copies. > For the live migration implementation, we only need this approach to send the guest's physical memory (in my tests, I observed that the guest's memory was represented by a single vm_map_entry for a virtual machine with 512MB of RAM. I found that by inspecting each bhyve instance's vm_map_entry and compared its start and end addresses with the virtual machine's base-address and memory size). What we are trying to implement is to send the initial memory while the virtual machine is running (that's why we need to mark that entry copy-on-write so that we have consistency), then stop the virtual machine execution (freeze the vCPUs) and send only the pages/memory areas that were modified meanwhile (using the copy-on-write mechanism, we could determine which pages were modified). This is "a simplified live migration". A live-migration feature will have multiple rounds to send the virtual memory (round1: send the entire memory, round2: send only the differences between round1 and round2, round3: send only the difference between round2 and round3 and so on, until a certain point when you stop the virtual machine and send to the destination only the differences and guest's CPU state). After the memory migration is completed (and of course, after migrating guest's CPU state), the virtual machine will be destroyed. So, the objects created using the copy-on-write mechanisms will be destroyed. As the number of rounds, it will be choose later, based on different performance tests, but it shouldn't be too big. Elena > > > 5. collapse the backing object into the shadow > > > 6. if the shadow object exists and was non-empty before the collapse, > > > goto 1 > > Are you trying to describe how to undo the COW marking ? Marking an > > entry as COW really changes its semantic, and we do not need the undo > > operation in the base so far. Collapsing the objects would lesser > > the pressure on the system pollution with objects, but it does not > > change back the meaning of mappings, e.g. their behaviour on inheritance > > on fork. > > I was just thinking about how to avoid creating a long chain of objects > if multiple iterations are in fact needed. > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Mon Jul 2 11:21:38 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F5B110166E7 for ; Mon, 2 Jul 2018 11:21:38 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A8BC382CCC for ; Mon, 2 Jul 2018 11:21:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6340210166E3; Mon, 2 Jul 2018 11:21:37 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 50D7A10166E2 for ; Mon, 2 Jul 2018 11:21:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFDE182CC4 for ; Mon, 2 Jul 2018 11:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1E26191C0 for ; Mon, 2 Jul 2018 11:21:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w62BLZ6w086291 for ; Mon, 2 Jul 2018 11:21:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w62BLZqP086290 for virtualization@FreeBSD.org; Mon, 2 Jul 2018 11:21:35 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Date: Mon, 02 Jul 2018 11:21:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: richard@primarysite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 11:21:38 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 --- Comment #9 from Richard Paul --- So, I managed to produce sufficient load to force this to happen on an m5.l= arge instance. I have tried to replicate this on a r4.large instance and have failed to do so so far but I will keep trying. As such it may not be the ENA adapter at all that is causing this issue; re= ad more at http://www.daemonology.net/blog/2017-11-17-FreeBSD-EC2-C5-instances.html --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Mon Jul 2 14:17:35 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1A037102AE71; Mon, 2 Jul 2018 14:17:35 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BA6878AD95; Mon, 2 Jul 2018 14:17:34 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id 80594B7AA; Mon, 2 Jul 2018 14:17:34 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [172.28.128.1] (d5152df30.static.telenet.be [81.82.223.48]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id 7A5645981A; Mon, 2 Jul 2018 16:17:31 +0200 (CEST) From: "Kristof Provost" To: "Jakub Chromy" Cc: freebsd-virtualization@freebsd.org, "FreeBSD PF List" Subject: Re: Possible bug: 11.2-RELEASE guest with vtnet and PF Date: Mon, 02 Jul 2018 16:17:30 +0200 X-Mailer: MailMate (2.0BETAr6113) Message-ID: <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> In-Reply-To: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> References: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 14:17:35 -0000 Hi Jakub, On 30 Jun 2018, at 17:07, Jakub Chromy wrote: > I've just installed a 11.2-RELEASE guest under bhyve (hypervisor is > 11.1-RELEASE)... and I cant use Virtio network interface with PF: > > odine:/boot/kernel# /sbin/pfctl -n -f ~/local/tmp/pf.work > *pfctl: pfi_get_ifaces: Bad file descriptor* > > the file contains the following single line only: > > pass out quick on vtnet0 proto tcp from any to any keep state > I’m pretty sure this is a pf bug rather than an issue with vtnet. Does this still happen if you don’t specify ‘-n’? I suspect this might be related to r333181, but that’s included in CURRENT too, and I’ve not been able to reproduce this on my CURRENT box. I’m updating my stable/11 test VM now, but that’ll take a while. Regards, Kristof From owner-freebsd-virtualization@freebsd.org Mon Jul 2 14:32:37 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04EDB102B66C; Mon, 2 Jul 2018 14:32:37 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel.cgi.cz [178.238.36.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E0D98B95D; Mon, 2 Jul 2018 14:32:34 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (localhost [127.0.0.1]) by hel.cgi.cz (Postfix) with ESMTP id 37F491135D6; Mon, 2 Jul 2018 16:32:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at cgi.cz Received: from hel.cgi.cz ([127.0.0.1]) by hel.cgi.cz (hel.cgi.cz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ReQmRxuFnQSa; Mon, 2 Jul 2018 16:32:25 +0200 (CEST) Received: from mail2.cgi.cz (hermes [172.17.174.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by hel.cgi.cz (Postfix) with ESMTPS id B13A51135A9; Mon, 2 Jul 2018 16:32:24 +0200 (CEST) Received: from [192.168.8.152] (unknown [82.100.31.11]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.cgi.cz (Postfix) with ESMTPSA id 4097B42049; Mon, 2 Jul 2018 16:32:24 +0200 (CEST) Subject: Re: Possible bug: 11.2-RELEASE guest with vtnet and PF To: Kristof Provost References: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> Cc: freebsd-virtualization@freebsd.org, freebsd-pf@freebsd.org From: Jakub Chromy Message-ID: <3e9271ae-d71d-013e-73c6-9a57570b03af@cgi.cz> Date: Mon, 2 Jul 2018 16:32:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> Content-Language: cs Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 14:32:37 -0000 Hello Kristof, I can give you access to that instance if you wish... -- regards Jakub Chromy CGI Systems div. ---------------- CGI CZ s.r.o. sales@cgi.cz 775 144 257 234 697 102 www.cgi.cz Dne 02.07.2018 v 16:17 Kristof Provost napsal(a): > > Hi Jakub, > > On 30 Jun 2018, at 17:07, Jakub Chromy wrote: > > I've just installed a 11.2-RELEASE guest under bhyve (hypervisor > is 11.1-RELEASE)... and I cant use Virtio network interface with PF: > > odine:/boot/kernel# /sbin/pfctl -n -f ~/local/tmp/pf.work > *pfctl: pfi_get_ifaces: Bad file descriptor* > > the file contains the following single line only: > > pass out quick on vtnet0 proto tcp from any to any keep state > > I’m pretty sure this is a pf bug rather than an issue with vtnet. > > Does this still happen if you don’t specify ‘-n’? > > I suspect this might be related to r333181, but that’s included in > CURRENT too, and I’ve not been able to reproduce this on my CURRENT > box. I’m updating my stable/11 test VM now, but that’ll take a while. > > Regards, > Kristof > From owner-freebsd-virtualization@freebsd.org Mon Jul 2 14:33:27 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ABA86102B6EC; Mon, 2 Jul 2018 14:33:27 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel.cgi.cz [178.238.36.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1A0928B9DD; Mon, 2 Jul 2018 14:33:27 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (localhost [127.0.0.1]) by hel.cgi.cz (Postfix) with ESMTP id 0D9B8113A60; Mon, 2 Jul 2018 16:33:26 +0200 (CEST) X-Virus-Scanned: amavisd-new at cgi.cz Received: from hel.cgi.cz ([127.0.0.1]) by hel.cgi.cz (hel.cgi.cz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0fiTomUkr2-j; Mon, 2 Jul 2018 16:33:23 +0200 (CEST) Received: from mail2.cgi.cz (hermes [172.17.174.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by hel.cgi.cz (Postfix) with ESMTPS id 87B9F113A3C; Mon, 2 Jul 2018 16:33:23 +0200 (CEST) Received: from [192.168.8.152] (unknown [82.100.31.11]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.cgi.cz (Postfix) with ESMTPSA id 3D74D42075; Mon, 2 Jul 2018 16:33:23 +0200 (CEST) Subject: Re: Possible bug: 11.2-RELEASE guest with vtnet and PF To: Kristof Provost Cc: freebsd-virtualization@freebsd.org, FreeBSD PF List References: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> From: Jakub Chromy Message-ID: Date: Mon, 2 Jul 2018 16:33:23 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> Content-Language: cs Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 14:33:27 -0000 ... will try without that "-n" parameter also... -- regards Jakub Chromy CGI Systems div. ---------------- CGI CZ s.r.o. sales@cgi.cz 775 144 257 234 697 102 www.cgi.cz Dne 02.07.2018 v 16:17 Kristof Provost napsal(a): > > Hi Jakub, > > On 30 Jun 2018, at 17:07, Jakub Chromy wrote: > > I've just installed a 11.2-RELEASE guest under bhyve (hypervisor > is 11.1-RELEASE)... and I cant use Virtio network interface with PF: > > odine:/boot/kernel# /sbin/pfctl -n -f ~/local/tmp/pf.work > *pfctl: pfi_get_ifaces: Bad file descriptor* > > the file contains the following single line only: > > pass out quick on vtnet0 proto tcp from any to any keep state > > I’m pretty sure this is a pf bug rather than an issue with vtnet. > > Does this still happen if you don’t specify ‘-n’? > > I suspect this might be related to r333181, but that’s included in > CURRENT too, and I’ve not been able to reproduce this on my CURRENT > box. I’m updating my stable/11 test VM now, but that’ll take a while. > > Regards, > Kristof > From owner-freebsd-virtualization@freebsd.org Mon Jul 2 15:55:52 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFD78102DBA1; Mon, 2 Jul 2018 15:55:51 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 962498E9C0; Mon, 2 Jul 2018 15:55:51 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from venus.codepro.be (venus.codepro.be [IPv6:2a01:4f8:162:1127::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.codepro.be", Issuer "Gandi Standard SSL CA 2" (verified OK)) (Authenticated sender: kp) by smtp.freebsd.org (Postfix) with ESMTPSA id 45BA1C1D2; Mon, 2 Jul 2018 15:55:51 +0000 (UTC) (envelope-from kp@FreeBSD.org) Received: from [172.28.128.1] (d5152df30.static.telenet.be [81.82.223.48]) (Authenticated sender: kp) by venus.codepro.be (Postfix) with ESMTPSA id ECC9959AB2; Mon, 2 Jul 2018 17:55:48 +0200 (CEST) From: "Kristof Provost" To: "Jakub Chromy" Cc: freebsd-virtualization@freebsd.org, "FreeBSD PF List" , "Andreas Longwitz" Subject: Re: Possible bug: 11.2-RELEASE guest with vtnet and PF Date: Mon, 02 Jul 2018 17:55:47 +0200 X-Mailer: MailMate (2.0BETAr6113) Message-ID: <65938540-E8D5-4E81-84C7-6AF64D533032@FreeBSD.org> In-Reply-To: <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> References: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 15:55:52 -0000 On 2 Jul 2018, at 16:17, Kristof Provost wrote: > Hi Jakub, > > On 30 Jun 2018, at 17:07, Jakub Chromy wrote: >> I've just installed a 11.2-RELEASE guest under bhyve (hypervisor is >> 11.1-RELEASE)... and I cant use Virtio network interface with PF: >> >> odine:/boot/kernel# /sbin/pfctl -n -f ~/local/tmp/pf.work >> *pfctl: pfi_get_ifaces: Bad file descriptor* >> >> the file contains the following single line only: >> >> pass out quick on vtnet0 proto tcp from any to any keep state >> > I’m pretty sure this is a pf bug rather than an issue with vtnet. > > Does this still happen if you don’t specify ‘-n’? > > I suspect this might be related to r333181, but that’s included in > CURRENT too, and I’ve not been able to reproduce this on my CURRENT > box. I’m updating my stable/11 test VM now, but that’ll take a > while. > Ah, I think I see the problem. I think you don’t have the pf module loaded, which is apparently not treated as a fatal error if ‘-n’ is specified, but the change in r333181 can’t cope with that. We should probably fix that, but it’s not a particularly critical problem. Regards, Kristof From owner-freebsd-virtualization@freebsd.org Mon Jul 2 16:24:35 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 276C3102E780; Mon, 2 Jul 2018 16:24:35 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel.cgi.cz [178.238.36.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AE23B8F8D4; Mon, 2 Jul 2018 16:24:34 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (localhost [127.0.0.1]) by hel.cgi.cz (Postfix) with ESMTP id 058A111389E; Mon, 2 Jul 2018 18:24:33 +0200 (CEST) X-Virus-Scanned: amavisd-new at cgi.cz Received: from hel.cgi.cz ([127.0.0.1]) by hel.cgi.cz (hel.cgi.cz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8VzhcufG7WCK; Mon, 2 Jul 2018 18:24:29 +0200 (CEST) Received: from mail2.cgi.cz (hermes [172.17.174.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by hel.cgi.cz (Postfix) with ESMTPS id AD478113866; Mon, 2 Jul 2018 18:24:29 +0200 (CEST) Received: from [192.168.8.152] (unknown [82.100.31.11]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.cgi.cz (Postfix) with ESMTPSA id 8C32942B2F; Mon, 2 Jul 2018 18:24:29 +0200 (CEST) Subject: Re: Possible bug: 11.2-RELEASE guest with vtnet and PF To: Kristof Provost Cc: freebsd-virtualization@freebsd.org, FreeBSD PF List , Andreas Longwitz References: <848b6851-89fb-b6c8-b412-d5ed897f63d2@cgi.cz> <753B1604-6BFE-48F6-9AA0-38A1C11B6E9B@FreeBSD.org> <65938540-E8D5-4E81-84C7-6AF64D533032@FreeBSD.org> From: Jakub Chromy Message-ID: <117b144b-d558-9319-e073-94e31085e441@cgi.cz> Date: Mon, 2 Jul 2018 18:24:29 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <65938540-E8D5-4E81-84C7-6AF64D533032@FreeBSD.org> Content-Language: cs Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 16:24:35 -0000 ... omg.. sorry. I've checked the r333181 revision, but I'm not as capable in C to understand it completely. So it looks like that in up to 11.1-RELEASE, one can run the /sbin/pfctl -n -f ./config successfully without having the pf module loaded. Now in 11.2, the pfctl without pf module in the kernel complains on something (eg interfaces) and exits with code greater than zero. This is the point where our script (of many years :) got stuck. Thank you. -- regards Jakub Chromy CGI Systems div. ---------------- CGI CZ s.r.o. sales@cgi.cz 775 144 257 234 697 102 www.cgi.cz > Ah, I think I see the problem. I think you don’t have the pf module > loaded, which is apparently not treated as a fatal error if ‘-n’ is > specified, but the change in r333181 can’t cope with that. > > We should probably fix that, but it’s not a particularly critical problem. > > Regards, > Kristof > From owner-freebsd-virtualization@freebsd.org Mon Jul 2 20:24:34 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9FB31103B26D for ; Mon, 2 Jul 2018 20:24:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3809C78D6B for ; Mon, 2 Jul 2018 20:24:34 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id E1F0D103B26C; Mon, 2 Jul 2018 20:24:33 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CDB32103B26B for ; Mon, 2 Jul 2018 20:24:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6369B78D67 for ; Mon, 2 Jul 2018 20:24:33 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 8D7E2DF30 for ; Mon, 2 Jul 2018 20:24:32 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w62KOWe8099029 for ; Mon, 2 Jul 2018 20:24:32 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w62KOWjX099028 for virtualization@FreeBSD.org; Mon, 2 Jul 2018 20:24:32 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Date: Mon, 02 Jul 2018 20:24:31 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cperciva@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Mon, 02 Jul 2018 20:24:34 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 --- Comment #10 from Colin Percival --- Have you been attaching/detaching EBS volumes while your [mc]5 instances are running? AFAIK the nvme driver is completely stable aside from that. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jul 3 07:57:08 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4A06F1026E67 for ; Tue, 3 Jul 2018 07:57:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id D0B1772B4C for ; Tue, 3 Jul 2018 07:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 902F21026E66; Tue, 3 Jul 2018 07:57:07 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7D4AC1026E65 for ; Tue, 3 Jul 2018 07:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A1BA72B4B for ; Tue, 3 Jul 2018 07:57:07 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 64C7113F84 for ; Tue, 3 Jul 2018 07:57:06 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w637v6c1024583 for ; Tue, 3 Jul 2018 07:57:06 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w637v6NH024582 for virtualization@FreeBSD.org; Tue, 3 Jul 2018 07:57:06 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Date: Tue, 03 Jul 2018 07:57:05 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: richard@primarysite.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 03 Jul 2018 07:57:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 --- Comment #11 from Richard Paul --- Hi Colin, I read the article about these drives earlier this year thanks, (p.s. is th= is more usable now in 11.2 or are we still waiting on an ability to hot remove drives), specifically on this test instance, no, I haven't we did do this on the original C5 server when we wanted to replace an IO2 drive which was cos= ting us a fortune, and had to schedule some down time to detach it. But in terms of the instance that I'm testing no, I didn't mess about with = the volumes. However, thinking about this, have you tried testing with a larger number of EBS volumes attached? And tested with load going to most of them at the same time? We have, UFS root vol, 2x mirrored ZFS for DB, 1x ZFS for logs, 1x ZFS local backups vol. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Jul 3 08:11:17 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 536C710281DE for ; Tue, 3 Jul 2018 08:11:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DE34773470 for ; Tue, 3 Jul 2018 08:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 9FB3610281D1; Tue, 3 Jul 2018 08:11:16 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8CF7B10281D0 for ; Tue, 3 Jul 2018 08:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 242D27346A for ; Tue, 3 Jul 2018 08:11:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 57B0E140FC for ; Tue, 3 Jul 2018 08:11:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w638BFkD069381 for ; Tue, 3 Jul 2018 08:11:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w638BFVw069380 for virtualization@FreeBSD.org; Tue, 3 Jul 2018 08:11:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 225791] ena driver causing kernel panics on AWS EC2 Date: Tue, 03 Jul 2018 08:11:15 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.1-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cperciva@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Tue, 03 Jul 2018 08:11:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 --- Comment #12 from Colin Percival --- Sadly nvme hotplug/unplug is still broken in 11.2 -- unfortunately it turned out that some of the people who would have been fixing that were also the people who needed to work on fixing the Spectre/Meltdown/etc. issues so this got pushed off. Right now I'm hoping that we'll have the bugs worked out in time for 12.0. The extent of the testing I've done is a few buildworlds on a single disk -- I've been busy chasing other issues (e.g., the IPI issue which was causing userland data corruption) so I haven't been able to do much testing here. = Any you can do will be much appreciated... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Jul 6 01:42:58 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20B7010272A1 for ; Fri, 6 Jul 2018 01:42:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A7BB681E44 for ; Fri, 6 Jul 2018 01:42:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 66FB810272A0; Fri, 6 Jul 2018 01:42:57 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52F67102729F for ; Fri, 6 Jul 2018 01:42:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DFAB781E41 for ; Fri, 6 Jul 2018 01:42:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 1EEB5166C8 for ; Fri, 6 Jul 2018 01:42:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w661gt0Z085239 for ; Fri, 6 Jul 2018 01:42:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w661gtdn085238 for virtualization@FreeBSD.org; Fri, 6 Jul 2018 01:42:55 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 220453] [Hyper-V] need to update Mellanox ConnectX-3 VF driver to support Live Migration Date: Fri, 06 Jul 2018 01:42:54 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: scorpionmage@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 01:42:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453 scorpionmage@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |scorpionmage@gmail.com --- Comment #18 from scorpionmage@gmail.com --- (In reply to Dexuan Cui from comment #7) Hi - this also happens when booting off the latest snapshots of Current ISO, and it also gave the same panic after the latest compile of Current. I am running on Hyper V. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Jul 6 08:22:58 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6008A102DF30 for ; Fri, 6 Jul 2018 08:22:58 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-b.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB41C7313B for ; Fri, 6 Jul 2018 08:22:57 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-b.userve.net (Postfix) with ESMTPS id EC5F9E33 for ; Fri, 6 Jul 2018 09:22:47 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1530865367; bh=O6UnB7nO40TebhdQmRGje3RMGR3kHWVZCafUHuWkex0=; h=From:To:Subject:Date; b=IZuxuFXBm4qIfwTvV3wQN6xVCmHYTvj2kqEe7WW2/lCgdKQWbGM99Mfw4LZ5qigQ+ cnLHUjLO85BTiURpFxw7ZhFKOpz6s4aXRjgVQxIfEM6jGOcB+D5DBqWmD1taRElXy0 qx4TUYPxvHM3q6Kv4hPRHDbTCKznH7rdZXW/vWzs= Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 6 Jul 2018 09:22:47 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Fri, 6 Jul 2018 09:22:47 +0100 From: Matt Churchyard To: "freebsd-virtualization@freebsd.org" Subject: bhyve server 2016 lockup Thread-Topic: bhyve server 2016 lockup Thread-Index: AdQVAW0nWsWHDtXsSjutX0LIBJ33UA== Date: Fri, 6 Jul 2018 08:22:46 +0000 Message-ID: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 08:22:58 -0000 Hello, I have a server 2016 virtual machine which I only created for testing and d= on't use much. Booting it up recently I've found that it locks up consisten= tly within a few minutes of booting. What can I do to try and figure out wh= at's causing the problem? Host was recently updated to 11.2 # uname -a FreeBSD dev.--- 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 04= :32:14 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENER= IC amd64 Bhyve command is as follows # bhyve -c 2 -m 2G -Huwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.= fd -U 841e8764-75f4-11e8-b2e3-50e549369bc6 -l com1,stdio -s 0,hostbridge -s 31,lpc -s 3:0,ahci-cd,/vm/.config/null.iso -s 4:0,ahci= -hd,/vm/w2016/disk0.img -s 5:0,e1000,tap1,mac=3D58:9c:fc:08:8e:70 -s 6:0,fbuf,tcp=3D0.0.0.0:5900 -s 7:0,xhci,tablet w2016 Top output - PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU COMMA= ND 29796 root 22 20 0 2122M 944M kqread 0 24:59 113.13% bhyve Regards, Matt Churchyard From owner-freebsd-virtualization@freebsd.org Fri Jul 6 10:06:57 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B91AA1038525 for ; Fri, 6 Jul 2018 10:06:57 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57548775A3 for ; Fri, 6 Jul 2018 10:06:57 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-oi0-x242.google.com with SMTP id w126-v6so22444076oie.7 for ; Fri, 06 Jul 2018 03:06:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fisc/j9TuKkyLTOUEypSnzBe7L8+M5q5hKVcTIY8/O0=; b=jbIPXQYst5CGgVWOr1uSXHbli0TqupooqZ+pKEp4+wCi+57o6FiAtmP4atozKC63dR MhstiXBFSDI2YRKTNJwdHn9O46TDMYQFH60qdd6hDeJ53UvFRaDsFoFXnUKHxZlGzVR+ ktsme8+m7GBqb9K60dkhLvK4EJKSCY16v/EenW7JxB5MxLluY+cUTlZavDKvuXoDWKxh 2Dqm5G22Zx3ABaIJS95lzp21ZwVODZ8yBYkZrnZqYkbqtBEZHstfkZ/oF17ZK/C+daaG afUTbyywMvJAuBwXp7Wlu1/bd8Z9kvcRdIjeNERQ7nOggU/A9cagO4mofOi/prLIsfxP kltw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fisc/j9TuKkyLTOUEypSnzBe7L8+M5q5hKVcTIY8/O0=; b=oVmgNUAKyv0OU7kN2pgmJYAoTk1sfq2nOiZRh+xh8CzDNWUrjdm6DvfIOjY+FdRoWh ij55bnl+Iwd1u2kHsGei3p9ADZjxVsHxKKDg6+YzwvS5LkphtNTMo43OuXrGtXhKpcXa fqn0KNu2zGCXtmJCE12aflX3mJk/S+pRaju+Z2XUgtHcKQMXNSzqgGxx+JlRhF26XHTS EGga4dXlYc2+k/ysE+XmPikBR27P2Cpqfji9J3F9sjBM8uBisVqmZvJUvV9AeaXeUq6j Q3N7ID2dejEajgCJ+W402+MiDugnsoLb6uQEXByFPQdBvF2QttSb3otTGAHXF5CeibKY S5Xg== X-Gm-Message-State: APt69E0NbdnZjOFgCxSJu03asVRZHOmtYPo6KrCLpIs3IQnkpLkqXyH6 CbLMzAP1BmY0DRUJSpf745O8PjJZc3mGoArXtV5vGQ== X-Google-Smtp-Source: AAOMgpfiOXtdOucwqrqR/chAtL0p4yBbwHgNF1oTb3WQP3DxD2Wv/xo3bgct0UZE4ry+1o5St/9l3oX0Z1Pzgrp4qzs= X-Received: by 2002:aca:5545:: with SMTP id j66-v6mr11473984oib.291.1530871616560; Fri, 06 Jul 2018 03:06:56 -0700 (PDT) MIME-Version: 1.0 References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> In-Reply-To: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> From: Jason Tubnor Date: Fri, 6 Jul 2018 20:06:43 +1000 Message-ID: Subject: Re: bhyve server 2016 lockup To: Matt Churchyard Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 10:06:59 -0000 Hi sorry on mobile so replying top. I've got some 2016 guests running close to 12 months uptime. Just some ideas below: RAM allocation a little low for 2016 so bump that a little. I use zvol for ahci storage with 4k blocks but have run 8k blocks as well. MSSQL doesn't like anything more than 4k. Swap out the nic e1000 for virtio. You'll get better throughput without emulation. Drivers are available in places but I can provide you the iso version that we use in production. I think this is what is causing you issues. Cheers. Jason. On Fri., 6 Jul. 2018, 18:22 Matt Churchyard, wrote: > Hello, > > I have a server 2016 virtual machine which I only created for testing and > don't use much. Booting it up recently I've found that it locks up > consistently within a few minutes of booting. What can I do to try and > figure out what's causing the problem? > > Host was recently updated to 11.2 > # uname -a > FreeBSD dev.--- 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 > 04:32:14 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC > amd64 > > Bhyve command is as follows > # bhyve -c 2 -m 2G -Huwl > bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -U 841e8764-75f4-11e8-b2e3-50e549369bc6 -l com1,stdio > -s 0,hostbridge -s 31,lpc -s 3:0,ahci-cd,/vm/.config/null.iso -s > 4:0,ahci-hd,/vm/w2016/disk0.img -s 5:0,e1000,tap1,mac=58:9c:fc:08:8e:70 > -s 6:0,fbuf,tcp=0.0.0.0:5900 -s 7:0,xhci,tablet w2016 > > Top output - > PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU > COMMAND > 29796 root 22 20 0 2122M 944M kqread 0 24:59 113.13% bhyve > > Regards, > Matt Churchyard > > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to " > freebsd-virtualization-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@freebsd.org Fri Jul 6 10:51:22 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 02A91103D158 for ; Fri, 6 Jul 2018 10:51:22 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD3D798C4 for ; Fri, 6 Jul 2018 10:51:21 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 70DFC21F86 for ; Fri, 6 Jul 2018 06:51:20 -0400 (EDT) Received: from web6 ([10.202.2.216]) by compute7.internal (MEProxy); Fri, 06 Jul 2018 06:51:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=VpBA9Cnp0NQ4v4rEn+Jdy52FwtCGW O29NNZVPPyQAb0=; b=KZ8/viCtxTjuNyd8fH+0N+zRUn4FCrYDohRgbtEEl/Jxv V06D233dMMnI9fOnNf74Ez/UgwfyAlbytWkbcCEiObETzfGaSj31AScpJeOf4fT5 ENCdV5gK7shaMyJZeb3/6UmEbHig0az+KyEyy5xR3G48rUsAqE5J4OTyIF8w+a7d hvQ5oj8IoRVdjiGdyL3lRmeopiQU+jCZp7Mzn6Cz89gfh4pJuIVT/qzKVYwmbPbJ 0EuDOqE07GAby55e0FhheZavlK1Vwc2cizm62BCaUvWhROa5187YAst3tfqRwNHH gK0vI7aBOR9itwo4qY4biqDfqLoI4wXux9AqGrSug== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=VpBA9C np0NQ4v4rEn+Jdy52FwtCGWO29NNZVPPyQAb0=; b=gsKCfcVwFm1sbpH++8zUWJ 5V8h4VzvYUoUsMj/bLaqo4qnqb+qrT8ahZllnuFq1xKleSwxZL9aLP+a/tZ47yz5 RdkH5KP6Z9e4zFvlbbaXRZF31IQOf/Kx7//T8HCTGFjmkafuD7MNxN5mNwRM4Xaz g8zAPzQiYw5qeXjB5YYnLBHzWu9SHi+9AQRg8nl1tba1o4HT+fLSi8azrC6Tg4C8 KGMdqnU3eb7M1dq35yqrr0V5C1ixAcunOm9kGOxJ0qSslU38VLJ3CnlrRzccGW3W BkgLQEe1idZZKl/VnoRmoaCiY2AiElpGojYHKQOHrDrZ+yBUkcqLx0uuhzaO+9ag == X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id DF80C410D; Fri, 6 Jul 2018 06:51:19 -0400 (EDT) Message-Id: <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> From: Dave Cottlehuber To: freebsd-virtualization@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-0d8ea36c References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> Subject: Re: bhyve server 2016 lockup In-Reply-To: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> Date: Fri, 06 Jul 2018 12:51:19 +0200 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 10:51:22 -0000 On Fri, 6 Jul 2018, at 10:22, Matt Churchyard wrote: > Hello, >=20 > I have a server 2016 virtual machine which I only created for testing=20 > and don't use much. Booting it up recently I've found that it locks up=20 > consistently within a few minutes of booting. What can I do to try and=20 > figure out what's causing the problem? >=20 > Host was recently updated to 11.2 > # uname -a > FreeBSD dev.--- 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22= =20 > 04:32:14 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/ > GENERIC amd64 >=20 > Bhyve command is as follows > # bhyve -c 2 -m 2G -Huwl bootrom,/usr/local/share/uefi-firmware/ > BHYVE_UEFI.fd > -U 841e8764-75f4-11e8-b2e3-50e549369bc6 -l com1,stdio > -s 0,hostbridge -s 31,lpc -s 3:0,ahci-cd,/vm/.config/null.iso -s=20 > 4:0,ahci-hd,/vm/w2016/disk0.img -s 5:0,e1000,tap1,mac=3D58:9c:fc:08:8e:70 > -s 6:0,fbuf,tcp=3D0.0.0.0:5900 -s 7:0,xhci,tablet w2016 Hi Matt, try using virtio for nic & storage to start with. I've used specifically th= ese drivers https://fedorapeople.org/groups/virt/virtio-win/direct-download= s/archive-virtio/virtio-win-0.1.96/virtio-win-0.1.96.iso and had trouble wi= th both later and earlier drivers, YMMV, and I sadly forget where I got thi= s advice. Also, it=E2=80=99s possible to install virtio drivers directly from the CD = without pointy-clicky stupidness. Just add the CD to your bhyve command, in= a later "PCI slot" than the existing =E2=80=9Chard disk=E2=80=9D, as the l= owest numbered slot is what=E2=80=99s used to boot from AFAICT.=20 - open an elevated command prompt - run for /d %i in (d:\*) do @pnputil -a %i\w7\amd64\*.inf (you may need a = different driver than w7 here) - some of those will fail but just carry on - reboot FTW more notes here on my bhyve setup https://hackmd.io/s/rJvJuE-CW# A+ Dave From owner-freebsd-virtualization@freebsd.org Fri Jul 6 11:56:25 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 012511042B10 for ; Fri, 6 Jul 2018 11:56:25 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel.cgi.cz [178.238.36.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6984C7C266 for ; Fri, 6 Jul 2018 11:56:23 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (localhost [127.0.0.1]) by hel.cgi.cz (Postfix) with ESMTP id 7800211728D for ; Fri, 6 Jul 2018 13:56:16 +0200 (CEST) X-Virus-Scanned: amavisd-new at cgi.cz Received: from hel.cgi.cz ([127.0.0.1]) by hel.cgi.cz (hel.cgi.cz [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WIv4JY64Qkt6 for ; Fri, 6 Jul 2018 13:56:13 +0200 (CEST) Received: from mail2.cgi.cz (hermes [172.17.174.1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by hel.cgi.cz (Postfix) with ESMTPS id AADE3117265 for ; Fri, 6 Jul 2018 13:56:12 +0200 (CEST) Received: from [192.168.8.106] (unknown [82.100.31.11]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail2.cgi.cz (Postfix) with ESMTPSA id 9EB70460F3 for ; Fri, 6 Jul 2018 13:56:12 +0200 (CEST) Subject: Re: bhyve server 2016 lockup To: freebsd-virtualization@freebsd.org References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> From: Jakub Chromy Message-ID: <1dbba8ac-eca4-bb09-9d3b-ec26ed1452e5@cgi.cz> Date: Fri, 6 Jul 2018 13:56:14 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 MIME-Version: 1.0 In-Reply-To: <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 11:56:25 -0000 Dave, you got working Windows guest with virtio-blk? I thought it was still unstable. I've tested virtio storage (on bhyve) + virtio storage drivers on several windows guest  ~ 2 months ago and they were crashing all the time. So I use ahci-hd with every windows guest we run (from 7 to Win Server 2012). -- regards Jakub Chromy CGI Systems div. ---------------- CGI CZ s.r.o. sales@cgi.cz 775 144 257 234 697 102 www.cgi.cz On 6.7.2018 12:51, Dave Cottlehuber wrote: > On Fri, 6 Jul 2018, at 10:22, Matt Churchyard wrote: >> Hello, >> >> I have a server 2016 virtual machine which I only created for testing >> and don't use much. Booting it up recently I've found that it locks up >> consistently within a few minutes of booting. What can I do to try and >> figure out what's causing the problem? >> >> Host was recently updated to 11.2 >> # uname -a >> FreeBSD dev.--- 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 >> 04:32:14 UTC 2018 root@releng2.nyi.freebsd.org:/usr/obj/usr/src/sys/ >> GENERIC amd64 >> >> Bhyve command is as follows >> # bhyve -c 2 -m 2G -Huwl bootrom,/usr/local/share/uefi-firmware/ >> BHYVE_UEFI.fd >> -U 841e8764-75f4-11e8-b2e3-50e549369bc6 -l com1,stdio >> -s 0,hostbridge -s 31,lpc -s 3:0,ahci-cd,/vm/.config/null.iso -s >> 4:0,ahci-hd,/vm/w2016/disk0.img -s 5:0,e1000,tap1,mac=58:9c:fc:08:8e:70 >> -s 6:0,fbuf,tcp=0.0.0.0:5900 -s 7:0,xhci,tablet w2016 > Hi Matt, > > try using virtio for nic & storage to start with. I've used specifically these drivers https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.96/virtio-win-0.1.96.iso and had trouble with both later and earlier drivers, YMMV, and I sadly forget where I got this advice. > > Also, it’s possible to install virtio drivers directly from the CD without pointy-clicky stupidness. Just add the CD to your bhyve command, in a later "PCI slot" than the existing “hard disk”, as the lowest numbered slot is what’s used to boot from AFAICT. > > - open an elevated command prompt > - run for /d %i in (d:\*) do @pnputil -a %i\w7\amd64\*.inf (you may need a different driver than w7 here) > - some of those will fail but just carry on > - reboot FTW > > more notes here on my bhyve setup https://hackmd.io/s/rJvJuE-CW# > > A+ > Dave > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@freebsd.org Fri Jul 6 12:05:04 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CC7FE1043FC8 for ; Fri, 6 Jul 2018 12:05:04 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59D1C7CB13 for ; Fri, 6 Jul 2018 12:05:04 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id 0D440943; Fri, 6 Jul 2018 13:05:02 +0100 (BST) Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 6 Jul 2018 13:05:01 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Fri, 6 Jul 2018 13:05:01 +0100 From: Matt Churchyard To: Jakub Chromy , "freebsd-virtualization@freebsd.org" Subject: RE: bhyve server 2016 lockup Thread-Topic: bhyve server 2016 lockup Thread-Index: AdQVAW0nWsWHDtXsSjutX0LIBJ33UAADXZGAAAJEZwAAAiXqkA== Date: Fri, 6 Jul 2018 12:05:01 +0000 Message-ID: References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> <1dbba8ac-eca4-bb09-9d3b-ec26ed1452e5@cgi.cz> In-Reply-To: <1dbba8ac-eca4-bb09-9d3b-ec26ed1452e5@cgi.cz> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 12:05:05 -0000 VGhhbmtzIGZvciB0aGUgcmVwbGllcyBndXlzLiBJJ3ZlIGluY3JlYXNlZCBtZW1vcnkgYW5kIHN3 aXRjaGVkIHRvIHZpcnRpby1uZXQuIEJlZW4gcnVubmluZyBmb3IgYW4gaG91ciBvciB0d28gc28g ZmFyLiBXaW5kb3dzIGp1c3QgY29tcGxhaW5zIGFib3V0IHRoZSBib290IGRldmljZSBpZiBJIHRy eSB0byBtb3ZlIHRvIHZpcnRpby1ibGsuDQpJIG1pZ2h0IHNldCB1cCBhbm90aGVyIHRlc3QgdXNp bmcgZGlmZmVyZW50IHNldHRpbmdzIGR1cmluZyBpbnN0YWxsYXRpb24gYW5kIHNlZSBob3cgdGhh dCBnb2VzLg0KDQpPbmx5IHJlYWxseSBwbGF5ZWQgYWJvdXQgd2l0aCBiaHl2ZSBzbyBmYXIgYnV0 IHN0YXJ0aW5nIHRvIGNvbnNpZGVyIHVzaW5nIGZvciBwcm9kdWN0aW9uIG1hY2hpbmVzLCBzbyBh bnkgaGFyZCBsb2NrdXAgaXMgYSBiaXQgb2YgYSB3b3JyeS4NCg0KUmVnYXJkcywNCk1hdHQNCg0K PiBEYXZlLA0KDQo+IHlvdSBnb3Qgd29ya2luZyBXaW5kb3dzIGd1ZXN0IHdpdGggdmlydGlvLWJs az8NCg0KPiBJIHRob3VnaHQgaXQgd2FzIHN0aWxsIHVuc3RhYmxlLiBJJ3ZlIHRlc3RlZCB2aXJ0 aW8gc3RvcmFnZSAob24gYmh5dmUpICsgdmlydGlvIHN0b3JhZ2UgZHJpdmVycyBvbiBzZXZlcmFs IHdpbmRvd3MgZ3Vlc3TCoCB+IDIgbW9udGhzIGFnbyBhbmQgdGhleSB3ZXJlIGNyYXNoaW5nIGFs bCB0aGUgdGltZS4NCg0KPiBTbyBJIHVzZSBhaGNpLWhkIHdpdGggZXZlcnkgd2luZG93cyBndWVz dCB3ZSBydW4gKGZyb20gNyB0byBXaW4gU2VydmVyIDIwMTIpLg0KDQo+IC0tIA0KDQoNCiAgICBy ZWdhcmRzDQoNCg0KSmFrdWIgQ2hyb215DQoNCg0KQ0dJIFN5c3RlbXMgZGl2Lg0KLS0tLS0tLS0t LS0tLS0tLQ0KQ0dJIENaIHMuci5vLg0Kc2FsZXNAY2dpLmN6DQo3NzUgMTQ0IDI1Nw0KMjM0IDY5 NyAxMDINCnd3dy5jZ2kuY3oNCg0KT24gNi43LjIwMTggMTI6NTEsIERhdmUgQ290dGxlaHViZXIg d3JvdGU6DQo+IE9uIEZyaSwgNiBKdWwgMjAxOCwgYXQgMTA6MjIsIE1hdHQgQ2h1cmNoeWFyZCB3 cm90ZToNCj4+IEhlbGxvLA0KPj4NCj4+IEkgaGF2ZSBhIHNlcnZlciAyMDE2IHZpcnR1YWwgbWFj aGluZSB3aGljaCBJIG9ubHkgY3JlYXRlZCBmb3IgdGVzdGluZyANCj4+IGFuZCBkb24ndCB1c2Ug bXVjaC4gQm9vdGluZyBpdCB1cCByZWNlbnRseSBJJ3ZlIGZvdW5kIHRoYXQgaXQgbG9ja3MgDQo+ PiB1cCBjb25zaXN0ZW50bHkgd2l0aGluIGEgZmV3IG1pbnV0ZXMgb2YgYm9vdGluZy4gV2hhdCBj YW4gSSBkbyB0byB0cnkgDQo+PiBhbmQgZmlndXJlIG91dCB3aGF0J3MgY2F1c2luZyB0aGUgcHJv YmxlbT8NCj4+DQo+PiBIb3N0IHdhcyByZWNlbnRseSB1cGRhdGVkIHRvIDExLjINCj4+ICMgdW5h bWUgLWENCj4+IEZyZWVCU0QgZGV2Li0tLSAxMS4yLVJFTEVBU0UgRnJlZUJTRCAxMS4yLVJFTEVB U0UgIzAgcjMzNTUxMDogRnJpIEp1biAyMg0KPj4gMDQ6MzI6MTQgVVRDIDIwMTggICAgIHJvb3RA cmVsZW5nMi5ueWkuZnJlZWJzZC5vcmc6L3Vzci9vYmovdXNyL3NyYy9zeXMvDQo+PiBHRU5FUklD ICBhbWQ2NA0KPj4NCj4+IEJoeXZlIGNvbW1hbmQgaXMgYXMgZm9sbG93cw0KPj4gIyBiaHl2ZSAt YyAyIC1tIDJHIC1IdXdsIGJvb3Ryb20sL3Vzci9sb2NhbC9zaGFyZS91ZWZpLWZpcm13YXJlLw0K Pj4gQkhZVkVfVUVGSS5mZA0KPj4gICAgLVUgODQxZTg3NjQtNzVmNC0xMWU4LWIyZTMtNTBlNTQ5 MzY5YmM2IC1sIGNvbTEsc3RkaW8NCj4+ICAgIC1zIDAsaG9zdGJyaWRnZSAtcyAzMSxscGMgLXMg MzowLGFoY2ktY2QsL3ZtLy5jb25maWcvbnVsbC5pc28gLXMgDQo+PiA0OjAsYWhjaS1oZCwvdm0v dzIwMTYvZGlzazAuaW1nIC1zIDU6MCxlMTAwMCx0YXAxLG1hYz01ODo5YzpmYzowODo4ZTo3MA0K Pj4gICAgLXMgNjowLGZidWYsdGNwPTAuMC4wLjA6NTkwMCAtcyA3OjAseGhjaSx0YWJsZXQgdzIw MTYNCj4gSGkgTWF0dCwNCj4NCj4gdHJ5IHVzaW5nIHZpcnRpbyBmb3IgbmljICYgc3RvcmFnZSB0 byBzdGFydCB3aXRoLiBJJ3ZlIHVzZWQgc3BlY2lmaWNhbGx5IHRoZXNlIGRyaXZlcnMgaHR0cHM6 Ly9mZWRvcmFwZW9wbGUub3JnL2dyb3Vwcy92aXJ0L3ZpcnRpby13aW4vZGlyZWN0LWRvd25sb2Fk cy9hcmNoaXZlLXZpcnRpby92aXJ0aW8td2luLTAuMS45Ni92aXJ0aW8td2luLTAuMS45Ni5pc28g YW5kIGhhZCB0cm91YmxlIHdpdGggYm90aCBsYXRlciBhbmQgZWFybGllciBkcml2ZXJzLCBZTU1W LCBhbmQgSSBzYWRseSBmb3JnZXQgd2hlcmUgSSBnb3QgdGhpcyBhZHZpY2UuDQo+DQo+IEFsc28s IGl04oCZcyBwb3NzaWJsZSB0byBpbnN0YWxsIHZpcnRpbyBkcml2ZXJzIGRpcmVjdGx5IGZyb20g dGhlIENEIHdpdGhvdXQgcG9pbnR5LWNsaWNreSBzdHVwaWRuZXNzLiBKdXN0IGFkZCB0aGUgQ0Qg dG8geW91ciBiaHl2ZSBjb21tYW5kLCBpbiBhIGxhdGVyICJQQ0kgc2xvdCIgdGhhbiB0aGUgZXhp c3Rpbmcg4oCcaGFyZCBkaXNr4oCdLCBhcyB0aGUgbG93ZXN0IG51bWJlcmVkIHNsb3QgaXMgd2hh dOKAmXMgdXNlZCB0byBib290IGZyb20gQUZBSUNULg0KPg0KPiAtIG9wZW4gYW4gZWxldmF0ZWQg Y29tbWFuZCBwcm9tcHQNCj4gLSBydW4gZm9yIC9kICVpIGluIChkOlwqKSBkbyBAcG5wdXRpbCAt YSAlaVx3N1xhbWQ2NFwqLmluZiAoeW91IG1heSANCj4gbmVlZCBhIGRpZmZlcmVudCBkcml2ZXIg dGhhbiB3NyBoZXJlKQ0KPiAtIHNvbWUgb2YgdGhvc2Ugd2lsbCBmYWlsIGJ1dCBqdXN0IGNhcnJ5 IG9uDQo+IC0gcmVib290IEZUVw0KPg0KPiBtb3JlIG5vdGVzIGhlcmUgb24gbXkgYmh5dmUgc2V0 dXAgaHR0cHM6Ly9oYWNrbWQuaW8vcy9ySnZKdUUtQ1cjDQo+DQo+IEErDQo+IERhdmUNCj4gX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gZnJlZWJzZC12 aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZyBtYWlsaW5nIGxpc3QgDQo+IGh0dHBzOi8vbGlzdHMu ZnJlZWJzZC5vcmcvbWFpbG1hbi9saXN0aW5mby9mcmVlYnNkLXZpcnR1YWxpemF0aW9uDQo+IFRv IHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVlYnNkLXZpcnR1YWxpemF0aW9uLXVu c3Vic2NyaWJlQGZyZWVic2Qub3JnIg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fXw0KZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZyBtYWls aW5nIGxpc3QgaHR0cHM6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVi c2QtdmlydHVhbGl6YXRpb24NClRvIHVuc3Vic2NyaWJlLCBzZW5kIGFueSBtYWlsIHRvICJmcmVl YnNkLXZpcnR1YWxpemF0aW9uLXVuc3Vic2NyaWJlQGZyZWVic2Qub3JnIg0K From owner-freebsd-virtualization@freebsd.org Fri Jul 6 12:59:43 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0CA1B1024704 for ; Fri, 6 Jul 2018 12:59:43 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from smtp-a.userve.net (smtp-outbound.userve.net [217.196.1.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.userve.net", Issuer "Thawte RSA CA 2018" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B74B7F946 for ; Fri, 6 Jul 2018 12:59:42 +0000 (UTC) (envelope-from matt.churchyard@userve.net) Received: from owa.usd-group.com (owa.usd-group.com [217.196.1.2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp-a.userve.net (Postfix) with ESMTPS id ECA56B33; Fri, 6 Jul 2018 13:59:40 +0100 (BST) Received: from SERVER.ad.usd-group.com (192.168.0.1) by SERVER.ad.usd-group.com (192.168.0.1) with Microsoft SMTP Server (TLS) id 15.0.847.32; Fri, 6 Jul 2018 13:59:40 +0100 Received: from SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9]) by SERVER.ad.usd-group.com ([fe80::b19d:892a:6fc7:1c9%12]) with mapi id 15.00.0847.030; Fri, 6 Jul 2018 13:59:40 +0100 From: Matt Churchyard To: Jakub Chromy CC: "freebsd-virtualization@freebsd.org" Subject: RE: bhyve server 2016 lockup Thread-Topic: bhyve server 2016 lockup Thread-Index: AdQVAW0nWsWHDtXsSjutX0LIBJ33UAADXZGAAAJEZwAAAiXqkP//9YUA///psUA= Date: Fri, 6 Jul 2018 12:59:39 +0000 Message-ID: <5845ecd4c7964964ab8a718ba7b686eb@SERVER.ad.usd-group.com> References: <1595599bd62b43b2842b9a652c6d1773@SERVER.ad.usd-group.com> <1530874279.512578.1431934576.27AF56F1@webmail.messagingengine.com> <1dbba8ac-eca4-bb09-9d3b-ec26ed1452e5@cgi.cz> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.0.10] MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 12:59:43 -0000 Tm9ybWFsbHkgSSB3b3VsZCBiZSB1c2luZyB2aXJ0aW8tbmV0LCBhbmQgYWR2aXNlIGFzIG11Y2gg d2l0aCB2bS1iaHl2ZS4NCkl0IGlzIHNvbWV0aW1lcyB1c2VmdWwgdG8gdXNlIGUxMDAwIGJyaWVm bHkgaW4gb3JkZXIgdG8gaGF2ZSBJbnRlcm5ldCBhY2Nlc3MgdG8gZG93bmxvYWQgZHJpdmVyc+KA pg0KVGhpcyBtYWNoaW5lIGlzIGp1c3QgZm9yIHRlc3RpbmcgYW5kIEkgaGFkbuKAmXQgYm90aGVy ZWQgZ29pbmcgdGhyb3VnaCB0aGUgcHJvY2VzcyBvZiBmaW5kaW5nIGFuZCBpbnN0YWxsaW5nIHZp cnRpbyBkcml2ZXJzLCBtaW5pbWFsIGFzIHRoYXQgaXMuDQoNCk5vdCB0aGF0IEkgdGhpbmsgbXkg bG9ja3VwcyB3ZXJlIG5pYyByZWxhdGVkLCBidXQgc29tZSB1c2VycyBtYXkgdXNlIGUxMDAwIGp1 c3QgZm9yIHNpbXBsaWNpdHkgYW5kIGlkZWFsbHkgaXQgc2hvdWxkIGJlIGEgc3RhYmxlIGNob2lj ZSwgYWxiZWl0IHdpdGggbG93ZXIgcGVyZm9ybWFuY2UgYW5kIG1vcmUgb3ZlcmhlYWQgdGhhbiB2 aXJ0aW8uDQoNClRoYW5rcyBmb3IgdGhlIGFkZGl0aW9uYWwgdm90ZSByZWdhcmRpbmcgc3RhYmls aXR5LiBJIHRoaW5rIG15IGlzc3VlIHdhcyBtb3N0IGxpa2VseSBsb3cgbWVtb3J5IHJlbGF0ZWQu IEluIHByb2R1Y3Rpb24gSSBwcm9iYWJseSB3b3VsZG7igJl0IHdhbnQgdG8gZ2l2ZSBhbnkgbGVz cyB0aGFuIDE2LTIwR0IgdG8gV1MyMDE2LCBtb3JlIGRlcGVuZGluZyBvbiBzZXJ2aWNlcyBpbnN0 YWxsZWQuDQoNCk1hdHQNCg0KPkkgdXNlIHZpcnRpby1uZXQgZm9yIGV2ZXJ5dGhpbmcuLi4gdGhl IG9ubHkgbW9tZW50IEkgbmVlZGVkIGFuIGVtMTAwMCB3YXMgd2l0aCA4LjItUkVMRUFTRSBndWVz dCA6KQ0KDQo+dGhlIGRyaXZlcnMgc2hvdWxkIGJlIGluIE5ldEtWTSBkaXJlY3Rvcnkgb3Igc29t ZXRoaW5nIGxpa2UgdGhhdC4NCg0KPmFkLiBwcm9kdWN0aW9uLi4uIGhhdmUgbm8gdHJvdWJsZSB3 aXRoIHN0YWJpbGl0eSBzbyBmYXIuLi4NCg0KLS0NCg0KDQoNCg0KDQogICByZWdhcmRzDQoNCg0K DQoNCg0KSmFrdWIgQ2hyb215DQoNCg0KDQoNCg0KQ0dJIFN5c3RlbXMgZGl2Lg0KDQotLS0tLS0t LS0tLS0tLS0tDQoNCkNHSSBDWiBzLnIuby4NCg0Kc2FsZXNAY2dpLmN6PG1haWx0bzpzYWxlc0Bj Z2kuY3o+DQoNCjc3NSAxNDQgMjU3DQoNCjIzNCA2OTcgMTAyDQoNCnd3dy5jZ2kuY3o8aHR0cDov L3d3dy5jZ2kuY3o+DQpPbiA2LjcuMjAxOCAxNDowNSwgTWF0dCBDaHVyY2h5YXJkIHdyb3RlOg0K DQpUaGFua3MgZm9yIHRoZSByZXBsaWVzIGd1eXMuIEkndmUgaW5jcmVhc2VkIG1lbW9yeSBhbmQg c3dpdGNoZWQgdG8gdmlydGlvLW5ldC4gQmVlbiBydW5uaW5nIGZvciBhbiBob3VyIG9yIHR3byBz byBmYXIuIFdpbmRvd3MganVzdCBjb21wbGFpbnMgYWJvdXQgdGhlIGJvb3QgZGV2aWNlIGlmIEkg dHJ5IHRvIG1vdmUgdG8gdmlydGlvLWJsay4NCg0KSSBtaWdodCBzZXQgdXAgYW5vdGhlciB0ZXN0 IHVzaW5nIGRpZmZlcmVudCBzZXR0aW5ncyBkdXJpbmcgaW5zdGFsbGF0aW9uIGFuZCBzZWUgaG93 IHRoYXQgZ29lcy4NCg0KDQoNCk9ubHkgcmVhbGx5IHBsYXllZCBhYm91dCB3aXRoIGJoeXZlIHNv IGZhciBidXQgc3RhcnRpbmcgdG8gY29uc2lkZXIgdXNpbmcgZm9yIHByb2R1Y3Rpb24gbWFjaGlu ZXMsIHNvIGFueSBoYXJkIGxvY2t1cCBpcyBhIGJpdCBvZiBhIHdvcnJ5Lg0KDQoNCg0KUmVnYXJk cywNCg0KTWF0dA0KDQoNCg0KRGF2ZSwNCg0KDQoNCnlvdSBnb3Qgd29ya2luZyBXaW5kb3dzIGd1 ZXN0IHdpdGggdmlydGlvLWJsaz8NCg0KDQoNCkkgdGhvdWdodCBpdCB3YXMgc3RpbGwgdW5zdGFi bGUuIEkndmUgdGVzdGVkIHZpcnRpbyBzdG9yYWdlIChvbiBiaHl2ZSkgKyB2aXJ0aW8gc3RvcmFn ZSBkcml2ZXJzIG9uIHNldmVyYWwgd2luZG93cyBndWVzdCAgfiAyIG1vbnRocyBhZ28gYW5kIHRo ZXkgd2VyZSBjcmFzaGluZyBhbGwgdGhlIHRpbWUuDQoNCg0KDQpTbyBJIHVzZSBhaGNpLWhkIHdp dGggZXZlcnkgd2luZG93cyBndWVzdCB3ZSBydW4gKGZyb20gNyB0byBXaW4gU2VydmVyIDIwMTIp Lg0KDQoNCg0KLS0NCg0KDQoNCg0KDQogICAgcmVnYXJkcw0KDQoNCg0KDQoNCkpha3ViIENocm9t eQ0KDQoNCg0KDQoNCkNHSSBTeXN0ZW1zIGRpdi4NCg0KLS0tLS0tLS0tLS0tLS0tLQ0KDQpDR0kg Q1ogcy5yLm8uDQoNCnNhbGVzQGNnaS5jejxtYWlsdG86c2FsZXNAY2dpLmN6Pg0KDQo3NzUgMTQ0 IDI1Nw0KDQoyMzQgNjk3IDEwMg0KDQp3d3cuY2dpLmN6PGh0dHA6Ly93d3cuY2dpLmN6Pg0KDQoN Cg0KT24gNi43LjIwMTggMTI6NTEsIERhdmUgQ290dGxlaHViZXIgd3JvdGU6DQoNCk9uIEZyaSwg NiBKdWwgMjAxOCwgYXQgMTA6MjIsIE1hdHQgQ2h1cmNoeWFyZCB3cm90ZToNCg0KSGVsbG8sDQoN Cg0KDQpJIGhhdmUgYSBzZXJ2ZXIgMjAxNiB2aXJ0dWFsIG1hY2hpbmUgd2hpY2ggSSBvbmx5IGNy ZWF0ZWQgZm9yIHRlc3RpbmcNCg0KYW5kIGRvbid0IHVzZSBtdWNoLiBCb290aW5nIGl0IHVwIHJl Y2VudGx5IEkndmUgZm91bmQgdGhhdCBpdCBsb2Nrcw0KDQp1cCBjb25zaXN0ZW50bHkgd2l0aGlu IGEgZmV3IG1pbnV0ZXMgb2YgYm9vdGluZy4gV2hhdCBjYW4gSSBkbyB0byB0cnkNCg0KYW5kIGZp Z3VyZSBvdXQgd2hhdCdzIGNhdXNpbmcgdGhlIHByb2JsZW0/DQoNCg0KDQpIb3N0IHdhcyByZWNl bnRseSB1cGRhdGVkIHRvIDExLjINCg0KIyB1bmFtZSAtYQ0KDQpGcmVlQlNEIGRldi4tLS0gMTEu Mi1SRUxFQVNFIEZyZWVCU0QgMTEuMi1SRUxFQVNFICMwIHIzMzU1MTA6IEZyaSBKdW4gMjINCg0K MDQ6MzI6MTQgVVRDIDIwMTggICAgIHJvb3RAcmVsZW5nMi5ueWkuZnJlZWJzZC5vcmc6L3Vzci9v YmovdXNyL3NyYy9zeXMvPG1haWx0bzpyb290QHJlbGVuZzIubnlpLmZyZWVic2Qub3JnOi91c3Iv b2JqL3Vzci9zcmMvc3lzLz4NCg0KR0VORVJJQyAgYW1kNjQNCg0KDQoNCkJoeXZlIGNvbW1hbmQg aXMgYXMgZm9sbG93cw0KDQojIGJoeXZlIC1jIDIgLW0gMkcgLUh1d2wgYm9vdHJvbSwvdXNyL2xv Y2FsL3NoYXJlL3VlZmktZmlybXdhcmUvDQoNCkJIWVZFX1VFRkkuZmQNCg0KICAgLVUgODQxZTg3 NjQtNzVmNC0xMWU4LWIyZTMtNTBlNTQ5MzY5YmM2IC1sIGNvbTEsc3RkaW8NCg0KICAgLXMgMCxo b3N0YnJpZGdlIC1zIDMxLGxwYyAtcyAzOjAsYWhjaS1jZCwvdm0vLmNvbmZpZy9udWxsLmlzbyAt cw0KDQo0OjAsYWhjaS1oZCwvdm0vdzIwMTYvZGlzazAuaW1nIC1zIDU6MCxlMTAwMCx0YXAxLG1h Yz01ODo5YzpmYzowODo4ZTo3MA0KDQogICAtcyA2OjAsZmJ1Zix0Y3A9MC4wLjAuMDo1OTAwIC1z IDc6MCx4aGNpLHRhYmxldCB3MjAxNg0KDQpIaSBNYXR0LA0KDQoNCg0KdHJ5IHVzaW5nIHZpcnRp byBmb3IgbmljICYgc3RvcmFnZSB0byBzdGFydCB3aXRoLiBJJ3ZlIHVzZWQgc3BlY2lmaWNhbGx5 IHRoZXNlIGRyaXZlcnMgaHR0cHM6Ly9mZWRvcmFwZW9wbGUub3JnL2dyb3Vwcy92aXJ0L3ZpcnRp by13aW4vZGlyZWN0LWRvd25sb2Fkcy9hcmNoaXZlLXZpcnRpby92aXJ0aW8td2luLTAuMS45Ni92 aXJ0aW8td2luLTAuMS45Ni5pc28gYW5kIGhhZCB0cm91YmxlIHdpdGggYm90aCBsYXRlciBhbmQg ZWFybGllciBkcml2ZXJzLCBZTU1WLCBhbmQgSSBzYWRseSBmb3JnZXQgd2hlcmUgSSBnb3QgdGhp cyBhZHZpY2UuDQoNCg0KDQpBbHNvLCBpdOKAmXMgcG9zc2libGUgdG8gaW5zdGFsbCB2aXJ0aW8g ZHJpdmVycyBkaXJlY3RseSBmcm9tIHRoZSBDRCB3aXRob3V0IHBvaW50eS1jbGlja3kgc3R1cGlk bmVzcy4gSnVzdCBhZGQgdGhlIENEIHRvIHlvdXIgYmh5dmUgY29tbWFuZCwgaW4gYSBsYXRlciAi UENJIHNsb3QiIHRoYW4gdGhlIGV4aXN0aW5nIOKAnGhhcmQgZGlza+KAnSwgYXMgdGhlIGxvd2Vz dCBudW1iZXJlZCBzbG90IGlzIHdoYXTigJlzIHVzZWQgdG8gYm9vdCBmcm9tIEFGQUlDVC4NCg0K DQoNCi0gb3BlbiBhbiBlbGV2YXRlZCBjb21tYW5kIHByb21wdA0KDQotIHJ1biBmb3IgL2QgJWkg aW4gKGQ6XCopIGRvIEBwbnB1dGlsIC1hICVpXHc3XGFtZDY0XCouaW5mICh5b3UgbWF5DQoNCm5l ZWQgYSBkaWZmZXJlbnQgZHJpdmVyIHRoYW4gdzcgaGVyZSkNCg0KLSBzb21lIG9mIHRob3NlIHdp bGwgZmFpbCBidXQganVzdCBjYXJyeSBvbg0KDQotIHJlYm9vdCBGVFcNCg0KDQoNCm1vcmUgbm90 ZXMgaGVyZSBvbiBteSBiaHl2ZSBzZXR1cCBodHRwczovL2hhY2ttZC5pby9zL3JKdkp1RS1DVyM8 aHR0cHM6Ly9oYWNrbWQuaW8vcy9ySnZKdUUtQ1c+DQoNCg0KDQpBKw0KDQpEYXZlDQoNCl9fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQoNCmZyZWVic2Qtdmly dHVhbGl6YXRpb25AZnJlZWJzZC5vcmc8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb25AZnJl ZWJzZC5vcmc+IG1haWxpbmcgbGlzdA0KDQpodHRwczovL2xpc3RzLmZyZWVic2Qub3JnL21haWxt YW4vbGlzdGluZm8vZnJlZWJzZC12aXJ0dWFsaXphdGlvbg0KDQpUbyB1bnN1YnNjcmliZSwgc2Vu ZCBhbnkgbWFpbCB0byAiZnJlZWJzZC12aXJ0dWFsaXphdGlvbi11bnN1YnNjcmliZUBmcmVlYnNk Lm9yZyI8bWFpbHRvOmZyZWVic2QtdmlydHVhbGl6YXRpb24tdW5zdWJzY3JpYmVAZnJlZWJzZC5v cmc+DQoNCg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f Xw0KDQpmcmVlYnNkLXZpcnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPG1haWx0bzpmcmVlYnNkLXZp cnR1YWxpemF0aW9uQGZyZWVic2Qub3JnPiBtYWlsaW5nIGxpc3QgaHR0cHM6Ly9saXN0cy5mcmVl YnNkLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2ZyZWVic2QtdmlydHVhbGl6YXRpb24NCg0KVG8gdW5z dWJzY3JpYmUsIHNlbmQgYW55IG1haWwgdG8gImZyZWVic2QtdmlydHVhbGl6YXRpb24tdW5zdWJz Y3JpYmVAZnJlZWJzZC5vcmciPG1haWx0bzpmcmVlYnNkLXZpcnR1YWxpemF0aW9uLXVuc3Vic2Ny aWJlQGZyZWVic2Qub3JnPg0KDQo= From owner-freebsd-virtualization@freebsd.org Fri Jul 6 15:08:15 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53CAA102FF83 for ; Fri, 6 Jul 2018 15:08:15 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C286285318 for ; Fri, 6 Jul 2018 15:08:14 +0000 (UTC) (envelope-from djfarid@gmail.com) Received: by mail-ed1-x536.google.com with SMTP id f12-v6so8892302edq.11 for ; Fri, 06 Jul 2018 08:08:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=cFIuZ5Ryp1OiIfu1tnUWCrxlGvrYau7oiJQM3fB28xs=; b=n9+dTVyATKzEcy0Fem8INx/5nDmi5Yx4PFHIxOcGBZCHfwkF9pR34zpAqe3ihae3jK wcrRu4tYRbJ1T84Lluw53WjmEDWqfM2IaEY7Ef2hFCEi8fHnCdyxLPcYnYBbWoSALXb/ sIQDmmD1mXhqjCAmsABsHIgdf3XOAYkT33wzUQV30R0OxUQ2BhHImnaM3koApYwyE7Ci mlMXkNfHNQNSOEnisc9nwGH1AvWACca5CUaqFcE5HkrpDLh4Tsw6OLcSeoDlg/rXyYky DnGPxJUUxKkItOPAgLSiK1K830qnCmeeW6HQYtqQQ7llfPKO7ll4JjU/fuoR+I+/pOU6 5Jnw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=cFIuZ5Ryp1OiIfu1tnUWCrxlGvrYau7oiJQM3fB28xs=; b=U/ufe0v1tcOa4h9lvSTVFuEIKFI18qv5ETBPz7o9dLOEDKI4KmIhSxHTM3NTRMzVP4 k7UB5xO3E+M/10UEm5+57XyfcFluhF1PZquJlkM+dNSatL57ZKiXpuWgZ42JCJoj0ypA 6b0YowTC3WyKcnrkGlPNxCY2RJzTbpZFkAjLmUAS6D1Bosk7j6d8/BxseeweJ+/CIeVP UhtdSuWwg8s9C2FDr4vyqhSgvcEJ+cZlNt5Tj9fUpPktmuR/S4a4pezTBcu/1bjJkFja iC3ktNvleN//S8cJWSezaMO/dx0vlCkzz5ukur9norzNsxkfhw1FPBiHBz9iY6d9DUM5 q9NQ== X-Gm-Message-State: APt69E1r0GDMbiPduM1Jk5UWOsjkmk5xFBxq4yQ3pSzMSfAEYhH/5D0w Y0VuTlFHnz8RouWsCyil5xi4zLqbPRVJg560nY0grD5v X-Google-Smtp-Source: AAOMgpf+Et7UFp2lannvM3sJYRD7+Pj0rPMT4I8uNY6flGZGxLC+5IPLQ8fcCxP9mdt3Ds636QLdkldlY+owkxKgr2k= X-Received: by 2002:a50:8607:: with SMTP id o7-v6mr10993780edo.243.1530889693528; Fri, 06 Jul 2018 08:08:13 -0700 (PDT) MIME-Version: 1.0 From: Farid Joubbi Date: Fri, 6 Jul 2018 17:07:48 +0200 Message-ID: Subject: Passthrough not working with OpenBSD nor NetBSD To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 15:08:15 -0000 Hello, I have configured passthrough of two different PCI Express network interface cards. I can't get neither OpenBSD nor NetBSD to work with these NICs. I get this in dmesg when booting the NetBSD install: wm0 at pci0 dev 5 function 0: 82576 quad-1000BaseT Ethernet (rev. 0x01) pci_intr_map: no mapping for pin B (line=ff) wm0: unable to map interrupt bge0 at pci0 dev 6 function 0: Broadcom BCM5720 Gigabit Ethernet pci_intr_map: no mapping for pin B (line=ff) bge0: couldn't map interrupt With OpenBSD it's the same error. I have no problems running FreeBSD or CentOS with the exact same setup. This is how vm is configured for the NetBSD install: loader="grub" cpu=1 memory=4G passthru0="12/0/1" passthru1="3/0/1" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="1c9596b9-80a0-11e8-960c-5cb9013bbb64" grub_install0="knetbsd -h -r cd0a /netbsd" grub_run0="knetbsd -h -r ld0a /netbsd" I started out with OpenBSD and a Intel NIC. Then I added the Broadcom NIC since I figured that maybe it's a driver issue. I'm running bhyve on 11.1-RELEASE-p11. Any ideas? From owner-freebsd-virtualization@freebsd.org Fri Jul 6 17:25:40 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2B83A103D537; Fri, 6 Jul 2018 17:25:40 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C9CCA8C521; Fri, 6 Jul 2018 17:25:39 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3F24520F02; Fri, 6 Jul 2018 13:25:39 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 06 Jul 2018 13:25:39 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=wHmyw5z2Q7yaJYYc8kVYQKjj/OkV0ffoRzB/OASm7MQ=; b=e8Zie7Ze IwfNEyeBgxQyz+HWm3mCRIGyeAR6dOV7EDnLNkRJYJruZEj7trAfx0pRQsmXAYZv cqCY5A57XwtIZEYSvViSfVw2ZAZS0gOtKe8Wsp11FQIeLoiDUo27aJ5+xbhMyoAK pCivq6GgMKLuz8Ks6dg8YuYN99gK1hdl1M9GL2X2n2aevZdx+DbE2qxEYR5TjyWJ kOqu/FThQCLljcXf+zVykOA4PfBaoIgPt4JSDBYlz8s9vmNVHQZLVJe0js9blGDU V16LfyOVQ1xOIA996w/93QgLZ7l/7G6VCINZqNUF48fKBxMaz0Puf0ieRnm3Mm+O GdaICv+rmpkJ5Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=wHmyw5z2Q7yaJYYc8kVYQKjj/OkV0 ffoRzB/OASm7MQ=; b=Ej2Xm8q3GXndGbCb2mOdD+fb/XHVp7D655aGSmamqu8f9 c8cLB4QiRxYpMa9l45YvLjqdPd8UYy8FyltZKbFEwkOVZSX/ifcFJXTmpu9EDluA YtcNQ4zJR6A6qusohMcs4JuhJpkrPnKJFSsS5/+n6BltDkJoX22WHIsS9jgBGMA2 Zu/3yTB3V1RpIIttrTSl+uG5jmm6tLAmAL7JFOn8+s7FSk4sdpPt920z5MlkXT+A 81sgwdP9qHw5i50W901bMOQs4oGDAmF+IuHxkc6nAmvrhOE80VdVQcxeNQBBwEcg UxL7c7TIyUp9BYdzWnWzr5YRAUhk16kMZafJaEydA== X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 540131025C; Fri, 6 Jul 2018 13:25:38 -0400 (EDT) To: freebsd-virtualization@freebsd.org Cc: freebsd-current@freebsd.org From: tech-lists Subject: bhyve and freebsd memstick installer Organization: none Message-ID: <7fdf88da-7692-8cfa-a42b-19314866977d@zyxst.net> Date: Fri, 6 Jul 2018 18:25:37 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 17:25:40 -0000 Hello, context: freebsd-12-current server, amd64 I usually install a freebsd guest like this: sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img -i -I FreeBSD-installation-dvd1.iso guestname I only have memstick.img - how do I either: 1. convert the memstick to dvd1.iso 2. make bhyve use the memstick installation iso (I don't think it can do this as the option to do so isn't in vmrun.sh) thanks, -- J. From owner-freebsd-virtualization@freebsd.org Fri Jul 6 17:32:45 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B8E56103E148; Fri, 6 Jul 2018 17:32:45 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39C578CDD4; Fri, 6 Jul 2018 17:32:45 +0000 (UTC) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: from pdx.rh.CN85.dnsmgr.net (localhost [127.0.0.1]) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3) with ESMTP id w66HWgIX053395; Fri, 6 Jul 2018 10:32:42 -0700 (PDT) (envelope-from freebsd-rwg@pdx.rh.CN85.dnsmgr.net) Received: (from freebsd-rwg@localhost) by pdx.rh.CN85.dnsmgr.net (8.13.3/8.13.3/Submit) id w66HWgJF053394; Fri, 6 Jul 2018 10:32:42 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201807061732.w66HWgJF053394@pdx.rh.CN85.dnsmgr.net> Subject: Re: bhyve and freebsd memstick installer In-Reply-To: <7fdf88da-7692-8cfa-a42b-19314866977d@zyxst.net> To: tech-lists Date: Fri, 6 Jul 2018 10:32:42 -0700 (PDT) CC: freebsd-virtualization@freebsd.org, freebsd-current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 17:32:45 -0000 > Hello, > > context: freebsd-12-current server, amd64 > > I usually install a freebsd guest like this: > > sh /usr/share/examples/bhyve/vmrun.sh -c 2 -m 4096M -t tap0 -d guest.img > -i -I FreeBSD-installation-dvd1.iso guestname > > I only have memstick.img - how do I either: > > 1. convert the memstick to dvd1.iso > 2. make bhyve use the memstick installation iso (I don't think it can do > this as the option to do so isn't in vmrun.sh) Untested, but since memstick is actually a "disk" image and not a "cdrom" image you should be able to do something like vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname Your memstick should show up as ada0, and your guest.img should be ada1. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Fri Jul 6 20:37:37 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0642102A306; Fri, 6 Jul 2018 20:37:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 48FB995E6E; Fri, 6 Jul 2018 20:37:37 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 88C7821B5A; Fri, 6 Jul 2018 16:37:36 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 06 Jul 2018 16:37:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=ZxxHlasZ8W+ZZVjj4jDj0tg4EHrei j/rF/hBO8Y4dI8=; b=vUAkFX6X+6EaJL2JdqzGRN6dyp2odd1U5m5iHbHb8n4wJ jdzL1uaQ1dtITEhojuaa0ua4tle+xeD32qcwLHZ36eK0vGu6qVW6+PE8Kf9Hfz4b BrFsPmXULwBFDbCYLTxBcPWRToiwCCBSl5mDOZmHASRk7cr0tz78EdEIYj+JVhU4 5gxNPpZsi0dCOo4Mj5HHQZY1ZDpNRR+m+ZtazQWR1A2M2Lck/QipDvIPEZ5qmUuP yaNj6YwkX/Hh21bhmG2teKgCJuAiFEEeGnpFy0BfN2648Zi/OZzSVR0Co9JBJAwv Q4srLC4AjWEsRrrqHWaNnf4OtKdxuqfdfvrbd37NA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; bh=ZxxHla sZ8W+ZZVjj4jDj0tg4EHreij/rF/hBO8Y4dI8=; b=Xyx1s6VXMVi2FZzVIno3LH pU3xSFgm8qGxozzFXqrTH6zihsrv/C7rx+hItvDAGS3R1Xguag/s7T2GCE3bpmX7 HGlObsPiks7j8nIwwLc6WMZ91PT/8oYZVsRQeOTlsmtq8a4GxTWar+3sNH5UWWsc gurQdqhXOB9z3CgdphFzxPNpVRs5j7nbdehgX4GOqnO/6mq3nOixG8eKNbaJH7eB 4lpIdUIXlI/ugMic8LglzTkUL/YGTTMGzge2MMaBA5RUuAa/szCxYhcoIqMOd6YM T01xSvlom5zlLFz6YBeD3vx1WOQl6kHHGER0/tHw5siL/4+SEKMkS5KNPATd9lPQ == X-ME-Proxy: X-ME-Sender: Received: from desktop.local (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 7EC1610266; Fri, 6 Jul 2018 16:37:35 -0400 (EDT) Subject: Re: bhyve and freebsd memstick installer To: "Rodney W. Grimes" Cc: freebsd-virtualization@freebsd.org, freebsd-current@freebsd.org References: <201807061732.w66HWgJF053394@pdx.rh.CN85.dnsmgr.net> From: tech-lists Organization: none Message-ID: <7cffa475-4d43-987c-f380-2384f4834ce1@zyxst.net> Date: Fri, 6 Jul 2018 21:37:34 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 In-Reply-To: <201807061732.w66HWgJF053394@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 20:37:37 -0000 On 06/07/2018 18:32, Rodney W. Grimes wrote: > Untested, but since memstick is actually a "disk" image and not > a "cdrom" image you should be able to do something like > vmrun.sh -c 2 -m 4096M -t tap0 -d memstick.img -d guest.img guestname > > Your memstick should show up as ada0, > and your guest.img should be ada1. Thanks for that, I'll try it next time I can. I got round it temporarily by mounting the memstick as /dev/md1p3 and pointing mkisofs at that. the -i -I thing of bhyve threw me. I thought I'd need it to point to bootable media. -- J. From owner-freebsd-virtualization@freebsd.org Fri Jul 6 23:28:25 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 787CF103BD7D for ; Fri, 6 Jul 2018 23:28:25 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C87E374CA7 for ; Fri, 6 Jul 2018 23:28:24 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.106] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id d9f0fefb TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Fri, 6 Jul 2018 16:28:22 -0700 (PDT) To: freebsd-virtualization@freebsd.org From: Pete Wright Subject: AWS M5 ena Issues Message-ID: <5c539880-6529-10aa-67d4-177e2ab3c78f@nomadlogic.org> Date: Fri, 6 Jul 2018 16:28:18 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Fri, 06 Jul 2018 23:28:25 -0000 hi there - this is in relation to this ticket: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225791 "ena driver causing kernel panics on AWS EC2" reading through the thread, and Colin's blog post on the new M5 instance types, it looks like the issues people are running into are related to NVMe devices fronting EBS block stores. My question is is this a discreet issue from other anomalies people have seen with ena network devices.  For example, on some currently lightly loaded m5.large instances I have been seeing this in the logs pretty regularly: ena0: device is going DOWN ena0: device is going UP ena0: queue 0 - cpu 0 ena0: queue 1 - cpu 1 These systems were previously running 11.1-RELEASE without any issues, I then upgraded them to 11.2-RELEASE via "freebsd-update".  These messages only started showing up after I had completed the upgrade. from reading the bug report above though it's not clear as to the state of the ena drivers themselves.  Are they considered unstable on 11.2-RELEASE? Cheers, -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA From owner-freebsd-virtualization@freebsd.org Sat Jul 7 00:38:17 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2E561041D55 for ; Sat, 7 Jul 2018 00:38:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6A13D7752E for ; Sat, 7 Jul 2018 00:38:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 260421041D4B; Sat, 7 Jul 2018 00:38:17 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1206F1041D49 for ; Sat, 7 Jul 2018 00:38:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9C57B77526 for ; Sat, 7 Jul 2018 00:38:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id DF81322681 for ; Sat, 7 Jul 2018 00:38:15 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w670cFVR041624 for ; Sat, 7 Jul 2018 00:38:15 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w670cFZu041621 for virtualization@FreeBSD.org; Sat, 7 Jul 2018 00:38:15 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 220453] [Hyper-V] need to update Mellanox ConnectX-3 VF driver to support Live Migration Date: Sat, 07 Jul 2018 00:38:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: decui@microsoft.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Sat, 07 Jul 2018 00:38:18 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220453 --- Comment #19 from Dexuan Cui --- (In reply to scorpionmage from comment #18) Let's track the vmbus_msghc_exec() panic in bug 229167. I'm going to commit= a fix soon. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat Jul 7 00:41:19 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 671741042454 for ; Sat, 7 Jul 2018 00:41:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 00D1E77E27 for ; Sat, 7 Jul 2018 00:41:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B4130104244D; Sat, 7 Jul 2018 00:41:18 +0000 (UTC) Delivered-To: virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1744104244C for ; Sat, 7 Jul 2018 00:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B0AA77E17 for ; Sat, 7 Jul 2018 00:41:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6E3EA226AA for ; Sat, 7 Jul 2018 00:41:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w670fH5G048174 for ; Sat, 7 Jul 2018 00:41:17 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w670fHGU048173 for virtualization@FreeBSD.org; Sat, 7 Jul 2018 00:41:17 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 229167] [Hyper-V] [Jun 19, 2018] Recently FreeBSD VM panics during boot-up, especially with Mellanox VF configured Date: Sat, 07 Jul 2018 00:41:17 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: regression X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.27 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: Sat, 07 Jul 2018 00:41:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D229167 --- Comment #14 from commit-hook@freebsd.org --- A commit references this bug: Author: dexuan Date: Sat Jul 7 00:41:05 UTC 2018 New revision: 336054 URL: https://svnweb.freebsd.org/changeset/base/336054 Log: hyperv: Fix boot-up after malloc() returns memory of NX by default now FreeBSD VM can't boot up on Hyper-V after the recent malloc change in r335068: Make UMA and malloc(9) return non-executable memory in most case= s. The hypercall page here must be executable. Fix the boot-up issue by adding M_EXEC. PR: 229167 Sponsored by: Microsoft Changes: head/sys/dev/hyperv/vmbus/hyperv.c --=20 You are receiving this mail because: You are the assignee for the bug.=