From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 16 11:09:28 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B6006A41 for ; Mon, 16 Feb 2015 11:09:28 +0000 (UTC) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.h3q.com", Issuer "Thawte DV SSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 08D8877E for ; Mon, 16 Feb 2015 11:09:27 +0000 (UTC) Received: (qmail 8180 invoked from network); 16 Feb 2015 11:09:18 -0000 Received: from mail.h3q.com (HELO mail.h3q.com) (cryx) by mail.h3q.com with ESMTPS (DHE-RSA-CAMELLIA256-SHA encrypted); 16 Feb 2015 11:09:18 -0000 Message-ID: <54E1CFDE.5050200@h3q.com> Date: Mon, 16 Feb 2015 12:09:18 +0100 From: Philipp Wuensche User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: Peter Grehan Subject: Re: bhyve and PCI Passthrough a USB Controller References: <54DC8B98.4090902@h3q.com> <54DD321C.80808@freebsd.org> In-Reply-To: <54DD321C.80808@freebsd.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 11:09:28 -0000 Peter Grehan wrote: > > Would you be willing to try a patch that relaxes that check ? Yes! The system isn't in production yet so I can try out stuff. >> Any suggestions for known to be working USB Controllers with bhyve and >> PCI passthrough? > > I've not tried with any discrete cards, but any XHCI controller that > has the table and PBA regions either in separate BARs or not in the same > 4K region (recommended behaviour in the PCIe spec) should be fine. I ordered another controller with an uPD720200 chipset, maybe this one will work out of the box. Greetings, Philipp From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 16 19:49:15 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8186CF5B; Mon, 16 Feb 2015 19:49:15 +0000 (UTC) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::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 13A2C798; Mon, 16 Feb 2015 19:49:15 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id k48so31028625wev.3; Mon, 16 Feb 2015 11:49:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=GiKdzDMIiEFz7yQnIIfw4v0/u8wz5jA5xOmNLbtOMp0=; b=DdUpZGYlw8viAG0wAWBNO9pjtSJFebD4hnrCWa7vBZwrzNCWPApNcDaFUwTg1qAKGr dhjFWXvHFkloESvMgbY2KLqjUQv3X0i8hbwoKorHJ74tUG3QMVSZWUJkbbB1rwc/0JAb eTTKj6YSxQhawavWFj2wQZ14NdzYvTbml7K+M+nOOJyxFAs/yibzwX7RPn84IcGCRTSn gZ8MOMTxy4MgtxTmajOJgf9qHi7gcyEgC5AcWsr4/ZCN6OZOkGR41AowvVfOMOjYBrrg d/9E1ZBCyhvsoEBtbJ2QigQq0sq1jRBxOSzxbyRRznryJQt7E0wdL24ZBB7SNlIMaOey AGPQ== MIME-Version: 1.0 X-Received: by 10.194.94.1 with SMTP id cy1mr52522296wjb.127.1424116152850; Mon, 16 Feb 2015 11:49:12 -0800 (PST) Received: by 10.27.91.79 with HTTP; Mon, 16 Feb 2015 11:49:12 -0800 (PST) In-Reply-To: <54E1CFDE.5050200@h3q.com> References: <54DC8B98.4090902@h3q.com> <54DD321C.80808@freebsd.org> <54E1CFDE.5050200@h3q.com> Date: Mon, 16 Feb 2015 11:49:12 -0800 Message-ID: Subject: Re: bhyve and PCI Passthrough a USB Controller From: Neel Natu To: Philipp Wuensche Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Feb 2015 19:49:15 -0000 Hi Philipp, On Mon, Feb 16, 2015 at 3:09 AM, Philipp Wuensche wrote: > Peter Grehan wrote: >> >> Would you be willing to try a patch that relaxes that check ? > > Yes! The system isn't in production yet so I can try out stuff. > Can you try this patch? https://people.freebsd.org/~neel/patches/bhyve_ignore_unsupported_pba.patch best Neel >>> Any suggestions for known to be working USB Controllers with bhyve and >>> PCI passthrough? >> >> I've not tried with any discrete cards, but any XHCI controller that >> has the table and PBA regions either in separate BARs or not in the same >> 4K region (recommended behaviour in the PCIe spec) should be fine. > > I ordered another controller with an uPD720200 chipset, maybe this one > will work out of the box. > > Greetings, > Philipp > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freebsd.org" From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 18 10:02:56 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A2317A3 for ; Wed, 18 Feb 2015 10:02:56 +0000 (UTC) Received: from mail.h3q.com (mail.h3q.com [213.73.89.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.h3q.com", Issuer "Thawte DV SSL CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 2DAF0E30 for ; Wed, 18 Feb 2015 10:02:55 +0000 (UTC) Received: (qmail 35691 invoked from network); 18 Feb 2015 10:02:46 -0000 Received: from mail.h3q.com (HELO mail.h3q.com) (cryx) by mail.h3q.com with ESMTPS (DHE-RSA-CAMELLIA256-SHA encrypted); 18 Feb 2015 10:02:46 -0000 Message-ID: <54E46344.607@h3q.com> Date: Wed, 18 Feb 2015 11:02:44 +0100 From: Philipp Wuensche User-Agent: Postbox 3.0.11 (Macintosh/20140602) MIME-Version: 1.0 To: Neel Natu Subject: Re: bhyve and PCI Passthrough a USB Controller References: <54DC8B98.4090902@h3q.com> <54DD321C.80808@freebsd.org> <54E1CFDE.5050200@h3q.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 18 Feb 2015 10:02:56 -0000 Neel Natu wrote: > Hi Philipp, > > On Mon, Feb 16, 2015 at 3:09 AM, Philipp Wuensche wrote: >> Peter Grehan wrote: >>> Would you be willing to try a patch that relaxes that check ? >> Yes! The system isn't in production yet so I can try out stuff. >> > > Can you try this patch? > https://people.freebsd.org/~neel/patches/bhyve_ignore_unsupported_pba.patch Just works! I'm seeing the usb controller from within the VM and I can use it. >From within the VM: xhci0: mem 0xc0004000-0xc0005fff irq 40 at device 7.0 on pci0 xhci0: 64 byte context size. usbus0 on xhci0 ugen0.2: at usbus0 umass0: on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:0:0:-1: Attached to scbus0 da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 da0: Removable Direct Access SCSI-4 device da0: Serial Number 22110508350000010125 da0: 400.000MB/s transfers da0: 15300MB (31334400 512 byte sectors: 255H 63S/T 1950C) da0: quirks=0x2 xhci0@pci0:0:7:0: class=0x0c0330 card=0x00151912 chip=0x00151912 rev=0x02 hdr=0x00 vendor = 'Renesas Technology Corp.' class = serial bus subclass = USB # usbconfig list ugen0.1: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA) ugen0.2: at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON (224mA) Greetings, Philipp From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 19 13:56:48 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 86E40F01 for ; Thu, 19 Feb 2015 13:56:48 +0000 (UTC) Received: from SNT004-OMC4S46.hotmail.com (snt004-omc4s46.hotmail.com [65.54.51.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "*.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49D82943 for ; Thu, 19 Feb 2015 13:56:47 +0000 (UTC) Received: from SNT150-W95 ([65.55.90.201]) by SNT004-OMC4S46.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Thu, 19 Feb 2015 05:55:41 -0800 X-TMN: [ypdfDX2TQOm83B/csm0E6FhZzYj96n51] X-Originating-Email: [mrashutosh@hotmail.com] Message-ID: From: Ashutosh Kumar To: "freebsd-virtualization@freebsd.org" Subject: AHCI disks have same serial number on Bhyve Date: Thu, 19 Feb 2015 13:55:40 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 19 Feb 2015 13:55:41.0418 (UTC) FILETIME=[BF9474A0:01D04C4B] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 13:56:48 -0000 Hi All=0A= =0A= =0A= =0A= We are running FreeNAS on Bhyve with 2 AHCI disks and are=0A= trying to add them using ZFS Volume Manager in FreeNAS with Encryption. The= =0A= disks fail to add with following error:=0A= =0A= =0A= =0A= MultipleObjectsReturned at /storage/volumemanager/=0A= =0A= get() returned more than one Disk -- it returned 2!=0A= =0A= =0A= =0A= =0A= =0A= FreeNAS uses disk serial number as identifier. We found that=0A= on Bhyve all AHCI controllers return common disk serial number i.e. =911234= 56=92.=0A= See attached screenshot. Due to this FreeNAS is not able to uniquely identi= fy=0A= an AHCI disk when encryption support is enabled. Kindly let us know if an= =0A= update to AHCI driver is in work to fix this issue.=0A= =0A= =20 RegardsAshutosh = From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 19 14:02:57 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBDCFAE for ; Thu, 19 Feb 2015 14:02:57 +0000 (UTC) Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::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 6BC77A0F for ; Thu, 19 Feb 2015 14:02:57 +0000 (UTC) Received: by mail-qa0-f43.google.com with SMTP id bm13so5758692qab.2 for ; Thu, 19 Feb 2015 06:02:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-type; bh=MpS48uz1IC3i2l5UAzxuMdY92oCLoqtqebR9Q2/BWeU=; b=kIBujThhPBnZ7LpETFPwzdQLkMajhdkAIfTS0VCa6M76lcjcEpUkmo+1EWQDpdjgyu Wwesv5qFSvaDHRX1Z1biC0qxQbcVDPqiVc4NS64j4C9NSb9MxRgu8lrwOaC9bdcctcds I1U2g9j5h1C6kLPIfYwZjsaIsUAaWZc6Q5jdWOnlQVdh2g4mCHzmwWxs/xH9fKagmZYV qI7rdNBF9x6EWqVGpkszleU/MMvQJZrXqkFIHrU+6ieJT3yZhifce5aPJ6C3R9H+nXLd i19rJ0r7YWjVbGpJ7jnRn5cme1vmBAFhwmse9TGrMQIV1pQbpnKAGq8kUdWTCGDsb73p QcuQ== X-Received: by 10.140.132.197 with SMTP id 188mr12822325qhe.24.1424354576615; Thu, 19 Feb 2015 06:02:56 -0800 (PST) Received: from shawn-work-laptop.localnet ([2001:470:e4fc:1::1017]) by mx.google.com with ESMTPSA id u5sm19853175qap.18.2015.02.19.06.02.55 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Feb 2015 06:02:55 -0800 (PST) From: Shawn Webb To: freebsd-virtualization@freebsd.org Subject: Re: AHCI disks have same serial number on Bhyve Date: Thu, 19 Feb 2015 09:02:57 -0500 Message-ID: <2322995.6d02k2RsH7@shawn-work-laptop> User-Agent: KMail/4.14.1 (Linux/3.16.0-30-generic; KDE/4.14.1; x86_64; ; ) In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1516860.d76Y0a5QYB"; micalg="pgp-sha1"; protocol="application/pgp-signature" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 14:02:57 -0000 --nextPart1516860.d76Y0a5QYB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" On Thursday, February 19, 2015 01:55:40 PM Ashutosh Kumar wrote: > FreeNAS uses disk serial number as identifier. We found that > on Bhyve all AHCI controllers return common disk serial number i.e. > =E2=80=98123456=E2=80=99. See attached screenshot. Due to this FreeNA= S is not able to > uniquely identify an AHCI disk when encryption support is enabled. Ki= ndly > let us know if an update to AHCI driver is in work to fix this issue.= Looks like your screenshot got scrubbed. Post it on a site like imgur? Thanks, Shawn --nextPart1516860.d76Y0a5QYB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAABAgAGBQJU5e0RAAoJEGqEZY9SRW7uOsAP/3cpkCbEuvS00AUxUekb72cL hv9srcP25NHWquvuG4loGVpspjz3h+XbBWNm+Kc4O8acQe3w1hSj4dQ45CI85pS+ Yp8+SKWJEST4Y8zJa+ZVdTEOwailuyX0+LAv1hl0HujhO1Xsbsn9z0p3csXjp9r0 D6rviSD9SCAa83JHj7yIXtobF+T6tSneMd1eLDbGiryxmBG2jW85S2x/uZQQz4yy ACwWlyj8mFL6i9ztS1SImkPOWvBQbE6FxE9eR4eh/NhcbaclTPfDF+lGb6aBT8Tz f4n2X+WACfIYUxVZrvhyTZQlNjmYLufdfkoHqZnzv/+Y1XPezwaPvMxzJuxJH+pn LoYX1N8Bg1eI2hSIJsa47LD6dPhGA3PBWEPBW8HzaLjJ+/U+WSLN9Z7eOt1bWmn8 Ey+CXs1a0dySS9D5X8fIFQSovVc2uMMXrr4+1KQ/Zn8Hkb1QtmH7VAO1KwLmkrG5 Pc6cxiy9J85Jc1taIxseR3ZTLAnQ5BspvukdMXJvMR+z2QCU+2CB0pJX4DExG+xA T+JtgzoOSLJBf6E1/k/Q01F1jLAiUNL+loDHVGrmczOzjWTaBpVz/fH37biv42ws n39X8/uYzMY364FzQbIfKtcNdkuxtUyVQTYtK8Jc9EXmJii06nAJFIKiBahw+3Di ffovq7ff51Wu+tqGFm6g =f+n1 -----END PGP SIGNATURE----- --nextPart1516860.d76Y0a5QYB-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 19 15:41:36 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D5FDC285 for ; Thu, 19 Feb 2015 15:41:36 +0000 (UTC) Received: from iredmail.onthenet.com.au (iredmail.onthenet.com.au [203.13.68.150]) (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 8DA91769 for ; Thu, 19 Feb 2015 15:41:36 +0000 (UTC) Received: from localhost (iredmail.onthenet.com.au [127.0.0.1]) by iredmail.onthenet.com.au (Postfix) with ESMTP id 386ED28110C for ; Fri, 20 Feb 2015 01:41:33 +1000 (EST) X-Amavis-Modified: Mail body modified (using disclaimer) - iredmail.onthenet.com.au X-Virus-Scanned: amavisd-new at 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 10024) with ESMTP id IRQXIdfjYw9M for ; Fri, 20 Feb 2015 01:41:33 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-76-126-65-88.hsd1.ca.comcast.net [76.126.65.88]) by iredmail.onthenet.com.au (Postfix) with ESMTPSA id 793362810BD; Fri, 20 Feb 2015 01:41:30 +1000 (EST) Message-ID: <54E60428.3090306@freebsd.org> Date: Thu, 19 Feb 2015 07:41:28 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Ashutosh Kumar Subject: Re: AHCI disks have same serial number on Bhyve References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Feb 2015 15:41:36 -0000 Hi Ashutosh, > FreeNAS uses disk serial number as identifier. We found that > on Bhyve all AHCI controllers return common disk serial number i.e. ‘123456’. > See attached screenshot. Due to this FreeNAS is not able to uniquely identify > an AHCI disk when encryption support is enabled. Kindly let us know if an > update to AHCI driver is in work to fix this issue. Known problem. The fix is to do what the virtio-blk emulation does, which is to use an md5 hash of the backing file/device name, and improve on that with an optional override similar to how MAC addresses are handled. It's on the todo list. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 21 23:48:52 2015 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 008EC496 for ; Sat, 21 Feb 2015 23:48:51 +0000 (UTC) Received: from smp5.smallcatbrain.com (m222-2.dsl.rawbw.com [198.144.222.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smp5.smallcatbrain.com", Issuer "PositiveSSL CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4C6B9CC for ; Sat, 21 Feb 2015 23:48:50 +0000 (UTC) Received: from smp5.smallcatbrain.com (smp5 [192.168.0.3]) by smp5.smallcatbrain.com (8.15.1/8.14.9) with ESMTPS id t1LNmiLx032715 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 21 Feb 2015 15:48:44 -0800 (PST) (envelope-from rdunkle@smallcatbrain.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=smallcatbrain.com; s=mail; t=1424562524; bh=g2ddw0xI6L9DxGdtAQIDVFv9toOLxVkx6ZGSuEpiwQg=; h=Date:From:To:Subject; b=ruUYKXOqA2YZxdDVSx9S2hEeo4phtsX4vdeuTitXA7tH+qbFcVWDZs/EZ7RXp9fCJ hI2xPey192KA8zSFKNm+OeoejFyxUWGm9inH9HE4HYU/ndwbPaES98BDAxBosRAgtP ImG4pv/EaLSXZin6HbYRdEa93Nt4/c/iT+/QEYZU= X-Authentication-Warning: smp5.smallcatbrain.com: Host smp5 [192.168.0.3] claimed to be smp5.smallcatbrain.com Message-ID: <54E9195C.5080708@smallcatbrain.com> Date: Sat, 21 Feb 2015 15:48:44 -0800 From: Rich Dunkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: openbsd 5.7 beta - not booting completely in bhyve Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 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, 21 Feb 2015 23:48:52 -0000 I am using FreeBSD 11 CURRENT r278872. I have an OpenBSD 5.7 beta image that was running on VirtualBox. I converted the vdi image using qemu-img. When I boot the OpenBSD with Bhyve I notice that the boot drive is not recognized the same as in VirtualBox. VirtualBox - wd0a Bhyve - sd0a I have to manually enter sda0 during the boot process. The OpenBSD slices are recognized and booting continues. I see: starting local daemons: cron. Then the date. At that point OpenBSD appears hung.