From owner-freebsd-virtualization@freebsd.org Sun May 20 02:27:10 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 D46A1EEE6E0 for ; Sun, 20 May 2018 02:27:10 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-yw0-x22b.google.com (mail-yw0-x22b.google.com [IPv6:2607:f8b0:4002:c05::22b]) (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 6F0516A2FD for ; Sun, 20 May 2018 02:27:10 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-yw0-x22b.google.com with SMTP id i17-v6so3565817ywg.13 for ; Sat, 19 May 2018 19:27:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=to:from:subject:message-id:date:user-agent:mime-version :content-transfer-encoding:content-language; bh=ylw8YrAcNq4LuLp44IZC3x8TBRwyfWabg7KcR7L/Q4c=; b=uZGA9k41JxqgLu+uxuDSr+2HQjuqOo7QPtlAofO2fXa3Cu2jz1r7j2FtuixLajaUt1 wO6eDSppQE1EeqWR2RyZuX2EWlBrh4BpUbkX/KOviEp06SVH8sWDPYEvDkM5VvnCyEN6 tjjd3Z3CPCrEk0rRUmlngdyJEq2wgtsITJFe1jKJ0f7wE+3dn2MjmYITlfXJfGT3gA4r hPMmTeA5zrIvCRXHA1FOHX/ZEBJ9qN2EBF/yIwt4UIRK3qTiPcxZLNoz6xvlCl4j8RuE TyS1oLshI1PwSwXRPWgMrpwFoxlcbC+D0RTjFpS220Acvsf4UVH6xBoIhfdtvmzAeAwG ASLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:from:subject:message-id:date:user-agent :mime-version:content-transfer-encoding:content-language; bh=ylw8YrAcNq4LuLp44IZC3x8TBRwyfWabg7KcR7L/Q4c=; b=ILgWgxt/NjexdSb3xJZKPKgWJdCpeVQPhlzp/qDiMiXLouv00ltMBIcLYJ8nJ8QoUH eO+kELQfkTsPuQnJhpf/K5KiWoMpbdp5DT1qhoxFnaPthRutnjIju6OVywkK6goisNVV /1tVxU3JRV4qA41Ov07eEIGLAD6HPYCWnLhx3E2eSdLas25/dL5mJfzzWgVZUTiVTsdC naPsK95zoKj/ulgOsMDwmo90UdQ9I8k3hfQ2samNsUvha0v0+SWonPCnO276MY0mzBUI 9kyXKel5NcQ0vw1shevk0ZPWPlfaDa5NF6TtvQ0tKCKWKUfzAGwbOn7qEThiIbmFswki izWw== X-Gm-Message-State: ALKqPwdLM6qnDJwnFTU3AImcunX7+436M+4onu9HF2EelVzosaVIZOSL 2d3ilOsaS0OvFCgflbt6SaTdgFEa X-Google-Smtp-Source: AB8JxZpxPVXI8YVsKDjmOmQGtw/Qo/eNNgbx1fw/+R2DcsHDkea6yErEw1MUlLUQJOmMWFkBuAPFCg== X-Received: by 2002:a0d:e187:: with SMTP id k129-v6mr7694112ywe.138.1526783229339; Sat, 19 May 2018 19:27:09 -0700 (PDT) Received: from [172.16.1.28] (c-98-194-61-92.hsd1.tx.comcast.net. [98.194.61.92]) by smtp.gmail.com with ESMTPSA id 130-v6sm1057942ywo.10.2018.05.19.19.27.08 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 19 May 2018 19:27:08 -0700 (PDT) To: freebsd-virtualization From: Rajil Saraswat Subject: Ubuntu 18.04 and bhyve Message-ID: Date: Sat, 19 May 2018 21:25:57 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 02:27:11 -0000 Hello, Has anybody managed to run Ubuntu 18.04 under bhyve? I was unable to get it working with churchers vm-bhyve tool. Thanks From owner-freebsd-virtualization@freebsd.org Sun May 20 03:16:39 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 89DC7EF01F0 for ; Sun, 20 May 2018 03:16:39 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 0611A6C057 for ; Sun, 20 May 2018 03:16:38 +0000 (UTC) (envelope-from grehan@freebsd.org) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) by alto.onthenet.com.au (Postfix) with ESMTPS id 6FE9B20B1AE7 for ; Sun, 20 May 2018 13:16:30 +1000 (AEST) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 6B8212809C1 for ; Sun, 20 May 2018 13:16:30 +1000 (AEST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au Received: from iredmail.onthenet.com.au ([127.0.0.1]) by localhost (iredmail.onthenet.com.au [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id nHG_4rCmBxgF for ; Sun, 20 May 2018 13:16:30 +1000 (AEST) Received: from [192.168.0.158] (unknown [121.214.88.156]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 4959D28095C; Sun, 20 May 2018 13:16:29 +1000 (AEST) Subject: Re: Ubuntu 18.04 and bhyve To: Rajil Saraswat References: Cc: freebsd-virtualization From: Peter Grehan Message-ID: Date: Sun, 20 May 2018 13:16:33 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-CMAE-Score: 0 X-CMAE-Analysis: v=2.3 cv=dNCIZtRb c=1 sm=1 tr=0 a=A6CF0fG5TOl4vs6YHvqXgw==:117 a=BuMYOwswHvrwJGShGEMWwA==:17 a=IkcTkHD0fZMA:10 a=VUJBJC2UJ8kA:10 a=O-tgrqTcMFYIQ4BmYvQA:9 a=QEXdDO2ut3YA:10 wl=host:3 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 03:16:39 -0000 > Has anybody managed to run Ubuntu 18.04 under bhyve? > > I was unable to get it working with churchers vm-bhyve tool. You either need the latest UEFI port, or run it under grub-bhyve. later, Peter. From owner-freebsd-virtualization@freebsd.org Sun May 20 03:23:42 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 5EEA7EF06CC for ; Sun, 20 May 2018 03:23:42 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (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 F40926C5F4 for ; Sun, 20 May 2018 03:23:41 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id EAC7787628; Sat, 19 May 2018 21:17:34 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Y3kCly1cYtAH; Sat, 19 May 2018 21:17:34 -0600 (MDT) Received: from [10.0.10.181] (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sat, 19 May 2018 21:17:34 -0600 (MDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (1.0) Subject: Re: Ubuntu 18.04 and bhyve From: Rebecca Cran X-Mailer: iPhone Mail (15E302) In-Reply-To: Date: Sat, 19 May 2018 21:17:29 -0600 Cc: freebsd-virtualization Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Rajil Saraswat X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 03:23:42 -0000 Could you give us some more information, such as what went wrong, and any er= ror messages? Rebecca=20 Sent from my phone > On May 19, 2018, at 8:25 PM, Rajil Saraswat wrote: >=20 > Hello, >=20 > Has anybody managed to run Ubuntu 18.04 under bhyve? >=20 > I was unable to get it working with churchers vm-bhyve tool. >=20 > Thanks >=20 > _______________________________________________ > 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 Sun May 20 05:00:18 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 D716AEF3C38 for ; Sun, 20 May 2018 05:00:17 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (vm1982.vellance.net [79.99.187.212]) (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 5B0EF6FB14 for ; Sun, 20 May 2018 05:00:17 +0000 (UTC) (envelope-from mail@osfux.nl) Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 9175F201FC for ; Sun, 20 May 2018 06:53:32 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1526792013; bh=eqtr9Yjgd214WSb1uPkf0Hg5VwTls5I2PiFe1Alhcw4=; h=Subject:To:References:From:Date:In-Reply-To; b=ThQ2TTGp8EDOUQIulQW9kBeHb7xhyN3COqg4L91UdG64fMlmBOQcUNDZLZzzliR9K 0GRKFd1OAjHwNQF84Vc9XiPaG/tRpuNvWl2+Nt+ZyjUraG2y1QAygchJKKQvRTZWUy px5iwAB8FLoR+KDKPT+QJ0dzJ60uxNYLfa75SPMf9g22i19qVKEh9DmhHoUmcuxEgM ckLmJ5oqUimk7H4JYaelr3OghZFbB/9gMwEaOE89H1ENLbuCEWevKXkD14ssgqHCPF kBuz0IEakgNPTFuzF6Hc0q0vpx3mzfRrtDLjPhXuYI5GLiT4/W+MOGmO6e26QoVT80 R4bQF4iPmXfprwhq8eJhM0JVh/hUCbqy9o4+dFrcjyUgmr6gaIfqMMIVJDx/9sNbLO x0FE21Npd+cSBXT3FYyEl/R5ORgs88MBMYKmi7GUmTLzczkvLfDD3OcuZKCYHDsSTc BBKs3JolOwSQvZ7ya99Erk/IDMWc50lKCt/g+/bZSdc1CtS776RBNkYutUwfrmpfu1 jE/3L1WtmJWkEaURVuqS9brdonfpDj6xaR8Om9dUHHHt7IU2R9bMshFwR7ddLjqz1T D03EpY2WPoyBKr3nCPlNnFhIVD7e2pcZQSP+dJGO2uyVkMLDL4th7ia5gVEtLwwZHf 9SYwsTKB3S0eyq8v4KZZQCj8= Received: from vm1982.vellance.net (localhost [127.0.0.1]) by vm1982.vellance.net (Postfix) with ESMTP id 3AB5E20142 for ; Sun, 20 May 2018 06:53:30 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=osfux.nl; s=default; t=1526792012; bh=eqtr9Yjgd214WSb1uPkf0Hg5VwTls5I2PiFe1Alhcw4=; h=Subject:To:References:From:Date:In-Reply-To; b=QbJuJCdOss6Me3ctEJZjdhTgNJrbNqnIQE5fL5Cgfj8A8kUcB+O+V0uOZ0vgoZAYU zPXNQcwxJrPTlI7anlyctYi7rhP7PDnCNv/gt2tCVVY71wWby30zIa5EXAeILBDbcS OOTkQFBieZiybqjeZcU75eOAnZpb/0uK7mVnxxiSWR1X28GV9N8GJWNQJyVYc8U6QB N6AiMbgPkGJol1CgYpq+cAjNQUQhv3sk0Zoc33hKam3Ot23qmC0t8u8S2dtq1vunh2 GZzw4vcWym8QfTAJ8qoC5d0UG0CMilDMwEsOnuEsf7mtwtOF+IpLZMs2W3JgAJARqb n/43Z31BfpaMAo3Hp78pj5RiQt/t72YhGtjKyQP/rifxJDaPZL+1rMGXmQwF+kIE5d qhn1y8BGLqeew2faTb85G31ZTTZ2SCj+qdNdtIM2w3mK42hZcp3Ppb/O0KvNQRW6IT vD+dMCtW8KwiemXk4gOt1p1QjuPNcG5KWZrfKsf/a/XCyBGB1bqidC0A2yXrG2iMgs UvAgY5MqQzex2YLmy2NtdXKUyfkr+9Mta5DznZ0WbhnJvgXBdcbe5aCL17mQZbgbAA XVfcTdB0lnrRvE3cIslUrtTVh/IwRobcM3mHxc7iPU0avVO64Q1KmwhX90CqO0ZmkO knVnvTZRxfzeynkOQgd3SzLU= X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on vm1982.vellance.net X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from rubens-MacBook-Air.local (unknown [82.171.119.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by vm1982.vellance.net (Postfix) with ESMTPSA for ; Sun, 20 May 2018 06:53:29 +0200 (CEST) Subject: Re: Ubuntu 18.04 and bhyve To: freebsd-virtualization@freebsd.org References: From: Ruben Message-ID: <348a31e5-a4e5-3fe0-2762-f87f9a6ccef5@osfux.nl> Date: Sun, 20 May 2018 06:53:54 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 05:00:18 -0000 Hi Raji, Runs fine with recent grub-bhyve (only using "server edition" vms, dunno about the desktop stuff). Regards, Ruben On 20/05/2018 04:25, Rajil Saraswat wrote: > Hello, > > Has anybody managed to run Ubuntu 18.04 under bhyve? > > I was unable to get it working with churchers vm-bhyve tool. > > Thanks > > _______________________________________________ > 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 Sun May 20 07:50: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 0224DEAAA4C for ; Sun, 20 May 2018 07:50:52 +0000 (UTC) (envelope-from fkr@grummel.net) Received: from smtp2.fra.bytemine.net (smtp2.fra.bytemine.net [91.212.95.46]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9666475343 for ; Sun, 20 May 2018 07:50:51 +0000 (UTC) (envelope-from fkr@grummel.net) Received: from hoza05.fra.bytemine.net ([91.212.95.158]) by smtp2.fra.bytemine.net with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1fKInx-0000RK-T7; Sun, 20 May 2018 07:30:57 +0000 Received: from ip5f5acb85.dynamic.kabel-deutschland.de ([95.90.203.133] helo=[192.168.11.17]) by hoza05.fra.bytemine.net with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1fKIns-0007DN-LQ; Sun, 20 May 2018 09:30:52 +0200 Subject: Re: Ubuntu 18.04 and bhyve To: Rajil Saraswat Cc: freebsd-virtualization References: From: Felix Kronlage Message-ID: <50173e44-90ed-2f5d-4d79-ada3defca7cd@grummel.net> Date: Sun, 20 May 2018 09:30:50 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 PostboxApp/6.0.8 MIME-Version: 1.0 In-Reply-To: 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.26 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, 20 May 2018 07:50:52 -0000 Hi Rjil, Rajil Saraswat wrote: > Has anybody managed to run Ubuntu 18.04 under bhyve? > I was unable to get it working with churchers vm-bhyve tool. worked for me just fine (also using `vm-bhyve`). I did the following: * grabbed the server live iso (http://ftp.uni-kl.de/pub/linux/ubuntu.iso/18.04/ubuntu-18.04-live-server-amd64.iso) via `vm iso url` * installed * halted and edited the config of the vm and added the line grub_run_partition="2" I've written a few lines about the install here as well: https://hazardous.org/archive/blog/2018/05/17/ubuntu1804-vs-bhyve And mainly I followed this post: https://www.davd.eu/install-ubuntu-on-freebsd-with-bhyve/ hope this helps, felix From owner-freebsd-virtualization@freebsd.org Sun May 20 08:38:44 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 59DD2EAC59A for ; Sun, 20 May 2018 08:38:44 +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 E6ED9768B9 for ; Sun, 20 May 2018 08:38:43 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id AB29CEAC599; Sun, 20 May 2018 08:38:43 +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 986B4EAC598 for ; Sun, 20 May 2018 08:38:43 +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 3546A768B6 for ; Sun, 20 May 2018 08:38:43 +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 7869B15065 for ; Sun, 20 May 2018 08:38:42 +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 w4K8cglo079802 for ; Sun, 20 May 2018 08:38:42 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4K8cgsf079801 for virtualization@FreeBSD.org; Sun, 20 May 2018 08:38:42 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 225558] [bhyve][patch] Add option to specify emulated NIC in vmrun.sh Date: Sun, 20 May 2018 08:38:42 +0000 X-Bugzilla-Reason: CC 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: patch X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: johalun0@gmail.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: rgrimes@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status 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.26 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, 20 May 2018 08:38:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225558 Johannes Lundberg changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|New |Closed --- Comment #9 from Johannes Lundberg --- Merged --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-virtualization@freebsd.org Sun May 20 13:29: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 E0505EE0F9B for ; Sun, 20 May 2018 13:29:29 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: from mail-yb0-x22d.google.com (mail-yb0-x22d.google.com [IPv6:2607:f8b0:4002:c09::22d]) (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 726C47F54C for ; Sun, 20 May 2018 13:29:29 +0000 (UTC) (envelope-from rajil.s@gmail.com) Received: by mail-yb0-x22d.google.com with SMTP id e7-v6so333089ybn.9 for ; Sun, 20 May 2018 06:29:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=PEs1rfk1U2NMYOatEMYA4JRVvxBIRdDTi36sT08OlbQ=; b=ibbylEcCHXoS/0/81eoHbJRfKWthOACqwsI5nIDpx7g/6l+pmrW71Z3E05E5rINOeg cwq1Rmx1kb/yVeqAWyBYJQUMB5lN4QOvuBTggQo6Z5WS9ynKABzITQ+05i5cg37qfGrg u5epyCUpxQuOszSDZ+Lf69DeRLomzf8FL/+IQopCAiDyZ1+thHMb5fF6i8A6X8okELwT hfFhB4/LkRE19G/ZrTXXvRVqtP2QMdzUwgm/OSwo5zQBl2TM8hFB5s1twfripOFxCnZ+ 0c7ZEsUClFHfO5Qp7e+sknlBlQPOPP5kPN8igZnMWZQQgtErZ4yXjrclehMudl3kVx8o aQXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=PEs1rfk1U2NMYOatEMYA4JRVvxBIRdDTi36sT08OlbQ=; b=r498zjw0PKJpXS6xOWDKzweSQbo/GlElbDyyFJB2aw3trkXVDcjvvWZR4Q2XKhJDue LirGMDpHbSYEq5XWlS0zf5vMEQPzUaTSilmXiu6b462B2/GYOxKVtjFhyd52hpaKBM3K TGyQjJoghQOOBwSgAQIUgpeIocgAiBRlH9+nAEeMG2nRrDKtGURqOGbUnlsY3+BH+f28 rFPf+6bDl39h+2t5HzLf3/1/aHsxNhG7CVTXnVfF4V3IEGYhGZlgci1ihxWUF57nViP4 85OPsUCa5qkbiE/LNe3+zXlnOyhAoTtVPN4/SH8T6alZ8hKhrMFYZ3kIeyeNUhgV1zmc QIDQ== X-Gm-Message-State: ALKqPwfCzjkfMycpAYjchuA+d6hrkfRLp0I/MsyQQbtt/cALA+CavqwV 7Heph9S1zySqQomRr4DuPVjO/LTl X-Google-Smtp-Source: AB8JxZp189+Eehzd/XOuMTKRqg9F2DXuVyO3zdGccPT6gmoPD+kQL+ke5o78w8I/k4mMlzBNHqxYcw== X-Received: by 2002:a25:b282:: with SMTP id k2-v6mr9167040ybj.254.1526822968580; Sun, 20 May 2018 06:29:28 -0700 (PDT) Received: from [172.16.1.28] (c-98-194-61-92.hsd1.tx.comcast.net. [98.194.61.92]) by smtp.gmail.com with ESMTPSA id z67-v6sm4680629ywd.50.2018.05.20.06.29.27 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 20 May 2018 06:29:27 -0700 (PDT) Subject: Re: Ubuntu 18.04 and bhyve To: freebsd-virtualization References: <50173e44-90ed-2f5d-4d79-ada3defca7cd@grummel.net> From: Rajil Saraswat Message-ID: <87ecc5c2-47bc-a130-55df-c8564656ea2e@gmail.com> Date: Sun, 20 May 2018 08:28:17 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <50173e44-90ed-2f5d-4d79-ada3defca7cd@grummel.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 13:29:30 -0000 On 05/20/2018 02:30 AM, Felix Kronlage wrote: > > * halted and edited the config of the vm and added the line > > grub_run_partition="2" > > Thanks, after sticking this in the config it boots up fine. From owner-freebsd-virtualization@freebsd.org Sun May 20 19:04: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 8EEDAEEC973 for ; Sun, 20 May 2018 19:04:21 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (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 301EA6BF1A for ; Sun, 20 May 2018 19:04:20 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-ot0-x22c.google.com with SMTP id n3-v6so14566429ota.5 for ; Sun, 20 May 2018 12:04:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=pAmvaFH8qcqcoJQhM9odUulVdJozgy4ELBjpu+Ee+Fo=; b=WTvgJ9pM2JHRNnoB8gz0foii83+2hVHWDoJQbNIFrwGiVA76iyZmpQTm3iH7eXGQ60 O62phaRNQzoBdatD9bNsax8fv80Hy/TxLODD4Qf+FtMXFMjPtdPv6CsYxUrBYVl8fxuD +bkfkKL9Xm0Uk6XhjKrp86OvE37AZ4cv9rkyU= 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=pAmvaFH8qcqcoJQhM9odUulVdJozgy4ELBjpu+Ee+Fo=; b=rUrUuZA9blgcBjIQM4jncQOP2sgEGcgSgjH2uGvNidHT8WxqTentUG71BgZ9qI+H5H LFeoCjfLkurf8z7TUOERTtI8+1pFR5QrDTDib0L7RXn+XerjKjJnWCiL4Suzzyh+JYQp esXD5Q4yleqAwLgf00PZ+jSqxj55j3CaBWRauAwTYexTgWDtt5MJhatEFYtThQCrVRku u1h8GtS1MefvixnwqJESw0vEnkITDlbdYi5jPDUymDyknVhUcBsoaKNAMvlyEIBEZj1I mjzLaEEThfJhb2RJM6BFs7Scn+LSlzgLKbzVsFp/Tl8JZLlwaYfM3hIb6gKC44NCODvs rsfg== X-Gm-Message-State: ALKqPwdmy+Q49NF+i7Wsro+oGPXJ0uXerbKhsur2N14yJBhlRMT827ga HXW9f2W0AlQwIwtoEfftR3W5PemiF0SyrIofKE/a8A== X-Google-Smtp-Source: AB8JxZrHhm+g+BWoNRGZpt61xsAOUdj3qbOYeQTxaZP3MRaTDTZ3zgCrzLacIAofF7BLT+jyby5hh3Ej9YAfhht4Y3g= X-Received: by 2002:a9d:1ec2:: with SMTP id n60-v6mr10837062otn.24.1526843060043; Sun, 20 May 2018 12:04:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.201.19.65 with HTTP; Sun, 20 May 2018 12:04:19 -0700 (PDT) In-Reply-To: <7167ea46-ee07-8ffa-615e-0f3d3eb92e64@palmen-it.de> References: <7167ea46-ee07-8ffa-615e-0f3d3eb92e64@palmen-it.de> From: Mario Lobo Date: Sun, 20 May 2018 16:04:19 -0300 Message-ID: Subject: Re: bhyve: passthrough of PCIe device without MSI possible? To: Felix Palmen Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 19:04:21 -0000 Hi Felix; I had the same impression and I was attempting to do the same with no success. Have you managed to make it work? 2018-05-11 12:26 GMT-03:00 Felix Palmen : > I have the following PCIe card on a host running 11.1-RELEASE: > > | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 > rev=0x14 hdr=0x00 > | vendor = 'OpenVox Communication Co. Ltd.' > | class = simple comms > > it doesn't support MSI according to `pciconf -lbc`: > > | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 > rev=0x14 hdr=0x00 > | bar [10] = type Memory, range 32, base 0xdfe00000, size 524288, > enabled > > Trying to pass this card to a guest using `vm-bhyve` gives me the > following in `bhyve.log`: > > | bhyve: failed to initialize MSI for PCI 5/0/0 > > and this in `vm-byve.log`: > > | [bhyve options: -c 2 -m 2G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd > -U 9f2546f5-5464-11e8-8b52-d05099c0f275 -S] > | [bhyve devices: -s 0,hostbridge -s 31,lpc -s > 4:0,virtio-blk,/dev/zvol/zroot/vm/pbx/disk0 -s > 5:0,virtio-net,tap2,mac=58:9c:fc:00:d7:6b -s 6:0,passthru,5/0/0 -s > 7:0,fbuf,tcp=0.0.0.0:5900] > | [bhyve console: -l com1,/dev/nmdm0A] > | [bhyve iso device: -s 3:0,ahci-cd,/var/vm/.config/null.iso] > | starting bhyve (run 1) > | bhyve exited with status 1 > > Now .. is it actually possible to pass such a device to a bhyve guest? > From the code comment here: > ve/pci_passthru.c#L257> > I assumed MSI would be "emulated" if necessary? > > TIA, Felix > > -- > Dipl.-Inform. Felix Palmen ,.//.......... > {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de > {pgp public key} http://palmen-it.de/pub.txt // """"""""""" > {pgp fingerprint} ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubs > cribe@freebsd.org" > -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] From owner-freebsd-virtualization@freebsd.org Sun May 20 21:00:09 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 AF65DEEF389 for ; Sun, 20 May 2018 21:00:09 +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 4D6C36FF2C for ; Sun, 20 May 2018 21:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 0DE78EEF37F; Sun, 20 May 2018 21:00:09 +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 EF5BFEEF37E for ; Sun, 20 May 2018 21:00:08 +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 8E99E6FF24 for ; Sun, 20 May 2018 21:00:08 +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 D214F1B7A0 for ; Sun, 20 May 2018 21:00:07 +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 w4KL07CT053761 for ; Sun, 20 May 2018 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4KL07ae053758 for virtualization@FreeBSD.org; Sun, 20 May 2018 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <201805202100.w4KL07ae053758@kenobi.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: Problem reports for virtualization@FreeBSD.org that need special attention Date: Sun, 20 May 2018 21:00:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 20 May 2018 21:00:09 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 212820 | FreeBSD 10-STABLE from latest HEAD and 11-RELEASE 1 problems total for which you should take action. From owner-freebsd-virtualization@freebsd.org Tue May 22 12:59:26 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 E1993EF4E12 for ; Tue, 22 May 2018 12:59:25 +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 7C1D973005 for ; Tue, 22 May 2018 12:59:25 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 39476EF4E11; Tue, 22 May 2018 12:59:25 +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 25136EF4E10 for ; Tue, 22 May 2018 12:59:25 +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 B077773000 for ; Tue, 22 May 2018 12:59:24 +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 E939210E46 for ; Tue, 22 May 2018 12:59:23 +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 w4MCxNqt085377 for ; Tue, 22 May 2018 12:59:23 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4MCxNwa085376 for virtualization@FreeBSD.org; Tue, 22 May 2018 12:59:23 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 228335] [patch] virtio indirect descriptors should use contiguous memory Date: Tue, 22 May 2018 12:59:24 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nreilly@blackberry.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.26 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, 22 May 2018 12:59:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228335 --- Comment #2 from Nick Reilly --- I'm actually taking the FreeBSD kernel networking components and running th= em in user space on another OS. I've got the kernel malloc(9) macro'd through = to the normal system malloc() and on this OS the allocations are not physically contiguous. I get an address that is close to the end of one virtual page a= nd it spans on to the next virtual page, however these virtual pages are not physically contiguous. I don't see anything on the man page for malloc(9) that specifies that it allocates from within a single page for smaller allocations. I agree that it will because of the use of the UMA layer, but I don't see it as required. This isn't a showstopper for me, I can work around it and others are unlike= ly to run in to it. If you just want to defer this and have it come out in the switch to bus_dma(9) that's OK. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Tue May 22 19:43: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 3D28EEAD792 for ; Tue, 22 May 2018 19:43:19 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (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 B63AF86917 for ; Tue, 22 May 2018 19:43:18 +0000 (UTC) (envelope-from neelnatu@gmail.com) Received: by mail-io0-x236.google.com with SMTP id z4-v6so19922680iof.5 for ; Tue, 22 May 2018 12:43:18 -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=fH3KzzYE+SJ/Z4W4Hm19Ap5QUAwN1YXK6lWdgGdWNk0=; b=F6g/ycb000IJgoVuIWaCx3Nec7PzPMLEKo/KX64y9l0ytlAFrjKeknfdeLDod77rZp yKya4Wmj5uT5iDxc9iMN/xWtsqES5sUvwWdHWnuqKsOvw85yXOM8frRPLUnKGajQoU0x tsWSB+5FNkSJfoSWSrBCj58PpJHJfR0hCKC8Ld/WHKQV8koK9AaReauBnZazJGT6LTZO GT97AAqJr1FuFihlIhLLHMCZryHguP1KesC4pqpANj26KE6GJ0UDaaCNYp9wGWRdu0iO iT1Y0M1LNcECupUJsVjsYMu2Jr/7N5dC7d+y1sNPXppcXh15lpD8ZTCgVNdFVJY/iNIc ipbg== 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=fH3KzzYE+SJ/Z4W4Hm19Ap5QUAwN1YXK6lWdgGdWNk0=; b=jglU6wReUJaPc0U4m0KQYiDltiVk6zGwY4dsjaGL+Bfs+ENooRxbDEJ4UKqQnDJMN8 vcWSsFCzjXBKKDkRuzlw1em4D67BUQis7Qf2YAlBvBx3ux+0XjZh3bMEkgBca3voaN6Q 8FLKHe8bsOKpdAz478h0nUfdb5vGPVvNTD5vFp8APWh8QGDM28iPY0+hwQL+VxIsiJbZ qX5EbJz0rIIlvxwDg3bAc9N/DB1VtUGhO92j1lxSQIqL8QMf9sintM7xGf7zQijUbq6/ Q4+Ekp+j585lxe7Uz6DjhTRh1c4/ZRztwSJCQ07NX5JLigOfiaSyqXBuCoJKUNjKt+ez C7jw== X-Gm-Message-State: ALKqPwchayLreWmjDl4gREVhnEpED1HF6/bGOdwvu6PsgnZInArLRpxL 7f7JAOOIjENM0Gq7It9Qsi2bbzLGZ1w8/7XxhPeIZA== X-Google-Smtp-Source: AB8JxZoFTpsiWmsCb4sQaXqM0TF8PUkW0X5KrAeF7AuYCPgCBrGm2QySPPx/pwInfffsNIQPWJ0ucT0s+IwmAE3aNfc= X-Received: by 2002:a6b:b9c6:: with SMTP id j189-v6mr1811569iof.230.1527018198112; Tue, 22 May 2018 12:43:18 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:7145:0:0:0:0:0 with HTTP; Tue, 22 May 2018 12:43:17 -0700 (PDT) In-Reply-To: References: <7167ea46-ee07-8ffa-615e-0f3d3eb92e64@palmen-it.de> From: Neel Natu Date: Tue, 22 May 2018 12:43:17 -0700 Message-ID: Subject: Re: bhyve: passthrough of PCIe device without MSI possible? To: Mario Lobo Cc: Felix Palmen , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 22 May 2018 19:43:19 -0000 On Sun, May 20, 2018 at 12:04 PM, Mario Lobo wrote: > Hi Felix; > > I had the same impression and I was attempting to do the same with no > success. > > Have you managed to make it work? > > 2018-05-11 12:26 GMT-03:00 Felix Palmen : > >> I have the following PCIe card on a host running 11.1-RELEASE: >> >> | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 >> rev=0x14 hdr=0x00 >> | vendor = 'OpenVox Communication Co. Ltd.' >> | class = simple comms >> >> it doesn't support MSI according to `pciconf -lbc`: >> >> | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 >> rev=0x14 hdr=0x00 >> | bar [10] = type Memory, range 32, base 0xdfe00000, size 524288, >> enabled >> >> Trying to pass this card to a guest using `vm-bhyve` gives me the >> following in `bhyve.log`: >> >> | bhyve: failed to initialize MSI for PCI 5/0/0 >> >> and this in `vm-byve.log`: >> >> | [bhyve options: -c 2 -m 2G -Hwl bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd >> -U 9f2546f5-5464-11e8-8b52-d05099c0f275 -S] >> | [bhyve devices: -s 0,hostbridge -s 31,lpc -s >> 4:0,virtio-blk,/dev/zvol/zroot/vm/pbx/disk0 -s >> 5:0,virtio-net,tap2,mac=58:9c:fc:00:d7:6b -s 6:0,passthru,5/0/0 -s >> 7:0,fbuf,tcp=0.0.0.0:5900] >> | [bhyve console: -l com1,/dev/nmdm0A] >> | [bhyve iso device: -s 3:0,ahci-cd,/var/vm/.config/null.iso] >> | starting bhyve (run 1) >> | bhyve exited with status 1 >> >> Now .. is it actually possible to pass such a device to a bhyve guest? >> From the code comment here: >> > ve/pci_passthru.c#L257> >> I assumed MSI would be "emulated" if necessary? >> I suspect that your PCI device does not advertise the capabilities bit in its status register. MSI emulation depends on this bit being set: https://github.com/freebsd/freebsd/blob/master/usr.sbin/bhyve/pci_passthru.c#L263 I can't see any reason this wouldn't work by emulating that bit and the capabilities pointer in config space. best Neel >> TIA, Felix >> >> -- >> Dipl.-Inform. Felix Palmen ,.//.......... >> {web} http://palmen-it.de {jabber} [see email] ,//palmen-it.de >> {pgp public key} http://palmen-it.de/pub.txt // """"""""""" >> {pgp fingerprint} ED9B 62D0 BE39 32F9 2488 5D0C 8177 9D80 5ECF F683 >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubs >> cribe@freebsd.org" >> > > > > -- > Mario Lobo > http://www.mallavoodoo.com.br > FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] > _______________________________________________ > 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 Tue May 22 20:13: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 5C8C7EAE1AE for ; Tue, 22 May 2018 20:13:35 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-ot0-x235.google.com (mail-ot0-x235.google.com [IPv6:2607:f8b0:4003:c0f::235]) (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 E7D8B87747 for ; Tue, 22 May 2018 20:13:34 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by mail-ot0-x235.google.com with SMTP id m11-v6so22513705otf.3 for ; Tue, 22 May 2018 13:13:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=d3d2XTAr5GGAXjh27GtK73HYbEA32fkGqPWacB338lk=; b=Jpp1MXx7vwyzo/X+wpD6wKbLDvbTbGBD6wCW4fpcCfPlMLKjtpqOM9kCDFAm7jSto3 IO7dj7Eyp5qqitpBmPCp+9l9uIlvbsQnnl7aslJ/gPd5S6d9SOmxNM8FRQSm5KQm1Rfa KC1rycc8mMQgjyBhfqYMDp2GBC4SVcsRzdcZA= 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=d3d2XTAr5GGAXjh27GtK73HYbEA32fkGqPWacB338lk=; b=eJVB0m1VJnPdYkX5Sg2TAKS7mNK2y+NpnlkMj0NL+sKOyNC7pJ3OtlZ3Hcta8CHd7f T9MvOfyKBnvhuVYBlHt/FcGJNIlc8sBlFpMPdI/dQ0N2u7uX9qyDXuJY5rFcMA0t5ZD3 PuY3rnPsCGqeiDIROW+408wmd1ZOxVWyDxMmjwQS8Tbs0EzJKL7mJ6+rFgiWGOn50fT4 v/FYyajR1l8bQZ97fPx5N3R/pBymI2ZCJNYF26E9emtVdP1/LMAGrNMVQPwr39lZBb1N 0Ta3IPoqCfurkwbWLeCa9BECz8IkEDHq9dlLjoKXoTRY9KZuajmQUaIOjmVgvj+qPF26 Srcw== X-Gm-Message-State: ALKqPwfoib/GK6TdKyYuDlB4er8S1tXSNGZ+xN0nG/MwVkM/o9GXvJBD TrNv9QB0b4FNp0ggUgi+bvX8BccfFjZMVoKyMGlYNQ== X-Google-Smtp-Source: AB8JxZoQnNlghuRp2caKIXuai4M1b/Q10XSAUbgcsS8AqafPlNj79n/hCM5YDFbO3NN6/X8NYhjwRtsodL5u8urQMp4= X-Received: by 2002:a9d:1535:: with SMTP id u50-v6mr18447950otf.197.1527020013951; Tue, 22 May 2018 13:13:33 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:1341:0:0:0:0:0 with HTTP; Tue, 22 May 2018 13:13:33 -0700 (PDT) In-Reply-To: References: <7167ea46-ee07-8ffa-615e-0f3d3eb92e64@palmen-it.de> From: Mario Lobo Date: Tue, 22 May 2018 17:13:33 -0300 Message-ID: Subject: Re: bhyve: passthrough of PCIe device without MSI possible? To: Neel Natu Cc: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 22 May 2018 20:13:35 -0000 2018-05-22 16:43 GMT-03:00 Neel Natu : > On Sun, May 20, 2018 at 12:04 PM, Mario Lobo wrote: > > Hi Felix; > > > > I had the same impression and I was attempting to do the same with no > > success. > > > > Have you managed to make it work? > > > > 2018-05-11 12:26 GMT-03:00 Felix Palmen : > > > >> I have the following PCIe card on a host running 11.1-RELEASE: > >> > >> | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 > >> rev=0x14 hdr=0x00 > >> | vendor = 'OpenVox Communication Co. Ltd.' > >> | class = simple comms > >> > >> it doesn't support MSI according to `pciconf -lbc`: > >> > >> | ppt0@pci0:5:0:0: class=0x078000 card=0x00011b74 chip=0x08101b74 > >> rev=0x14 hdr=0x00 > >> | bar [10] = type Memory, range 32, base 0xdfe00000, size 524288, > >> enabled > >> > >> Trying to pass this card to a guest using `vm-bhyve` gives me the > >> following in `bhyve.log`: > >> > >> | bhyve: failed to initialize MSI for PCI 5/0/0 > >> > >> and this in `vm-byve.log`: > >> > >> | [bhyve options: -c 2 -m 2G -Hwl bootrom,/usr/local/share/uefi- > firmware/BHYVE_UEFI.fd > >> -U 9f2546f5-5464-11e8-8b52-d05099c0f275 -S] > >> | [bhyve devices: -s 0,hostbridge -s 31,lpc -s > >> 4:0,virtio-blk,/dev/zvol/zroot/vm/pbx/disk0 -s > >> 5:0,virtio-net,tap2,mac=58:9c:fc:00:d7:6b -s 6:0,passthru,5/0/0 -s > >> 7:0,fbuf,tcp=0.0.0.0:5900] > >> | [bhyve console: -l com1,/dev/nmdm0A] > >> | [bhyve iso device: -s 3:0,ahci-cd,/var/vm/.config/null.iso] > >> | starting bhyve (run 1) > >> | bhyve exited with status 1 > >> > >> Now .. is it actually possible to pass such a device to a bhyve guest? > >> From the code comment here: > >> >> ve/pci_passthru.c#L257> > >> I assumed MSI would be "emulated" if necessary? > >> > > I suspect that your PCI device does not advertise the capabilities bit > in its status register. > > MSI emulation depends on this bit being set: > https://github.com/freebsd/freebsd/blob/master/usr.sbin/ > bhyve/pci_passthru.c#L263 > > I can't see any reason this wouldn't work by emulating that bit and > the capabilities pointer in config space. > > best > Neel > > > Could you give us some hint on how the capabilities bit could be "faked"? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] From owner-freebsd-virtualization@freebsd.org Tue May 22 22:25: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 BC555EB1F75 for ; Tue, 22 May 2018 22:25:22 +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 4E38F6BF67 for ; Tue, 22 May 2018 22:25:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 07B07EB1F74; Tue, 22 May 2018 22:25:22 +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 C107DEB1F72 for ; Tue, 22 May 2018 22:25:21 +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 598976BF65 for ; Tue, 22 May 2018 22:25:21 +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 89D1315DC2 for ; Tue, 22 May 2018 22:25:20 +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 w4MMPKQa012964 for ; Tue, 22 May 2018 22:25:20 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4MMPKFi012958 for virtualization@FreeBSD.org; Tue, 22 May 2018 22:25:20 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, 22 May 2018 22:25:20 +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: terje@elde.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: 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.26 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, 22 May 2018 22:25:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225791 Terje Elde changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |terje@elde.net --- Comment #1 from Terje Elde --- We're also affected by this, running c5.large, handling about 13 000 connections through haproxy, then varnish and on to other systems. Activity was about 4000 requests pr. minute leading up to the crash, which doesn't s= eem all that high. It's possible that it could have spiked shortly before the crash though, without getting that in the logs. This is: FreeBSD [host snipped] 11.1-RELEASE-p8 FreeBSD 11.1-RELEASE-p8 #0: Tue Mar = 13 17:07:05 UTC 2018=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 It's a lightly modified/configured version of one of the usual FreeBSD AMIs= , I don't recall the AMI ID exactly, sorry. Kernel etc is stock, we've just ma= de additions in terms of software etc for our own AMI. We have two virtually identical machines exposed under the same hostname, receiving a near identical load, and have so far only been noticing this wi= th one of the machines. Could be coincidental, but figured it worthwhile to mention. It strikes me as noteworthy that the data rate was only about 700kBps at the last data point I have before the crash. Unfortunately I don't know anythi= ng about packet rate, and again it's possible that there could have been a peak leading up to the crash, without getting the logs of it. If anyone is interested in any other data from this, please do let me know.= =20 Also, this is part of a redundant setup, allowing some extra room for moving things around if anyone wants anything tested or tried on the setup. >> Crash itself: Limiting open port RST response from 457 to 200 packets/sec Limiting open port RST response from 487 to 200 packets/sec Limiting open port RST response from 541 to 200 packets/sec Limiting open port RST response from 517 to 200 packets/sec Limiting open port RST response from 586 to 200 packets/sec Limiting open port RST response from 237 to 200 packets/sec ena0: Found a Tx that wasn't completed on time, qid 1, index 324. pid 3639 (varnishd), uid 429: exited on signal 6 Limiting open port RST response from 259 to 200 packets/sec Limiting open port RST response from 380 to 200 packets/sec ena0: Found a Tx that wasn't completed on time, qid 1, index 181. Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x1c fault code =3D supervisor write data, page not present instruction pointer =3D 0x20:0xffffffff82173f8c stack pointer =3D 0x28:0xfffffe0110f43180 frame pointer =3D 0x28:0xfffffe0110f43260 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 12 (irq261: ena0) trap number =3D 12 panic: page fault cpuid =3D 0 KDB: stack backtrace: #0 0xffffffff80aadac7 at kdb_backtrace+0x67 #1 0xffffffff80a6bba6 at vpanic+0x186 #2 0xffffffff80a6ba13 at panic+0x43 #3 0xffffffff80ee3092 at trap_fatal+0x322 #4 0xffffffff80ee30eb at trap_pfault+0x4b #5 0xffffffff80ee290a at trap+0x2ca #6 0xffffffff80ec3d40 at calltrap+0x8 #7 0xffffffff80a321ec at intr_event_execute_handlers+0xec #8 0xffffffff80a324d6 at ithread_loop+0xd6 #9 0xffffffff80a2f845 at fork_exit+0x85 #10 0xffffffff80ec4a0e at fork_trampoline+0xe Uptime: 8d22h59m55s Rebooting... >> boot log: Copyright (c) 1992-2017 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.1-RELEASE-p8 #0: Tue Mar 13 17:07:05 UTC 2018 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 4.0.0 (tags/RELEASE_400/final 297347) (based on LLVM 4.0.0) VT(vga): text 80x25 CPU: HammerEM64T (3000.05-MHz K8-class CPU) Origin=3D"GenuineIntel" Id=3D0x50653 Family=3D0x6 Model=3D0x55 Steppi= ng=3D3 =20 Features=3D0x1f83fbff =20 Features2=3D0xfffa3203 AMD Features=3D0x2c100800 AMD Features2=3D0x121 Structured Extended Features=3D0xd11f4fbb Structured Extended Features2=3D0x8 XSAVE Features=3D0xf TSC: P-state invariant, performance statistics Hypervisor: Origin =3D "KVMKVMKVM" real memory =3D 5114953728 (4878 MB) avail memory =3D 3844890624 (3666 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 hardware threads random: unblocking device. ioapic0 irqs 0-23 on motherboard SMP: AP CPU #1 Launched! random: entropy device external interface kbd1 at kbdmux0 netmap: loaded module module_register_init: MOD_LOAD (vesa, 0xffffffff80f5eb40, 0) error 19 random: registering fast source Intel Secure Key RNG random: fast provider: "Intel Secure Key RNG" nexus0 vtvga0: on motherboard cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 atrtc0: port 0x70-0x71,0x72-0x77 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 pci0: at device 1.3 (no driver attached) vgapci0: mem 0xfe400000-0xfe7fffff at device 3.0 on pci0 vgapci0: Boot video device nvme0: mem 0xfebf0000-0xfebf3fff irq 11 at device 4.0= on pci0 ena0: mem 0xfebf4000-0xfebf7fff at device 5.0 on pci0 ena0: Elastic Network Adapter (ENA)ena v0.7.0 ena0: initalize 2 io queues ena0: Ethernet address: 02:2b:3a:f4:70:8c ena0: Allocated msix_entries, vectors (cnt: 3) nvme1: mem 0xfebf8000-0xfebfbfff irq 11 at device 31.= 0 on pci0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] uart0: port 0x3f8-0x3ff irq 4 f= lags 0x10 on acpi0 uart0: console (115200,n,8,1) orm0: at iomem 0xef000-0xeffff on isa0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 attimer0: at port 0x40 on isa0 Timecounter "i8254" frequency 1193182 Hz quality 0 attimer0: Can't map interrupt. ppc0: cannot reserve I/O port range ena0: link is UP ena0: link state changed to UP Timecounters tick every 1.000 msec usb_needs_explore_all: no devclass nvme cam probe device init nvme0: temperature threshold not supported nvd0: NVMe namespace nvd0: 20480MB (41943040 512 byte sectors) nvme1: temperature threshold not supported nvd1: NVMe namespace GEOM: nvd1: corrupt or invalid GPT detected. nvd1: 20480MB (41943040 512 byte sectors) GEOM: nvd1: GPT rejected -- may not be recoverable. Trying to mount root from ufs:/dev/gpt/rootfs [rw]... --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed May 23 05:20: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 2255BEEF99C for ; Wed, 23 May 2018 05:20:43 +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 AF4BB77D47 for ; Wed, 23 May 2018 05:20:42 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 73EEBEEF99A; Wed, 23 May 2018 05:20:42 +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 61610EEF999 for ; Wed, 23 May 2018 05:20:42 +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 F247A77D41 for ; Wed, 23 May 2018 05:20:41 +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 378A3196C4 for ; Wed, 23 May 2018 05:20:41 +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 w4N5Kf6C006984 for ; Wed, 23 May 2018 05:20:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4N5KfbK006982 for virtualization@FreeBSD.org; Wed, 23 May 2018 05:20:41 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 228335] [patch] virtio indirect descriptors should use contiguous memory Date: Wed, 23 May 2018 05:20:40 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: bryanv@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.26 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: Wed, 23 May 2018 05:20:43 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228335 --- Comment #3 from Bryan Venteicher --- While the malloc(9) behavior may not be documented, VirtIO is not alone in depending on the behavior. In fact, bus_dmamem_alloc(9) uses malloc(9) for = <=3D PAGE_SIZE allocations (given suitable alignment and attributes) so you may still be susceptible to this depending on what kernel interfaces have been reimplemented. Also, note there is a strong assumpting in the network stack= and drivers that mbuf clusters (including jumbo) are physically contiguous. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed May 23 10:27:47 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 5D997EF82F9 for ; Wed, 23 May 2018 10:27:47 +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 B05B282A97 for ; Wed, 23 May 2018 10:27:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 60A6FEF82F2; Wed, 23 May 2018 10:27:46 +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 4865BEF82F1 for ; Wed, 23 May 2018 10:27:46 +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 F2E2382A91 for ; Wed, 23 May 2018 10:27:45 +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 189B61C27A for ; Wed, 23 May 2018 10:27:45 +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 w4NARiG8086879 for ; Wed, 23 May 2018 10:27:44 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4NARiqZ086877 for virtualization@FreeBSD.org; Wed, 23 May 2018 10:27:44 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 187006] [hyper-v] dynamic address (dhcp) obtaining doesn't work on HYPER-V OS 2012 R2 Date: Wed, 23 May 2018 10:27:44 +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: unspecified X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: eadler@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status 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.26 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: Wed, 23 May 2018 10:27:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D187006 Eitan Adler changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Progress |Open --- Comment #8 from Eitan Adler --- batch change of PRs untouched in 2018 marked "in progress" back to open. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Wed May 23 16:41:20 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 6FDC4F1E507 for ; Wed, 23 May 2018 16:41:20 +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 06DF372A71 for ; Wed, 23 May 2018 16:41:20 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id B6F73F1E504; Wed, 23 May 2018 16:41:19 +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 A5626F1E503 for ; Wed, 23 May 2018 16:41:19 +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 443B672A6B for ; Wed, 23 May 2018 16:41:19 +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 840371F7F1 for ; Wed, 23 May 2018 16:41:18 +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 w4NGfIF3038501 for ; Wed, 23 May 2018 16:41:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w4NGfIrm038500 for virtualization@FreeBSD.org; Wed, 23 May 2018 16:41:18 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 228335] [patch] virtio indirect descriptors should use contiguous memory Date: Wed, 23 May 2018 16:41:18 +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: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: nreilly@blackberry.com X-Bugzilla-Status: Closed X-Bugzilla-Resolution: Works As Intended X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: virtualization@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution 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.26 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: Wed, 23 May 2018 16:41:20 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D228335 Nick Reilly changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Closed Resolution|--- |Works As Intended --- Comment #4 from Nick Reilly --- Closing because this is working as intended. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-virtualization@freebsd.org Fri May 25 06:07:42 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 AC64BF7397C for ; Fri, 25 May 2018 06:07:42 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 2591973E12 for ; Fri, 25 May 2018 06:07:41 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1fM5iS-000G5J-TJ for freebsd-virtualization@freebsd.org; Fri, 25 May 2018 08:56:40 +0300 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: bhyve client: who is hosting me? Message-Id: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> Date: Fri, 25 May 2018 08:56:40 +0300 To: freebsd-virtualization@freebsd.org X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 25 May 2018 06:07:42 -0000 Hi, I=E2=80=99m trying out bhyve with different setups, but mailny FreeBSD = (11.2 and 12), and was wondering if there is any way for the client to know who is hosting = it? thanks, danny From owner-freebsd-virtualization@freebsd.org Fri May 25 07:02:59 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 A9BB8F74973 for ; Fri, 25 May 2018 07:02:59 +0000 (UTC) (envelope-from dariusmihaim@gmail.com) Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (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 4BB467587F for ; Fri, 25 May 2018 07:02:59 +0000 (UTC) (envelope-from dariusmihaim@gmail.com) Received: by mail-qt0-x235.google.com with SMTP id c2-v6so5330488qtn.9 for ; Fri, 25 May 2018 00:02:59 -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:content-transfer-encoding; bh=tbT4nZ/qtpQf4+ItLkQWtLSYC5dV5ywy9iqh5LoyZs8=; b=JlioNI27bBf54fQgGcK0lpxRek/NsbajBIWxYQkaok4tYla6HFgmy/wh8D1rujuXgz tOLySGGyojHe0b1L45Ki9YPMj2qWWa4gDk/NGIsUg/3EcZTaTK8wylIbK7HqIfsIGqOn 2u9Q2lR0OcAjOQYahN5K6GitzP8Zxu4tsVrHkl2gm4uhIEdvLct2Qmkkew71CdW8LTin BGxfWgDPh7NagtElbg5wLy4zXPzaV7exK66o3l9igSri87NvRgMeoXYswyepMeMe41Fx iDIu8f9KwC/UUjJWViViSwJUn8en5TbtVDNbueFyLzzqE3Cp/Gv6AsFc36PF85uhSj91 4bEA== 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:content-transfer-encoding; bh=tbT4nZ/qtpQf4+ItLkQWtLSYC5dV5ywy9iqh5LoyZs8=; b=XVC8h2WXr1Ufxmgr9FEfalbrwzAZqZa6etP5ifTL+zJWHqiksTq1gq98+oga7aCSVu ajjb3+HVaepU6WYaHjwAzsukfCFhIs36rJlrpCAqNtvlQwjkVG4gBwyMmqW/y/hKGjPA Vql3IdP+D8XFzt7+rnGVt1gv37s1SFcZPtBo5l111hcvkjz6Nr5ViWDCyWCz1FSuRvv4 dtbH+pUPNcD9Qerkjb+2Ue//tH8Th6rdov0hTiNY7q59PeVMjV9yxbLMkiRqgRJgtlxq Zv/rjFnw3gYuB+kyKJuuS81+gJb1mrM+U0nCsoWnpHJINGGkpJ1+2mdCGmCD9NcVPd+O 7Qjw== X-Gm-Message-State: ALKqPwcHFlRsTx8795lkNO+SkaDtSaczRF5+ziefiTIpkvn/uNt9Bmfs D+5PMcqoWOdsumHjBHMSfQjkQXmVoYA9dnURKVc= X-Google-Smtp-Source: ADUXVKKG4BHFYK/bX2D77fpNlWlGzCKfKfIs+FTM2SHmQ82WejSqeO2zaeEKE6m0nThMgx8wASXQjoj0634kZeLPbBw= X-Received: by 2002:ac8:2243:: with SMTP id p3-v6mr1055047qtp.201.1527231778731; Fri, 25 May 2018 00:02:58 -0700 (PDT) MIME-Version: 1.0 References: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> In-Reply-To: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> From: Darius Mihai Date: Fri, 25 May 2018 10:02:22 +0300 Message-ID: Subject: Re: bhyve client: who is hosting me? To: danny@cs.huji.ac.il Cc: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 25 May 2018 07:03:00 -0000 On Fri, May 25, 2018 at 9:08 AM Daniel Braniss wrote: > Hi, > I=E2=80=99m trying out bhyve with different setups, but mailny FreeBSD (1= 1.2 and 12), and > was wondering if there is any way for the client to know who is hosting it? > thanks, > danny Hi, What do you mean 'knowing who is hosting it?' If you mean obtaining information such as IP address or hostname of the host from inside the guest operating system, it should not be possible and is likely a security flaw if it were allowed by default. Operating systems should ideally be unable to determine even that the system is a virtual machine instead of a hardware based host; however since bhyve uses VirtIO devices and other virtualization mechanisms due to performance issues you are indeed able to determine that the OS is running in a virtual machine. More specific information should be impossible to obtain if not injected by the host (e.g., running a web server on the host with some information, adding a virtual block device with a configuration file, and so on). Darius > _______________________________________________ > 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 May 25 08:05:16 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 7FD7EF759AF for ; Fri, 25 May 2018 08:05:16 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) (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 0410A774F9 for ; Fri, 25 May 2018 08:05:15 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from bach.cs.huji.ac.il ([132.65.80.20]) by kabab.cs.huji.ac.il with esmtp id 1fM7io-000KIm-7L; Fri, 25 May 2018 11:05:10 +0300 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\)) Subject: Re: bhyve client: who is hosting me? From: Daniel Braniss In-Reply-To: Date: Fri, 25 May 2018 11:05:09 +0300 Cc: freebsd-virtualization@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <8B1DEC42-1B40-4957-AEB6-2D9BA019287F@cs.huji.ac.il> References: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> To: Darius Mihai X-Mailer: Apple Mail (2.3445.6.18) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 25 May 2018 08:05:16 -0000 > On 25 May 2018, at 10:02, Darius Mihai wrote: >=20 > On Fri, May 25, 2018 at 9:08 AM Daniel Braniss = wrote: >=20 >> Hi, >> I=E2=80=99m trying out bhyve with different setups, but mailny = FreeBSD (11.2 and > 12), and >> was wondering if there is any way for the client to know who is = hosting > it? >=20 >> thanks, >> danny >=20 > Hi, >=20 > What do you mean 'knowing who is hosting it?' > If you mean obtaining information such as IP address or hostname of = the > host from inside the guest operating system, it should not be possible = and > is likely a security flaw if it were allowed by default. ok, so not by default, but is there a way? i don=E2=80=99t know why this is a security flaw - maybe security by = obscurity? in any case since the client knows that it=E2=80=99s running as a bhive client, = (hw.hv_vendor), again, if this is also a security flaw, it could be set/reset when the client is = being configured? thanks, danny =20 >=20 > Operating systems should ideally be unable to determine even that the > system is a virtual machine instead of a hardware based host; however = since > bhyve uses VirtIO devices and other virtualization mechanisms due to > performance issues you are indeed able to determine that the OS is = running > in a virtual machine. More specific information should be impossible = to > obtain if not injected by the host (e.g., running a web server on the = host > with some information, adding a virtual block device with a = configuration > file, and so on). >=20 > Darius >=20 >> _______________________________________________ >> 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 May 25 08:07:06 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 13B97F75AEC for ; Fri, 25 May 2018 08:07:06 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 7B3FB775C2 for ; Fri, 25 May 2018 08:07:05 +0000 (UTC) (envelope-from araujobsdport@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id x9-v6so7593454wrl.13 for ; Fri, 25 May 2018 01:07:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=AiPhObcQGzDvWu9aKVEnCtPMWCO8QKQuWRbR4+g6DdU=; b=lqlfYh4mmVsawvYnxls+MC3j6Hv4m2zxTywXEYpb4m335cBC2aI1XQWYc7cCUIeT8X xo9paUGzCzEdc+XZqfOnjYXibq1i6H3ejk/9F8/sky76v0Yv6P9A4njL2PS0g9fu7j2T hsqWvSxZJr2EVc1Ah48mrp4jUlCNenmZcpHki2mExf/vluZYoq/4bYUfQy8qn4qHWflV D+KG6iayxaKYr1aOtUn4bwk3Y4UXJtZNHBwCPQhH/QxofruzVcFNhU5s8THClpwrECyk rtbg02cZtQu+Y1zKOejIMqb2Zr+BU+4k4Uly1MlgX3m2MRomVaLxP5IPxeldaDmVrilc 0e6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=AiPhObcQGzDvWu9aKVEnCtPMWCO8QKQuWRbR4+g6DdU=; b=j5WNP2DQu84eL5Tv160mHVxovN1M28qvtZqc+ys31w61qyTAcd3KURafb/4e1XknDA jXUJEwhGAquqrZHCzV5csG6s8jGi2pHNXsp++0KywZbEDYWO4mppVFnr/yjdEDH8oBZ9 5EikcWSZrpvC0ZSDbeqyzgmoyvWVcQ5oJxk46nX0CkONeOzWsx0yt5GeDg39pP9pIVPR 9W+reATTNpzRA3L2fBSNZWVgHnc4CsyAs2SIEc4Irdijf3CKl/nZ2RyoJxPbd+cgcDLq tLf/mEgY/xF3Y1CJ7XwT43lbxsCbKv3BoEtfbeCOUBrvSr69Yng4V4jXCvgCSYz8ec0S RQmw== X-Gm-Message-State: ALKqPwcLKFs1ywk3nnmIV0hR34NpwFGPqhq9QhiVhI0FdwMwsoj+khBB 5UrhLo+9hq5UkL6b6q8jNxtdcO//8INp4JeCDu0= X-Google-Smtp-Source: ADUXVKLSHbC4zsC5oAG3cUbpb8avweEPUUTGV8qHzyDyVhs4yagkdrkIk8Rg/cKoMqPQf+WZPVeKz0hjh+zv8NsVZDo= X-Received: by 2002:a19:9a10:: with SMTP id c16-v6mr819873lfe.60.1527235623988; Fri, 25 May 2018 01:07:03 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a19:1fc9:0:0:0:0:0 with HTTP; Fri, 25 May 2018 01:07:03 -0700 (PDT) Reply-To: araujo@freebsd.org In-Reply-To: <8B1DEC42-1B40-4957-AEB6-2D9BA019287F@cs.huji.ac.il> References: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> <8B1DEC42-1B40-4957-AEB6-2D9BA019287F@cs.huji.ac.il> From: Marcelo Araujo Date: Fri, 25 May 2018 16:07:03 +0800 Message-ID: Subject: Re: bhyve client: who is hosting me? To: Daniel Braniss Cc: Darius Mihai , freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 25 May 2018 08:07:06 -0000 2018-05-25 16:05 GMT+08:00 Daniel Braniss : > > > > On 25 May 2018, at 10:02, Darius Mihai wrote: > > > > On Fri, May 25, 2018 at 9:08 AM Daniel Braniss > wrote: > > > >> Hi, > >> I=E2=80=99m trying out bhyve with different setups, but mailny FreeBSD= (11.2 and > > 12), and > >> was wondering if there is any way for the client to know who is hostin= g > > it? > > > >> thanks, > >> danny > > > > Hi, > > > > What do you mean 'knowing who is hosting it?' > > If you mean obtaining information such as IP address or hostname of the > > host from inside the guest operating system, it should not be possible > and > > is likely a security flaw if it were allowed by default. > > ok, so not by default, but is there a way? > i don=E2=80=99t know why this is a security flaw - maybe security by obsc= urity? in > any case > since the client knows that it=E2=80=99s running as a bhive client, > (hw.hv_vendor), again, if > this is also a security flaw, it could be set/reset when the client is > being configured? > > thanks, > danny > > Maybe you can use virtio-console and bhyve-vm-goagent? https://github.com/freenas/bhyve-vm-goagent Best, > > > > Operating systems should ideally be unable to determine even that the > > system is a virtual machine instead of a hardware based host; however > since > > bhyve uses VirtIO devices and other virtualization mechanisms due to > > performance issues you are indeed able to determine that the OS is > running > > in a virtual machine. More specific information should be impossible to > > obtain if not injected by the host (e.g., running a web server on the > host > > with some information, adding a virtual block device with a configurati= on > > file, and so on). > > > > Darius > > > >> _______________________________________________ > >> 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" > > _______________________________________________ > 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" > --=20 --=20 Marcelo Araujo (__)araujo@FreeBSD.org \\\'',)http://www.FreeBSD.org \/ \ ^ Power To Server. .\. /_) From owner-freebsd-virtualization@freebsd.org Fri May 25 08:33:32 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 DDF83F761CC for ; Fri, 25 May 2018 08:33:31 +0000 (UTC) (envelope-from dariusmihaim@gmail.com) Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d:c09::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 53C2E7803E; Fri, 25 May 2018 08:33:31 +0000 (UTC) (envelope-from dariusmihaim@gmail.com) Received: by mail-qk0-x242.google.com with SMTP id h140-v6so3471765qke.2; Fri, 25 May 2018 01:33:31 -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:content-transfer-encoding; bh=sEvFUo4Z67Chi8SAvfhogc9lqESxAoea6t2qj7XgXr0=; b=OUHDm3s2DX47Mt5G8hFX8lkN2k1Aam4Cy/pFmKtxWETodwz+8Mm6VKP0++efmd0To/ 7IlWICYMFkMqeu3pZXERAMTRzYRmyMXbAQeRxZXD4hPSOCn5Et4mgl7BHZ5Csd1PrJiF Q0zdfpw57Q279n1cpe763htfdNpjxI8rtZ+YviTBu4syT2i+11c1L9hIiaCUfuaVTWwN M35UWN2q9Sn+n230/sxfkfhvAikTfYRPngcgFdveVuH5rzZYFZ5BNbytdMlhxotbiSJH Tvnxog8Pkh9U7EIrANUTstgUrp8oeIevhgDy/t1QO3rC7ZQawWttPjHcduHWtqRwaqu6 /P7w== 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:content-transfer-encoding; bh=sEvFUo4Z67Chi8SAvfhogc9lqESxAoea6t2qj7XgXr0=; b=qSPNzK8bP/B5li4HC18OWNYBUnxgLIA+7DhOsFE5mh2Ay1jsFJtjaMAqJfFuvdZfpu 31EIx3YmX6rMxVf7B933oQXgKltiuK7ZCPAsObCozrFi+/1jsURs+w076KumsZ3Fwd5S oLYqwtHKY2232e/S9VWLteYJt/zyWhUFnrNzzMYTeAalPWxoBdIkpsYEwAbVyzrSWRf8 iFDKJNMeVOt4xflQ3mDuFoXtLcWBfGo0fSs+bvhC2g4Fuwsgng28FDuWu14A8K/KfgEi AD2Bh3pmwhcJ11ndb1S6nll/xPdl2emdBAzHnaI6YNS2LUmi0EhsyXRu0buzMJDGcFqX ZWQg== X-Gm-Message-State: ALKqPweVvCFSucGTJj+biYidVpznIxmA8Rv7f1cAD1NYp/k2VMgLRHJl hhzN2DiOpAsLePcPQdhmH+PpYDXnT35F8WYzlic= X-Google-Smtp-Source: ADUXVKIwHgctoT/OtNzjmlaCyJKHL81xfpGx3Ee2GVX12R6lfBzB4/yXy/0XFXQm5gIhf3+vhf76iffjKECmbw0tgV4= X-Received: by 2002:a37:8202:: with SMTP id e2-v6mr1120369qkd.202.1527237210807; Fri, 25 May 2018 01:33:30 -0700 (PDT) MIME-Version: 1.0 References: <49FCEBE6-5551-42C1-8A9F-5F84ECAD0581@cs.huji.ac.il> <8B1DEC42-1B40-4957-AEB6-2D9BA019287F@cs.huji.ac.il> In-Reply-To: From: Darius Mihai Date: Fri, 25 May 2018 11:32:54 +0300 Message-ID: Subject: Re: bhyve client: who is hosting me? To: araujo@freebsd.org Cc: danny@cs.huji.ac.il, freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 25 May 2018 08:33:32 -0000 On Fri, May 25, 2018 at 11:07 AM Marcelo Araujo wrote: > 2018-05-25 16:05 GMT+08:00 Daniel Braniss : >> > On 25 May 2018, at 10:02, Darius Mihai wrote: >> > >> > On Fri, May 25, 2018 at 9:08 AM Daniel Braniss wrote: >> > >> >> Hi, >> >> I=E2=80=99m trying out bhyve with different setups, but mailny FreeBS= D (11.2 and >> > 12), and >> >> was wondering if there is any way for the client to know who is hosting >> > it? >> > >> >> thanks, >> >> danny >> > >> > Hi, >> > >> > What do you mean 'knowing who is hosting it?' >> > If you mean obtaining information such as IP address or hostname of th= e >> > host from inside the guest operating system, it should not be possible and >> > is likely a security flaw if it were allowed by default. >> ok, so not by default, but is there a way? >> i don=E2=80=99t know why this is a security flaw - maybe security by obs= curity? in any case >> since the client knows that it=E2=80=99s running as a bhive client, (hw.hv_vendor), again, if >> this is also a security flaw, it could be set/reset when the client is being configured? Not really security by obscurity. The virtual machine should be a standalone construct that leaks no outside information to a malicious entity (e.g., a compromised HTTP server that an attacker used to obtain root permissions on the virtual machine). That being said, some information (e.g., that the OS is running as a virtual machine) is required by specific drivers for virtual devices with increased performance (e.g., networking without vtnet is almost unusable; vtnet is a VirtIO device that declares a specific device number to the driver). This information is considered largely harmless, since you cannot obtain information on host IP address, name, hardware resources, host operating system version and applications, etc., but may require rework in the future if exploits based on it emerge. >> thanks, >> danny > Maybe you can use virtio-console and bhyve-vm-goagent? > https://github.com/freenas/bhyve-vm-goagent I'm not sure about how this works; on the readme it says you can read guest information. If it is bidirectional, it is similar to the webserver idea I had in mind. > Best, >> > >> > Operating systems should ideally be unable to determine even that the >> > system is a virtual machine instead of a hardware based host; however since >> > bhyve uses VirtIO devices and other virtualization mechanisms due to >> > performance issues you are indeed able to determine that the OS is running >> > in a virtual machine. More specific information should be impossible t= o >> > obtain if not injected by the host (e.g., running a web server on the host >> > with some information, adding a virtual block device with a configuration >> > file, and so on). >> > >> > Darius >> > >> >> _______________________________________________ >> >> 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" >> _______________________________________________ >> 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" > -- > -- > Marcelo Araujo (__) > araujo@FreeBSD.org \\\'',) > http://www.FreeBSD.org \/ \ ^ > Power To Server. .\. /_) Darius From owner-freebsd-virtualization@freebsd.org Sat May 26 12:46:33 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 A009BF74D4D for ; Sat, 26 May 2018 12:46:33 +0000 (UTC) (envelope-from sudh.cse@gmail.com) Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (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 3BCD96E977 for ; Sat, 26 May 2018 12:46:33 +0000 (UTC) (envelope-from sudh.cse@gmail.com) Received: by mail-io0-x233.google.com with SMTP id a10-v6so9328924ioc.9 for ; Sat, 26 May 2018 05:46:33 -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=9zob60gWNHwhhqAqDNI2BA8CgCt+V/z0KUPRunWIa7E=; b=JLXadfpoN2b8907J6THCIYIhu9okWaheYnwJ1Tuk96yclKdg4gl7NIQeFpbwenE967 vtx68cC37x2AfxqmLoZF6SFgjQONzqJt0w6L4R26GlUK4CTiJcV/oatxJULXrfFrunVL yfgQYAfcoMlh01dw7k//hiBj9om66HqCggFBRxsLAkurVGu0wc/63sWoQkg7uJ/5BVC/ gl952Qaq1LxpZkxjlsBYXRlL6ru8DbCyPFPSqE5DxRSCVfOCASfF5y58u6XGAhZBJ+0i xDwHhPqcpDjhGsPyV29FIBpAG8oH0Z93NJ0v2B675lM5Ij+HlV6n+92jQXKUrWcOQzOP 0Z4g== 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=9zob60gWNHwhhqAqDNI2BA8CgCt+V/z0KUPRunWIa7E=; b=qlzdpcYYCSx0moKAZvSLXuFpndF4CERtpOjK8mf/lbRSTM3QttDSORYJ3cqSjKSmRM IVxp6sngOKItYW3mBPWCk/Yv3IwW/Itea8YXDjt70NZsGz8RFha92SFPah5OYL794Qtf hQIdRXRk+lQgJQyKSeptYjKhKorz6pSbh1fNsUEjMaaz+4EdhY1BuYfO6x71bK6RaZQr vpmZlnASpY4p5PckmgjEYloFIOHFgsVGAQcSoTpFF+Zd/7MPsbLBXyNLsnl8FANoH6Bk lNB2zFxsc1n7uJd6CzkbuD0TSBQ49ObtXUZtew0UnzwNvexmfBqxBk8Mzw+gZ50hv8Cz zbTA== X-Gm-Message-State: ALKqPweKHpXXL6doM36OjDusDBZbvZLFFkluSI9Fwbnve34WAbFBOWpa 0fSB0YEvJ+YIFUF1mw1d4wMpQtBE1lUp0r/BCAGO+Q== X-Google-Smtp-Source: AB8JxZprnkbpq0FJT3flHQFH6srLzvwf8E5xxovyVuPmqnhJx9Z8Zc3UmnZ6+CsospwOJKdE1NWB5Usji0abixDIehA= X-Received: by 2002:a6b:a390:: with SMTP id m138-v6mr5400597ioe.116.1527338792467; Sat, 26 May 2018 05:46:32 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:1802:0:0:0:0:0 with HTTP; Sat, 26 May 2018 05:46:31 -0700 (PDT) From: Sudhanshu Saurav Date: Sat, 26 May 2018 18:16:31 +0530 Message-ID: Subject: Regarding Bhyve emulation Instructions To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.26 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, 26 May 2018 12:46:33 -0000 Hi Everyone! I am Sudhanshu Saurav from NIT Durgapur doing a project verification of bhyve emulation instructions using Intel XED tool for FreeBSD in Gsoc 2k18. I read the examples and documentation of Intel XED but still, I am facing very much difficulties in writing a Test harness for these Instructions. Actually what I understood till now https://svnweb.freebsd.org/base/head/sys/amd64/vmm/vmm_instruction_emul.c this is all the Instructions present on this link are needs to be verified by XED but Decoder of XED is taking bytes in the range from 1-15 for decode the Instructions and I think for these all instructions I have to use the only decoder of XED. please help me in emulating these Instructions with XED or any sort of help is really very helpful for me. you will guide me only for writing a Test harness for just one Instruction and verify using XED rest for all the Instructions I will do on my own. THANKS Sudhanshu