From owner-freebsd-virtualization@freebsd.org Tue Sep 25 13:36:55 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 7AF3110B272A for ; Tue, 25 Sep 2018 13:36:55 +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 17DDF72530 for ; Tue, 25 Sep 2018 13:36:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id D077310B2729; Tue, 25 Sep 2018 13:36:54 +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 BF3E010B2728 for ; Tue, 25 Sep 2018 13:36:54 +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 607A07252F for ; Tue, 25 Sep 2018 13:36:54 +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 B8C826F0D for ; Tue, 25 Sep 2018 13:36:53 +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 w8PDarQi012047 for ; Tue, 25 Sep 2018 13:36:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8PDarNw012046 for virtualization@FreeBSD.org; Tue, 25 Sep 2018 13:36:53 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 216009] Floppy does not work under KVM Date: Tue, 25 Sep 2018 13:36:53 +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: 10.3-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: josh@servebyte.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: Tue, 25 Sep 2018 13:36:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216009 Josh Jameson changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |josh@servebyte.com --- Comment #1 from Josh Jameson --- I've ran into this issue on 11.2-RELEASE-p3 Does anyone know how to fix this? I tried disabling device hints in /boot/device.hints but no dice. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue Sep 25 23:02:28 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 6942B1092B11 for ; Tue, 25 Sep 2018 23:02:28 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F111484F78 for ; Tue, 25 Sep 2018 23:02:27 +0000 (UTC) (envelope-from olevole@olevole.ru) Received: by mail-io1-xd2d.google.com with SMTP id n18-v6so21822025ioa.9 for ; Tue, 25 Sep 2018 16:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=olevole-ru.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=ID5A46i9skf7SrTod4Y1IGGwjerZZDLUgi547WBLnhQ=; b=khFzIPXqjgfm8h13gYXGeA04CtMuUCdK8u5/yv6+r1CyFo/whmS3TGoNa63vigbEbj L5ddB9FTTHtV5uU5co4Ff+lytiVaN+t8jvuEIqefEr472VmUqTuPU1FLc4h+s1GXvzRs j8ZqhCP0WXFur1lt+32I1uUzdb3jBXuveyXeuBnpt3n01kQ4NfElIngT14IaoXgcKNXl RBXsmOTFvIpzVGXJ8+/jiou3k4lLR/QYN4UzR3WaISI4nOi1pOv56Zq/NVhiqzpI19Ze CwtdgJuqW+C2EuZbIvhAWRrq7VaDdRqOFHvh/dq3Ov3R9EL4s2CDHF8jNGgF0VhRKHrP YW+w== 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=ID5A46i9skf7SrTod4Y1IGGwjerZZDLUgi547WBLnhQ=; b=JghWRHjXQnLPXI15+5vukJXzR0HYu7bC60sOGJVRju85MgdGP04GrUNOwjHwaQB3F7 gy4QSudXB6JeypeO1o/zaH4Ig/fISslonD43k24lF891NX6GsQ6ccp6gX9zYa0iVWOC2 A9Moh3yeT4wKpyCXq9CevqVayzXQUaXiAf6huA2qnGmTxMv21rdZLmSCdpHjEMlQHjyD GJKHjLaeGmJnUUGZ+hLwBs82Lp5ChoieuHOxkdaQzA+4XCML1DoSAuxx9IWpw5nF3E5I L0vRQ+FrAEqYJPL/ep4B1Qyv28M1WvwxYGoMBX4HuQasGiOJK3OQQcVFChoN8PB4zDFn Wcww== X-Gm-Message-State: ABuFfohr+/WC0yvzeij+sFe7NPVN65JH0LGnvbfyMbJBY4Xr+HSZAlho wwG2RMu07s96UF9rUW/+R3/pF67ZsUzQOCb2snEDefdy4dM= X-Google-Smtp-Source: ACcGV60xQG2q5r4feQqtyLQLkimGQKnwfghgyUp2IRMgTNtW8msZurFJs6aTCRTgawXr0psiXtuV0k28lpPqQ1g4DBA= X-Received: by 2002:a5e:8215:: with SMTP id l21-v6mr2968323iom.232.1537916546944; Tue, 25 Sep 2018 16:02:26 -0700 (PDT) MIME-Version: 1.0 From: Oleg Ginzburg Date: Wed, 26 Sep 2018 02:02:15 +0300 Message-ID: Subject: NetBSD 8.0/amd64+ bhyve (FreeBSD 12)+xhci = SIGSEGV To: freebsd-virtualization@freebsd.org, tech-kern@netbsd.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: Tue, 25 Sep 2018 23:02:28 -0000 Hello. NetBSD works fine in bhyve, except for the case when the bhyve emulates eXtensible Host Controller Interface (xHCI) USB controller. ( -s 30,xhci,tablet ) Perhaps SIGSEGV of bhyve is caused by the abnormal behavior of xhci on the NetBSD guest, so I decided to write both mailing lists. LLDB output upon bhyve crash (guest screen: https://pasteboard.co/HFAqTOk.png ): https://github.com/freebsd/freebsd/blob/ebeb3285f598d6c1214c49598c951493d09e1067/usr.sbin/bhyve/pci_xhci.c#L735 Process 57083 stopped * thread #20, name = 'vcpu 0', stop reason = signal SIGSEGV: invalid address (fault address: 0x0) frame #0: 0x00000000002587d8 bhyve`pci_xhci_insert_event(sc=0x00000008010a5100, evtrb=0x00007fffddbeba78, do_intr=0) at pci_xhci.c:735 732 rts = &sc->rtsregs; 733 734 erdp = rts->intrreg.erdp & ~0xF; -> 735 erdp_idx = (erdp - rts->erstba_p[rts->er_deq_seg].qwEvrsTablePtr) / 736 sizeof(struct xhci_trb); 737 738 DPRINTF(("pci_xhci: insert event 0[%lx] 2[%x] 3[%x]\r\n" (lldb) frame variable erdp_idx (int) erdp_idx = 0 in all likelihood, the problem in the rts->erstba_p structure because when I commenting 735 line ( erdp_idx is used only in DPRINTF debug output ) the next stop when working with this structure again, e.g: Process 58354 stopped * thread #20, name = 'vcpu 0', stop reason = signal SIGSEGV: invalid address (fault address: 0x8) frame #0: 0x0000000000258881 bhyve`pci_xhci_insert_event(sc=0x00000008010a5100, evtrb=0x00007fffddbeba78, do_intr=0) at pci_xhci.c:750 747 evtrbptr = &rts->erst_p[rts->er_enq_idx]; 748 749 /* TODO: multi-segment table */ -> 750 if (rts->er_events_cnt >= rts->erstba_p->dwEvrsTableSize) { 751 DPRINTF(("pci_xhci[%d] cannot insert event; ring full\r\n", 752 __LINE__)); 753 err = XHCI_TRB_ERROR_EV_RING_FULL; What can I do to find out the reasons for this behavior? Thanks! From owner-freebsd-virtualization@freebsd.org Thu Sep 27 10:46: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 F351A10AA676 for ; Thu, 27 Sep 2018 10:46:03 +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 90CE8803C0 for ; Thu, 27 Sep 2018 10:46:03 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 551EA10AA673; Thu, 27 Sep 2018 10:46:03 +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 43B3A10AA671 for ; Thu, 27 Sep 2018 10:46:03 +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 D3FE2803BE for ; Thu, 27 Sep 2018 10:46:02 +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 2D605269B9 for ; Thu, 27 Sep 2018 10:46:02 +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 w8RAk2JW062826 for ; Thu, 27 Sep 2018 10:46:02 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8RAk2Oh062824 for virtualization@FreeBSD.org; Thu, 27 Sep 2018 10:46:02 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 231756] Vagrant boxes don't work with vagrant-bhyve by default Date: Thu, 27 Sep 2018 10:46:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: linimon@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: assigned_to 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: Thu, 27 Sep 2018 10:46:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231756 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |virtualization@FreeBSD.org --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Thu Sep 27 17:30:56 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 D21F210B4060 for ; Thu, 27 Sep 2018 17:30:56 +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 6F0918E8E9 for ; Thu, 27 Sep 2018 17:30:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 3477110B405F; Thu, 27 Sep 2018 17:30:56 +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 2365710B405E for ; Thu, 27 Sep 2018 17:30:56 +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 B79FC8E8DE for ; Thu, 27 Sep 2018 17:30:55 +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 223C82A213 for ; Thu, 27 Sep 2018 17:30:55 +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 w8RHUt9f044583 for ; Thu, 27 Sep 2018 17:30:55 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8RHUtsK044582 for virtualization@FreeBSD.org; Thu, 27 Sep 2018 17:30: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 230773] [bhyve] GDT limit needs reset on VMX exit Date: Thu, 27 Sep 2018 17:30: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: jhb@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: blocked 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: Thu, 27 Sep 2018 17:30:57 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230773 John Baldwin changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |228911 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228911 [Bug 228911] FreeBSD 12.0 Release action items --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri Sep 28 13:23: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 5D42210B0B87 for ; Fri, 28 Sep 2018 13:23:40 +0000 (UTC) (envelope-from darcy@druid.net) Received: from mail.vex.net (mail.vex.net [IPv6:2605:2600:1001::44]) by mx1.freebsd.org (Postfix) with ESMTP id 01ACD7302E for ; Fri, 28 Sep 2018 13:23:39 +0000 (UTC) (envelope-from darcy@druid.net) Received: from dilbert.druid.net (dilbert.druid.net [207.35.13.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: darcy) by mail.vex.net (Postfix) with ESMTPSA id DC61F4A47907 for ; Fri, 28 Sep 2018 09:23:38 -0400 (EDT) To: freebsd-virtualization@freebsd.org From: D'Arcy Cain Subject: New bhyve user Openpgp: preference=signencrypt Message-ID: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> Date: Fri, 28 Sep 2018 09:23:38 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 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, 28 Sep 2018 13:23:40 -0000 Greetings. I have just recently started using bhyve (previously a Xen user). I am using vm-bhyve to manage it. I have a few questions. First question, am I making the right choice by switching and, if so, is bhyve the right choice to switch to? I realize that that is an impossible question but perhaps some pros and cons as well as war stories will help me. I created a switch and clients using the examples on the vm-bhyve web site. However, I could not get IP working until I put an IP address on the vm-public interface. I duplicated the address of the interface that it is connected to (re0 in my case) and used DHCP to assign addresses to the clients. If this is the correct way, shouldn't it have happened automatically? In any case, I saw I see that it can be added at creation time but how do I modify it later? I saw "switch address a.b.c.d/xx|none" in the man page but no way to specify which switch the address should be applied to. I tried adding the switch name before and after the address but that gave me an error. I tried to boot into a Linux install but even though I set grahics to yes, it doesn't seem to be serving VNC. On the console I can only get into the live CD. How do I get it installed? I am thinking of creating a base install with various install options and then copy that over to new installs as a starting point. I was going to use rsync with the -S option to copy over the file as sparse. Is there another way that is preferred? In Xen there is a maxvcpus which limit the number of CPUs but they could baloon down if not busy so that other clients who are busy can use the CPUs. In bhyve (at least in vm-bhyve) there is only a cpus line in the config. Is this a minimum, maximum or is it a hard limit? That's it for now. Thanks for any help. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@Vex.Net, VoIP: sip:darcy@druid.net From owner-freebsd-virtualization@freebsd.org Fri Sep 28 14:29: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 7F19810B2379 for ; Fri, 28 Sep 2018 14:29:08 +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 0F488756B3 for ; Fri, 28 Sep 2018 14:29:07 +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 AB127BD4; Fri, 28 Sep 2018 15:28:58 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=userve.net; s=201508; t=1538144938; bh=pbYdI8X0lH5OkawVAl/93dTFssQKQFOil1EVQcdm/hk=; h=From:To:Subject:Date:References:In-Reply-To; b=LYd8Fvc0FpJzaltHwmLr6J+dWOxAdebBHGi1WIvPnUogy1lCP1h1bKugf/mPpVpYz V5xWf/2MwgllUL0qmqT9vT79JuwVZ8m2kHFY9R5Q2k2/QInNsNDje2FGusatUtYI6f QaYrJ4RucVNJH1MGvaGHXrAOlB/5vM4kKkDAVwro= 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, 28 Sep 2018 15:28:58 +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, 28 Sep 2018 15:28:58 +0100 From: Matt Churchyard To: D'Arcy Cain , "freebsd-virtualization@freebsd.org" Subject: RE: New bhyve user Thread-Topic: New bhyve user Thread-Index: AQHUVy6KIM8IRd4MokidnpkHvp6wJqUFvCZA Date: Fri, 28 Sep 2018 14:28:57 +0000 Message-ID: <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> In-Reply-To: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> 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="us-ascii" Content-Transfer-Encoding: quoted-printable 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, 28 Sep 2018 14:29:08 -0000 -----Original Message----- From: owner-freebsd-virtualization@freebsd.org On Behalf Of D'Arcy Cain Sent: 28 September 2018 14:24 To: freebsd-virtualization@freebsd.org Subject: New bhyve user >Greetings. I have just recently started using bhyve (previously a Xen use= r). I am using vm-bhyve to manage it. I have a few questions. >First question, am I making the right choice by switching and, if so, is b= hyve the right choice to switch to? I realize that that is an impossible q= uestion but perhaps some pros and cons as well as war stories will help me. It really depends on how well bhyve supports what you need to do. The main = downside of bhyve at the moment is that it's very new and lacks many featur= es and performance optimisations you may find in more established hyperviso= rs. I can't really say yes you should use bhyve or no you should stick with= Xen. >I created a switch and clients using the examples on the vm-bhyve web site= . However, I could not get IP working until I put an IP address on the vm-= public interface. I duplicated the address of the interface that it is >co= nnected to (re0 in my case) and used DHCP to assign addresses to the client= s. If this is the correct way, shouldn't it have happened automatically? No, you should not be duplicating IP addresses. A virtual "switch" is really just an ethernet bridge. If you want guests to= be on the same lan as the host, then you can just create a virtual switch = and add your physical interface to it # vm switch create public # vm switch add public re0 Any guest that is connected to the vm-public switch will be bridged to re0,= and as such to the network re0 is connected to. In that instance you would= give guests IP addresses on the same range as re0 (or they could get addre= sses from your local DHCP server). If you want to guests to have a separate network, then you can assign an ad= dress to the virtual switch (using a different address range to the host) # vm switch create guests # vm switch address guests 192.168.100.1/24 In this case you would assign guests address in that network, with 192.168.= 100.1 as the gateway. (Alternatively you could install something to provide= dhcp. There are guides on the vm-bhyve GitHub for using dnsmasq). For this to work you would either need to configure the host to perform NAT= , or configure the rest of your network to know that any traffic to 192.168= .100.0/24 should be routed to the bhyve host. (NAT is probably the easier o= ption) >In any case, I saw I see that it can be added at creation time but how do = I modify it later? I saw "switch address a.b.c.d/xx|none" in the man page = but no way to specify which switch the address should be applied to. I tri= ed >adding the switch name before and after the address but that gave me an= error. I've just tested the above address command and it seems to be working for m= e... >I tried to boot into a Linux install but even though I set grahics to yes,= it doesn't seem to be serving VNC. On the console I can only get into the= live CD. How do I get it installed? Did you have uefi=3D"yes" in the configuration? Graphics are only available= when using UEFI boot. >I am thinking of creating a base install with various install options and = then copy that over to new installs as a starting point. I was going to us= e rsync with the -S option to copy over the file as sparse. >Is there another way that is preferred? For this sort of setup, ZFS is the obvious answer as you can use send/recv = to duplicate guests (or even clone to create an instant copy without using = additional disk space). If not using ZFS then rsync would be a reasonable o= ption to create copies of guests. >In Xen there is a maxvcpus which limit the number of CPUs but they could b= aloon down if not busy so that other clients who are busy can use the CPUs.= In bhyve (at least in vm-bhyve) there is only a cpus line in the config. = >Is this a minimum, maximum or is it a hard limit? This is the number of virtual cpus that the guest will see. Remember that a= s far as the host is concerned, the guests are processes that are using res= ources, just like any other program. A guest that is not doing much will no= t being using much cpu time on the host, and the host will happily run othe= r guests (or system processes) on the same physical cpus. >That's it for now. Thanks for any help. >--=20 >D'Arcy J.M. Cain | Democracy is three wolves >http://www.druid.net/darcy/ | and a sheep voting on >+1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. >IM: darcy@Vex.Net, VoIP: sip:darcy@druid.net _____________________________= __________________ >freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/= mailman/listinfo/freebsd-virtualization >To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freeb= sd.org" From owner-freebsd-virtualization@freebsd.org Fri Sep 28 14:41:29 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 3A56510B2852 for ; Fri, 28 Sep 2018 14:41:29 +0000 (UTC) (envelope-from ghislain@ghislain.net) Received: from mail02.aqueos.net (mail02.aqueos.net [94.125.164.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C930375DD6 for ; Fri, 28 Sep 2018 14:41:28 +0000 (UTC) (envelope-from ghislain@ghislain.net) Received: from localhost (localhost [127.0.0.1]) by mail02.aqueos.net (Postfix) with ESMTP id 643B15CE7D1 for ; Fri, 28 Sep 2018 16:41:20 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail02.aqueos.net Received: from mail02.aqueos.net ([127.0.0.1]) by localhost (mail02.aqueos.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id b-YKKffYkHTr for ; Fri, 28 Sep 2018 16:41:19 +0200 (CEST) Received: from localhost.localdomain (adsl2.aqueos.com [81.56.195.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail02.aqueos.net (Postfix) with ESMTPSA id 79E645CE7D0 for ; Fri, 28 Sep 2018 16:41:19 +0200 (CEST) Subject: Re: New bhyve user To: freebsd-virtualization@freebsd.org References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> From: ghislain Message-ID: <54298eaf-dcc1-fffb-fb01-1519eac7bd72@ghislain.net> Date: Fri, 28 Sep 2018 16:41:18 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> Content-Language: fr-FR 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: Fri, 28 Sep 2018 14:41:29 -0000 >> In Xen there is a maxvcpus which limit the number of CPUs but they could baloon down if not busy so that other clients who are busy can use the CPUs. In bhyve (at least in vm-bhyve) there is only a cpus line in the config. >Is this a minimum, maximum or is it a hard limit? > This is the number of virtual cpus that the guest will see. Remember that as far as the host is concerned, the guests are processes that are using resources, just like any other program. A guest that is not doing much will not being using much cpu time on the host, and the host will happily run other guests (or system processes) on the same physical cpus. if i understood the other comments on the list on previous thread there is not any mecanism to prioritize guest from other guest and share fairly between them when they share a cpu core.  The freebsd kernel will treat all process equaly. If i am correct the only way to have a fair distribution is to bind guest to a cpu but then you loose the sharing possibility if one is idle. If you let just everyone have the whole cpu access then there is no rule about which guest will have the cpu time as the kernel do not know how to partition the cpu time per guest, only per process.  So if one guest launch a lot of cpu hungry thread it could "starve" the others guests with less thread usgin cpu time. Correct me if i read that wrong :) Ghislain. From owner-freebsd-virtualization@freebsd.org Fri Sep 28 14:54: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 B7B4C10B2C0C for ; Fri, 28 Sep 2018 14:54:43 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from bsd.cgi.cz (bsd.cgi.cz [178.238.45.112]) (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 52299763E0 for ; Fri, 28 Sep 2018 14:54:43 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel [192.168.66.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by bsd.cgi.cz (Postfix) with ESMTPS id 5E6A323CF8D for ; Fri, 28 Sep 2018 17:13:26 +0200 (CEST) Received: from localhost (unknown [192.168.66.11]) by hel.cgi.cz (Postfix) with ESMTP id 3254014DD19 for ; Fri, 28 Sep 2018 16:47:46 +0200 (CEST) Received: from hel.cgi.cz ([192.168.66.6]) by localhost (antispam1.cgi.cz [192.168.66.11]) (amavisd-new, port 10024) with LMTP id dID0v9QUbAUe for ; Fri, 28 Sep 2018 16:47:08 +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 C39F214DCE5 for ; Fri, 28 Sep 2018 16:47:43 +0200 (CEST) Received: from [192.168.8.136] (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 A87D2846C7 for ; Fri, 28 Sep 2018 16:47:43 +0200 (CEST) Subject: Re: New bhyve user To: "freebsd-virtua." References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> <54298eaf-dcc1-fffb-fb01-1519eac7bd72@ghislain.net> From: Jakub Chromy Message-ID: <60055d7f-c378-7242-5bd5-7f5b60779b61@cgi.cz> Date: Fri, 28 Sep 2018 16:47:07 +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: <54298eaf-dcc1-fffb-fb01-1519eac7bd72@ghislain.net> 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, 28 Sep 2018 14:54:43 -0000 > >  So if one guest launch a lot of cpu hungry thread it could "starve" > the others guests with less thread usgin cpu time. As far as what I heard here on this forum, you should NOT overcommit the vCPUs. When you keep the number of vCPUs assigned to your vms lower than physical CPUs (= hyperthreaded cores), you should be fine. -- regards Jakub Chromy CGI Systems div. ---------------- CGI CZ s.r.o. sales@cgi.cz 775 144 257 234 697 102 www.cgi.cz > >  So if one guest launch a lot of cpu hungry thread it could "starve" > the others guests with less thread usgin cpu time. > > Correct me if i read that wrong :) > > Ghislain. > _______________________________________________ > 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 Sep 28 15:07:49 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 17D5910B2F1D for ; Fri, 28 Sep 2018 15:07:49 +0000 (UTC) (envelope-from darcy@druid.net) Received: from mail.vex.net (mail.vex.net [IPv6:2605:2600:1001::44]) by mx1.freebsd.org (Postfix) with ESMTP id 9D49676896 for ; Fri, 28 Sep 2018 15:07:48 +0000 (UTC) (envelope-from darcy@druid.net) Received: from dilbert.druid.net (dilbert.druid.net [207.35.13.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: darcy) by mail.vex.net (Postfix) with ESMTPSA id 3D9454A478F3; Fri, 28 Sep 2018 11:07:48 -0400 (EDT) Subject: Re: New bhyve user To: Matt Churchyard , "freebsd-virtualization@freebsd.org" References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> From: D'Arcy Cain Openpgp: preference=signencrypt Message-ID: <4fa7f24d-1d77-0c62-22ef-6b6f8172798a@druid.net> Date: Fri, 28 Sep 2018 11:07:47 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> Content-Type: text/plain; charset=utf-8 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, 28 Sep 2018 15:07:49 -0000 On 9/28/18 10:28 AM, Matt Churchyard wrote: >> I created a switch and clients using the examples on the vm-bhyve web site. However, I could not get IP working until I put an IP address on the vm-public interface. I duplicated the address of the interface that it is >connected to (re0 in my case) and used DHCP to assign addresses to the clients. If this is the correct way, shouldn't it have happened automatically? > > No, you should not be duplicating IP addresses. Yes, it seemed wrong but... > A virtual "switch" is really just an ethernet bridge. If you want guests to be on the same lan as the host, then you can just create a virtual switch and add your physical interface to it > > # vm switch create public > # vm switch add public re0 > > Any guest that is connected to the vm-public switch will be bridged to re0, and as such to the network re0 is connected to. In that instance you would give guests IP addresses on the same range as re0 (or they could get addresses from your local DHCP server). That's what I did at first but I could not make the clients talk to the host. I will try again. > If you want to guests to have a separate network, then you can assign an address to the virtual switch (using a different address range to the host) > > # vm switch create guests > # vm switch address guests 192.168.100.1/24 I have another installation where I will probably do this. > In this case you would assign guests address in that network, with 192.168.100.1 as the gateway. (Alternatively you could install something to provide dhcp. There are guides on the vm-bhyve GitHub for using dnsmasq). > For this to work you would either need to configure the host to perform NAT, or configure the rest of your network to know that any traffic to 192.168.100.0/24 should be routed to the bhyve host. (NAT is probably the easier option) I assume that this won't be necessary if I have a bank of live IPs. even if I don't, wouldn't my gateway NAT be enough? >> In any case, I saw I see that it can be added at creation time but how do I modify it later? I saw "switch address a.b.c.d/xx|none" in the man page but no way to specify which switch the address should be applied to. I tried >adding the switch name before and after the address but that gave me an error. > > I've just tested the above address command and it seems to be working for me... What exactly did you type? The man page suggests something like this: $ vm switch address 192.168.100.0/24 How does it know which switch to add the address to? >> I tried to boot into a Linux install but even though I set grahics to yes, it doesn't seem to be serving VNC. On the console I can only get into the live CD. How do I get it installed? > > Did you have uefi="yes" in the configuration? Graphics are only available when using UEFI boot. Yes. I copied it right off the web site. >> I am thinking of creating a base install with various install options and then copy that over to new installs as a starting point. I was going to use rsync with the -S option to copy over the file as sparse. >> Is there another way that is preferred? > > For this sort of setup, ZFS is the obvious answer as you can use send/recv to duplicate guests (or even clone to create an instant copy without using additional disk space). If not using ZFS then rsync would be a reasonable option to create copies of guests. I am using ZFS but I am also new to that and I am still exploring. That sounds like a good idea. >> In Xen there is a maxvcpus which limit the number of CPUs but they could baloon down if not busy so that other clients who are busy can use the CPUs. In bhyve (at least in vm-bhyve) there is only a cpus line in the config. >Is this a minimum, maximum or is it a hard limit? > > This is the number of virtual cpus that the guest will see. Remember that as far as the host is concerned, the guests are processes that are using resources, just like any other program. A guest that is not doing much will not being using much cpu time on the host, and the host will happily run other guests (or system processes) on the same physical cpus. So if I have 16 CPUs and 8 clients, there is no problem giving them each 4 CPUs? Is that the maximum that they can use? Thanks. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@Vex.Net, VoIP: sip:darcy@druid.net From owner-freebsd-virtualization@freebsd.org Fri Sep 28 16:32: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 D860D10B44DA for ; Fri, 28 Sep 2018 16:32:17 +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 5CCFC79654 for ; Fri, 28 Sep 2018 16:32:17 +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 w8SGUvY6078065; Fri, 28 Sep 2018 09:30:57 -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 w8SGUuB4078064; Fri, 28 Sep 2018 09:30:56 -0700 (PDT) (envelope-from freebsd-rwg) From: "Rodney W. Grimes" Message-Id: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net> Subject: Re: New bhyve user In-Reply-To: <60055d7f-c378-7242-5bd5-7f5b60779b61@cgi.cz> To: Jakub Chromy Date: Fri, 28 Sep 2018 09:30:56 -0700 (PDT) CC: "freebsd-virtua." 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, 28 Sep 2018 16:32:18 -0000 > > > > ?So if one guest launch a lot of cpu hungry thread it could "starve" > > the others guests with less thread usgin cpu time. > > As far as what I heard here on this forum, you should NOT overcommit the > vCPUs. You seemed to have heard incorrectly. There is little to no issues overcommiting CPU's in bhyve, I have a 2 core, 4 thread system with 6 VM's, each vm using 1 vCPU, this is a 50% overcommit and it my base line load. I frequently fire up 2 and 4 core VM's to do real work without any issues. Now, you do NOT want to end up in situation where these VM's are over loading the actually avaliable CPU cycles, what I am doing works becasue my base line 6 VM's only actually consume about 1.5 cpus, so I actually do have 2.5 sitting idle. What does NOT work well is overcommiting Memory, that kinda puts you in a real bad state. I also stronly recommend using -S (wire memory) option, this insures you actually can hard allocate any memory that a VM needs. > > When you keep the number of vCPUs assigned to your vms lower than > physical CPUs (= hyperthreaded cores), you should be fine. It is all a mater of Load, as long as your host load stays below the number of CPU threads you actually have things in this aspect tend to work just fine. And if you do exceed this everyone slows down in a fairly fair fashion. -- Rod Grimes rgrimes@freebsd.org From owner-freebsd-virtualization@freebsd.org Fri Sep 28 17:10:21 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 1AEDE10B51B7 for ; Fri, 28 Sep 2018 17:10:21 +0000 (UTC) (envelope-from ghislain@ghislain.net) Received: from mail02.aqueos.net (mail02.aqueos.net [94.125.164.53]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A7B607A876 for ; Fri, 28 Sep 2018 17:10:20 +0000 (UTC) (envelope-from ghislain@ghislain.net) Received: from localhost (localhost [127.0.0.1]) by mail02.aqueos.net (Postfix) with ESMTP id EF7CC5CE7D7 for ; Fri, 28 Sep 2018 19:10:18 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail02.aqueos.net Received: from mail02.aqueos.net ([127.0.0.1]) by localhost (mail02.aqueos.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LjY_Ac_dmqdm for ; Fri, 28 Sep 2018 19:10:18 +0200 (CEST) Received: from [192.168.200.223] (adsl2.aqueos.com [81.56.195.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail02.aqueos.net (Postfix) with ESMTPSA id E11DD5CE744 for ; Fri, 28 Sep 2018 19:10:17 +0200 (CEST) Subject: Re: New bhyve user To: freebsd-virtualization@freebsd.org References: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net> From: ghislain Message-ID: <1f83e1d4-5356-beec-f67e-b0caa659ed78@ghislain.net> Date: Fri, 28 Sep 2018 19:10:18 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: fr 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, 28 Sep 2018 17:10:21 -0000 > It is all a mater of Load, as long as your host load stays > below the number of CPU threads you actually have things > in this aspect tend to work just fine. And if you do exceed > this everyone slows down in a fairly fair fashion. > > well virtualisation is used for a lot of things but if you want to > isolate things you do not want a rogue VM taking all cpu so sharing > cpu in the current state is a risk as the policeman that is the kernel > do not seems to know bhyve guests :) (i speak conditionnal as i dont > use it myself i am just curious). Ghislain. From owner-freebsd-virtualization@freebsd.org Fri Sep 28 17:38:13 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 C312110B5982 for ; Fri, 28 Sep 2018 17:38:13 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-it1-x12c.google.com (mail-it1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C8F57B786 for ; Fri, 28 Sep 2018 17:38:13 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: by mail-it1-x12c.google.com with SMTP id q70-v6so3496820itb.3 for ; Fri, 28 Sep 2018 10:38:13 -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=ot/nxUjutc9dX8kRWL2mHn9wohsaOaa6HjryAh30OvU=; b=NQtK1AbFdPCI9cq/Cn40jncrgU3g5hfexgb1Wz/HT8b4Je7GG+kXU+qSJSR++7hfMI 2akVRT+aS+RYQd3wU7r1U0vUTHM8Tnu5lGd7V3OP9RT5S3LNRy37FgOJrBAD3NypsBIi JhOwyOh+i9cyLp2FGlrbHEIoN8X7s3KxlXdfqHLb+JYI0ZAt/RiEfWGrpt78PATLLdpz 9/ifMHGy2o3S9WJ3YacDaQKdg0zTh0ktoY+SNQRe0D91/V5k6emO4PzeROyFohFgvx1q p7sn5N95S8OKa59O0qwuvTGo9YCJ8crwjC2ElP0lFDkUQnTMhwLI32xxAMJaJGX8TcSR h+IA== 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=ot/nxUjutc9dX8kRWL2mHn9wohsaOaa6HjryAh30OvU=; b=PWaRksyOFgPFK8RxERHIOqXSj6S6MmKCayRwsgqIUPeAo7pnZF4NR6Us8Rx9zmzXZm 26dPdMLqVwU8LGKac89eppjcaxcoUmPLB0Q0PHE58nYXfdQSSx4jv7HZk40r2PegoeIP VGZu54n03dV7z3JCNgnjl3BFeOMDHd4Z6n8Dy5T+CPHAejvwNsMPM78PhL7HKmGfIHmA wt2fHim1CJQqGwBksXf00EJrKmjFjwrqkeW3bSBbNseMSvTRuOEfDEbw8KsQZT3Ijatf NP9TdAoDnmtHNNFRBjuJw3vHuiq/O7BosNI8mUIgxfToqBPZBGwdRma22pmQPnWZghuG M1xw== X-Gm-Message-State: ABuFfogFSRbhx+LQnpOfMnurJKXa8VBMF0jXaIlyr3EP02J7hxHbiFCP mlQ54Gi5aXzIjrvg1MPtS5x3n/HNKGjisxfFyj2o4d7i X-Google-Smtp-Source: ACcGV61YhBQdIBb6BqPpsfeFyVW3VOsDce6tjzakNY5zyRPJftfJBPk99MOvaRnWKConZkPZayJjWaoguRQLNpMLng8= X-Received: by 2002:a02:8a5a:: with SMTP id e26-v6mr13850335jal.89.1538156292286; Fri, 28 Sep 2018 10:38:12 -0700 (PDT) MIME-Version: 1.0 References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> <4fa7f24d-1d77-0c62-22ef-6b6f8172798a@druid.net> In-Reply-To: <4fa7f24d-1d77-0c62-22ef-6b6f8172798a@druid.net> From: Adam Date: Fri, 28 Sep 2018 12:38:00 -0500 Message-ID: Subject: Re: New bhyve user To: darcy@druid.net Cc: Matt Churchyard , FreeBSD virtualization 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, 28 Sep 2018 17:38:14 -0000 On Fri, Sep 28, 2018 at 10:08 AM D'Arcy Cain wrote: > > This is the number of virtual cpus that the guest will see. Remember > that as far as the host is concerned, the guests are processes that are > using resources, just like any other program. A guest that is not doing > much will not being using much cpu time on the host, and the host will > happily run other guests (or system processes) on the same physical cpus. > > So if I have 16 CPUs and 8 clients, there is no problem giving them each > 4 CPUs? Is that the maximum that they can use? > The comments of this bug report contain more detail about what you can expect. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 That stuff would be good in the wiki. -- Adam From owner-freebsd-virtualization@freebsd.org Fri Sep 28 17:47: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 14D0C10B5C60 for ; Fri, 28 Sep 2018 17:47:40 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from bsd.cgi.cz (bsd.cgi.cz [178.238.45.112]) (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 92D757BD6D for ; Fri, 28 Sep 2018 17:47:39 +0000 (UTC) (envelope-from hicks@cgi.cz) Received: from hel.cgi.cz (hel [192.168.66.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by bsd.cgi.cz (Postfix) with ESMTPS id 70874240D5F for ; Fri, 28 Sep 2018 20:06:33 +0200 (CEST) Received: from localhost (unknown [192.168.66.11]) by hel.cgi.cz (Postfix) with ESMTP id DE9AA14D924 for ; Fri, 28 Sep 2018 19:48:15 +0200 (CEST) Received: from hel.cgi.cz ([192.168.66.6]) by localhost (antispam1.cgi.cz [192.168.66.11]) (amavisd-new, port 10024) with LMTP id 3RMdVTwYWXUH for ; Fri, 28 Sep 2018 19:47:36 +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 6A83214D919 for ; Fri, 28 Sep 2018 19:48:14 +0200 (CEST) Received: from [192.168.8.136] (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 40F3684AFF for ; Fri, 28 Sep 2018 19:48:14 +0200 (CEST) Subject: Re: New bhyve user To: freebsd-virtualization@freebsd.org References: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net> From: Jakub Chromy Message-ID: <449d4e47-f4c7-263b-761a-afb634755994@cgi.cz> Date: Fri, 28 Sep 2018 19:47:37 +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: <201809281630.w8SGUuB4078064@pdx.rh.CN85.dnsmgr.net> Content-Language: en-GB Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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, 28 Sep 2018 17:47:40 -0000 > You seemed to have heard incorrectly. There is little to no issues > overcommiting CPU's in bhyve, I have a 2 core, 4 thread system with > 6 VM's, each vm using 1 vCPU, this is a 50% overcommit and it my > base line load. No I have not. As far as you stick with 1 vCPU per virtual host, you should be fine. The problem is with multi-core VMs and spinlocks: https://lists.freebsd.org/pipermail/freebsd-virtualization/2018-July/006613.html quote from Alan Somers below: An anonymous BHyve expert has explained things to me off-list. Details below. On Tue, Jul 24, 2018 at 3:30 PM, Alan Somers > wrote: >/What are people's experiences with overcommitting CPUs in BHyve? I have />/an 8-core machine that often runs VMs totalling up to 5 allocated CPUs />/without problems. But today I got greedy. I assigned 8 cores to one VM />/for a big build job. Obviously, some of those were shared with the host. />/I also assigned it 8GB of RAM (out of 16 total). Build performance fell />/through the floor, even though the host was idle. Eventually I killed the />/build and restarted it with a more modest 2 make jobs (but the VM still had />/8 cores). Performance improved. But eventually the system seemed to be />/mostly hung, while I had a build job running on the host as well as in the />/VM. I killed both build jobs, which resolved the hung processes. Then I />/restarted the host's build alone, and my system completely hung, with />/top(1) indicating that many processes were in the pfault state. />//>/So my questions are: />/1) Is it a known problem to overcommit CPUs with BHyve? />// Yes it's a problem, and it's not just BHyve. The problem comes from stuff like spinlocks. Unlike normal userland locks, when two CPUs contend on a spinlock both are running at the same time. When two vCPUs are contending on a spinlock, the host has no idea how to prioritize them. Normally that's not a problem, because physical CPUs are always supposed to be able to run. But when you overcommit vCPUs, some of them must get swapped out at all times. If a spinlock is being contended by both a running vCPU and a swapped out vCPU, then it might be contended for a long time. The host's scheduler simply isn't able to fix that problem. The problem is even worse when you're using hyperthreading (which I am) because those eight logical cores are really only four physical cores, and spinning on a spinlock doesn't generate enough pipeline stalls to cause a hyperthread switch. So it's probably best to stick with the n - 1 rule. Overcommitting is ok if all guests are single-cored because then they won't use spinlocks. But my guests aren't all single-cored. 2) Could this be related to the pfault hang, even though the guest was idle >/at the time? />// The expert suspects the ZFS ARC was competing with the guest for RAM. IIUC, ZFS will sometimes greedily grow its ARC by swapping out idle parts of the guest's RAM. But the guest isn't aware of this behavior, and will happily allocate memory from the swapped-out portion. The result is a battle between the ARC and the guest for physical RAM. The best solution is to limit the maximum amount of RAM used by the ARC with the vfs.zfs.arc_max sysctl. More info:https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222916 Thanks to everyone who commented, especially the Anonymous Coward. -Alan Jakub From owner-freebsd-virtualization@freebsd.org Sat Sep 29 11:05: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 4524A10C3810 for ; Sat, 29 Sep 2018 11:05:57 +0000 (UTC) (envelope-from darcy@druid.net) Received: from mail.vex.net (mail.vex.net [98.158.139.68]) by mx1.freebsd.org (Postfix) with ESMTP id C027977111 for ; Sat, 29 Sep 2018 11:05:56 +0000 (UTC) (envelope-from darcy@druid.net) Received: from dilbert.druid.net (dilbert.druid.net [207.35.13.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: darcy) by mail.vex.net (Postfix) with ESMTPSA id D6BE24A47919 for ; Sat, 29 Sep 2018 07:05:49 -0400 (EDT) Subject: Re: New bhyve user To: freebsd-virtualization@freebsd.org References: <2edf93d1-58c2-92bc-48e2-92a493a36e7e@druid.net> <2a95db911caf43afba6408423597533c@SERVER.ad.usd-group.com> <4fa7f24d-1d77-0c62-22ef-6b6f8172798a@druid.net> From: D'Arcy Cain Openpgp: preference=signencrypt Message-ID: Date: Sat, 29 Sep 2018 07:05:49 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.0 MIME-Version: 1.0 In-Reply-To: <4fa7f24d-1d77-0c62-22ef-6b6f8172798a@druid.net> Content-Type: text/plain; charset=utf-8 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: Sat, 29 Sep 2018 11:05:57 -0000 On 9/28/18 11:07 AM, D'Arcy Cain wrote: >>> I tried to boot into a Linux install but even though I set grahics to yes, it doesn't seem to be serving VNC. On the console I can only get into the live CD. How do I get it installed? >> >> Did you have uefi="yes" in the configuration? Graphics are only available when using UEFI boot. > > Yes. I copied it right off the web site. For future searches I found the problem. I can connect to VNC OK if I just run from a regular terminal but it fails in screen. I am not sure why as it seemed OK when I connected to a FreeBSD host running vncconnect manually. However, I have a new issue. The install goes fine right up to near the end when it fails with a "Executing 'grub-install /dev/vda' failed" error and the install fails. A second attempt says that there is a system already on the disk but it won't boot up and leaves the console at a grub prompt. I have grub2-bhyve installed. Here is my config: guest="linux" uefi="yes" loader="grub" grub_run_partition="msdos1" cpu=2 memory=1024 network0_type="virtio-net" network0_switch="public" network0_mac="22:22:22:22:22:03" disk0_type="virtio-blk" disk0_name="disk0.img" uuid="532fb166-c1bb-11e8-9e80-b4b52fcc4894" graphics="yes" xhci_mouse="yes" -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 788 2246 (DoD#0082) (eNTP) | what's for dinner. IM: darcy@Vex.Net, VoIP: sip:darcy@druid.net From owner-freebsd-virtualization@freebsd.org Sat Sep 29 11:34:55 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 01DF0109715F for ; Sat, 29 Sep 2018 11:34:55 +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 92A3B77CE0 for ; Sat, 29 Sep 2018 11:34:54 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 57B35109715A; Sat, 29 Sep 2018 11:34:54 +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 465131097158 for ; Sat, 29 Sep 2018 11:34:54 +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 DBF7B77CDE for ; Sat, 29 Sep 2018 11:34:53 +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 3680D15599 for ; Sat, 29 Sep 2018 11:34:53 +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 w8TBYrs7006903 for ; Sat, 29 Sep 2018 11:34:53 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8TBYrXF006902 for virtualization@FreeBSD.org; Sat, 29 Sep 2018 11:34:53 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 231797] [hyper-v] hn driver drops UDP traffic with EIO error when TXCSUM_IPV6 flag on Date: Sat, 29 Sep 2018 11:34:53 +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 Some People X-Bugzilla-Who: linimon@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: assigned_to short_desc 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, 29 Sep 2018 11:34:55 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231797 Mark Linimon changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|bugs@FreeBSD.org |virtualization@FreeBSD.org Summary|hn driver drops UDP traffic |[hyper-v] hn driver drops |with EIO error when |UDP traffic with EIO error |TXCSUM_IPV6 flag on |when TXCSUM_IPV6 flag on --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Sat Sep 29 23:05:12 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 547DD10AE12E for ; Sat, 29 Sep 2018 23:05:12 +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 E66378B77D for ; Sat, 29 Sep 2018 23:05:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AA8F610AE12D; Sat, 29 Sep 2018 23:05:11 +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 9931810AE12C for ; Sat, 29 Sep 2018 23:05:11 +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 367818B779 for ; Sat, 29 Sep 2018 23:05:11 +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 6BA1619600 for ; Sat, 29 Sep 2018 23:05:10 +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 w8TN5Asu017932 for ; Sat, 29 Sep 2018 23:05:10 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8TN5Axs017931 for virtualization@FreeBSD.org; Sat, 29 Sep 2018 23:05:10 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 231430] 'Fatal trap 9: general protection fault while in kernel mode' when rebooting after installkernel on VirtualBox VM Date: Sat, 29 Sep 2018 23:05:10 +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: crash X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yasu@utahime.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, 29 Sep 2018 23:05:12 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231430 --- Comment #7 from Yasuhiro KIMURA --- While updating from ALPHA7 to ALPHA8, reboot succeeded without crash. So th= is problem may be resolved. But just in case I would like to wait next update = to check if crash doesn't happen before closing this problem report. --=20 You are receiving this mail because: You are the assignee for the bug.=