From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 16 17:54:15 2014 Return-Path: Delivered-To: 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 6EA9CC07; Sun, 16 Nov 2014 17:54:15 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 2F5C32BF; Sun, 16 Nov 2014 17:54:14 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 1A8891534C9; Sun, 16 Nov 2014 18:54:11 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C9B0SLuKELav; Sun, 16 Nov 2014 18:54:01 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:806:2b43:477a:23d] (unknown [IPv6:2001:4cb8:3:1:806:2b43:477a:23d]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 47147153416; Sun, 16 Nov 2014 18:54:01 +0100 (CET) Message-ID: <5468E4B9.5090205@digiware.nl> Date: Sun, 16 Nov 2014 18:54:01 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Peter Grehan , "freebsd-virtualization@freebsd.org" Subject: Re: Trying to run an older head in a recent Bhyve. References: <5467BC49.4080308@digiware.nl> <5467E8E6.1000509@freebsd.org> In-Reply-To: <5467E8E6.1000509@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 16 Nov 2014 17:54:15 -0000 On 16-11-2014 0:59, Peter Grehan wrote: > Hi Willem, > >> I'm trying to run one of my older VM's and get the crash below in the VM >> when trying to boot... >> >> This happens both on an older BSD: >> FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST >> 2014 >> As well as on a very recent: >> FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2014 >> >> The older 10.0 VM's do boot normally >> >> Any suggestions on what this might be, and/or how to debug this.. > > Did the disk image backing file change by any chance ? e.g. from file > to zvol ? > > What's the version of the VM that has the issue ? Not sure what you mean by that exactely, but the VM runs a relatively old HEAD: FreeBSD 11.0-CURRENT #1 r262690: Sun Mar 2 21:28:19 CET 2014 root@bhyve-head:/usr/obj/usr/src/sys/GENERIC amd64 It boots in single mode. I'tt try and manually assign an IP number and will see what that brings. --WjW From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 16 18:19:32 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 704FE5AF for ; Sun, 16 Nov 2014 18:19:32 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 30D6A6C2 for ; Sun, 16 Nov 2014 18:19:31 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 43BB170C43 for ; Sun, 16 Nov 2014 18:19:24 +0000 (UTC) Message-ID: <5468EAC7.3030601@freebsd.org> Date: Sun, 16 Nov 2014 13:19:51 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: Trying to run an older head in a recent Bhyve. References: <5467BC49.4080308@digiware.nl> <5467E8E6.1000509@freebsd.org> <5468E4B9.5090205@digiware.nl> In-Reply-To: <5468E4B9.5090205@digiware.nl> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E" 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: Sun, 16 Nov 2014 18:19:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-11-16 12:54, Willem Jan Withagen wrote: > On 16-11-2014 0:59, Peter Grehan wrote: >> Hi Willem, >> >>> I'm trying to run one of my older VM's and get the crash below in the= VM >>> when trying to boot... >>> >>> This happens both on an older BSD: >>> FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST= >>> 2014 >>> As well as on a very recent: >>> FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2= 014 >>> >>> The older 10.0 VM's do boot normally >>> >>> Any suggestions on what this might be, and/or how to debug this.. >> >> Did the disk image backing file change by any chance ? e.g. from file= >> to zvol ? >> >> What's the version of the VM that has the issue ? >=20 > Not sure what you mean by that exactely, but the VM runs a relatively > old HEAD: >=20 > FreeBSD 11.0-CURRENT #1 r262690: Sun Mar 2 21:28:19 CET 2014 > root@bhyve-head:/usr/obj/usr/src/sys/GENERIC amd64 >=20 > It boots in single mode. >=20 > I'tt try and manually assign an IP number and will see what that brings= =2E >=20 > --WjW >=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 He is asking how the virtual disk is setup, specifically, if it is a zvol= Judging by the backtrace, the VM is panicing when trying to write to the disk and it fails =46rom my experience, the two most likely causes are: 1) The disk is a zvol, and does not have the volmode set, and GEOM on the host is grabbing the disk and locking it, preventing writes 2) The VM was shutdown ungracefully and the file system needs a fsck. Since you can get into single user mode, this should be doable. --=20 Allan Jude --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUaOrKAAoJEJrBFpNRJZKfy7YP/RliVOqMVMNQHzNleJzgeyGV J2OTuLWytjyM3Y0F9iBhC0cbG6cQBAYF3L39kj4aXi8D/faW+ZNISqJuA8UcBiv2 WfZUo+t7ROfH3eWO/RYkS2n0d3fiOShrjY0G3PFX3qeuWYcAJx6MtPthWVY0lFpb 9izIMDlT+iwMobXrvkiOokaIcHZS73OyEBXBKrLT6TMV/K9SZzrcJVWPXPw3UhN7 WkfvTiLjK16OsgcezcASGmaO7ek53Wzm9ABSW49P9uAivJtzzBaUA2F941F5z1WL 1hud3z6UtIlcIbVleN/BGuOKlPfegb9vYIr9x6qaO+/CZPmQSjGqwzZcasaIukI2 HsSq7CtUOQxCY05oGf/kv/bzpUIP/b+FkUH5HZ7kPiNg59bA0v94l7gA8rfGAZSr GLDRsIuOTl3yh4LuityciPZ/nv3Z0UypwbYXZYITTpg9VKPI3tBjVReyrxT6n8mH wf3tyZoiAgKVYz4Ilp2x3qN8jmWsWKXLCUt1S2iQu28idAemiG4eB4mNGuqCEooX bnYyBh+jifqouYl8VWfLDWh8JMlIWSCf693CymlW/5+eRI38+zlDWv2K2xaU/F/6 bLXKtw0kqzinjBcCiYQ71SKBlp3P1kxwuBLqICLIGBzOwz8syYm+SAaeTyH07iL+ JkVmlUSFvsS2XPuZTb75 =TM9y -----END PGP SIGNATURE----- --3EeOcWLrrBX8CaG3DlpaP06fp40VRbk9E-- From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 16 23:09:56 2014 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 20F059BB for ; Sun, 16 Nov 2014 23:09:56 +0000 (UTC) Received: from mail1.bur200.uecomm.net.au (mail1.bur200.uecomm.net.au [218.185.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id D1D5E7DE for ; Sun, 16 Nov 2014 23:09:54 +0000 (UTC) Received: from mail.flexibledrive.com.au (unknown [115.186.196.106]) by mail1.bur200.uecomm.net.au (Postfix) with ESMTP id C1636D4E0; Mon, 17 Nov 2014 10:09:44 +1100 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.flexibledrive.com.au (Postfix) with ESMTP id 23EF3E6ADE; Mon, 17 Nov 2014 10:09:44 +1100 (EST) X-Virus-Scanned: amavisd-new at fdrive.com.au Received: from mail.flexibledrive.com.au ([127.0.0.1]) by localhost (mail.flexibledrive.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dtY27HyINiJc; Mon, 17 Nov 2014 10:09:35 +1100 (EST) Received: from ws-pross.vv.fda (ws-pross.vv.fda [192.168.50.199]) by mail.flexibledrive.com.au (Postfix) with ESMTPS id A9111E62B3; Mon, 17 Nov 2014 10:09:35 +1100 (EST) Date: Mon, 17 Nov 2014 10:09:35 +1100 (AEDT) From: Peter Ross X-X-Sender: petros@linux-vic-05.vv.fda To: Nikos Vassiliadis Subject: Re: VIMAGE and VirtualBox networking question In-Reply-To: <54677B7B.4080202@gmx.com> Message-ID: References: <54677B7B.4080202@gmx.com> User-Agent: Alpine 2.11 (LRH 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Sun, 16 Nov 2014 23:09:56 -0000 Hi Nikos, On Sat, 15 Nov 2014, Nikos Vassiliadis wrote: > On 11/11/14 00:39, Peter Ross wrote: >> >> I was not brave enough to enable VIMAGE and VirtualBox on the same >> server. But I may do that soon. I plan a major reconfiguration ca. end >> of the year. I hope it is stable enough. > > Just want to add that everything works as expected with VIMAGE and VBox. Thanks. Then I will try that too:-) Regards Peter From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 05:14:44 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 564FCDB0 for ; Mon, 17 Nov 2014 05:14:44 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 19A9ACBF for ; Mon, 17 Nov 2014 05:14:43 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 531241279B; Mon, 17 Nov 2014 15:14:41 +1000 (EST) Received: from Peters-MacBook-Pro.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZU11703 (AUTH peterg@ptree32.com.au); Mon, 17 Nov 2014 15:14:39 +1000 Message-ID: <5469843D.4010004@freebsd.org> Date: Sun, 16 Nov 2014 21:14:37 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: John-Mark Gurney Subject: Re: bhyve remote kgdb does not support kernel modules... References: <20141115093713.GY24601@funkthat.com> <20141115094340.GZ24601@funkthat.com> In-Reply-To: <20141115094340.GZ24601@funkthat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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, 17 Nov 2014 05:14:44 -0000 Hi John-Mark, >> Where those should be in the aesni.ko module... If I run kgdb on a >> local machine, it properly finds the kernel modules... Any hits on >> how to fix this? To add to Julian's reply, there's also some info in the thread starting at http://docs.FreeBSD.org/cgi/mid.cgi?5363F399.40709 > Also, any plans to support the Z2 write-watchpoint packet? > > (kgdb) watch *(char *)0xfffff80002919708 > Hardware watchpoint 1: *(char *) 18446735277659625224 > (kgdb) c > Continuing. > Can't clear hardware watchpoints without the 'Z2' (write-watchpoint) packet You'd have to write some code to glue the MI gdb/gdb_main.c packet handler to the routines in ddb/db_watch.c. (I'm sure this exists somewhere out there - certainly did at my previous workplace). If you want to take that on, we can do the other piece which is to context-switch the debug registers on guest entry/exit. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 07:46:35 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E49A8FC9; Mon, 17 Nov 2014 07:46:34 +0000 (UTC) Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DEE9C62; Mon, 17 Nov 2014 07:46:34 +0000 (UTC) Received: by mail-lb0-f176.google.com with SMTP id 10so15204176lbg.7 for ; Sun, 16 Nov 2014 23:46:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=4D2Q1NBEuceahcHQqKbIR7QdoXqzHuxlVhcNZsXbwiQ=; b=zVDesiR8Pp86l8ArcFpf/Ha9qmNOJSTHAgYtrRwxqj+QBdWCqtgtChXfXyKoO4E41V Hr1CHXtRFK0CkXiV/KW2iO7tTHZntcGQ1njy4ubYWYRcv9MOAXsJa/QtfWICOwOwLupj pz2T8778wGGjaX7GtJWCtBFfHUReXomDqqeakAz6fxMINLd2gWnyTYJFJpIjTxDc/OnT DKI+KbB0K+1f8cfO/5BluFz7Kz84TOHS8Dls9rNN9+FwLDvdPQG9ZppSj1hcJVWPReQw 0pxTgELge3VhWtCSDjX25OpWyqN6Kf9TdUfVPYNO/W60JoOS4tU7Hd51CMxEjfWSjHUv M+kw== MIME-Version: 1.0 X-Received: by 10.112.225.225 with SMTP id rn1mr1410596lbc.98.1416210392299; Sun, 16 Nov 2014 23:46:32 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sun, 16 Nov 2014 23:46:32 -0800 (PST) Date: Sun, 16 Nov 2014 23:46:32 -0800 X-Google-Sender-Auth: 7fMsckax5obPRoH-ujZxjGQN9sg Message-ID: Subject: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: freebsd-arch , FreeBSD Net , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 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: Mon, 17 Nov 2014 07:46:35 -0000 Hi, PROPOSAL ========== I would like to get feedback on the following proposal. In the head branch (CURRENT), I would like to enable VIMAGE with this commit: PATCH ====== Index: sys/conf/NOTES =================================================================== --- sys/conf/NOTES (revision 274300) +++ sys/conf/NOTES (working copy) @@ -784,8 +784,8 @@ device mn # Munich32x/Falc54 Nx64kbit/sec cards. # Network stack virtualization. -#options VIMAGE -#options VNET_DEBUG # debug for VIMAGE +options VIMAGE +options VNET_DEBUG # debug for VIMAGE # # Network interfaces: I would like to enable VIMAGE for the following reasons: REASONS ======== (1) VIMAGE cannot be enabled off to the side in a separate library or kernel module. When enabled, it is a kernel ABI incompatible change. This has impact on 3rd party code such as the kernel modules which come with VirtualBox. So the time to do it in CURRENT is now, otherwise we can't consider doing it until FreeBSD-12 timeframe, which is quite a while away. (2) VIMAGE is used in some 3rd party products, such as FreeNAS. These 3rd party products are mostly happy with VIMAGE, but sometimes they encounter problems, and FreeBSD doesn't see these problems because it is disabled by default. (3) Most of the major subsystems like ipfw and pf have been fixed for VIMAGE, and the only way to shake out the last few issues is to make it the default and get feedback from the community. ipfilter still needs to be VIMAGE-ified. (4) Not everyone uses bhyve. FreeBSD jails are an excellent virtualization platform for FreeBSD. Jails are still very popular and performant. VIMAGE makes jails even better by allowing per-jail network stacks. (5) Olivier Cochard-Labbe has provided good network performance results in VIMAGE vs. non-VIMAGE kernels: https://lists.freebsd.org/pipermail/freebsd-net/2014-October/040091.html (6) Certain people like Vitaly "wishmaster" have been running VIMAGE jails in a production environment for quite a while, and would like to see it be the default. ACTION PLAN =========== (1) Coordinate/communicate with portmgr, since this has kernel ABI implications (2) Work with clusteradm@, and try to get a test instance of one of the PF firewalls in the cluster working with a VIMAGE enabled kernel. (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO and https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=vimage%20or%20vnet and try to clean things up. Get help from net@ developers to do this. (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help from the ipfilter maintainers for this and some net@ developers. (5) Enable VIMAGE by default in CURRENT on January 5, 2015. This will *not* be enabled in STABLE. What do people think? Thanks. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 11:08:24 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD6CCA57 for ; Mon, 17 Nov 2014 11:08:24 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7B09E348 for ; Mon, 17 Nov 2014 11:08:24 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ey11so5155161pad.24 for ; Mon, 17 Nov 2014 03:08:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=LoaI3nAt93fTZvdmmEn2YhsbR0P0/uMmmTNQfu/MLWw=; b=d+MjBXQpqr3+Vyhjrb8lzVjucHcCLxeoHr28qXr4KVHmOKSrmdLt3oEEyObs1oR3UA Az4g7YRqE+cmiGIMYYsrHZBuT7Chz00ulBOjeMXEmmHYbOkKa7pdqUsE5NqX+q/bKzrv MLvHCrBgPWh3Nd3mbPTgmtgjvNl6UanIkYsRDC0T3f+U+WO9l2Z+hZrRpq0I/c/SbPiN E2Ur63ycllSrwZuurs5Bk7KDPm65cggvGnNpQpJnr33SclNXZRFMjT/ohBaf89W3AhCJ TlzOM19bsdMdRZIgpG3p3Bs6Dtf88/tq+HK+ELfmjoP6K1HIr5ZPFNmlg9b4RMg0vQym eWGQ== X-Gm-Message-State: ALoCoQmBpupp/Y6idNQa+efiGArqFxrLzVEjTm0iK23ecqB0LxTxUq5t7Cf6hZDHkgXUv9L1nM4/ X-Received: by 10.70.63.9 with SMTP id c9mr29020132pds.104.1416222169244; Mon, 17 Nov 2014 03:02:49 -0800 (PST) Received: from lgwl-achen.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id h1sm34979301pat.6.2014.11.17.03.02.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 17 Nov 2014 03:02:48 -0800 (PST) Sender: Warner Losh Content-Type: multipart/signed; boundary="Apple-Mail=_F38375C2-112A-4E06-9440-FCEC35A46B7E"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Warner Losh In-Reply-To: Date: Mon, 17 Nov 2014 04:02:38 -0700 Message-Id: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> References: To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 17 Nov 2014 11:08:24 -0000 --Apple-Mail=_F38375C2-112A-4E06-9440-FCEC35A46B7E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 17, 2014, at 12:46 AM, Craig Rodrigues = wrote: > Hi, >=20 > PROPOSAL > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > I would like to get feedback on the following proposal. > In the head branch (CURRENT), I would like to enable > VIMAGE with this commit: >=20 >=20 > PATCH > =3D=3D=3D=3D=3D=3D >=20 > Index: sys/conf/NOTES > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sys/conf/NOTES (revision 274300) > +++ sys/conf/NOTES (working copy) > @@ -784,8 +784,8 @@ > device mn # Munich32x/Falc54 Nx64kbit/sec cards. >=20 > # Network stack virtualization. > -#options VIMAGE > -#options VNET_DEBUG # debug for VIMAGE > +options VIMAGE > +options VNET_DEBUG # debug for VIMAGE >=20 > # > # Network interfaces: >=20 >=20 >=20 > I would like to enable VIMAGE for the following reasons: >=20 > REASONS > =3D=3D=3D=3D=3D=3D=3D=3D >=20 > (1) VIMAGE cannot be enabled off to the side in a separate library or > kernel module. When enabled, it is a kernel ABI incompatible = change. > This has impact on 3rd party code such as the kernel modules > which come with VirtualBox. > So the time to do it in CURRENT is now, otherwise we can't = consider > doing it until FreeBSD-12 timeframe, which is quite a while = away. >=20 > (2) VIMAGE is used in some 3rd party products, such as FreeNAS. > These 3rd party products are mostly happy with VIMAGE, > but sometimes they encounter problems, and FreeBSD doesn't > see these problems because it is disabled by default. >=20 > (3) Most of the major subsystems like ipfw and pf have been fixed for > VIMAGE, and the only > way to shake out the last few issues is to make it the default = and > get feedback from the community. ipfilter still needs to be > VIMAGE-ified. >=20 >=20 > (4) Not everyone uses bhyve. FreeBSD jails are an excellent = virtualization > platform for FreeBSD. Jails are still very popular and > performant. VIMAGE makes jails even better by allowing per-jail > network stacks. >=20 > (5) Olivier Cochard-Labbe has provided good network performance = results > in VIMAGE vs. non-VIMAGE kernels: >=20 >=20 > = https://lists.freebsd.org/pipermail/freebsd-net/2014-October/040091.html >=20 > (6) Certain people like Vitaly "wishmaster" have = been > running VIMAGE > jails in a production environment for quite a while, and would = like > to see it > be the default. >=20 >=20 > ACTION PLAN > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > (1) Coordinate/communicate with portmgr, since this has kernel ABI > implications >=20 > (2) Work with clusteradm@, and try to get a test instance of one of = the > PF firewalls in the cluster working with a VIMAGE enabled = kernel. >=20 > (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO > and > = https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=3Dvimage%20or%20= vnet > and try to clean things up. Get help from net@ developers to = do > this. And if these don=92t get cleaned up? > (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help = from > the ipfilter maintainers for this and some net@ developers. And if this doesn=92t happen? > (5) Enable VIMAGE by default in CURRENT on January 5, 2015. > This will *not* be enabled in STABLE. >=20 > What do people think? How do you plan to address the problems seen by FreeNAS in #2 above? I = don=92t see that in the action plan. Without it, we=92re enabling an = option that has know, serious issue making 11 potentially a more = unstable release. Warner --Apple-Mail=_F38375C2-112A-4E06-9440-FCEC35A46B7E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJUadXPAAoJEGwc0Sh9sBEAvYAP/iwf6hIRHekLe0WOXLKpmJJG 5Do3lUbWaKSsUMPQUVhrZCEqaktFvNl3KXREGz3vIYir6/VKUD9pHm2aKWHaH4Dh ug7BwaGnX0F+Lrs+ztE09oqkMM2e/IRYPlpXFtBkfYssSEPTVekWu5nyCeJ2/bfC fyobYns+3PvpfoLSo9NZolDT5FwwuireoAJcpQ8XDXzdRd94IQOxoXw3OZSI+uig yP076NgBxe0hfVsREUU4NoPEsmWX5EW9RXO4PcucnvoovPsUj5eGECIinpeKr+70 k9+qyhZfvuUg1bgwy33Xn+r1mVj7BYpLb2RLERfsf5C154r0ULAEzkszo16T+B8x e+JajoSRxQtjpw7VQtZLKmLzJk1xfKbndL1bKEmmq3BNyOU6U8lsb1cbQ/WamxBp SbRlx/h9viK9xIyZ0lpqtkvn5zeTSHTG6BTQMdI4e5t02lmsNB3kSE3ioMyCCNSI 5UOlDPRolosCWfyswWkLA47JE54x938SQdRcSSDXhxCCTeXRXMlyNTH0MtQKx1Ui vfINNqg95ohsLjtfdFvGKpJNTJ7t0glvtnkusNvcZc/45aO0n3s4wN8qIo+J10WA kryjtn2OyaeBL2x961vE91r3OBBH+s6RcywbLH4gfA3Lu+ACP7hI93CunwXDO80D vItyld7BvOsjk+e7pdkA =NjCp -----END PGP SIGNATURE----- --Apple-Mail=_F38375C2-112A-4E06-9440-FCEC35A46B7E-- From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 11:20:22 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 00847E4A; Mon, 17 Nov 2014 11:20:21 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (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 9C2B7640; Mon, 17 Nov 2014 11:20:21 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 22EF3153408; Mon, 17 Nov 2014 12:20:13 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dfIreQrOjHzi; Mon, 17 Nov 2014 12:20:01 +0100 (CET) Received: from [192.168.101.102] (vpn.ecoracks.nl [31.223.170.173]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 4226E153416; Mon, 17 Nov 2014 12:20:01 +0100 (CET) Message-ID: <5469D9E1.2060400@digiware.nl> Date: Mon, 17 Nov 2014 12:20:01 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Warner Losh , Craig Rodrigues Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> In-Reply-To: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 17 Nov 2014 11:20:22 -0000 On 17-11-2014 12:02, Warner Losh wrote: > > On Nov 17, 2014, at 12:46 AM, Craig Rodrigues > wrote: > >> Hi, >> >> PROPOSAL ========== I would like to get feedback on the following >> proposal. In the head branch (CURRENT), I would like to enable >> VIMAGE with this commit: >> >> >> PATCH ====== >> >> Index: sys/conf/NOTES >> =================================================================== >> >> --- sys/conf/NOTES (revision 274300) >> +++ sys/conf/NOTES (working copy) @@ -784,8 +784,8 @@ device >> mn # Munich32x/Falc54 Nx64kbit/sec cards. >> >> # Network stack virtualization. -#options VIMAGE -#options >> VNET_DEBUG # debug for VIMAGE +options VIMAGE +options >> VNET_DEBUG # debug for VIMAGE >> >> # # Network interfaces: >> >> >> >> I would like to enable VIMAGE for the following reasons: >> >> REASONS ======== >> >> (1) VIMAGE cannot be enabled off to the side in a separate library >> or kernel module. When enabled, it is a kernel ABI incompatible >> change. This has impact on 3rd party code such as the kernel >> modules which come with VirtualBox. So the time to do it in CURRENT >> is now, otherwise we can't consider doing it until FreeBSD-12 >> timeframe, which is quite a while away. >> >> (2) VIMAGE is used in some 3rd party products, such as FreeNAS. >> These 3rd party products are mostly happy with VIMAGE, but >> sometimes they encounter problems, and FreeBSD doesn't see these >> problems because it is disabled by default. >> >> (3) Most of the major subsystems like ipfw and pf have been fixed >> for VIMAGE, and the only way to shake out the last few issues is to >> make it the default and get feedback from the community. ipfilter >> still needs to be VIMAGE-ified. >> >> >> (4) Not everyone uses bhyve. FreeBSD jails are an excellent >> virtualization platform for FreeBSD. Jails are still very popular >> and performant. VIMAGE makes jails even better by allowing >> per-jail network stacks. >> >> (5) Olivier Cochard-Labbe has provided good network performance >> results in VIMAGE vs. non-VIMAGE kernels: >> >> >> https://lists.freebsd.org/pipermail/freebsd-net/2014-October/040091.html >> >> >> (6) Certain people like Vitaly "wishmaster" have been >> running VIMAGE jails in a production environment for quite a while, >> and would like to see it be the default. >> >> >> ACTION PLAN =========== >> >> (1) Coordinate/communicate with portmgr, since this has kernel >> ABI implications >> >> (2) Work with clusteradm@, and try to get a test instance of one >> of the PF firewalls in the cluster working with a VIMAGE enabled >> kernel. >> >> (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO and >> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=vimage%20or%20vnet >> >> and try to clean things up. Get help from net@ developers to do >> this. > > And if these don’t get cleaned up? > >> (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help >> from the ipfilter maintainers for this and some net@ developers. > > And if this doesn’t happen? > >> (5) Enable VIMAGE by default in CURRENT on January 5, 2015. This >> will *not* be enabled in STABLE. >> >> What do people think? > > How do you plan to address the problems seen by FreeNAS in #2 above? > I don’t see that in the action plan. Without it, we’re enabling an > option that has know, serious issue making 11 potentially a more > unstable release. Hi Warner, I think I understand your critique, but then on the other hand I wonder where the reluctance is.... As I read it, things are going to be enabled in CURRENT only (for the time). Which is exactly for the reasons you worry about: Is it going to be reliable enough?? But for that it needs exposure... So I would expect it to be turned off as a default IF things are not in a stable state that warrants a default enabling of the options. Things need to move forward, and taking this step is going to be required.. Otherwise I see a big risk of bit-rot somewhere down in the dungeons. --Willem Jan From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 11:43:02 2014 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 5506A9D8; Mon, 17 Nov 2014 11:43:02 +0000 (UTC) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 078F7961; Mon, 17 Nov 2014 11:43:01 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 3928125D388C; Mon, 17 Nov 2014 11:42:57 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id C81F6C770D8; Mon, 17 Nov 2014 11:42:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id noVUGNh3OCde; Mon, 17 Nov 2014 11:42:53 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6] (orange-tun0-ula.sbone.de [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 17AE1C77042; Mon, 17 Nov 2014 11:42:47 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: RFC: Enabling VIMAGE in GENERIC From: "Bjoern A. Zeeb" In-Reply-To: <5469D9E1.2060400@digiware.nl> Date: Mon, 17 Nov 2014 11:42:42 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <5469D9E1.2060400@digiware.nl> To: Willem Jan Withagen X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , Warner Losh , freebsd-arch 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, 17 Nov 2014 11:43:02 -0000 On 17 Nov 2014, at 11:20 , Willem Jan Withagen wrote: > I think I understand your critique, but then on the other hand I = wonder > where the reluctance is.... As I read it, things are going to be = enabled > in CURRENT only (for the time). Which is exactly for the reasons you > worry about: Is it going to be reliable enough?? No, the answer to that still is =93no=94 in it=92s current state and we = know that. I think one of the main problems is that no one has been able to pull = the thing to the end in the last three years. Why should it happen within 6 = weeks now? I think it would be a really good idea to do that but the current TODO = list, I think, is by far not sufficing. There=92s a second problem we=92ll hit in that same timeframe: general = network stack breakage; we=92ll hit the times when we=92ll not be sure if = things broke because of VIMAGE or are also broken in the normal network stack. = There=92ll be a lot of regression test writing and debugging to be done. That all said, I=92d like to see it happen as well, but I=92d love to = have a lot of the issues being addressed first before putting a date on it to = enable it in GENERIC in HEAD. /bz =97=20 Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 12:42:51 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0C932B87; Mon, 17 Nov 2014 12:42:51 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 916F1EFF; Mon, 17 Nov 2014 12:42:50 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id A6FBC153448; Mon, 17 Nov 2014 13:42:46 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kh6hyyq0wydl; Mon, 17 Nov 2014 13:42:37 +0100 (CET) Received: from [192.168.101.102] (vpn.ecoracks.nl [31.223.170.173]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 9A4C4153413; Mon, 17 Nov 2014 13:42:37 +0100 (CET) Message-ID: <5469ED3D.2060307@digiware.nl> Date: Mon, 17 Nov 2014 13:42:37 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Bjoern A. Zeeb" Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <5469D9E1.2060400@digiware.nl> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 17 Nov 2014 12:42:51 -0000 On 17-11-2014 12:42, Bjoern A. Zeeb wrote: > On 17 Nov 2014, at 11:20 , Willem Jan Withagen wrote: > >> I think I understand your critique, but then on the other hand I wonder >> where the reluctance is.... As I read it, things are going to be enabled >> in CURRENT only (for the time). Which is exactly for the reasons you >> worry about: Is it going to be reliable enough?? > > No, the answer to that still is “no” in it’s current state and we know that. > > I think one of the main problems is that no one has been able to pull the > thing to the end in the last three years. Why should it happen within 6 weeks now? > > I think it would be a really good idea to do that but the current TODO list, > I think, is by far not sufficing. > > There’s a second problem we’ll hit in that same timeframe: general network > stack breakage; we’ll hit the times when we’ll not be sure if things broke > because of VIMAGE or are also broken in the normal network stack. There’ll > be a lot of regression test writing and debugging to be done. > > > That all said, I’d like to see it happen as well, but I’d love to have a lot > of the issues being addressed first before putting a date on it to enable > it in GENERIC in HEAD. Hi Bjoern, The constraints as you put them are indeed rather tight. There is little to be done about it. I was not aware of the fact that 11.0 is planned for release in such short time. Somewhere in the back op my head is: planning is start release cycle around Q2 2015. And I took the liberty to add some testing & QA time to that, so I expect it after summer holidays in 2015. Now I admit: I don't write code for this, nor do I have the knowledge to so. But do run CURRENT to test exactly all these visualization options... Have not (yet) found a requirement to put VIMAGE to good use, so I never switched it on. The down side of all this, is that if we cannot turn it on during the 11-STABLE lifetime. Then it is going to take a full version release cycle to make it to the front. Which I find a pity, since it misses the opportunity for FreeBSD to add another distinctive element to their visualization possibilities. I prefer not to take this into a debate about the way things should go. Over time I've seen too many of these discussions turn in to shouting wars/bikesheds/and what not.... So given the fact I'm not going to do it, I'll leave the rest of the discussion to those that are actual doing all the work... (for which already 20 year of thanks) --WjW From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 15:37:19 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED9E8CC5; Mon, 17 Nov 2014 15:37:19 +0000 (UTC) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id AA91485E; Mon, 17 Nov 2014 15:37:19 +0000 (UTC) Received: from nine.des.no (smtp.des.no [194.63.250.102]) by smtp-int.des.no (Postfix) with ESMTP id BE9C5A982; Mon, 17 Nov 2014 15:37:18 +0000 (UTC) Received: by nine.des.no (Postfix, from userid 1001) id 07A301B9C; Mon, 17 Nov 2014 16:37:17 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Willem Jan Withagen Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <5469D9E1.2060400@digiware.nl> <5469ED3D.2060307@digiware.nl> Date: Mon, 17 Nov 2014 16:37:17 +0100 In-Reply-To: <5469ED3D.2060307@digiware.nl> (Willem Jan Withagen's message of "Mon, 17 Nov 2014 13:42:37 +0100") Message-ID: <86lhn96doy.fsf@nine.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: "Bjoern A. Zeeb" , freebsd-arch , "freebsd-virtualization@freebsd.org" , FreeBSD Net 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, 17 Nov 2014 15:37:20 -0000 Willem Jan Withagen writes: > The constraints as you put them are indeed rather tight. There is little > to be done about it. I was not aware of the fact that 11.0 is planned > for release in such short time. It isn't. ISTR that the target is 2015Q4. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 17:47:53 2014 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 B8DFAF99; Mon, 17 Nov 2014 17:47:53 +0000 (UTC) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 9D325B9E; Mon, 17 Nov 2014 17:47:53 +0000 (UTC) Received: from AlfredMacbookAir.local (c-76-21-10-192.hsd1.ca.comcast.net [76.21.10.192]) by elvis.mu.org (Postfix) with ESMTPSA id 177B7341F872; Mon, 17 Nov 2014 09:47:53 -0800 (PST) Message-ID: <546A34C8.6060004@freebsd.org> Date: Mon, 17 Nov 2014 09:47:52 -0800 From: Alfred Perlstein Organization: FreeBSD User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Warner Losh , Craig Rodrigues Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> In-Reply-To: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 17 Nov 2014 17:47:53 -0000 On 11/17/14, 3:02 AM, Warner Losh wrote: > On Nov 17, 2014, at 12:46 AM, Craig Rodrigues wrote: > >> Hi, >> >> PROPOSAL >> ========== >> I would like to get feedback on the following proposal. >> In the head branch (CURRENT), I would like to enable >> VIMAGE with this commit: >> >> >> PATCH >> ====== >> >> Index: sys/conf/NOTES >> =================================================================== >> --- sys/conf/NOTES (revision 274300) >> +++ sys/conf/NOTES (working copy) >> @@ -784,8 +784,8 @@ >> device mn # Munich32x/Falc54 Nx64kbit/sec cards. >> >> # Network stack virtualization. >> -#options VIMAGE >> -#options VNET_DEBUG # debug for VIMAGE >> +options VIMAGE >> +options VNET_DEBUG # debug for VIMAGE >> >> # >> # Network interfaces: >> >> >> >> I would like to enable VIMAGE for the following reasons: >> >> REASONS >> ======== >> >> (1) VIMAGE cannot be enabled off to the side in a separate library or >> kernel module. When enabled, it is a kernel ABI incompatible change. >> This has impact on 3rd party code such as the kernel modules >> which come with VirtualBox. >> So the time to do it in CURRENT is now, otherwise we can't consider >> doing it until FreeBSD-12 timeframe, which is quite a while away. >> >> (2) VIMAGE is used in some 3rd party products, such as FreeNAS. >> These 3rd party products are mostly happy with VIMAGE, >> but sometimes they encounter problems, and FreeBSD doesn't >> see these problems because it is disabled by default. >> >> (3) Most of the major subsystems like ipfw and pf have been fixed for >> VIMAGE, and the only >> way to shake out the last few issues is to make it the default and >> get feedback from the community. ipfilter still needs to be >> VIMAGE-ified. >> >> >> (4) Not everyone uses bhyve. FreeBSD jails are an excellent virtualization >> platform for FreeBSD. Jails are still very popular and >> performant. VIMAGE makes jails even better by allowing per-jail >> network stacks. >> >> (5) Olivier Cochard-Labbe has provided good network performance results >> in VIMAGE vs. non-VIMAGE kernels: >> >> >> https://lists.freebsd.org/pipermail/freebsd-net/2014-October/040091.html >> >> (6) Certain people like Vitaly "wishmaster" have been >> running VIMAGE >> jails in a production environment for quite a while, and would like >> to see it >> be the default. >> >> >> ACTION PLAN >> =========== >> >> (1) Coordinate/communicate with portmgr, since this has kernel ABI >> implications >> >> (2) Work with clusteradm@, and try to get a test instance of one of the >> PF firewalls in the cluster working with a VIMAGE enabled kernel. >> >> (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO >> and >> https://bugs.freebsd.org/bugzilla/buglist.cgi?quicksearch=vimage%20or%20vnet >> and try to clean things up. Get help from net@ developers to do >> this. > And if these don’t get cleaned up? If they are not cleaned/stable up by 11-RELEASE then we turn it off. That is simple. > >> (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help from >> the ipfilter maintainers for this and some net@ developers. > And if this doesn’t happen? Well we do have 2 other firewalls in the kernel to pick, but we do need VIMAGE so I will let you draw your own conclusions. -Alfred From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 17 20:57:10 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E39DABA4; Mon, 17 Nov 2014 20:57:10 +0000 (UTC) Received: from smtp.digiware.nl (unknown [IPv6:2001:4cb8:90:ffff::3]) (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 9F220392; Mon, 17 Nov 2014 20:57:10 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id DFFD9153416; Mon, 17 Nov 2014 21:57:05 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HFBhL4hyRQjE; Mon, 17 Nov 2014 21:57:04 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:daa2:5eff:fe4e:36d2] (unknown [IPv6:2001:4cb8:3:1:daa2:5eff:fe4e:36d2]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPS id B4137153413; Mon, 17 Nov 2014 21:57:04 +0100 (CET) References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <5469D9E1.2060400@digiware.nl> <5469ED3D.2060307@digiware.nl> <86lhn96doy.fsf@nine.des.no> In-Reply-To: <86lhn96doy.fsf@nine.des.no> Mime-Version: 1.0 (1.0) Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Message-Id: <17C50DD9-B155-478C-B5E1-61F0A01616EC@digiware.nl> X-Mailer: iPad Mail (9B206) From: Willem Jan Withagen Subject: Re: RFC: Enabling VIMAGE in GENERIC Date: Mon, 17 Nov 2014 21:57:12 +0100 To: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= Cc: "Bjoern A. Zeeb" , freebsd-arch , "freebsd-virtualization@freebsd.org" , FreeBSD Net 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, 17 Nov 2014 20:57:11 -0000 Op 17 nov. 2014 om 16:37 heeft Dag-Erling Sm=C3=B8rgrav het vol= gende geschreven: > Willem Jan Withagen writes: >> The constraints as you put them are indeed rather tight. There is little >> to be done about it. I was not aware of the fact that 11.0 is planned >> for release in such short time. >=20 > It isn't. ISTR that the target is 2015Q4. >=20 So even further in the future than what I expected. But still, somebody(tm) needs to do the actual work. So they get the say. --WjW= From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 03:07:33 2014 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 6AEEBA18; Wed, 19 Nov 2014 03:07:33 +0000 (UTC) Received: from mail1.bur200.uecomm.net.au (mail1.bur200.uecomm.net.au [218.185.0.70]) by mx1.freebsd.org (Postfix) with ESMTP id 1DD6FD22; Wed, 19 Nov 2014 03:07:32 +0000 (UTC) Received: from mail.flexibledrive.com.au (unknown [115.186.196.106]) by mail1.bur200.uecomm.net.au (Postfix) with ESMTP id 7BE89D400; Wed, 19 Nov 2014 14:07:28 +1100 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.flexibledrive.com.au (Postfix) with ESMTP id D8BA3E6C0D; Wed, 19 Nov 2014 14:07:27 +1100 (EST) X-Virus-Scanned: amavisd-new at fdrive.com.au Received: from mail.flexibledrive.com.au ([127.0.0.1]) by localhost (mail.flexibledrive.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J42y4+f5yYhY; Wed, 19 Nov 2014 14:07:19 +1100 (EST) Received: from ws-pross.vv.fda (ws-pross.vv.fda [192.168.50.199]) by mail.flexibledrive.com.au (Postfix) with ESMTPS id 64597E623B; Wed, 19 Nov 2014 14:07:19 +1100 (EST) Date: Wed, 19 Nov 2014 14:07:18 +1100 (AEDT) From: Peter Ross X-X-Sender: petros@linux-vic-05.vv.fda To: Craig Rodrigues Subject: Re: RFC: Enabling VIMAGE in GENERIC Message-ID: User-Agent: Alpine 2.11 (LRH 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-net@freebsd.org, freebsd-virtualization@freebsd.org, freebsd-arch@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, 19 Nov 2014 03:07:33 -0000 On Sun, 16 Nov 2014, Craig Rodrigues wrote: > (4) Not everyone uses bhyve. FreeBSD jails are an excellent virtualization > platform for FreeBSD. Jails are still very popular and > performant. VIMAGE makes jails even better by allowing per-jail > network stacks. I am using jails and VIMAGE for ca. 4 years, btw. On the other side of the fence (see Linux) containers became quite popular with Docker and are also used for process management and separation (systemd e.g.) Just to add this as a motivation for using jails and possibly VIMAGE, from a sysadmin perspective. Regards Peter From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 03:28:08 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 01086F50; Wed, 19 Nov 2014 03:28:07 +0000 (UTC) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 70949F09; Wed, 19 Nov 2014 03:28:07 +0000 (UTC) Received: by mail-la0-f42.google.com with SMTP id s18so7259758lam.15 for ; Tue, 18 Nov 2014 19:28:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=AaS3LXE8s4tueoBKaQu1DRvqPKO2t73RzBNcmRfqN5A=; b=R8KqIplC7EQjD9z4qWUFT6jo0oqhB/n9huMPO5v5gLKJSy9RlI2HWYfr197Lpxj5sz Qr/JjME0F2/ruHHZ8SP8USg+3YtaSniqPTlMgsgInhNeL2ODZB/CHMz6UXrYkZOlCzeE I0PJfg51NYlRBehYRLBiBjWehY/0D4rnc//1CP+rpSG+YS2CWhFnEwWAFnzL8TJNfUY0 rAEjAkKmJtdGegmcq5dlL+aMmLTtJ7XMzDcbCK0PQ263W+nFfJCYY+1bIwnvPfWHL38I EJdaI+BNaStA2C7W8UEm0IeRXMrY/LTUdZevILgvTyuqDLfCo4S2sToZYd5K/9CuSm5L 2Zkg== MIME-Version: 1.0 X-Received: by 10.112.135.229 with SMTP id pv5mr2928817lbb.52.1416367685372; Tue, 18 Nov 2014 19:28:05 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Tue, 18 Nov 2014 19:28:05 -0800 (PST) In-Reply-To: <546A34C8.6060004@freebsd.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> Date: Tue, 18 Nov 2014 19:28:05 -0800 X-Google-Sender-Auth: TTScpdATYtYmx9Wo88nvuv4WoVY Message-ID: Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: FreeBSD Net Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-virtualization@freebsd.org" , Warner Losh , freebsd-arch 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, 19 Nov 2014 03:28:08 -0000 On Mon, Nov 17, 2014 at 9:47 AM, Alfred Perlstein wrote: > > On 11/17/14, 3:02 AM, Warner Losh wrote: > >> On Nov 17, 2014, at 12:46 AM, Craig Rodrigues >> wrote: >> >> >>> (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO >>> and >>> https://bugs.freebsd.org/bugzilla/buglist.cgi? >>> quicksearch=vimage%20or%20vnet >>> and try to clean things up. Get help from net@ developers to >>> do >>> this. >>> >> And if these don't get cleaned up? >> > If they are not cleaned/stable up by 11-RELEASE then we turn it off. That > is simple. > Yes, I agree with Alfred that we can turn VIMAGE back off before 11-RELEASE if things don't get cleaned up. We have approximately until the end of 2015, so that gives us time. > > >> (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help from >>> the ipfilter maintainers for this and some net@ developers. >>> >> And if this doesn't happen? >> > > Well we do have 2 other firewalls in the kernel to pick, but we do need > VIMAGE so I will let you draw your own conclusions. > Again, I agree with Alfred on this. Darren Reed originally imported ipfilter into FreeBSD, but hasn't actively maintained it (in FreeBSD) in a while. Cy Schubert has recently expressed interest in ipfilter and has committed some fixes in the past year, but has not fixed the VIMAGE problems ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176992 ). I can take an initial effort at trying to fix VIMAGE + ipfilter. In the past, I've delved into areas I'm not so familiar with in order to fix VIMAGE + Bluetooth. If Cy can provide any knowledge or guidance, that will be great. A lot of bug fixes have gone into VIMAGE in the past 2 years, and I have received multiple reports of people using it in production environments. See the latest post by Peter Ross. To flush out the last few issues and corner cases, I think we need to turn VIMAGE on by default and get feedback and help from the FreeBSD user community and developers to identify and fix the problems. We have about 1 year until 11-RELEASE, so I think it is OK to do this. I would also add two items to my action plan. (6) Ask clusteradm to run one of the machines they use for PF firewalls + IPv6 with a VIMAGE enabled kernel, and provide feedback. (7) Ask for help with testing from companies who have more involvement with the network stack. Two of the people in the CC: line of this e-mail work for such places. :) -- Craig -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 12:08:16 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6DD28988; Wed, 19 Nov 2014 12:08:16 +0000 (UTC) Received: from mail.ipfw.ru (mail.ipfw.ru [IPv6:2a01:4f8:120:6141::2]) (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 0400EC86; Wed, 19 Nov 2014 12:08:16 +0000 (UTC) Received: from [2a02:6b8:0:401:222:4dff:fe50:cd2f] (helo=ptichko.yndx.net) by mail.ipfw.ru with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82 (FreeBSD)) (envelope-from ) id 1Xr02N-00044f-0h; Wed, 19 Nov 2014 11:50:51 +0400 Message-ID: <546C8812.2070904@FreeBSD.org> Date: Wed, 19 Nov 2014 16:07:46 +0400 From: "Alexander V. Chernikov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: Craig Rodrigues , FreeBSD Net Subject: Re: RFC: Enabling VIMAGE in GENERIC References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: Warner Losh , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 19 Nov 2014 12:08:16 -0000 On 19.11.2014 07:28, Craig Rodrigues wrote: > On Mon, Nov 17, 2014 at 9:47 AM, Alfred Perlstein > wrote: > >> On 11/17/14, 3:02 AM, Warner Losh wrote: >> >>> On Nov 17, 2014, at 12:46 AM, Craig Rodrigues >>> wrote: >>> >>> >>>> (3) Take a pass through http://wiki.freebsd.org/VIMAGE/TODO >>>> and >>>> https://bugs.freebsd.org/bugzilla/buglist.cgi? >>>> quicksearch=vimage%20or%20vnet >>>> and try to clean things up. Get help from net@ developers to >>>> do >>>> this. >>>> >>> And if these don't get cleaned up? >>> >> If they are not cleaned/stable up by 11-RELEASE then we turn it off. That >> is simple. >> > Yes, I agree with Alfred that we can turn VIMAGE back off before > 11-RELEASE if things don't get cleaned up. > We have approximately until the end of 2015, so that gives > us time. > > > >> >>> (4) Take a pass on trying to VIMAGE-ify ipfilter. I'll need help from >>>> the ipfilter maintainers for this and some net@ developers. >>>> >>> And if this doesn't happen? >>> >> Well we do have 2 other firewalls in the kernel to pick, but we do need >> VIMAGE so I will let you draw your own conclusions. >> > > Again, I agree with Alfred on this. Darren Reed originally imported > ipfilter into FreeBSD, but hasn't actively maintained it (in FreeBSD) in a > while. Cy Schubert has recently expressed interest in ipfilter and has > committed some fixes in the past year, but has not fixed the VIMAGE problems > ( https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=176992 ). > I can take an initial effort at trying to fix VIMAGE + ipfilter. > In the past, I've delved into areas I'm not so familiar with in > order to fix VIMAGE + Bluetooth. If Cy can provide any knowledge or > guidance, that will be great. > > A lot of bug fixes have gone into VIMAGE in the past 2 years, > and I have received multiple reports of people using it in production > environments. See the latest post by Peter Ross. > > To flush out the last few issues and corner cases, I think we > need to turn VIMAGE on by default and get feedback and help from > the FreeBSD user community and developers to identify and fix the problems. Can we have some wiki/man/docs on how particular subsystem should interact with VNET first? This can probably help to make proper vnet fixes in less number of attempts :) For example, even attach/detach is handled differently in different places: tcp_subr.c: /* Skip initialization of globals for non-default instances. */ if (!IS_DEFAULT_VNET(curvnet)) return; in6_rmx.c: /* * Initialize our routing tree. */ static VNET_DEFINE(int, _in6_rt_was_here); #define V__in6_rt_was_here VNET(_in6_rt_was_here) if (V__in6_rtwas_here == 0) { callout_init(&V_rtq_mtutimer, CALLOUT_MPSAFE); in6_mtutimo(curvnet); /* kick off timeout first time */ V__in6_rt_was_here = 1; } return (1); } It would be great to get a bit more details on the following (at least from my point of view): * what is the proper procedure of handling non-default VNET attach/detach (locking mostly) * how can one properly cache needed VNET context (e.g. is it safe just to save "struct vnet *" pointer) and is this right thing to do at all? * Is it safe to to CURVNET_SET without holding any VNET locks ? P.S. I'm not against VIMAGE in any kind, I think we really should move forward towards making it stable. However, "just turn it on" concept with a bunch of known (and unresolved issues) is not the best thing IMO. > > We have about 1 year until 11-RELEASE, so I think it is OK to do this. > > I would also add two items to my action plan. > > > (6) Ask clusteradm to run one of the machines they use > for PF firewalls + IPv6 with a VIMAGE enabled kernel, and provide > feedback. > > (7) Ask for help with testing from companies who have more involvement > with the network stack. Two of the people in the CC: line of this > e-mail work for such places. :) > > -- > Craig > > > -- > Craig > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 12:58:05 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8FBAAAE; Wed, 19 Nov 2014 12:58:04 +0000 (UTC) Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.fer.hr", Issuer "TERENA SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4D1361F3; Wed, 19 Nov 2014 12:58:03 +0000 (UTC) Received: from x23 (31.147.125.196) by MAIL.fer.hr (161.53.72.233) with Microsoft SMTP Server (TLS) id 14.2.342.3; Wed, 19 Nov 2014 13:56:50 +0100 Date: Wed, 19 Nov 2014 13:56:51 +0100 From: Marko Zec To: "Alexander V. Chernikov" Subject: Re: RFC: Enabling VIMAGE in GENERIC Message-ID: <20141119135651.789c6766@x23> In-Reply-To: <546C8812.2070904@FreeBSD.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd9.1) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [31.147.125.196] Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , Warner Losh , freebsd-arch 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, 19 Nov 2014 12:58:05 -0000 On Wed, 19 Nov 2014 16:07:46 +0400 "Alexander V. Chernikov" wrote: ... > Can we have some wiki/man/docs on how particular subsystem should > interact with VNET first? > This can probably help to make proper vnet fixes in less number of > attempts :) > > For example, even attach/detach is handled differently in different > places: > > tcp_subr.c: > /* Skip initialization of globals for non-default instances. > */ if (!IS_DEFAULT_VNET(curvnet)) > return; > in6_rmx.c: > /* > * Initialize our routing tree. > */ > static VNET_DEFINE(int, _in6_rt_was_here); > #define V__in6_rt_was_here VNET(_in6_rt_was_here) > > if (V__in6_rtwas_here == 0) { > callout_init(&V_rtq_mtutimer, CALLOUT_MPSAFE); > in6_mtutimo(curvnet); /* kick off timeout first > time */ V__in6_rt_was_here = 1; > } > > return (1); > } > > It would be great to get a bit more details on the following (at > least from my point of view): > * what is the proper procedure of handling non-default VNET > attach/detach (locking mostly) In general, VNET_SYSINIT() / VNET_SYSUNINIT() macros should be used to invoke per-subsystem ctors / dtors on per-vnet basis. > * how can one properly cache needed VNET context (e.g. is it safe > just to save "struct vnet *" pointer) and is this right thing to do > at all? Caching a VNET context should be avoided, as it yields similar problems as queuing mbufs does (in dummynet or similar queues) pointing to rcvifs which may disappear by the time the mbuf gets dequeued. > * Is it safe to to CURVNET_SET without holding any VNET locks ? Yes, if the VNET context is derived from some of the arguments in the current call graph. > P.S. I'm not against VIMAGE in any kind, I think we really should > move forward towards making it stable. > However, "just turn it on" concept with a bunch of known (and > unresolved issues) is not the best thing IMO. > > > > We have about 1 year until 11-RELEASE, so I think it is OK to do > > this. > > > > I would also add two items to my action plan. > > > > > > (6) Ask clusteradm to run one of the machines they use > > for PF firewalls + IPv6 with a VIMAGE enabled kernel, and > > provide feedback. > > > > (7) Ask for help with testing from companies who have more > > involvement with the network stack. Two of the people in the CC: > > line of this e-mail work for such places. :) > > > > -- > > Craig > > > > > > -- > > Craig > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to > > "freebsd-net-unsubscribe@freebsd.org" > > > > _______________________________________________ > 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 Nov 19 14:05:41 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 64E92E2A; Wed, 19 Nov 2014 14:05:41 +0000 (UTC) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A1F2BAE; Wed, 19 Nov 2014 14:05:41 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 6BC1725D37D1; Wed, 19 Nov 2014 14:05:37 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 723E2C76FD7; Wed, 19 Nov 2014 14:05:36 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id wJgvp_sLs7Mu; Wed, 19 Nov 2014 14:05:35 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6] (orange-tun0-ula.sbone.de [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 3DD82C76FCE; Wed, 19 Nov 2014 14:05:32 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: RFC: Enabling VIMAGE in GENERIC From: "Bjoern A. Zeeb" In-Reply-To: Date: Wed, 19 Nov 2014 14:05:29 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <362F742A-BA6F-483A-947C-62D4C5510F31@FreeBSD.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 19 Nov 2014 14:05:41 -0000 On 19 Nov 2014, at 03:28 , Craig Rodrigues wrote: >=20 > (6) Ask clusteradm to run one of the machines they use > for PF firewalls + IPv6 with a VIMAGE enabled kernel, and provide > feedback. For people to use pf with VIMAGE we first MUST have the security fix = imported that I pointed out a couple of times in the past. It won=92t matter on the firewalls with just a VIMAGE enabled kernel but = using VIMAGE + pf inside a jail (once that really works if it doesn=92t = already) will allow everyone how can administer pf inside the jail to = take over the entire machine otherwise. =97=20 Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 19:59:25 2014 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 05387AAE; Wed, 19 Nov 2014 19:59:25 +0000 (UTC) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "funkthat.com", Issuer "funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AC1EFB99; Wed, 19 Nov 2014 19:59:23 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id sAJJxNJG080874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Nov 2014 11:59:23 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id sAJJxNGh080873; Wed, 19 Nov 2014 11:59:23 -0800 (PST) (envelope-from jmg) Date: Wed, 19 Nov 2014 11:59:23 -0800 From: John-Mark Gurney To: "Alexander V. Chernikov" Subject: Re: RFC: Enabling VIMAGE in GENERIC Message-ID: <20141119195923.GS24601@funkthat.com> Mail-Followup-To: "Alexander V. Chernikov" , Craig Rodrigues , FreeBSD Net , Alfred Perlstein , Warner Losh , "freebsd-virtualization@freebsd.org" , freebsd-arch References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <546C8812.2070904@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Wed, 19 Nov 2014 11:59:23 -0800 (PST) Cc: "freebsd-virtualization@freebsd.org" , FreeBSD Net , freebsd-arch , Warner Losh 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, 19 Nov 2014 19:59:25 -0000 Alexander V. Chernikov wrote this message on Wed, Nov 19, 2014 at 16:07 +0400: > Can we have some wiki/man/docs on how particular subsystem should > interact with VNET first? Yes, we need a man page talking about this feature first, how to enable it, compile it into the kernel, how to manage it, what subsystems it interacts w/, what sysctl nodes it provides, etc. W/o man page(s) the feature is not complete. $ man -k vnet revnetgroup(8) - generate reverse netgroup data $ man -k vimage XvCreateImage(3), XvShmCreateImage(3) - create an XvImage XvPutImage(3), XvShmPutImage(3) - display an XvImage hmm.. nope... jail has something about vnets, but not nearly enough to be useful... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 22:38:22 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25FDBE98; Wed, 19 Nov 2014 22:38:22 +0000 (UTC) Received: from smtp.digiware.nl (smtp.digiware.nl [31.223.170.169]) (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 D7A8AA9; Wed, 19 Nov 2014 22:38:21 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 30B801534C9; Wed, 19 Nov 2014 23:38:12 +0100 (CET) X-Virus-Scanned: amavisd-new at digiware.nl Received: from smtp.digiware.nl ([127.0.0.1]) by rack1.digiware.nl (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kHN9kFouowdi; Wed, 19 Nov 2014 23:38:03 +0100 (CET) Received: from [IPv6:2001:4cb8:3:1:553d:9b2b:8ec7:38d2] (unknown [IPv6:2001:4cb8:3:1:553d:9b2b:8ec7:38d2]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.digiware.nl (Postfix) with ESMTPSA id 555DB1534DE; Wed, 19 Nov 2014 23:27:27 +0100 (CET) Message-ID: <546D194F.4090501@digiware.nl> Date: Wed, 19 Nov 2014 23:27:27 +0100 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Allan Jude , freebsd-virtualization@freebsd.org Subject: Re: Trying to run an older head in a recent Bhyve. References: <5467BC49.4080308@digiware.nl> <5467E8E6.1000509@freebsd.org> <5468E4B9.5090205@digiware.nl> <5468EAC7.3030601@freebsd.org> In-Reply-To: <5468EAC7.3030601@freebsd.org> 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: Wed, 19 Nov 2014 22:38:22 -0000 On 16-11-2014 19:19, Allan Jude wrote: > On 2014-11-16 12:54, Willem Jan Withagen wrote: >> On 16-11-2014 0:59, Peter Grehan wrote: >>> Hi Willem, >>> >>>> I'm trying to run one of my older VM's and get the crash below in the VM >>>> when trying to boot... >>>> >>>> This happens both on an older BSD: >>>> FreeBSD 11.0-CURRENT (FREETEST) #1 r273066M: Sun Oct 19 00:59:06 CEST >>>> 2014 >>>> As well as on a very recent: >>>> FreeBSD 11.0-CURRENT (BHYVE00) #0 r274490M: Fri Nov 14 02:42:43 CET 2014 >>>> >>>> The older 10.0 VM's do boot normally >>>> >>>> Any suggestions on what this might be, and/or how to debug this.. >>> >>> Did the disk image backing file change by any chance ? e.g. from file >>> to zvol ? >>> >>> What's the version of the VM that has the issue ? >> >> Not sure what you mean by that exactely, but the VM runs a relatively >> old HEAD: >> >> FreeBSD 11.0-CURRENT #1 r262690: Sun Mar 2 21:28:19 CET 2014 >> root@bhyve-head:/usr/obj/usr/src/sys/GENERIC amd64 >> >> It boots in single mode. >> >> I'tt try and manually assign an IP number and will see what that brings. > He is asking how the virtual disk is setup, specifically, if it is a zvol > > Judging by the backtrace, the VM is panicing when trying to write to the > disk and it fails > > From my experience, the two most likely causes are: > > 1) The disk is a zvol, and does not have the volmode set, and GEOM on > the host is grabbing the disk and locking it, preventing writes > > 2) The VM was shutdown ungracefully and the file system needs a fsck. > Since you can get into single user mode, this should be doable. The VM-disk is a file, very early on I tried things with ZVOL but have not yet returned to testing those. Well the system passes the fsck-check during boot. And I can manually config the network, and /etc/resolv.conf Then the system stays up, and I was able to download the new sources and build them without crashing the system... I really crashed right after DHCP answers.... --WjW From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 19 23:14:07 2014 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 87CB18F2; Wed, 19 Nov 2014 23:14:07 +0000 (UTC) Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F2D3367C; Wed, 19 Nov 2014 23:14:06 +0000 (UTC) Received: by mail-lb0-f179.google.com with SMTP id l4so1370883lbv.24 for ; Wed, 19 Nov 2014 15:14:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=BrzUgkBksN2yvMlbd+anLBQC1tHhDjVGNHLtzyXveRw=; b=ityUjPieOr8zRykYuLY39pBz1+JT9t62I4AZT10rFx3b6123hrKH5u0Dt4O/6rWZVG q5HcJb0OiNp63OCu/gOgAC4DvqC59aCtjF+euW2y2d5o2sJhywjF88rxSBtGBJiamzna 75sX+IusRNTWMulaaufKQhNE0Bpjjewujgk8du05cq4sS/57CvBj5C5QrombybsezPt7 S5lA9WFDEF22udNQEjt8oQuyloBkhMlVI/gsc9pIqoA+2GTirRQyuaxWs24qspHR8I5K VsDv60zqIJtjFYPU8fd+lyTTFFZe0V0RhZT/8kpIlJNrg53/vyYzVxOQqp3cKKcujggk AJ+Q== MIME-Version: 1.0 X-Received: by 10.112.169.106 with SMTP id ad10mr44624026lbc.13.1416438843958; Wed, 19 Nov 2014 15:14:03 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Wed, 19 Nov 2014 15:14:03 -0800 (PST) In-Reply-To: <20141119195923.GS24601@funkthat.com> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> <20141119195923.GS24601@funkthat.com> Date: Wed, 19 Nov 2014 15:14:03 -0800 X-Google-Sender-Auth: XhhWaC7yBsuP3aIDpEKdaZYuYv0 Message-ID: Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: Marko Zec , FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch Content-Type: text/plain; charset=ISO-8859-1 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: Wed, 19 Nov 2014 23:14:07 -0000 On Wed, Nov 19, 2014 at 11:59 AM, John-Mark Gurney wrote: > > Yes, we need a man page talking about this feature first, how to enable > it, compile it into the kernel, how to manage it, what subsystems it > interacts w/, what sysctl nodes it provides, etc. > Marko, Do you have any text which can be put into a vnet(9) man page? It doesn't have to be perfect, but just something that we can start from. I tried looking at some of the notes and presentations that you have done on VIMAGE: https://wiki.freebsd.org/?action=fullsearch&context=180&value=VIMAGE&titlesearch=Titles but didn't see anything that could be readily turned into a man page. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 00:33:26 2014 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 17068FA0; Thu, 20 Nov 2014 00:33:26 +0000 (UTC) Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:130:3ffc::401:25]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B5F3AEB3; Thu, 20 Nov 2014 00:33:25 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 1DC3725D3A05; Thu, 20 Nov 2014 00:33:13 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id BD343C76FE5; Thu, 20 Nov 2014 00:33:12 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id voukIar2mHY2; Thu, 20 Nov 2014 00:33:11 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6] (orange-tun0-ula.sbone.de [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 35A8CC76FCE; Thu, 20 Nov 2014 00:33:09 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: RFC: Enabling VIMAGE in GENERIC From: "Bjoern A. Zeeb" In-Reply-To: Date: Thu, 20 Nov 2014 00:33:09 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> <20141119195923.GS24601@funkthat.com> To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Net , Marko Zec , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 20 Nov 2014 00:33:26 -0000 On 19 Nov 2014, at 23:14 , Craig Rodrigues wrote: > On Wed, Nov 19, 2014 at 11:59 AM, John-Mark Gurney = wrote: >=20 >>=20 >> Yes, we need a man page talking about this feature first, how to = enable >> it, compile it into the kernel, how to manage it, what subsystems it >> interacts w/, what sysctl nodes it provides, etc. >>=20 >=20 > Marko, >=20 > Do you have any text which can be put into a vnet(9) man page? > It doesn't have to be perfect, but just something that we can start = from. >=20 > I tried looking at some of the notes and presentations that you have = done > on VIMAGE: > = https://wiki.freebsd.org/?action=3Dfullsearch&context=3D180&value=3DVIMAGE= &titlesearch=3DTitles >=20 > but didn=92t see anything that could be readily turned into a man = page. https://people.freebsd.org/~bz/20100530-02.vnet.9.html The man page should be in that perforce branch you converted to github. =97=20 Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 06:31:48 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9001F3F5 for ; Thu, 20 Nov 2014 06:31:48 +0000 (UTC) Received: from SNT004-OMC4S15.hotmail.com (snt004-omc4s15.hotmail.com [65.55.90.218]) (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 606CA61F for ; Thu, 20 Nov 2014 06:31:48 +0000 (UTC) Received: from SNT150-W8 ([65.55.90.199]) by SNT004-OMC4S15.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Wed, 19 Nov 2014 22:30:41 -0800 X-TMN: [aTiI+YPm9I3DodCNyj0HKIxS4kQZDyJZ] X-Originating-Email: [mrashutosh@hotmail.com] Message-ID: From: Ashutosh Kumar To: "freebsd-virtualization@freebsd.org" Subject: 'repz' instruction not supported. Date: Thu, 20 Nov 2014 06:30:41 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 20 Nov 2014 06:30:41.0435 (UTC) FILETIME=[818F1EB0:01D0048B] Content-Type: text/plain; charset="iso-8859-1" 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, 20 Nov 2014 06:31:48 -0000 Hi We have found that emulation of 'repz' instruction is not supported in bhyv= e. This is causing VM_EXIT for Guest OS. Do we have plans to add support fo= r instructions like 'repz'.=20 RegardsAshutosh = From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 06:49:24 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50498B6C for ; Thu, 20 Nov 2014 06:49:24 +0000 (UTC) Received: from fallback2.mail.ru (fallback2.mail.ru [94.100.179.22]) by mx1.freebsd.org (Postfix) with ESMTP id EE782796 for ; Thu, 20 Nov 2014 06:49:23 +0000 (UTC) Received: from f125.i.mail.ru (f125.i.mail.ru [94.100.178.188]) by fallback2.mail.ru (mPOP.Fallback_MX) with ESMTP id ABAD449FF013 for ; Thu, 20 Nov 2014 09:40:45 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2; h=Content-Type:Message-ID:Reply-To:Date:MIME-Version:Subject:To:From; bh=ccMf/b/c8NBgbVMfu2194nrIa7fwSK94RP2NhjY3uNA=; b=VWg/X0ixfyBhyTOGjca0LKytQtIndg1CscgRNyRMPDnqeBQGDP2sw4ki7Oz/H+Ednc0VWpkXO1W02CwW2ApzN4Pq7co0Ag52UXv/Ia+qxCufOWkd62QSnMbbuLHdkW0vrcJs+4EG8Gc0LbmsPQr8gSFs2qKQYQAcGpN12ChwEvw=; Received: from [80.83.239.115] (ident=mail) by f125.i.mail.ru with local (envelope-from ) id 1XrLPw-0001zM-OF for freebsd-virtualization@freebsd.org; Thu, 20 Nov 2014 09:40:37 +0300 Received: from [80.83.239.115] by e.mail.ru with HTTP; Thu, 20 Nov 2014 09:40:36 +0300 From: =?UTF-8?B?SWx5YSBMYXJpbg==?= To: =?UTF-8?B?ZnJlZWJzZC12aXJ0dWFsaXphdGlvbkBmcmVlYnNkLm9yZw==?= Subject: =?UTF-8?B?SG93IHRvIHVwZGF0ZSBiaHl2ZSAoc3VwcG9ydGluZyBhbWQpIGZyb20gZnJl?= =?UTF-8?B?ZWJzZC0xMC4x?= MIME-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [80.83.239.115] Date: Thu, 20 Nov 2014 09:40:36 +0300 Reply-To: =?UTF-8?B?SWx5YSBMYXJpbg==?= X-Priority: 3 (Normal) Message-ID: <1416465636.164055963@f125.i.mail.ru> X-Mras: Ok X-Spam: undefined Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 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, 20 Nov 2014 06:49:24 -0000 CkhpISAKSSBrbm93LCB0aGF0IGJoeXZlIHN1cHBvcnQgQU1EIHByb2Nlc3NvcnMgZnJvbSB2ZXJz aW9uIHIyNzMzNzUuLgpJIGhhdmUgcHJvY2Vzc29yLCB0aGF0IHN1cHBvcnQgUlZJIGFuZCBGcmVl YnNkLTEwLjEgKHJlbGVhc2UpLgpTby4uIEhvdyB0byB1cGRhdGUgKHBhdGNoL3JlYnVpbGQvc29t ZXRoaW5nIGVsc2UpIGJoeXZlIHRvIHIyNzczMzc1IG9uIG15IGZyZXNoIGZyZWVic2QgMTAuMT8g SXMgaXQgcG9zc2libGU/IApJIGp1c3Qgd2FudCB0byBpbnN0YWxsIHNldmVyYWwgdmlydHVhbCBm cmVlYnNkICkpIAotLQpXaXRoIHJlc3BlY3QsIElseWE= From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 10:08:26 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 41001F26; Thu, 20 Nov 2014 10:08:26 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AF9F0F23; Thu, 20 Nov 2014 10:08:25 +0000 (UTC) Received: by mail-lb0-f182.google.com with SMTP id f15so544924lbj.27 for ; Thu, 20 Nov 2014 02:08:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ekyEPaGHxvs0/gVvVYUMMOj/Eb6uRdJcntP4d89m2Zk=; b=Al/dYUuZsJbQ4Yq0ciaxa4DnUg79Dsw5Mm1nKaZzOaA0t1F02fp1iR+goz2g5nbzBU nzW4uwz7rfyWn0YBlPfQ81PmNlarv9mYj83Bw2osXoFnSevfDPybLB+yfiVAtbAyuKoo dt4xIXAL2M5un/Q5mCRbS7V+1RdWLCTn0+YbXw65JCcMO7EUZgLl5r+xyKUwMh8P9qVc F13eIrLvDCIsiDqkwV5d9zaIVFnq7tHXODzki0mlaojgoqT11w5EzjEchEoM1OYuxpAr rS2lruwkUQ6BpJ9fghe6E3qRjRoweYVC29qhZadQ6mrUV/n2sT88M39Ku6YwiKF8OncN PMoA== MIME-Version: 1.0 X-Received: by 10.152.179.1 with SMTP id dc1mr1227131lac.88.1416478103851; Thu, 20 Nov 2014 02:08:23 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Thu, 20 Nov 2014 02:08:23 -0800 (PST) In-Reply-To: <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> References: <1423616F-F44D-47E5-8595-DE862DC04464@bsdimp.com> <546A34C8.6060004@freebsd.org> <546C8812.2070904@FreeBSD.org> <20141119195923.GS24601@funkthat.com> <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> Date: Thu, 20 Nov 2014 02:08:23 -0800 X-Google-Sender-Auth: jAvs6Val3Yu-p9qKy2mJbwKpEtk Message-ID: Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net , Marko Zec , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 20 Nov 2014 10:08:26 -0000 On Wed, Nov 19, 2014 at 4:33 PM, Bjoern A. Zeeb wrote: > > > https://people.freebsd.org/~bz/20100530-02.vnet.9.html > > The man page should be in that perforce branch you converted to github. > Thank you for pointing that out. It is indeed in github: https://github.com/rodrigc/bz-vimage/tree/master/share/man/man9 I committed it to HEAD: https://lists.freebsd.org/pipermail/svn-src-all/2014-November/095037.html I used the textproc/igor port ( http://www.wonkity.com/~wblock/igor/ ) to check the syntax of the man page. It's a great new utility written by wblock@ and I encourage anyone creating or modifying man pages should run it. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 13:16:05 2014 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 325B272C for ; Thu, 20 Nov 2014 13:16:05 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 0BB64839 for ; Thu, 20 Nov 2014 13:16:04 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 1EAF7732D7; Thu, 20 Nov 2014 13:15:58 +0000 (UTC) Message-ID: <546DE997.8010106@freebsd.org> Date: Thu, 20 Nov 2014 08:16:07 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Ilya Larin , "freebsd-virtualization@freebsd.org" Subject: Re: How to update bhyve (supporting amd) from freebsd-10.1 References: <1416465636.164055963@f125.i.mail.ru> In-Reply-To: <1416465636.164055963@f125.i.mail.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K1vNqJ4McBQegV2wKjf4It8AkHek2ebMR" 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, 20 Nov 2014 13:16:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --K1vNqJ4McBQegV2wKjf4It8AkHek2ebMR Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-11-20 01:40, Ilya Larin wrote: >=20 > Hi!=20 > I know, that bhyve support AMD processors from version r273375.. > I have processor, that support RVI and Freebsd-10.1 (release). > So.. How to update (patch/rebuild/something else) bhyve to r2773375 on = my fresh freebsd 10.1? Is it possible?=20 > I just want to install several virtual freebsd ))=20 > -- > With respect, Ilya > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 Currently, you would have to upgrade to running FreeBSD 11-CURRENT rather than 10.1-RELEASE to get that feature. Eventually, once the feature is considered stable, it will be merged back to FreeBSD 10-STABLE (what will eventually be 10.2 some day). This section of the handbook describes the steps required to upgrade your system to FreeBSD 11-CURRENT: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable= =2Ehtml#current --=20 Allan Jude --K1vNqJ4McBQegV2wKjf4It8AkHek2ebMR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUbembAAoJEJrBFpNRJZKf1McP/1EhqPckIlN6kJJgqUikgy87 O38a9OMKiyVkXL71jKO7WyxKl6DhD7hJoxrUWcR5wYUwZjhsFn7Uca5VotXbtgrQ RZedTTq8afQzkkrXhBMwMv2xYSJNdQ0pJWQBccKYtgMRPq7ak+KHlrcpqnNfnVWC /cltRWTmIU0JOCBlp6xEeUT6Ql+Mx8uKqWfTKakObzMTN3Fe2Ej06Las+SxnNJjM 48GzM1O+nbTt41g/Wg7CTT8O0+CP32Cm4m+I718uDGksXH4Zaq7dQVj2FKNqSP/e S/9a+hGgmCemUnMxl7lL1WMMGHl036cIQ4AxVYgbyEtU93CE6PrWt8Yyhy4ezpVc 6b0iMCcigunxrdC1/AJOjE5L9Zkt7uuziPFuVkas/xtC2BMCin3H1h99n3SJ+/oI Jk2Gn2pu0VBV+iI03XRADlh5zrvicBaOK3fgb9wf5J6inu8NfaGlBgwyGiJZcZ6Z ktjKWuRxuaikffXV3Q3x7sWvnIpSGM0QgGi6y8N85GX7YMBMg4xm7lpJq1nCUCCr 46du6kYZ8FO9EsWhHwJJU9taybFu9hwv8ngfv+pgB5EHjdNMfr9VpGS7iCXF7nx5 uY8M8TtjwYk34ckCWFV6cKrLU9Dm1TSNAXeg3QEaLvX1PamTnMsfTBb5RRn46ZZj k4iMKmoX6dwDL85qwN+I =gmAJ -----END PGP SIGNATURE----- --K1vNqJ4McBQegV2wKjf4It8AkHek2ebMR-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 15:34:32 2014 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 9B4F3D90 for ; Thu, 20 Nov 2014 15:34:32 +0000 (UTC) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id D339AB92 for ; Thu, 20 Nov 2014 15:34:31 +0000 (UTC) Received: (qmail 55769 invoked from network); 20 Nov 2014 18:34:28 +0300 Received: from tarkhil.infotel.ru (tarkhil.infotel.ru [195.170.223.197]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 31 Dec 1969 23:59:59 -0000 Message-ID: <546E09FE.80703@webmail.sub.ru> Date: Thu, 20 Nov 2014 18:34:22 +0300 From: Alex Povolotsky User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: CentOS in bhyve Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 141120-0, 20.11.2014), Outbound message X-Antivirus-Status: Clean 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, 20 Nov 2014 15:34:32 -0000 Hello I'm trying to install CentOS in bhyve. I do everything accordnig to https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html [18:30] backup:/<1>bhyve/oracle # cat /etc/bhyve/oracle/device.map (hd0) /dev/zvol/data/oracle (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m /etc/bhyve/oracle/device.map -M 16G oracle grub> ls (cd0)/isolinux boot.cat boot.msg grub.conf initrd.img isolinux.bin isolinux.cfg memtest splash.jpg TRANS.TBL vesamenu.c32 vmlinuz grub> linux (cd0)/isolinux/vmlinuz grub> initrd (cd0)/isolinux/initrd.img error: you need to load the kernel first. grub> And that's all Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my bhyve OK, but need Linux... Alex From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 15:38:32 2014 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 87523E65 for ; Thu, 20 Nov 2014 15:38:32 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5F6ECBDE for ; Thu, 20 Nov 2014 15:38:31 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 1D48972CDB for ; Thu, 20 Nov 2014 15:38:29 +0000 (UTC) Message-ID: <546E0AFF.5070808@freebsd.org> Date: Thu, 20 Nov 2014 10:38:39 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: CentOS in bhyve References: <546E09FE.80703@webmail.sub.ru> In-Reply-To: <546E09FE.80703@webmail.sub.ru> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="kqEehqUA7jJlan0HTNFdIUTnLx3Km8rAC" 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, 20 Nov 2014 15:38:32 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --kqEehqUA7jJlan0HTNFdIUTnLx3Km8rAC Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-11-20 10:34, Alex Povolotsky wrote: > Hello >=20 > I'm trying to install CentOS in bhyve. >=20 > I do everything accordnig to > https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html >=20 > [18:30] backup:/<1>bhyve/oracle # cat /etc/bhyve/oracle/device.map > (hd0) /dev/zvol/data/oracle > (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso >=20 >=20 > [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m > /etc/bhyve/oracle/device.map -M 16G oracle >=20 > grub> ls (cd0)/isolinux > boot.cat boot.msg grub.conf initrd.img isolinux.bin isolinux.cfg > memtest splash.jpg TRANS.TBL vesamenu.c32 vmlinuz >=20 > grub> linux (cd0)/isolinux/vmlinuz > grub> initrd (cd0)/isolinux/initrd.img > error: you need to load the kernel first. > grub> >=20 >=20 > And that's all >=20 > Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my bhyve OK, > but need Linux... >=20 > Alex > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@fr= eebsd.org" >=20 If you read the handbook, it first does an 'ls' on the cd. You have to load files that actually exist, they might have slightly different names.= The instructions in the handbook were based on how the files were named on a CentOS 6.5 cd, 6.6 might be slightly different. --=20 Allan Jude --kqEehqUA7jJlan0HTNFdIUTnLx3Km8rAC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUbgsDAAoJEJrBFpNRJZKfBywP/RZvAVE4EBKJFMNhwhW+xSyK wTKsBQPyuTliCaEZwCFpWfPB46YP0E8100jHYWPwERBcNbfvqN4GCPpcrzpek1gM KhqqSHt2gUF8TGUg78ysucxgA5EA6Hllrab41hwI0Hy+4PDfJh5XSVRdDiOgyClX Dxk/5pduhKH//3k0hEpYDgPzFfBrl7MqENJsOZUqcRTLOrwYkjo7B2kHA9mXJvWA 45zRHGGfPfmOI+lSgBVB8ZeKjUD94XRfdvgW5m1clK/wvYG+GjdYEIcLOQ6ATNzg Y0DhzLISdft3XpECxM6ZW9dfG2FFlNvOJmRiWKg8V0OFAAdZoiQ9A2tLyZmUcCy3 lgX6UfgWF14uwtlGnE+HyQ+q/wel5qbwUsk9eNhrtgR1G0jXGtPZlxuQ9I+ZkIYg oNkAAHbk+7mgifjP9/PyyoNAf4+pqotQqvZ3Mdys3SuH6ORKZlRBxKcYPUv+M44v GIQXbhbOx9A/iEQbn/GXNyqYfa2o9pwu3xVux+jtDll0JHcNZQw5QL9Dxo1J5/AB 2Y8ONesO6esuewn2SQ33pOx1tmfRgw929+JcSVdm0DQ5T+qczxzrZmNYFeRzDT3l p8EJc6qhkWRCBblzLxVuv5fQgFV+I1ZCPy4QKhcdZTBjMgC7jdHi23Patfy1NSYI wDeN7Sd2wlQiP1Q2QQM4 =u08r -----END PGP SIGNATURE----- --kqEehqUA7jJlan0HTNFdIUTnLx3Km8rAC-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 15:47:01 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E87E7FAF for ; Thu, 20 Nov 2014 15:47:01 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id C2000CD3 for ; Thu, 20 Nov 2014 15:47:01 +0000 (UTC) Received: from [192.168.1.2] (Seawolf.HML3.ScaleEngine.net [209.51.186.28]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id C7C0372D23 for ; Thu, 20 Nov 2014 15:47:00 +0000 (UTC) Message-ID: <546E0D02.3050305@freebsd.org> Date: Thu, 20 Nov 2014 10:47:14 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: CentOS in bhyve References: <546E09FE.80703@webmail.sub.ru> <546E0AFF.5070808@freebsd.org> In-Reply-To: <546E0AFF.5070808@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="frso1FSQjrDRaJMS0kkErkxtsRXf9UOrt" 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, 20 Nov 2014 15:47:02 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --frso1FSQjrDRaJMS0kkErkxtsRXf9UOrt Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2014-11-20 10:38, Allan Jude wrote: > On 2014-11-20 10:34, Alex Povolotsky wrote: >> Hello >> >> I'm trying to install CentOS in bhyve. >> >> I do everything accordnig to >> https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html >> >> [18:30] backup:/<1>bhyve/oracle # cat /etc/bhyve/oracle/device.map >> (hd0) /dev/zvol/data/oracle >> (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso >> >> >> [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m >> /etc/bhyve/oracle/device.map -M 16G oracle >> >> grub> ls (cd0)/isolinux >> boot.cat boot.msg grub.conf initrd.img isolinux.bin isolinux.cfg >> memtest splash.jpg TRANS.TBL vesamenu.c32 vmlinuz >> >> grub> linux (cd0)/isolinux/vmlinuz >> grub> initrd (cd0)/isolinux/initrd.img >> error: you need to load the kernel first. >> grub> >> >> >> And that's all >> >> Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my bhyve OK, >> but need Linux... >> >> Alex >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@f= reebsd.org" >> >=20 > If you read the handbook, it first does an 'ls' on the cd. You have to > load files that actually exist, they might have slightly different name= s. >=20 > The instructions in the handbook were based on how the files were named= > on a CentOS 6.5 cd, 6.6 might be slightly different. >=20 Er, I see you did that, my bad. --=20 Allan Jude --frso1FSQjrDRaJMS0kkErkxtsRXf9UOrt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJUbg0CAAoJEJrBFpNRJZKfldoQAKegJ0N4yWI8pyKrJWiGrHtp vnLoWINb+76+5LX6fsZwMBWfujKDUWZlG9wotKTFQmcVGTOTqaEmDwot7grer5PX gxowc0Nqg2xkmUf4ysuccqNgBIHsHb4fsLqM5pbDpw5C8Qhzo0dzv1obdWbR4ySY 3U4RDfJ0wgGEr1jzo6fVTx8IqsWMI3SLsqKAltUKRcpdEr/CSg7tI3XgORgg97U2 KQ49zzPkwrrNHXbbvXMF44m/m/6GCmGiaw5VMlHBKK84zZ542zM+Gqo5ym2V0ddn 0W9r2syeAfO7vWL9spOsEyOBu8izWkomI1SBLKx+H1X9oAUeNp1P+rmD7dmXmY0a +QAmNBdF3z84VMeC855C5GdCDUqtcLQcZ9PtQIFx8Ap80Rib4RxEUdiEDFGO4sYY mK99VA3jcmEDLHFS0YRM6qzLV10ap2d6fJGdlMAAFG/kUzFzhTmcon9VTa53E7Gv QmpgSy82iUreywhZXeasfFyuj+nDvo6T60LzzNPlCKNr6JFZG+ZkwJg6Tx0g2W53 iV8QawV/pBTm4z83Y1/ojI+4TbvZ+eEbmsE1Qe012qBKGye4czy4vciudNEGzeA5 0Bb3yf/Vr+dtHqM1/0iVHA0tjMSbLYnOvsSpBhQt82Hou7DLhXevBIeU1kBAiOTE N0mPayaxf13v72dWiFLD =V2mx -----END PGP SIGNATURE----- --frso1FSQjrDRaJMS0kkErkxtsRXf9UOrt-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 16:18:45 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4860558F for ; Thu, 20 Nov 2014 16:18:45 +0000 (UTC) Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 14BA9FFE for ; Thu, 20 Nov 2014 16:18:44 +0000 (UTC) Received: by mail-ie0-f175.google.com with SMTP id at20so3079738iec.20 for ; Thu, 20 Nov 2014 08:18:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=UdSKn6whWkdgFymkl9OMWfyoR8HxoYbhj/WCMKqk/Yw=; b=NlMXGMqqOrIp6M4jYfNKllirVVfcjjWg98bpHwUw3XM5nka3S6hBI8ek4HpDvASnfW NRfCBphvandhDLyVYtJZzA+3QPHVVMQs443M3wlgJAwEzEkSLCm/AfzCv6BpN2pdVmF0 MymUdsMUxT252WD5qLCflVdutCSNTAku4d/pDqxbAyAhl1d8APS4a8VTzbBSfGST9OAQ bgNlvvag8fbXaCKgbh3juRWHcRWLPEOKy9th7VaZlEKSm0arIpCLs/xJg/tKjN2t9BcE JPe0Z88KtF7gOJS0ZKaFf3Avhcc2HzLVAW20XtKFKM5kEJVcWUBI0cdiiC3DfaN2ltK+ dDzA== X-Gm-Message-State: ALoCoQnXAGaJa0arQzkMV1LWt6ZHW5zIObsBuph3V/m/+29hTWgOGze7HSKQuayXbBF4OUIXrRGc X-Received: by 10.42.204.81 with SMTP id fl17mr1650363icb.57.1416500318216; Thu, 20 Nov 2014 08:18:38 -0800 (PST) Received: from m (c-98-209-117-232.hsd1.mi.comcast.net. [98.209.117.232]) by mx.google.com with ESMTPSA id kb7sm2664025igb.16.2014.11.20.08.18.36 for (version=SSLv3 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 20 Nov 2014 08:18:37 -0800 (PST) From: Conrad Meyer X-Google-Original-From: Conrad Meyer Date: Thu, 20 Nov 2014 11:18:35 -0500 To: Alex Povolotsky Subject: Re: CentOS in bhyve Message-ID: <20141120111835.45fe7efc@m> In-Reply-To: <546E09FE.80703@webmail.sub.ru> References: <546E09FE.80703@webmail.sub.ru> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.24; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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, 20 Nov 2014 16:18:45 -0000 On Thu, 20 Nov 2014 18:34:22 +0300 Alex Povolotsky wrote: > Hello >=20 > I'm trying to install CentOS in bhyve. >=20 > I do everything accordnig to > https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html >=20 > [18:30] backup:/<1>bhyve/oracle # > cat /etc/bhyve/oracle/device.map (hd0) /dev/zvol/data/oracle > (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso >=20 >=20 > [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m > /etc/bhyve/oracle/device.map -M 16G oracle >=20 > grub> ls (cd0)/isolinux > boot.cat boot.msg grub.conf initrd.img isolinux.bin > isolinux.cfg memtest splash.jpg TRANS.TBL vesamenu.c32 > vmlinuz >=20 > grub> linux (cd0)/isolinux/vmlinuz > grub> initrd (cd0)/isolinux/initrd.img > error: you need to load the kernel first. > grub> >=20 >=20 > And that's all >=20 > Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my > bhyve OK, but need Linux... >=20 > Alex Hi Alex, Ok I'm dumb =E2=80=94 my earlier issue was a result of failing to create the backing HDD. Now it boots and loads CentOS 6.6 fine. Try updating grub-bhyve? Best, Conrad From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 16:40:46 2014 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 923EEE2A for ; Thu, 20 Nov 2014 16:40:46 +0000 (UTC) Received: from mail.sub.ru (mail.sub.ru [88.212.205.2]) by mx1.freebsd.org (Postfix) with SMTP id C92D42E6 for ; Thu, 20 Nov 2014 16:40:45 +0000 (UTC) Received: (qmail 11020 invoked from network); 20 Nov 2014 19:40:43 +0300 Received: from tarkhil.infotel.ru (tarkhil.infotel.ru [195.170.223.197]) by mail.sub.ru ([88.212.205.2]) with ESMTP via TCP; 31 Dec 1969 23:59:59 -0000 Message-ID: <546E1985.8090801@webmail.sub.ru> Date: Thu, 20 Nov 2014 19:40:37 +0300 From: Alex Povolotsky User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Conrad Meyer Subject: Re: CentOS in bhyve References: <546E09FE.80703@webmail.sub.ru> <20141120111835.45fe7efc@m> In-Reply-To: <20141120111835.45fe7efc@m> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Antivirus: avast! (VPS 141120-0, 20.11.2014), Outbound message X-Antivirus-Status: Clean 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, 20 Nov 2014 16:40:46 -0000 grub2-bhyve-0.24 Updated to 0.30 And everything worked on. Sorry, I did not think that grub2-bhyve evolves THAT fast! On 20.11.2014 19:18, Conrad Meyer wrote: > On Thu, 20 Nov 2014 18:34:22 +0300 Alex Povolotsky > wrote: > >> Hello >> >> I'm trying to install CentOS in bhyve. >> >> I do everything accordnig to >> https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html >> >> >> [18:30] backup:/<1>bhyve/oracle # >> cat /etc/bhyve/oracle/device.map (hd0) /dev/zvol/data/oracle >> (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso >> >> >> [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m >> /etc/bhyve/oracle/device.map -M 16G oracle >> >> grub> ls (cd0)/isolinux boot.cat boot.msg grub.conf initrd.img >> isolinux.bin isolinux.cfg memtest splash.jpg TRANS.TBL >> vesamenu.c32 vmlinuz >> >> grub> linux (cd0)/isolinux/vmlinuz grub> initrd >> (cd0)/isolinux/initrd.img error: you need to load the kernel >> first. grub> >> >> >> And that's all >> >> Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my bhyve >> OK, but need Linux... >> >> Alex > > Hi Alex, > > Ok I'm dumb — my earlier issue was a result of failing to create > the backing HDD. Now it boots and loads CentOS 6.6 fine. Try > updating grub-bhyve? > > Best, Conrad > From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 16:42:32 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 282CDEB4 for ; Thu, 20 Nov 2014 16:42:32 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id E005C38F for ; Thu, 20 Nov 2014 16:42:31 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 9446B1235C; Fri, 21 Nov 2014 02:42:29 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZW30748 (AUTH peterg@ptree32.com.au); Fri, 21 Nov 2014 02:42:28 +1000 Message-ID: <546E19F1.1040906@freebsd.org> Date: Thu, 20 Nov 2014 08:42:25 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alex Povolotsky Subject: Re: CentOS in bhyve References: <546E09FE.80703@webmail.sub.ru> In-Reply-To: <546E09FE.80703@webmail.sub.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Thu, 20 Nov 2014 16:42:32 -0000 Hi Alex, > [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m > /etc/bhyve/oracle/device.map -M 16G oracle grub-bhyve only accepts memory in units of MB, so you'll have to change that to 1024. Note that grub-bhyve has now been fixed to allow the K|M|G|T suffixes to be used. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 17:57:18 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67B104E6 for ; Thu, 20 Nov 2014 17:57:18 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 43538F1C for ; Thu, 20 Nov 2014 17:57:18 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 5B99DB99A; Thu, 20 Nov 2014 12:57:17 -0500 (EST) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: 'repz' instruction not supported. Date: Thu, 20 Nov 2014 11:54:18 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201411201154.19007.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 20 Nov 2014 12:57:17 -0500 (EST) 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, 20 Nov 2014 17:57:18 -0000 On Thursday, November 20, 2014 1:30:41 am Ashutosh Kumar wrote: > Hi > We have found that emulation of 'repz' instruction is not supported in bhyve. This is causing VM_EXIT for Guest OS. Do we have plans to add support for instructions like 'repz'. What are you using repz for? Is it memory access to some device? -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 17:57:17 2014 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 E03704E4; Thu, 20 Nov 2014 17:57:17 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B8CEFF1B; Thu, 20 Nov 2014 17:57:17 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A7F61B999; Thu, 20 Nov 2014 12:57:16 -0500 (EST) From: John Baldwin To: freebsd-virtualization@freebsd.org Subject: Re: bhyve remote kgdb does not support kernel modules... Date: Thu, 20 Nov 2014 11:52:09 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <20141115093713.GY24601@funkthat.com> <54677DFC.70708@freebsd.org> <20141115181523.GA24601@funkthat.com> In-Reply-To: <20141115181523.GA24601@funkthat.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201411201152.09805.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 20 Nov 2014 12:57:16 -0500 (EST) 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, 20 Nov 2014 17:57:18 -0000 On Saturday, November 15, 2014 1:15:23 pm John-Mark Gurney wrote: > Julian Elischer wrote this message on Sun, Nov 16, 2014 at 00:23 +0800: > > On 11/15/14, 5:43 PM, John-Mark Gurney wrote: > > >John-Mark Gurney wrote this message on Sat, Nov 15, 2014 at 01:37 -0800: > > >>So, I got remote kgdb working w/ bhyve, but kernel modules aren't > > >>loaded... > > >> > > >>I'm getting: > > >>(kgdb) bt > > >>#0 kdb_enter (why=0xffffffff8102ee88 "panic", msg=) > > >> at ../../../kern/subr_kdb.c:444 > > >>#1 0xffffffff8094aa79 in vpanic (fmt=, > > >> ap=) at ../../../kern/kern_shutdown.c:739 > > >>#2 0xffffffff8094a8c9 in kassert_panic (fmt=) > > >> at ../../../kern/kern_shutdown.c:634 > > >>#3 0xffffffff8093583c in __mtx_lock_flags (c=0xfffff80002919720, opts=0, > > >> file=0xffffffff81c3f0fa > > >> "/usr/home/jmg/freebsd.p4/opencrypto/sys/modules/aesni/../../crypto/aesni/aesni.c", line=442) at ../../../kern/kern_mutex.c:217 > > >>#4 0xffffffff81c3e3a7 in ?? () > > >>#5 0xfffff80002a474a0 in ?? () > > >>#6 0xfffff80002919720 in ?? () > > >> > > >>Where those should be in the aesni.ko module... If I run kgdb on a > > >>local machine, it properly finds the kernel modules... Any hits on > > >>how to fix this? > > > > works for me.. > > the modules I'm debugging are not compiled in. > > you have to have the modules in the standard place ONE THE GDB HOST. > > I make a chroot with an image of the machine being debugged, PLUS the > > sources. > > and then run kgdb from inside that chroot. > > Ahh, that's right, kgdb isn't smart enough to know when you've pointed > it to the kernel build dir whereh the modules are... :( gdb isn't smart enough if you run with all the shared libraries in the current directory either. Note you can always use 'add-kld /path/to/foo.ko' when it can't find a useful module path. Also, you don't have to use a chroot. You can use 'solib-absolute-prefix' (it's documented for shared libraries and kgdb treats modules as shared libraries) and set it to the DESTDIR you use when you install the kernel. That is: % cd /path/to/kernel/amd64/compile/FOO % make % make install BINOWN= DESTDIR=/someplace % kgdb kernel.debug (kgdb) set solib-absolute-prefix /someplace/ (kgdb) target remote (I have a local patch to vmrun.sh on my laptop that always ties a nmdm interface on COM2 if nmdm is loaded so I can now attach kgdb to any VM without having to plan ahead). -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 18:07:36 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2F58DA53; Thu, 20 Nov 2014 18:07:36 +0000 (UTC) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A46BED2; Thu, 20 Nov 2014 18:07:35 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id hz20so2821554lab.20 for ; Thu, 20 Nov 2014 10:07:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=tFFKI6JR2xalCMzQyjPJ2FLLwUoR7ngwdpMvbVZZIZs=; b=yZlm9h4q1MmPeMw8SfFWYUKOfPdckoeyhVFGSubIGhb0uLYP7iQHmS1+vYSd1WNERz kJXNhoRtqtX8GRdxIThApc5I0NfRNzF1yFcJpgr7D2U8Bct22h8f157iY8odCzJ0MEuI /OVjiWp1RKPT2WoOmY6ZOEts7C4izzX54H10PfElmBCapYvqvKHTIHUVALUpN3FBkFWk alb/QS82HVqRli1J2IUGxy/lFWbS0jAgARvKxMjcq16Kooo3Xu2h/YjcHUyscO9XT+rd 1OOdPbrdrGUwQC0Z0nAkziENGCMPtogPl0BCC9dwlQNZBDPoZBq0MbjrLNf9tRGmKFTg UwwQ== MIME-Version: 1.0 X-Received: by 10.112.137.39 with SMTP id qf7mr12556323lbb.47.1416506853187; Thu, 20 Nov 2014 10:07:33 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Thu, 20 Nov 2014 10:07:33 -0800 (PST) Date: Thu, 20 Nov 2014 10:07:33 -0800 X-Google-Sender-Auth: FuQzAL6KAc12PdfjdXlO_eFU5Lo Message-ID: Subject: VIMAGE + pf security fix? From: Craig Rodrigues To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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, 20 Nov 2014 18:07:36 -0000 On Wed, Nov 19, 2014 at 6:05 AM, Bjoern A. Zeeb wrote: > > For people to use pf with VIMAGE we first MUST have the security fix > imported that I pointed out a couple of times in the past. > At this link: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 I see the security issue mentioned, but I can't find the patch that fixes the problem. Where is the patch? Thanks. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 20 20:09:50 2014 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 EBB7EACC for ; Thu, 20 Nov 2014 20:09:50 +0000 (UTC) Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7C6D401 for ; Thu, 20 Nov 2014 20:09:50 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id y20so3487736ier.4 for ; Thu, 20 Nov 2014 12:09:44 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:date:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=V0LZQtUgx5+jCYxux7bhxnOq6KuhZLYWqIkOcdNNHCs=; b=MKzsL/VNBtHZFo3Pw7fabA2TiWnUfRc4Ob61SfE3ZQn6Rp7zrHYCvlTGLw1Xo8ZKaC xrvjmZQ7fdFWdzxpTBSOI/dAmkmEgATWsIozU0swF/5HClcziPJpNnG0vJC+2YjL+pdt lFUh3oNSVwZ8cicF0DroHOck3BunW2qxpiC6eACpQjpVecn6LaFFO/udPmHxeIkV7o5g /jfmWhHQ1KKMnCxcJnO/94NzysfrdEfcAqgcJPVnxcriDgb3Ao46u6ZN5VErodd0rA1a fwBTjdn9ntGOTEqWjXWr+faLlPMnnuKVeNF+ff+iDm7P5L5Q0i8ejbHQx1ugrBgRruXd eOtw== X-Gm-Message-State: ALoCoQn2sW2CTpb3DFaEA1TVuSsOjSjWF/FtnAwgKRKIs2N3NCynMbfvSEv7tq7Vcbkf33F8WfHb X-Received: by 10.43.148.74 with SMTP id kf10mr8784713icc.9.1416499708507; Thu, 20 Nov 2014 08:08:28 -0800 (PST) Received: from m (c-98-209-117-232.hsd1.mi.comcast.net. [98.209.117.232]) by mx.google.com with ESMTPSA id vf6sm1691177igb.6.2014.11.20.08.08.26 for (version=SSLv3 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 20 Nov 2014 08:08:27 -0800 (PST) From: Conrad Meyer X-Google-Original-From: Conrad Meyer Date: Thu, 20 Nov 2014 11:08:25 -0500 To: Alex Povolotsky Subject: Re: CentOS in bhyve Message-ID: <20141120110825.1b452056@m> In-Reply-To: <546E09FE.80703@webmail.sub.ru> References: <546E09FE.80703@webmail.sub.ru> X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.24; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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: Thu, 20 Nov 2014 20:09:51 -0000 On Thu, 20 Nov 2014 18:34:22 +0300 Alex Povolotsky wrote: > Hello > > I'm trying to install CentOS in bhyve. > > I do everything accordnig to > https://www.freebsd.org/doc/handbook/virtualization-host-bhyve.html > > [18:30] backup:/<1>bhyve/oracle # > cat /etc/bhyve/oracle/device.map (hd0) /dev/zvol/data/oracle > (cd0) /home/bhyve/CentOS-6.6-x86_64-netinstall.iso > > > [18:30] backup:/<1>bhyve/oracle # grub-bhyve -r cd0 -m > /etc/bhyve/oracle/device.map -M 16G oracle > > grub> ls (cd0)/isolinux > boot.cat boot.msg grub.conf initrd.img isolinux.bin > isolinux.cfg memtest splash.jpg TRANS.TBL vesamenu.c32 > vmlinuz > > grub> linux (cd0)/isolinux/vmlinuz > grub> initrd (cd0)/isolinux/initrd.img > error: you need to load the kernel first. > grub> Hi Alex, I don't see the same (maybe a newer version of grub-bhyve). Instead: grub> linux (cd)/isolinux/vmlinuz grub> initrd (cd)/isolinux/initrd.img grub> boot And then grub-bhyve crashes: 2014-11-20 16:05:11.251+0000: 34493981696: error : bhyveMonitorIO:88 : Guest centos got signal 11 and crashed (I am running bhyve under libvirt. The "monitor" patch is pending upstream.) > > > And that's all > > Tried CentOS 7.0 and 6.6. No difference. FreeBSD runs in my > bhyve OK, but need Linux... > > Alex I'll give 7.0 a whirl... Best, Conrad From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 07:50:18 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7EF96DBE; Fri, 21 Nov 2014 07:50:18 +0000 (UTC) Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A77B7C6; Fri, 21 Nov 2014 07:50:18 +0000 (UTC) Received: by mail-pa0-f48.google.com with SMTP id rd3so4329121pab.7 for ; Thu, 20 Nov 2014 23:50:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=gBjZP8/z0kWpf4B4OSBMSijxxUZ6Sbrh4w3+5CXQJDw=; b=d4zOTjPjaz4Qm7jamU34xW97AVz3tIgaxmpzMdLF+OgKXh5xcz9ul6gHHxsffZnwWv uaEKu55xwaT2/KtEKqPw2adLq4S0Br2LZkdrV13Xbc3EzBWM+KCPTeE9NUOYOq9Nzxqw MwDP2fomh/4sAGvTsHyGlSc92AUt3aO24f1DsdvIWeXT9aolLcHjQoeglyVcFE15Mb3P xi9oIpbo6SgDYuBvpj8skCSIz2SFAhYZP00kJj9s/w2BxpHItu8DOpPgmvl7yyM1U9A/ Swno1VAvoOLnU29r17GgO4fggmG9VX3YznUH+BlJ7lxgr0ohChd3csoGkFi3+I6rxpwy uWdQ== MIME-Version: 1.0 X-Received: by 10.66.241.239 with SMTP id wl15mr4388381pac.15.1416556217854; Thu, 20 Nov 2014 23:50:17 -0800 (PST) Sender: ermal.luci@gmail.com Received: by 10.70.70.166 with HTTP; Thu, 20 Nov 2014 23:50:17 -0800 (PST) In-Reply-To: References: Date: Fri, 21 Nov 2014 08:50:17 +0100 X-Google-Sender-Auth: oYKMc_0f6wmYX4NTIA8ivYej6t4 Message-ID: Subject: Re: VIMAGE + pf security fix? From: =?UTF-8?Q?Ermal_Lu=C3=A7i?= To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net , "Bjoern A. Zeeb" , "freebsd-virtualization@freebsd.org" , freebsd-arch 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: Fri, 21 Nov 2014 07:50:18 -0000 The fix for that was imported with the new import of pf(4) AFARIR. On Thu, Nov 20, 2014 at 7:07 PM, Craig Rodrigues wrote: > On Wed, Nov 19, 2014 at 6:05 AM, Bjoern A. Zeeb wrote: > > > > > For people to use pf with VIMAGE we first MUST have the security fix > > imported that I pointed out a couple of times in the past. > > > > At this link: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 > > I see the security issue mentioned, but I can't find the patch that fixes > the problem. > Where is the patch? > > Thanks. > -- > Craig > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > -- Ermal From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 08:07:00 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A5E1AEC; Fri, 21 Nov 2014 08:07:00 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3FA7196F; Fri, 21 Nov 2014 08:07:00 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id gf13so3786685lab.14 for ; Fri, 21 Nov 2014 00:06:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=R6NaaR9sUPaIWwpNqAZOXjKSZ2hiSD7+wU7brstTvew=; b=lwGL8fO4IZs2Q789fdDJNV1LczNaheEFzY6b6BfP5Vn664k9nbzseGUb1Ml8gP3EB7 dJe7GBkC6j5xKuZxEuWUXpmGuMW2UB5T+or/6wBwilmmQApzYHgoJa/2CL7217/bqJbP duFq1EGpiPAwssx5qqu3hyUFpqaLL1qGv4NOYGWMQuKMiejkfAnN2qbIt62qgBD6eNOP 0gIXz3lfyZP7bEhFpQ7XL2cTD/64cGosjwvzSCDAHuFzD7Nv4HbKgfOS8hq0ZqHNahGo KFb6hHzpU/57q/9HKSjGQ2BN6rk56rI88NbteHGZpwyTpCwEjMLJ0Ra093yr1mlAH4RH wlmQ== MIME-Version: 1.0 X-Received: by 10.112.16.39 with SMTP id c7mr2550923lbd.19.1416557218197; Fri, 21 Nov 2014 00:06:58 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Fri, 21 Nov 2014 00:06:58 -0800 (PST) In-Reply-To: References: Date: Fri, 21 Nov 2014 00:06:58 -0800 X-Google-Sender-Auth: NvEn0fM3QA5OFreLz0ufAqhcRlg Message-ID: Subject: Re: VIMAGE + pf security fix? From: Craig Rodrigues To: "Bjoern A. Zeeb" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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: Fri, 21 Nov 2014 08:07:00 -0000 On Thu, Nov 20, 2014 at 10:07 AM, Craig Rodrigues wrote: > On Wed, Nov 19, 2014 at 6:05 AM, Bjoern A. Zeeb wrote: > >> >> For people to use pf with VIMAGE we first MUST have the security fix >> imported that I pointed out a couple of times in the past. >> > > At this link: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 > > I see the security issue mentioned, but I can't find the patch that fixes > the problem. > Where is the patch? > I read this link: http://esec-lab.sogeti.com/post/2010/12/09/CVE-2010-3830-iOS-4.2.1-packet-filter-local-kernel-vulnerability and I think this is the fix: http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf_ioctl.c?rev=1.236&content-type=text/x-cvsweb-markup but I can't even apply that patch to our pf_ioctl.c. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 08:08:18 2014 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 44081273 for ; Fri, 21 Nov 2014 08:08:18 +0000 (UTC) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id CB2D7983 for ; Fri, 21 Nov 2014 08:08:17 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id k14so5802996wgh.10 for ; Fri, 21 Nov 2014 00:08:16 -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=lYLwtPsyXKBfiFJLYj++WMBRCwjorRP2p6wRf0aHvhw=; b=vTol8s0dCjAez5f8ePAeFoZVfdhofmKbZ6GBabLRfZfS36GnncLtrwemGjZUEXQQM2 jGiuaNT/UuQnzNDQKu2H9m0C7E4Cb7ADHbYz7q4aAj4svAHCdLmvIRNWZeOvLscU7TPz jA91btKqCi2DaEc9205CsGQja3dabq/7Z0qvDb4tlJZrpY/QKrTPIPnEnjpwdZRX1o7v CLCWnXepqZiEpFv5hKHK8qi6DwieXfZ3tiOaLSFlKStOMw4IYBC2tj+9BLiR6phPCyZu mXmMKAPnFnAwiCkmUkCQSgMUorV/KBpje3NfQd1y8dZfDozYHjudvPEw733kas7ZYRGd +YOA== MIME-Version: 1.0 X-Received: by 10.194.243.164 with SMTP id wz4mr4634714wjc.129.1416557295237; Fri, 21 Nov 2014 00:08:15 -0800 (PST) Received: by 10.27.12.168 with HTTP; Fri, 21 Nov 2014 00:08:15 -0800 (PST) In-Reply-To: References: Date: Fri, 21 Nov 2014 00:08:15 -0800 Message-ID: Subject: Re: 'repz' instruction not supported. From: Neel Natu To: Ashutosh Kumar 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: Fri, 21 Nov 2014 08:08:18 -0000 Hi Ashutosh, On Wed, Nov 19, 2014 at 10:30 PM, Ashutosh Kumar wrote: > Hi > We have found that emulation of 'repz' instruction is not supported in bhyve. This is causing VM_EXIT for Guest OS. Do we have plans to add support for instructions like 'repz'. > 'repz' is actually an instruction prefix. The two instructions with which 'repz' is allowed are 'cmps' and 'scas'. Both these instructions typically don't need to be emulated since they operate on strings in "regular" guest memory. Is your guest emitting these instructions to access MMIO? Can you share an objdump with the offending instructions? best Neel > RegardsAshutosh > _______________________________________________ > 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 Fri Nov 21 10:08:15 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6277AE04 for ; Fri, 21 Nov 2014 10:08:15 +0000 (UTC) Received: from SNT004-OMC1S44.hotmail.com (snt004-omc1s44.hotmail.com [65.54.61.81]) (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 3A03C8BF for ; Fri, 21 Nov 2014 10:08:15 +0000 (UTC) Received: from SNT150-W9 ([65.55.90.9]) by SNT004-OMC1S44.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Fri, 21 Nov 2014 02:07:08 -0800 X-TMN: [UgYeEPh+sOGjXsnBCYrK9xo8/iCe8sGE] X-Originating-Email: [mrashutosh@hotmail.com] Message-ID: From: Ashutosh Kumar To: Neel Natu Subject: RE: 'repz' instruction not supported. Date: Fri, 21 Nov 2014 10:07:08 +0000 Importance: Normal In-Reply-To: References: , MIME-Version: 1.0 X-OriginalArrivalTime: 21 Nov 2014 10:07:08.0678 (UTC) FILETIME=[E8F8E260:01D00572] Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Fri, 21 Nov 2014 10:08:15 -0000 Yes you are right 'repz' prefixes is added to the =91cmps=92 and 'scas' ins= tructions.=0A= =0A= The actual opcode is =93F3 A5=94 which is =91rep movs=92 (disassembly is sh= owing=0A= =91repz=92).=0A= =0A= =0A= =0A= Yes the guest is emitting these instructions to access MMIO=0A= (local apic) RegardsAshutosh > Date: Fri=2C 21 Nov 2014 00:08:15 -0800 > Subject: Re: 'repz' instruction not supported. > From: neelnatu@gmail.com > To: mrashutosh@hotmail.com > CC: freebsd-virtualization@freebsd.org >=20 > Hi Ashutosh=2C >=20 > On Wed=2C Nov 19=2C 2014 at 10:30 PM=2C Ashutosh Kumar wrote: > > Hi > > We have found that emulation of 'repz' instruction is not supported in = bhyve. This is causing VM_EXIT for Guest OS. Do we have plans to add suppor= t for instructions like 'repz'. > > >=20 > 'repz' is actually an instruction prefix. The two instructions with > which 'repz' is allowed are 'cmps' and 'scas'. Both these instructions > typically don't need to be emulated since they operate on strings in > "regular" guest memory. >=20 > Is your guest emitting these instructions to access MMIO? Can you > share an objdump with the offending instructions? >=20 > best > Neel >=20 > > RegardsAshutosh > > _______________________________________________ > > freebsd-virtualization@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > > To unsubscribe=2C send any mail to "freebsd-virtualization-unsubscribe@= freebsd.org" = From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 10:52:14 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8BBA38F7; Fri, 21 Nov 2014 10:52:14 +0000 (UTC) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E7EFD54; Fri, 21 Nov 2014 10:52:13 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id C817425D3AB1; Fri, 21 Nov 2014 10:52:10 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 0511FC76FCE; Fri, 21 Nov 2014 10:52:10 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id S2Zsv9uDAm70; Fri, 21 Nov 2014 10:52:08 +0000 (UTC) Received: from [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6] (orange-tun0-ula.sbone.de [IPv6:fde9:577b:c1a9:4420:cabc:c8ff:fe8b:4fe6]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 3AD78C76FE0; Fri, 21 Nov 2014 10:52:06 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: VIMAGE + pf security fix? From: "Bjoern A. Zeeb" In-Reply-To: Date: Fri, 21 Nov 2014 10:52:05 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Craig Rodrigues X-Mailer: Apple Mail (2.1878.6) Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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: Fri, 21 Nov 2014 10:52:14 -0000 On 21 Nov 2014, at 08:06 , Craig Rodrigues wrote: > On Thu, Nov 20, 2014 at 10:07 AM, Craig Rodrigues = > wrote: >=20 >> On Wed, Nov 19, 2014 at 6:05 AM, Bjoern A. Zeeb = wrote: >>=20 >>>=20 >>> For people to use pf with VIMAGE we first MUST have the security fix >>> imported that I pointed out a couple of times in the past. >>>=20 >>=20 >> At this link: = http://cve.mitre.org/cgi-bin/cvename.cgi?name=3DCVE-2010-3830 >>=20 >> I see the security issue mentioned, but I can't find the patch that = fixes >> the problem. >> Where is the patch? >>=20 >=20 > I read this link: > = http://esec-lab.sogeti.com/post/2010/12/09/CVE-2010-3830-iOS-4.2.1-packet-= filter-local-kernel-vulnerability >=20 > and I think this is the fix: > = http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf_ioctl.c?rev=3D1.23= 6&content-type=3Dtext/x-cvsweb-markup >=20 > but I can=92t even apply that patch to our pf_ioctl.c. to my best knowledge we have never pulled a fix for this in. The last = =93sync=94 of pf was way before that vulnerability (unless I completely = missed something). =97=20 Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 15:58:43 2014 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 AAC8BCC9; Fri, 21 Nov 2014 15:58:43 +0000 (UTC) Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 62ACA21C; Fri, 21 Nov 2014 15:58:43 +0000 (UTC) Received: from mx.elandsys.com (IDENT:logan@localhost [127.0.0.1]) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id sALFweOF008023 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Nov 2014 07:58:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1416585521; x=1416671921; bh=GUTTJGAZaS3KWrR2LQmcTiY1Gvfb/C7LGwVwlD/eLnw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=j8hEZBV8UvlULwgCiamh3qGNiLnoRTTEj6Mgng5zbiD1WYxUF5EzzDL56H5l8fk6U 4/RzUCxcZAiTkRE3HJpK5E9ERcjJImZD7cT4f7PlqCEIrbi6xNhiMu1CZMFhh49gN+ Pxf/tNbOZnnMt++ucoYkxnE7gU2BWHFu6zsefL/w= DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1416585521; x=1416671921; i=@elandsys.com; bh=GUTTJGAZaS3KWrR2LQmcTiY1Gvfb/C7LGwVwlD/eLnw=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=UEidzyoOco0RtOHoWObL3Eyvb2Qr5eKUZhcf2bVU9SgUoPv3Ux6YF6+vuBTnF0unc zCzAs1ifbwWPdcwt/URkaIfqVfWuj+gtd8UdBVYuw5V0Ksj3VMa+SOGE976ZI4Z9GV uzKw1FIWz80VBAMJfDyMRM2S+x36VScaG1Uq5tBM= Received: (from logan@localhost) by mx.elandsys.com (8.14.5/8.14.5/Submit) id sALFwd0Z016967; Fri, 21 Nov 2014 07:58:39 -0800 (PST) X-Authentication-Warning: mx.elandsys.com: logan set sender to logan@elandsys.com using -f Date: Fri, 21 Nov 2014 07:58:39 -0800 From: Loganaden Velvindron To: "Bjoern A. Zeeb" Subject: Re: VIMAGE + pf security fix? Message-ID: <20141121155839.GA15001@mx.elandsys.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Net , "freebsd-virtualization@freebsd.org" , freebsd-arch 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: Fri, 21 Nov 2014 15:58:43 -0000 On Fri, Nov 21, 2014 at 10:52:05AM +0000, Bjoern A. Zeeb wrote: > > On 21 Nov 2014, at 08:06 , Craig Rodrigues wrote: > > > On Thu, Nov 20, 2014 at 10:07 AM, Craig Rodrigues > > wrote: > > > >> On Wed, Nov 19, 2014 at 6:05 AM, Bjoern A. Zeeb wrote: > >> > >>> > >>> For people to use pf with VIMAGE we first MUST have the security fix > >>> imported that I pointed out a couple of times in the past. > >>> > >> > >> At this link: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3830 > >> > >> I see the security issue mentioned, but I can't find the patch that fixes > >> the problem. > >> Where is the patch? > >> > > > > I read this link: > > http://esec-lab.sogeti.com/post/2010/12/09/CVE-2010-3830-iOS-4.2.1-packet-filter-local-kernel-vulnerability > > > > and I think this is the fix: > > http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/sys/net/pf_ioctl.c?rev=1.236&content-type=text/x-cvsweb-markup > > > > but I can?t even apply that patch to our pf_ioctl.c. > > to my best knowledge we have never pulled a fix for this in. The last ?sync? of pf was way before that vulnerability (unless I completely missed something). I'd be interested in helping to fix this, as I depend on this. > > ? > Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 21 19:22:09 2014 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 EBBC49D3 for ; Fri, 21 Nov 2014 19:22:08 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8C9ABDEB for ; Fri, 21 Nov 2014 19:22:08 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id n3so206251wiv.17 for ; Fri, 21 Nov 2014 11:22:06 -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:content-transfer-encoding; bh=rL6K2FHHnDvorlbb3P0sWNquO0p5+WDxPZig/madq8E=; b=yfr9/3gztTz1ZWS9hY+sbU2k485VooB/MVpax9LvEmexsw0QeCj8+/i2SsB+QncNJL 5X9VSiebId82mSRs/icqvvdDL6lOCjXbOHCDctF1aK0QD/KZSbMmZE9lCx/M+Xuj802/ Z/Lm1nCpnlJwRWMJ7i8v8/mMiL6gggqWvwDGeqjWtnUKgykdojQGaMZ/D1hW/YCTYSbz C2OoHOlADf9CgKla+Sj7XAwyQBLKcpL8AvF4pPqe16tVajTbergUKjoG9j3fSGkJsrbF 1kHUJqJXtHiO/6LV2p3ol14y4LPz7dPEP7E6VUF7u0ChyEZeGNjai/ie6mKQBLbi+zUb yjyQ== MIME-Version: 1.0 X-Received: by 10.194.203.105 with SMTP id kp9mr10559312wjc.81.1416597726880; Fri, 21 Nov 2014 11:22:06 -0800 (PST) Received: by 10.27.12.168 with HTTP; Fri, 21 Nov 2014 11:22:06 -0800 (PST) In-Reply-To: References: Date: Fri, 21 Nov 2014 11:22:06 -0800 Message-ID: Subject: Re: 'repz' instruction not supported. From: Neel Natu To: Ashutosh Kumar Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: Fri, 21 Nov 2014 19:22:09 -0000 Hi Ashutosh, On Fri, Nov 21, 2014 at 2:07 AM, Ashutosh Kumar wr= ote: > Yes you are right 'repz' prefixes is added to the =E2=80=98cmps=E2=80=99 = and 'scas' > instructions. > > The actual opcode is =E2=80=9CF3 A5=E2=80=9D which is =E2=80=98rep movs= =E2=80=99 (disassembly is showing > =E2=80=98repz=E2=80=99). > > > > Yes the guest is emitting these instructions to access MMIO (local apic) > Bummer. I was hoping that it was a prefix stuck by the compiler for optimization (that could be ignored): http://repzret.org/p/repzret/ In any case, the primitives you will need to emulate MOVS exist in vmm_instruction_emul.c. I don't have any plans to work on this but would be happy to review/submit the patch that does the emulation. best Neel > > > Regards > Ashutosh > > >> Date: Fri, 21 Nov 2014 00:08:15 -0800 >> Subject: Re: 'repz' instruction not supported. >> From: neelnatu@gmail.com >> To: mrashutosh@hotmail.com >> CC: freebsd-virtualization@freebsd.org > >> >> Hi Ashutosh, >> >> On Wed, Nov 19, 2014 at 10:30 PM, Ashutosh Kumar >> wrote: >> > Hi >> > We have found that emulation of 'repz' instruction is not supported in >> > bhyve. This is causing VM_EXIT for Guest OS. Do we have plans to add s= upport >> > for instructions like 'repz'. >> > >> >> 'repz' is actually an instruction prefix. The two instructions with >> which 'repz' is allowed are 'cmps' and 'scas'. Both these instructions >> typically don't need to be emulated since they operate on strings in >> "regular" guest memory. >> >> Is your guest emitting these instructions to access MMIO? Can you >> share an objdump with the offending instructions? >> >> best >> Neel >> >> > RegardsAshutosh >> > _______________________________________________ >> > 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 Fri Nov 21 23:06:50 2014 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 97FDC647 for ; Fri, 21 Nov 2014 23:06:50 +0000 (UTC) Received: from mail-pd0-f172.google.com (mail-pd0-f172.google.com [209.85.192.172]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C6F4A79 for ; Fri, 21 Nov 2014 23:06:50 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id v10so6142422pde.17 for ; Fri, 21 Nov 2014 15:06:43 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=7Od6XCRlyr2EtUzo6gcAft6JPgP6PnPX186QV5N8c0U=; b=ION+sWs5aSOsccY1Ir8E0weqIpA7S61EGP1LUpfqFyig69NRelPdFuCYrr2rsl7iPO 7+JMMhdhR53HuXaoX/fh9BXG2vEUTDxzBiuqCdnKbwE9RxX+4WNp6XKmjtjsYTblJwZG F66rUzf89akNfCSMRvPf1q9L6Hh+zbqvh0wgMEkXkHVUhX0tBLsYPSM9gKa2WnoMoMp0 RKiA0XX+/scdzLWTeD6Bm/zgfU28y4YbdnERsF2K9xFrufrJq2y2NxGwSqoGDGXHkAu+ VJvBLj0ItB2Zf4GZMuOzohBj7a1BDIoo3AyCoO7vR86ZqGu1+1n1/d2CTYsqJ1MArL0J XD+g== X-Gm-Message-State: ALoCoQnYzQXakq7gasqpOX1QW16dQ4/EdQXLrNm7VtYS9h02xolTqBPaH0OH1U7OoT8TBkoLmWVM MIME-Version: 1.0 X-Received: by 10.70.128.132 with SMTP id no4mr11507473pdb.125.1416611203863; Fri, 21 Nov 2014 15:06:43 -0800 (PST) Sender: bsd-src@helfman.org Received: by 10.70.101.2 with HTTP; Fri, 21 Nov 2014 15:06:43 -0800 (PST) In-Reply-To: References: Date: Fri, 21 Nov 2014 15:06:43 -0800 X-Google-Sender-Auth: IBCC_U-4MY2VPWteu5acUMjd7C0 Message-ID: Subject: Re: Patch to virt-manager port for bhyve From: Jason Helfman To: Craig Rodrigues Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Jason Helfman , "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: Fri, 21 Nov 2014 23:06:50 -0000 On Fri, Aug 15, 2014 at 4:26 PM, Craig Rodrigues wrote: > Jason, > > Can you apply this patch to the virt-manager port: > > https://people.freebsd.org/~rodrigc/libvirt/patch-virtmanager-bhyve.txt > > > This allows using virt-manager to start a bhyve VM. I gave a > presentation on this > at Bay Area FreeBSD Users Group (BAFUG) recently: > > http://www.slideshare.net/CraigRodrigues1/libvirt-bhyve > > Roman Bogorodskiy has pushed a similar patch upstream, but the upstream > virt-manager code now depends on gtk3, and we don't fully have that > supported > in ports yet. Getting the newer virt-manager in ports with gtk3 > supported is a big job, that > I don't have the bandwidth for right now, but this patch helps a lot. > > Thanks! > -- > Craig > > Can you please send a new patch to me. I've updated the port to 1.1.0 and would be willing to add this in. Additionally, feel free to submit this patch upstream. Thanks! -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 22 05:12:07 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A8FB71AE; Sat, 22 Nov 2014 05:12:07 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6C031B7; Sat, 22 Nov 2014 05:12:06 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTP id 4E5C41222B; Sat, 22 Nov 2014 15:11:59 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZX00399 (AUTH peterg@ptree32.com.au); Sat, 22 Nov 2014 15:11:58 +1000 Message-ID: <54701B1D.40401@freebsd.org> Date: Fri, 21 Nov 2014 21:11:57 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Hiroki Sato Subject: Re: centos 4 bhyve guest References: <20141106.073131.1811725327096373192.hrs@allbsd.org> In-Reply-To: <20141106.073131.1811725327096373192.hrs@allbsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Sat, 22 Nov 2014 05:12:07 -0000 > Does anyone have an experience on booting CentOS 4 as a bhyve guest? This should now be partly fixed with grub2-bhyve 0.30 (the latest version in ports). I've tried the 4.8 x86_64 install DVD and booted with a single vCPU guest. SMP isn't yet working. 4.8/i386 has issues with the atpic and detecting PCI devices that I'm still looking into. With 4.8, I used ahci-hd for disks since there seemed to be sporadic issues with virtio-blk. In addition, 5.11 now seems to work fine, UP/SMP and with virtio-blk. later, Peter.