From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 02:52:47 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 D3E1A793 for ; Sun, 23 Nov 2014 02:52:47 +0000 (UTC) Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (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 8CCE980C for ; Sun, 23 Nov 2014 02:52:47 +0000 (UTC) Received: by mail-qg0-f49.google.com with SMTP id a108so5367988qge.22 for ; Sat, 22 Nov 2014 18:52:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; bh=WIMjZOUHbnP4FTg6yRGAsibrq0QG1aweL0aYsdkgf20=; b=wukJAddKZGOSZjXk/j1MT8IZokf330ZwdG5ERQDNc26V090yYa5x5vFKfVTz9jhESP SG9JDqHuiK7wF5NnJI6I6gbGx8SjR6RQgtQg6C4JP7dapxru83r5Y06RYvXrnZIAjxfw pqH728ayF6sCH2uyaKlDuXBBnHtRKfon9jw0x1fYhWBucoEtiOXKmOqoPClLRnaIp0Be kAnGpJGGJIx5BnsuCZpZBZS0+UdGe8BPobxMosCKmHmRzVZFX0NOE+TXrVGlbeA6dH0e c2FKrpFgCcJmTq4gbGy0a9kBqbU2lE+e/REHF+dHzAzA78HWQGwV/bWS4+1CTxHXT4he x3+A== X-Received: by 10.229.188.137 with SMTP id da9mr18526803qcb.6.1416711166723; Sat, 22 Nov 2014 18:52:46 -0800 (PST) Received: from hbsd-dev-local ([73.173.99.185]) by mx.google.com with ESMTPSA id p106sm8560340qgd.36.2014.11.22.18.52.46 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Nov 2014 18:52:46 -0800 (PST) Date: Sat, 22 Nov 2014 21:52:45 -0500 From: Shawn Webb To: freebsd-virtualization@freebsd.org Subject: bhyve cannot allocate memory Message-Id: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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, 23 Nov 2014 02:52:47 -0000 So I just built a new dev box with 32GB ram and an Intel Core i7-4790S (Haswell). I've enabled virtualization in the BIOS. I'm running 11.0-CURRENT, updated today. When I run `bhyveload -m 4G -d /dev/zvol/tank/vol/bhyve/latt-dev-01/disk-01 latt-dev-01`, bhyveload errors out with: vm_setup_memory: Cannot allocate memory But I've got 32GB ram, so I'm a little unsure as to why it can't allocate the required space. Can anyone shed some light on this? Is this a bug? Thanks, Shawn Webb From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:02:04 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 D0BA59C8 for ; Sun, 23 Nov 2014 03:02:04 +0000 (UTC) Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::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 872DB9F8 for ; Sun, 23 Nov 2014 03:02:04 +0000 (UTC) Received: by mail-qa0-f42.google.com with SMTP id j7so5161324qaq.29 for ; Sat, 22 Nov 2014 19:02:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=2f+b0/6AxPkkiAWQNh1U+kmcMzO+QXTmBwiV1uun3sI=; b=t+bYLxYvyVscWP3Rr17n0LlUHvbTqONYtKHOncJO3ANUepS8RXXFmVwEtYrLyGcXc7 li7fjQTTYwDLoZtkCvrxw/mTsyvhzaNxPkXDgVDqPpVbeo5FR3m2Dahsj4DKwaCGcSUa koEv7s85sBq1n+gwmzNzOXM2BdpQQI0424kqaqI/4E5Leg/1fsKMncl3ef5ozS+emDp+ srygF/+rBSMJODAdkyOUqvTT/6Vk9ZnL2OHtIp/3+v7Vd4XV1gugIeR5QTwd6o4B2RpG 3w35BHr74tLY2FgRAnbCprEJdj01wivU/xOh+Qr2hJ2TUNdOWtcXUsLRxRnvd3xEQFxr Ml1g== X-Received: by 10.224.40.202 with SMTP id l10mr18575714qae.7.1416711723715; Sat, 22 Nov 2014 19:02:03 -0800 (PST) Received: from hbsd-dev-local ([73.173.99.185]) by mx.google.com with ESMTPSA id z32sm8570416qgd.40.2014.11.22.19.02.03 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 22 Nov 2014 19:02:03 -0800 (PST) Date: Sat, 22 Nov 2014 22:02:02 -0500 From: Shawn Webb To: freebsd-virtualization@freebsd.org Subject: Re: bhyve cannot allocate memory Message-Id: <20141122220202.09523b0ae828993174af05d8@gmail.com> In-Reply-To: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII 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, 23 Nov 2014 03:02:04 -0000 On Sat, 22 Nov 2014 21:52:45 -0500 Shawn Webb wrote: > So I just built a new dev box with 32GB ram and an Intel Core i7-4790S (Haswell). I've enabled virtualization in the BIOS. I'm running 11.0-CURRENT, updated today. > > When I run `bhyveload -m 4G -d /dev/zvol/tank/vol/bhyve/latt-dev-01/disk-01 latt-dev-01`, bhyveload errors out with: vm_setup_memory: Cannot allocate memory > > But I've got 32GB ram, so I'm a little unsure as to why it can't allocate the required space. Can anyone shed some light on this? Is this a bug? > > Thanks, > > Shawn Webb Forgot to mention, I'm on r274859. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:15: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 3946DB97 for ; Sun, 23 Nov 2014 03:15:14 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id F0205AD7 for ; Sun, 23 Nov 2014 03:15:13 +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 68510129CF; Sun, 23 Nov 2014 13:15:11 +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 BZX17170 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:15:10 +1000 Message-ID: <5471513C.6040400@freebsd.org> Date: Sat, 22 Nov 2014 19:15:08 -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: Shawn Webb , freebsd-virtualization@freebsd.org Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> In-Reply-To: <20141122220202.09523b0ae828993174af05d8@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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, 23 Nov 2014 03:15:14 -0000 Hi Shawn, > Forgot to mention, I'm on r274859. I have a working system at r274783. A quick glance doesn't show anything obvious that may cause a regression, but I'm rebuilding now and will give it a try. Is your system stock FreeBSD or HardenedBSD ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:20:33 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 AF8FBD27; Sun, 23 Nov 2014 03:20:33 +0000 (UTC) Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::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 71C2DAFE; Sun, 23 Nov 2014 03:20:33 +0000 (UTC) Received: by mail-ob0-f170.google.com with SMTP id wp18so5799259obc.29 for ; Sat, 22 Nov 2014 19:20:32 -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=sQqiD3LHpecBd92jr8EenVfa4GCrtLA3ex/lJXoKmaQ=; b=eXjGLAANLbA5zAzJTRt/6GDfMEq+yfhh9U4XXLrjLHihD8m2LatSVJjKXve80BITtA 33tjsktyOZxI3P5cLmna+OpmukoDflFLTbyEG/AO6d85jIM//+ICmmpR4GCHkioqE6PZ gwhvwGj/z4+4xVa8ogyZjl0MBPLFK6po4tHxOMlle38PkIRfnxXA1fFjTovRp+dTHg5g R01KiFXQsEe+/0gEl03qySBn8FtFG6++bSAqsPHkb4VinucBQPg3Ax+TnZODlsNcnQvK L9dx+qgnfDDQen+/yRcJ/kjg2NqbvYhYDdumFerPZeP39Cnkit2EJ6xbAaHIjP/gBDuz l4zA== MIME-Version: 1.0 X-Received: by 10.60.156.165 with SMTP id wf5mr8079536oeb.21.1416712832681; Sat, 22 Nov 2014 19:20:32 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:20:32 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:20:32 -0800 (PST) In-Reply-To: <5471513C.6040400@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> Date: Sat, 22 Nov 2014 22:20:32 -0500 Message-ID: Subject: Re: bhyve cannot allocate memory From: Shawn Webb To: Peter Grehan Content-Type: text/plain; charset=UTF-8 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: Sun, 23 Nov 2014 03:20:33 -0000 On Nov 22, 2014 10:15 PM, "Peter Grehan" wrote: > > Hi Shawn, > > >> Forgot to mention, I'm on r274859. > > > I have a working system at r274783. A quick glance doesn't show anything obvious that may cause a regression, but I'm rebuilding now and will give it a try. > > Is your system stock FreeBSD or HardenedBSD ? It's hardenedBSD. I'll try a stock build tomorrow. The only change we have that could affect bhyve is the removal of map_at_zero. I've disabled all our other hardening features. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:27:57 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 4FD06D91 for ; Sun, 23 Nov 2014 03:27:57 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 11C3ABB4 for ; Sun, 23 Nov 2014 03:27:56 +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 DDD2C123FE; Sun, 23 Nov 2014 13:27:54 +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 BZX17342 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:27:53 +1000 Message-ID: <54715438.3090905@freebsd.org> Date: Sat, 22 Nov 2014 19:27:52 -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: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; 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: Sun, 23 Nov 2014 03:27:57 -0000 Hi Shawn, > It's hardenedBSD. I'll try a stock build tomorrow. The only change we > have that could affect bhyve is the removal of map_at_zero. This may be the issue. bhyve creates a kernel-use-only vmspace that represents guest memory (starting at 0), and is used to allow the VM system to manage the EPT paging structures (full details in the AsiaBSDcon paper at http://people.freebsd.org/~neel/bhyve/bhyve_nested_paging.pdf). Is there a way to bypass the map-at-zero check for this usage in HardenedBSD ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:30:06 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 D96BBDE0; Sun, 23 Nov 2014 03:30:05 +0000 (UTC) Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::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 A2493BBC; Sun, 23 Nov 2014 03:30:05 +0000 (UTC) Received: by mail-oi0-f44.google.com with SMTP id e131so5384737oig.3 for ; Sat, 22 Nov 2014 19:30:05 -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=lXrrEoFnWT6n67GWLdwV/85L8WVf9jiNpj3tuK10i2U=; b=GQVQpwklxzrB8/xQ6g0FJqLqXs2wxzrGwp9WvVOkRmV/rmEMQFKUlX+VqzAh1zFPcS 3PfPZETYY179EP+eEPpnDbdaKkNeqA43850I3VPYQJwGcnt8K/fL45IGz6/yAUkWeuz6 L2TQbsKqKWn98ajKO+kAu/SGZiP+gHD1qpLODGnemg/Dym9nGKIbln9IF+NKj342ihij m5tNloOsNooz2vSseY5FB3HHoWXMzBngzb8Vfbkkg06TuPmBjNGrORXXhRvDc3HNKyEn wi1W3/Ggqa5fePu2VNYod6zypmGSAPyhfSOvRCSQggQ4akzXGO3J40om3NFNMIt5lZqm 35tg== MIME-Version: 1.0 X-Received: by 10.202.201.77 with SMTP id z74mr6789012oif.70.1416713404994; Sat, 22 Nov 2014 19:30:04 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:30:04 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:30:04 -0800 (PST) In-Reply-To: <54715438.3090905@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> Date: Sat, 22 Nov 2014 22:30:04 -0500 Message-ID: Subject: Re: bhyve cannot allocate memory From: Shawn Webb To: Peter Grehan Content-Type: text/plain; charset=UTF-8 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: Sun, 23 Nov 2014 03:30:06 -0000 On Nov 22, 2014 10:27 PM, "Peter Grehan" wrote: > > Hi Shawn, > > >> It's hardenedBSD. I'll try a stock build tomorrow. The only change we >> have that could affect bhyve is the removal of map_at_zero. > > > This may be the issue. bhyve creates a kernel-use-only vmspace that represents guest memory (starting at 0), and is used to allow the VM system to manage the EPT paging structures (full details in the AsiaBSDcon paper at http://people.freebsd.org/~neel/bhyve/bhyve_nested_paging.pdf). > > Is there a way to bypass the map-at-zero check for this usage in HardenedBSD ? > > later, > > Peter. > There isn't. map_at_zero was fully removed. I can revert that change, though. Or is there a way to make bhyve work with out it (with a patch)? From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:31:40 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 7B910E3A; Sun, 23 Nov 2014 03:31:40 +0000 (UTC) Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::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 466A5C54; Sun, 23 Nov 2014 03:31:40 +0000 (UTC) Received: by mail-pd0-f172.google.com with SMTP id v10so7794353pde.3 for ; Sat, 22 Nov 2014 19:31:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=b9vqE8pe2vT6rpcr3StlUw78sQbfq8JCsgtNnm6x4Pk=; b=gBQpnY5C58sPRX65rdT87ofynTnfeN/B9PQeMNpSaiVPgvP/odzUuwEdXsQqPMo+pG wCL8A7V2gqCpqP7zHSxAIhRYrC3DkbPCYI6uJuSMVvp+ReCtXsyZqbCjgjcnjlUcOzXk UU8q1KYefzFfJKOl0jUWo38Q13ujvkyblDsYu6Gol30kBtS0GYOKSbvlupwh6+ngjW2j cgA9NQXlJ9rtsReNhLWqifHb9UspTFfQBSISFvPeWvbmdfnpOaJLPcp8oax5wJHpIEyx a3Cr5vCD/EyhONFMnkFhPq5WzV153s7SoeBtyCIgS2GAl1l81MyZUFrTBbt9ZYKlVy7G /fVQ== X-Received: by 10.70.91.71 with SMTP id cc7mr21035683pdb.79.1416713499903; Sat, 22 Nov 2014 19:31:39 -0800 (PST) Received: from neil.creepingfur.org (tessier.creepingfur.is. [70.36.196.188]) by mx.google.com with ESMTPSA id s6sm8627579pdr.95.2014.11.22.19.31.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 22 Nov 2014 19:31:39 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bhyve cannot allocate memory From: Benjamin Perrault In-Reply-To: Date: Sat, 22 Nov 2014 19:31:32 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <8581C174-0464-4024-83F4-13AC87F0763C@gmail.com> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> To: Shawn Webb X-Mailer: Apple Mail (2.1993) 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, 23 Nov 2014 03:31:40 -0000 Digging thru my system - I have (2) stock FreeBSD system (HP DL385s) at = r274859 - bhyve seems to be working fine for FreeBSD and Linux guests. = r274900 also appears to be good.=20 I know it=E2=80=99s not a ton of help of resolving the issue cheers, -bp > On Nov 22, 2014, at 7:20 PM, Shawn Webb wrote: >=20 > On Nov 22, 2014 10:15 PM, "Peter Grehan" wrote: >>=20 >> Hi Shawn, >>=20 >>=20 >>> Forgot to mention, I'm on r274859. >>=20 >>=20 >> I have a working system at r274783. A quick glance doesn't show = anything > obvious that may cause a regression, but I'm rebuilding now and will = give > it a try. >>=20 >> Is your system stock FreeBSD or HardenedBSD ? >=20 > It's hardenedBSD. I'll try a stock build tomorrow. The only change we = have > that could affect bhyve is the removal of map_at_zero. I've disabled = all > our other hardening features. > _______________________________________________ > 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 Sun Nov 23 03:44: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 1B142EF1 for ; Sun, 23 Nov 2014 03:44:41 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id CF516D16 for ; Sun, 23 Nov 2014 03:44:40 +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 AF4B212A0F; Sun, 23 Nov 2014 13:44:38 +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 BZX17588 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:44:37 +1000 Message-ID: <54715822.2010309@freebsd.org> Date: Sat, 22 Nov 2014 19:44:34 -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: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; 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: Sun, 23 Nov 2014 03:44:41 -0000 Hi Shawn, > There isn't. map_at_zero was fully removed. I can revert that change, > though. Or is there a way to make bhyve work with out it (with a patch)? I just set sysctl security.bsd.map_at_zero=1 .. on my test system and was able to run bhyveload without any issues. Does HardenedBSD have additional checks in the VM system ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:46:44 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 B97ABF48; Sun, 23 Nov 2014 03:46:44 +0000 (UTC) Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::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 79977D27; Sun, 23 Nov 2014 03:46:44 +0000 (UTC) Received: by mail-oi0-f48.google.com with SMTP id u20so5293695oif.21 for ; Sat, 22 Nov 2014 19:46:43 -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=bJEhZd/a3mQ7/3wqRt37CgMROi6m/EcZqqlAkcPZLlE=; b=S9DmS5OVtSG98UqNrjpo6kwxzHxR283FD1K/KL4K3beT21F3Ew4JL7Zc8IRy91WBLL oPC9XZ41EkMv4yEAlK52Ok+B9ytS+wbfhs8KFA88jXiH42cqFhHktzvY0uIITY466FeW LHdSi3A3v6oCTeQOsKYLs8d38ydYnprNhn3Ul1TYFbEhql2yNwW8GlnowKMpRkZhSKh4 kjjfbGkkuRZoEemqQWNA88O3ghXFAVvBMW2/K0oc7mj8cKVjXUFl/1NeE7l3rNwLfXhm 1QS0X6BEgYmvikeseSHSmqpn/ATnp9i1nctv7Je1vBD1p0daIxX8DYV2V9KIHeKr6iC/ K48g== MIME-Version: 1.0 X-Received: by 10.182.104.40 with SMTP id gb8mr7187321obb.61.1416714403712; Sat, 22 Nov 2014 19:46:43 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:46:43 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:46:43 -0800 (PST) In-Reply-To: <54715822.2010309@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> Date: Sat, 22 Nov 2014 22:46:43 -0500 Message-ID: Subject: Re: bhyve cannot allocate memory From: Shawn Webb To: Peter Grehan Content-Type: text/plain; charset=UTF-8 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: Sun, 23 Nov 2014 03:46:44 -0000 On Nov 22, 2014 10:44 PM, "Peter Grehan" wrote: > > Hi Shawn, > > >> There isn't. map_at_zero was fully removed. I can revert that change, >> though. Or is there a way to make bhyve work with out it (with a patch)? > > > I just set > > sysctl security.bsd.map_at_zero=1 > > .. on my test system and was able to run bhyveload without any issues. > > Does HardenedBSD have additional checks in the VM system ? > > later, > > Peter. Nope. What if you have map_at_zero set to 0? Dies bhyve work then? From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:48:37 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 568B8F8F for ; Sun, 23 Nov 2014 03:48:37 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 15DBED2B for ; Sun, 23 Nov 2014 03:48:36 +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 111CA12527; Sun, 23 Nov 2014 13:48:36 +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 BZX17647 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:48:35 +1000 Message-ID: <54715911.1090100@freebsd.org> Date: Sat, 22 Nov 2014 19:48:33 -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: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; 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: Sun, 23 Nov 2014 03:48:37 -0000 > Nope. What if you have map_at_zero set to 0? Dies bhyve work then? Works with the default of 0, and also with it being set to 1. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:53: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 B4B2D1CC; Sun, 23 Nov 2014 03:53:07 +0000 (UTC) Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (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 72E77DD7; Sun, 23 Nov 2014 03:53:07 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id gq1so5653558obb.26 for ; Sat, 22 Nov 2014 19:53: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; bh=Sv5S2MviIvC9J+JI9o1ebMiGkbZutOIL0f0L3Qpfv70=; b=ScvTsgpjt5NMG0P+dOr3nA4R5QACKZ3IItuCnAWp9tPnK+tIwOmkgypha3qfX83Aw7 eCMPgzosYX3kCAahi/eLuVZwKUFKWPNye2jQ/m8C/c/0NzodMWfw0fHa9VtoOoGDfIzo Opcw0zM19jAFaxkzBJUrr/sJvtd4/oknCivbtEUoH0nJid/ftDCNTlLEBekCuClztX0M u6j0scMHbz1Zed5DVHJLtM4LitOQzyiGtqRWz3Iybr8iHkrFiG+xMMPT2JfzLLbH9ZJR 8KJnNc53rLMR/ozRBXpb68xWmK50aHtyUboYyveqbAXAi0talBf3Foy3cGzuz1GlGPTp pDgg== MIME-Version: 1.0 X-Received: by 10.182.216.137 with SMTP id oq9mr7181973obc.70.1416714786845; Sat, 22 Nov 2014 19:53:06 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:53:06 -0800 (PST) Received: by 10.202.184.7 with HTTP; Sat, 22 Nov 2014 19:53:06 -0800 (PST) In-Reply-To: <54715911.1090100@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> <54715911.1090100@freebsd.org> Date: Sat, 22 Nov 2014 22:53:06 -0500 Message-ID: Subject: Re: bhyve cannot allocate memory From: Shawn Webb To: Peter Grehan Content-Type: text/plain; charset=UTF-8 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: Sun, 23 Nov 2014 03:53:07 -0000 On Nov 22, 2014 10:48 PM, "Peter Grehan" wrote: >> >> Nope. What if you have map_at_zero set to 0? Dies bhyve work then? > > > Works with the default of 0, and also with it being set to 1. > > later, > > Peter. > Interesting. I'll have to do more digging. Because removing map_at_zero support is the same as keeping it at the default of 0. It's not possible that our ASLR implementation is affecting bhyve, since our ASLR implementation is in sys_mmap and the elf image activator. At this stage, bhyve's vmm.ko is directly accessing vm_map_*, which we haven't touched. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 03:57:12 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 E6C1D230 for ; Sun, 23 Nov 2014 03:57:12 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id A4976DF2 for ; Sun, 23 Nov 2014 03:57:12 +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 9942412179; Sun, 23 Nov 2014 13:57:10 +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 BZX17768 (AUTH peterg@ptree32.com.au); Sun, 23 Nov 2014 13:57:09 +1000 Message-ID: <54715B13.9020303@freebsd.org> Date: Sat, 22 Nov 2014 19:57:07 -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: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> <54715911.1090100@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; 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: Sun, 23 Nov 2014 03:57:13 -0000 Hi Shawn, > Interesting. I'll have to do more digging. Because removing map_at_zero > support is the same as keeping it at the default of 0. It's not possible > that our ASLR implementation is affecting bhyve, since our ASLR > implementation is in sys_mmap and the elf image activator. At this > stage, bhyve's vmm.ko is directly accessing vm_map_*, which we haven't > touched. One thing you may be able to try is ktrace the bhyveload process and see which syscall is failing. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 06:04: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 2B05DD7E for ; Sun, 23 Nov 2014 06:04:14 +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 027F9A86 for ; Sun, 23 Nov 2014 06:04:13 +0000 (UTC) Received: from SNT150-W46 ([65.55.90.9]) by SNT004-OMC1S44.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.22751); Sat, 22 Nov 2014 22:04:07 -0800 X-TMN: [xqO8FCU1jsEs+CwOXOy2uet9zJlF5KkwBZ/dRBivYz4=] X-Originating-Email: [mrashutosh@hotmail.com] Message-ID: From: Ashutosh Kumar To: Subject: RE: 'repz' instruction not supported. Date: Sun, 23 Nov 2014 06:04:06 +0000 Importance: Normal In-Reply-To: References: , , , MIME-Version: 1.0 X-OriginalArrivalTime: 23 Nov 2014 06:04:07.0332 (UTC) FILETIME=[4AA38E40:01D006E3] 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: Sun, 23 Nov 2014 06:04:14 -0000 Thanks. Will share the code sometime this week with you. Regards Ashutosh > Date: Fri=2C 21 Nov 2014 11:22:06 -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 Fri=2C Nov 21=2C 2014 at 2:07 AM=2C Ashutosh Kumar wrote: > > Yes you are right 'repz' prefixes is added to the =91cmps=92 and 'scas' > > instructions. > > > > The actual opcode is =93F3 A5=94 which is =91rep movs=92 (disassembly i= s showing > > =91repz=92). > > > > > > > > Yes the guest is emitting these instructions to access MMIO (local apic= ) > > >=20 > Bummer. >=20 > I was hoping that it was a prefix stuck by the compiler for > optimization (that could be ignored): > http://repzret.org/p/repzret/ >=20 > In any case=2C 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. >=20 > best > Neel >=20 > > > > > > Regards > > Ashutosh > > > > > >> 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 > > > >> > >> Hi Ashutosh=2C > >> > >> 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= 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=2C send any mail to > >> > "freebsd-virtualization-unsubscribe@freebsd.org" = From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 19:43:52 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 54288E43; Sun, 23 Nov 2014 19:43:52 +0000 (UTC) Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) (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 04E62D1D; Sun, 23 Nov 2014 19:43:52 +0000 (UTC) Received: by mail-qg0-f53.google.com with SMTP id q108so5818244qgd.26 for ; Sun, 23 Nov 2014 11:43:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; bh=Nz3B8zR0Ql/Jfp4PP9oeeLauC0+y04rS+G5id7IQKBA=; b=baWeg9aJkegUVcb9XyMzNmjwTxoDX78xiDy6wjw180NNwlXdn+iLQT6q8H5Uzvs5mk PQromvoYbrm3YYATw6EfYKy/gZJ1nkL8KA8YLM+8r3BmHRbDxFgZ7CWC1Jf+2fCvwDpO G/7C0Pxq4/nWc/gw1HLVT1x6EKb/m1g82Y3SkiLz+jXmfgRfsEjYDhGIU8DaI9B8gvbK c4SZKhGi7+kSaxpGOnvaETD63hOcOapOvntglL4Wmiw4LHK7HeTwr2Gvix0iLF3Y4iVh 4aXMF1yzHwhBp99W735hniJAJsPkewc+Ofvr5fQ17Tm6hhDlWfICKnDXv/yI5euKkdm1 tylw== X-Received: by 10.140.96.203 with SMTP id k69mr23537525qge.33.1416771831117; Sun, 23 Nov 2014 11:43:51 -0800 (PST) Received: from hbsd-dev-local ([73.173.99.185]) by mx.google.com with ESMTPSA id p106sm10046349qgd.36.2014.11.23.11.43.50 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 23 Nov 2014 11:43:50 -0800 (PST) Date: Sun, 23 Nov 2014 14:43:49 -0500 From: Shawn Webb To: Peter Grehan Subject: Re: bhyve cannot allocate memory Message-Id: <20141123144349.84f648dcfc1169bf952c7ee7@gmail.com> In-Reply-To: <54715B13.9020303@freebsd.org> References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> <54715911.1090100@freebsd.org> <54715B13.9020303@freebsd.org> X-Mailer: Sylpheed 3.4.2 (GTK+ 2.24.22; amd64-portbld-freebsd11.0) 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: Sun, 23 Nov 2014 19:43:52 -0000 On Sat, 22 Nov 2014 19:57:07 -0800 Peter Grehan wrote: > Hi Shawn, > > > Interesting. I'll have to do more digging. Because removing map_at_zero > > support is the same as keeping it at the default of 0. It's not possible > > that our ASLR implementation is affecting bhyve, since our ASLR > > implementation is in sys_mmap and the elf image activator. At this > > stage, bhyve's vmm.ko is directly accessing vm_map_*, which we haven't > > touched. > > One thing you may be able to try is ktrace the bhyveload process and > see which syscall is failing. Oliver fixed the problem. bhyve's vmm.ko uses VM_MIN_ADDRESS, which defaults to NULL in FreeBSD. We modified that to be at 64k to prevent NULL dereferences. Combine that with the removal of map_at_zero, NULL deref is not possible anymore. But since we bumped VM_MIN_ADDRESS up, bhyve's vmm.ko no longer attempts to map at NULL (which it absolutely needs to). The change Oliver made simply uses 0 instead of VM_MIN_ADDRESS. If this is a change FreeBSD wants upstream, we'd love it merged upstream. Commit for reference: https://github.com/HardenedBSD/hardenedBSD/commit/23bd719ce1e3a8cc42fc8317b1c7c6d9e74dcba0 Thanks, Shawn From owner-freebsd-virtualization@FreeBSD.ORG Sun Nov 23 19:45:47 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 28BCEF93 for ; Sun, 23 Nov 2014 19:45:47 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D98E4D3C for ; Sun, 23 Nov 2014 19:45:46 +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 A763B12837; Mon, 24 Nov 2014 05:45:44 +1000 (EST) Received: from Dana-Toroks-MBP.att.net (107-214-150-206.lightspeed.sntcca.sbcglobal.net [107.214.150.206]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BZX30058 (AUTH peterg@ptree32.com.au); Mon, 24 Nov 2014 05:45:43 +1000 Message-ID: <54723963.1010101@freebsd.org> Date: Sun, 23 Nov 2014 11:45:39 -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: Shawn Webb Subject: Re: bhyve cannot allocate memory References: <20141122215245.d9380cc4e43cb5e60d479009@gmail.com> <20141122220202.09523b0ae828993174af05d8@gmail.com> <5471513C.6040400@freebsd.org> <54715438.3090905@freebsd.org> <54715822.2010309@freebsd.org> <54715911.1090100@freebsd.org> <54715B13.9020303@freebsd.org> <20141123144349.84f648dcfc1169bf952c7ee7@gmail.com> In-Reply-To: <20141123144349.84f648dcfc1169bf952c7ee7@gmail.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: Sun, 23 Nov 2014 19:45:47 -0000 > Oliver fixed the problem. bhyve's vmm.ko uses VM_MIN_ADDRESS, which > defaults to NULL in FreeBSD. We modified that to be at 64k to prevent > NULL dereferences. Combine that with the removal of map_at_zero, NULL > deref is not possible anymore. But since we bumped VM_MIN_ADDRESS up, > bhyve's vmm.ko no longer attempts to map at NULL (which it absolutely > needs to). The change Oliver made simply uses 0 instead of > VM_MIN_ADDRESS. If this is a change FreeBSD wants upstream, we'd love > it merged upstream. > > Commit for reference: > https://github.com/HardenedBSD/hardenedBSD/commit/23bd719ce1e3a8cc42fc8317b1c7c6d9e74dcba0 Thanks - we'll submit this. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 24 01:09: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 7E79EB66 for ; Mon, 24 Nov 2014 01:09:07 +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 F3E27F32 for ; Mon, 24 Nov 2014 01:09:06 +0000 (UTC) Received: by mail-la0-f41.google.com with SMTP id gf13so6935863lab.28 for ; Sun, 23 Nov 2014 17:09:05 -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=6V2SQQdibTW7lf9U4PdiOzSwTkz+vnSsEwSnhQVLyXA=; b=MOcyk2lZbOG2rwUh8Vf3yGif6kxca57Nyw3WfPS3ocYUz6AjsUt4TfZyf1XyZpDvE1 FKRYCwBsfL0y/WrZc5Ln5t5HB05JzPRM78zWddYyphX/cS3nLMXl/16nRZPUa79JESSr e1/qQR9S7dJJ7W99isjvHGGXSVTmTeO0idxVpAQFQnjbXMH610P0V9f1JER7WczS/HYj cbegje21HLls0tsaGFK5YdtOtEowxsYrQJGzlSQcN4x9VStjKtC6SPm4bdPcbIfguewh JIvCtqeb1EN0mQkngwoVId4st/0tKPcuOR7bY2Eu4ZFXfC4kogR4klMokJV9qGVxUqky v2iQ== MIME-Version: 1.0 X-Received: by 10.152.22.135 with SMTP id d7mr17654904laf.46.1416791345025; Sun, 23 Nov 2014 17:09:05 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sun, 23 Nov 2014 17:09:04 -0800 (PST) Date: Sun, 23 Nov 2014 17:09:04 -0800 X-Google-Sender-Auth: mbaTW8inLGFBIOlBXcmhxuNCIR0 Message-ID: Subject: cu -l /dev/nmdm not setting rows and columns From: Craig Rodrigues To: "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, 24 Nov 2014 01:09:07 -0000 Hi, I am configuring bhyve VM's with serial consoles directing to /dev/nmdm[n]. I am using cu -l /dev/nmdm[n]B to connect to the console. However, cu does not properly set the value of the rows and columns of my screen. For example, before connecting: # stty -a speed 9600 baud; 30 rows; 91 columns; # echo $TERM xterm # cu -l /dev/nmdm0B Inside the VM which is FreeBSD 10.1: # stty -a speed 9600 baud; 0 rows; 0 columns; # echo $TERM dialup Any idea how I can fix this? The console inside the VM is quite unusable when it does not have the correct rows/colums set. Thanks. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 24 02:13: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 8AFBD86B; Mon, 24 Nov 2014 02:13:35 +0000 (UTC) Received: from alto.onthenet.com.au (alto2.onthenet.com.au [203.13.68.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4E4927AE; Mon, 24 Nov 2014 02:13:34 +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 0CBD512425; Mon, 24 Nov 2014 12:04:23 +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 BZY22724 (AUTH peterg@ptree32.com.au); Mon, 24 Nov 2014 12:04:22 +1000 Message-ID: <54729224.3060402@freebsd.org> Date: Sun, 23 Nov 2014 18:04:20 -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: Craig Rodrigues Subject: Re: cu -l /dev/nmdm not setting rows and columns References: In-Reply-To: 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, 24 Nov 2014 02:13:35 -0000 Hi Craig, > # stty -a > speed 9600 baud; 0 rows; 0 columns; > # echo $TERM > dialup > > Any idea how I can fix this? The console inside the VM > is quite unusable when it does not have the correct > rows/colums set. Not sure how you're getting 'dialup' as the terminal type: the default ttys file for 10.1 shouldn't need to be edited, and has ttyu0 "/usr/libexec/getty std.9600" vt100 onifconsole secure The rows/columns is always 0 for uart-style serial lines since it's not possible to know what's on the other end. That's why $TERM has to be set correctly for these. Having an xterm attached to the other end of an nmdm device isn't too different from swapping say a vt100 with a vt420 or some other terminal with a different resolution on a real serial line. There's no way for the serial driver to know this has happened. The only way to fix the changing-size problem is to have a paravirtualized tty device that has a way of reading the terminal window size and being informed of changes. The virtio-serial specification has this ability, however, the FreeBSD driver for this can't operate in polled mode so can't be the main console port, and in any event there's no bhyve backend for it currently. Or, you can network-login to the guest in which case xterm works fine :) later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 24 08:00: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 C1B694FD for ; Mon, 24 Nov 2014 08:00:41 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A3BCFC00 for ; Mon, 24 Nov 2014 08:00:41 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAO80fNA026614 for ; Mon, 24 Nov 2014 08:00:41 GMT (envelope-from bugzilla-noreply@freebsd.org) Message-Id: <201411240800.sAO80fNA026614@kenobi.freebsd.org> From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [FreeBSD Bugzilla] Commit Needs MFC MIME-Version: 1.0 X-Bugzilla-Type: whine X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated Date: Mon, 24 Nov 2014 08:00:41 +0000 Content-Type: text/plain 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, 24 Nov 2014 08:00:41 -0000 Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by eadler@FreeBSD.org. (8 bugs) Bug 143808: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=143808 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [pf] pf does not work inside jail Bug 147950: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147950 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage] [carp] VIMAGE + CARP = kernel crash Bug 148155: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148155 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage] [pf] Kernel panic with PF + VIMAGE kernel option Bug 160496: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160496 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage] [pf] [patch] kernel panic with pf + VIMAGE Bug 160541: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=160541 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage][pf][patch] panic: userret: Returning on td 0xxxxxxxxx (pid xxxx, pftop) with vnet 0xxxxxxxxx set in pfioctl Bug 161094: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=161094 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage] [pf] [panic] kernel panic with pf + VIMAGE when stopping a jail Bug 165252: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165252 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: [vimage] [pf] [panic] kernel panics with VIMAGE and PF on FreeBSD 9.0 rel Bug 186146: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=186146 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-virtualization@FreeBSD.org Status: In Progress Resolution: Summary: vtscsi detects two disks when only one s configured From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 24 17:03:57 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 B17AB2B9; Mon, 24 Nov 2014 17:03:57 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 60DA4FD1; Mon, 24 Nov 2014 17:03:56 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sAOH3i8Z014319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 24 Nov 2014 09:03:46 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <547364EB.7090505@freebsd.org> Date: Tue, 25 Nov 2014 01:03:39 +0800 From: Julian Elischer 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: "Bjoern A. Zeeb" , Craig Rodrigues Subject: Re: RFC: Enabling VIMAGE in GENERIC 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> In-Reply-To: <69A8C06F-A7F6-49EC-8601-91AC4CDBFB13@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit 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: Mon, 24 Nov 2014 17:03:57 -0000 On 11/20/14, 8:33 AM, Bjoern A. Zeeb wrote: > On 19 Nov 2014, at 23:14 , Craig Rodrigues wrote: > >> 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 didnt 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. also look at the following: (a little dated) http://p4web.freebsd.org/@md=d&cd=//depot/projects/vimage/&cdf=//depot/projects/vimage/porting_to_vimage.txt&c=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 > > > Bjoern A. Zeeb "Come on. Learn, goddamn it.", WarGames, 1983 > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > > From owner-freebsd-virtualization@FreeBSD.ORG Mon Nov 24 18:10:27 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 31B588A7 for ; Mon, 24 Nov 2014 18:10:27 +0000 (UTC) Received: from mail-pa0-x243.google.com (mail-pa0-x243.google.com [IPv6:2607:f8b0:400e:c03::243]) (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 02AB79A1 for ; Mon, 24 Nov 2014 18:10:27 +0000 (UTC) Received: by mail-pa0-f67.google.com with SMTP id lj1so5576354pab.2 for ; Mon, 24 Nov 2014 10:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:from:to:reply-to:subject:date; bh=IKX1ulqMG5ahJrjudIIjRzhMPYUxS/BSTM2RDuT08wU=; b=TIwUpKYktqL9JzavjPc5ykTxPZHXluHbDdRiLK4PPePqY/uBK2UfLUyG8mezT6etDM ho1Ub2GC5gPkt3DewPqABY/Y6EvOv3shjR96Zn0qUz3nceYYPsFQCX7LbakVMW93l2S4 hfvXnPMhCtK73VQ7naJJK4QIMnvZh3D2DxHv155mneigEopo9lqD911jusgHid/lGQTY mGtyKWw/0vc5Bdj9QqP6u7On4hlPMfsrRu38Vugtgwy0owykibFULdbkSvp1t225j6a/ PexAbCIszZlG/sgrKCNpyFX2DYFfHbMsH8AzFaf1C0C7Hyf2hMe5FzOLbBD13Ockh/Nt LwKQ== X-Received: by 10.67.23.134 with SMTP id ia6mr36248076pad.50.1416851908188; Mon, 24 Nov 2014 09:58:28 -0800 (PST) Received: from localhost.localdomain ([27.255.204.186]) by mx.google.com with ESMTPSA id lg8sm13090520pab.41.2014.11.24.09.58.26 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Mon, 24 Nov 2014 09:58:27 -0800 (PST) Message-ID: <547371c3.0879420a.5cd0.4f07@mx.google.com> From: poetise98990@gmail.com To: freebsd-virtualization@freebsd.org Reply-To: julia.kites@yahoo.com Subject: Fix Penguin Penalty 17th October2014 ( mail-archive.com ) Date: Mon, 24 Nov 2014 23:28:29 +0530 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, 24 Nov 2014 18:10:27 -0000 Dear Sir Did your website get hit by Google Penguin update on October 17th 2014? What basically is Google Penguin Update? It is actually a code name for Google algorithm which aims at decreasing your websites search engine rankings that violate Googles guidelines by using black hat SEO techniques to rank your webpage by giving number of spammy links to the page. We are one of those few SEO companies that can help you avoid penalties from Google Updates like Penguin and Panda. Our clients have survived all the previous and present updates with ease. They have never been hit because we use 100% white hat SEO techniques to rank Webpages. Simple thing that we do to keep websites away from any Penguin or Panda penalties is follow Google guidelines and we give Google users the best answers to their queries. If you are looking to increase the quality of your websites and to get more targeted traffic or save your websites from these Google penalties email us back with your interest. We will be glad to serve you and help you grow your business. Regards Julia kites SEO Manager ( TOB ) B7 Green Avenue, Amritsar 143001 Punjab ____________________________ NO CLICK in the subject to STOP EMAILS From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 26 17:24:37 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 8C872DEE; Wed, 26 Nov 2014 17:24:37 +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 4D05A7CB; Wed, 26 Nov 2014 17:24:36 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id B6BD3153408; Wed, 26 Nov 2014 18:24:32 +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 bF8DaQcRucz1; Wed, 26 Nov 2014 18:24:22 +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 4B1FB153416; Wed, 26 Nov 2014 18:24:22 +0100 (CET) Message-ID: <54760CC9.1060902@digiware.nl> Date: Wed, 26 Nov 2014 18:24:25 +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 , Craig Rodrigues Subject: Re: cu -l /dev/nmdm not setting rows and columns References: <54729224.3060402@freebsd.org> In-Reply-To: <54729224.3060402@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 17:24:37 -0000 On 24-11-2014 3:04, Peter Grehan wrote: > Hi Craig, > >> # stty -a >> speed 9600 baud; 0 rows; 0 columns; >> # echo $TERM >> dialup >> >> Any idea how I can fix this? The console inside the VM >> is quite unusable when it does not have the correct >> rows/colums set. > > Not sure how you're getting 'dialup' as the terminal type: the default > ttys file for 10.1 shouldn't need to be edited, and has > > ttyu0 "/usr/libexec/getty std.9600" vt100 onifconsole secure > > The rows/columns is always 0 for uart-style serial lines since it's not > possible to know what's on the other end. That's why $TERM has to be set > correctly for these. > > Or, you can network-login to the guest in which case xterm works fine :) Or, like in the old days, just assign a TERM env value in your shell-login script based on the device the shell is connected too. That'll give you a basic working setup. Resizing will probably still not automagically work, and will require extra intervention. --WjW From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 26 23:34:12 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 06C95ED1 for ; Wed, 26 Nov 2014 23:34:12 +0000 (UTC) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (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 78DE83B2 for ; Wed, 26 Nov 2014 23:34:11 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id z12so3252493lbi.4 for ; Wed, 26 Nov 2014 15:34:09 -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=+vBe6TkGA8oL3L0Udar96KqF5d7ea4cwJK2qCHjGujM=; b=hXynQgzo/cJeDe1FjToOn7tbNySXPHXUsDZG5k9vIS3nZpFAnigCWuvy0M8O6Wl+bX fugTwByjjCoxKW2JuZ6p7O8SRwcubenTFSckmFTLmiGhS+H20gdsfuS3AZOx2vAaMh2P MRRCYyKOB5GgZWh8kW5GtlYwztzGj1iLDgFFsVp4pytLiSpqDdN6YRvEVvkGes64wZBQ pBmS1oV9+yEXa/LQ8l9XfFNhPmn3V5QUopbmgMOjUDdhfp8hDomIXwKy+l3JBjUDGUG6 UzvyBGD+KqbTuG0KQmPwSwJ5xdxKwSpXArccQER8dv62Sfzb8BPRKLrnoYWXgvkveaKE 683w== MIME-Version: 1.0 X-Received: by 10.112.137.39 with SMTP id qf7mr36074493lbb.47.1417044849631; Wed, 26 Nov 2014 15:34:09 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Wed, 26 Nov 2014 15:34:09 -0800 (PST) In-Reply-To: <54729224.3060402@freebsd.org> References: <54729224.3060402@freebsd.org> Date: Wed, 26 Nov 2014 15:34:09 -0800 X-Google-Sender-Auth: Z3ymHc_5xh68eno6RP3ZaPIxVAE Message-ID: Subject: Re: cu -l /dev/nmdm not setting rows and columns From: Craig Rodrigues To: "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: Wed, 26 Nov 2014 23:34:12 -0000 On Sun, Nov 23, 2014 at 6:04 PM, Peter Grehan wrote: > Hi Craig, > > # stty -a >> speed 9600 baud; 0 rows; 0 columns; >> # echo $TERM >> dialup >> >> Any idea how I can fix this? The console inside the VM >> is quite unusable when it does not have the correct >> rows/colums set. >> > > Not sure how you're getting 'dialup' as the terminal type: the default > ttys file for 10.1 shouldn't need to be edited, and has > > ttyu0 "/usr/libexec/getty std.9600" vt100 onifconsole secure > > The rows/columns is always 0 for uart-style serial lines since it's not > possible to know what's on the other end. That's why $TERM has to be set > correctly for these. > > Having an xterm attached to the other end of an nmdm device isn't too > different from swapping say a vt100 with a vt420 or some other terminal > with a different resolution on a real serial line. There's no way for the > serial driver to know this has happened. > > The only way to fix the changing-size problem is to have a > paravirtualized tty device that has a way of reading the terminal window > size and being informed of changes. The virtio-serial specification has > this ability, however, the FreeBSD driver for this can't operate in polled > mode so can't be the main console port, and in any event there's no bhyve > backend for it currently. > > Or, you can network-login to the guest in which case xterm works fine :) > Hi, I need to log into the serial console for two reasons: -> networking has not been set up yet, and I need to log in to see what is going on -> networking has failed or been misconfigured, so I cannot ssh into the VM, but I still need to log in to see what is going on cu and tip are in the base system, so they are handy to use, but they are quite primitive. Do programs like minicom work better for this type of thing, in terms of presenting a usable terminal? I haven't used these types of programs for serial port communication since the 1990's, so it's been a while for me. -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Nov 26 23:44: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 591ED15F; Wed, 26 Nov 2014 23:44:33 +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 31F70674; Wed, 26 Nov 2014 23:44:32 +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 sAQNiVon092907 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Nov 2014 15:44:32 -0800 (PST) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id sAQNiVc1092906; Wed, 26 Nov 2014 15:44:31 -0800 (PST) (envelope-from jmg) Date: Wed, 26 Nov 2014 15:44:31 -0800 From: John-Mark Gurney To: Craig Rodrigues Subject: Re: cu -l /dev/nmdm not setting rows and columns Message-ID: <20141126234431.GN99957@funkthat.com> References: <54729224.3060402@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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, 26 Nov 2014 15:44:32 -0800 (PST) Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Nov 2014 23:44:33 -0000 Craig Rodrigues wrote this message on Wed, Nov 26, 2014 at 15:34 -0800: > On Sun, Nov 23, 2014 at 6:04 PM, Peter Grehan wrote: > > > Hi Craig, > > > > # stty -a > >> speed 9600 baud; 0 rows; 0 columns; > >> # echo $TERM > >> dialup > >> > >> Any idea how I can fix this? The console inside the VM > >> is quite unusable when it does not have the correct > >> rows/colums set. > >> > > > > Not sure how you're getting 'dialup' as the terminal type: the default > > ttys file for 10.1 shouldn't need to be edited, and has > > > > ttyu0 "/usr/libexec/getty std.9600" vt100 onifconsole secure > > > > The rows/columns is always 0 for uart-style serial lines since it's not > > possible to know what's on the other end. That's why $TERM has to be set > > correctly for these. > > > > Having an xterm attached to the other end of an nmdm device isn't too > > different from swapping say a vt100 with a vt420 or some other terminal > > with a different resolution on a real serial line. There's no way for the > > serial driver to know this has happened. > > > > The only way to fix the changing-size problem is to have a > > paravirtualized tty device that has a way of reading the terminal window > > size and being informed of changes. The virtio-serial specification has > > this ability, however, the FreeBSD driver for this can't operate in polled > > mode so can't be the main console port, and in any event there's no bhyve > > backend for it currently. > > > > Or, you can network-login to the guest in which case xterm works fine :) > > I need to log into the serial console for two reasons: > -> networking has not been set up yet, and I need to log in to see what > is going on > -> networking has failed or been misconfigured, so I cannot ssh into the > VM, but I still need to log in to see what is going on > > cu and tip are in the base system, so they are handy to use, but they are > quite primitive. > Do programs like minicom work better for this type of thing, in terms of > presenting > a usable terminal? I haven't used these types > of programs for serial port communication since the 1990's, so it's been a > while for me. So, what exactly is the problem again? If you're complaining about terminal not being set correctly, or rows/columns not being set correctly, welcom to the world of dumb serial devices, and they have to be set manually and correctly... termcap does contain default rows/columns for when they aren't provided (i.e. dumb terminals)... Is there another issue that you're having issues with? -- 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 Thu Nov 27 01:02: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 2C488573 for ; Thu, 27 Nov 2014 01:02:41 +0000 (UTC) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::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 9E09BE17 for ; Thu, 27 Nov 2014 01:02:40 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id w7so3403464lbi.15 for ; Wed, 26 Nov 2014 17:02:38 -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=AVUKg1f8iyFJH6/xHu95Cwd+njj2VWUH/B3JtbPN+cc=; b=Xm3CM41x+AznDnXkjkrBBPJUaTeeDM067C8Af8a4TJJpEcKiBwR8ifAQmCfmofvOQc tylVhD0n0b8ofKT9sETvUmvGkK+oopvwFf4lPsc7fDal+RTEvNFkUPPusK9inL9JFRYN vKPwW5HNuT8S078ka8OU2DEIH3szC9ieUUPXxC0zAqAD5Aw9CtvF7zRBbiovWN5UomTx NTIVVGO6nd+TlR4t0yLsdo7zV02w38/0mIzXHUs4+EnX9KWVZ9xF/+oeX+SWR2b88aq9 WuuGQc53NfdlrTnVd4D5q/dJV/sD46kKqlG8ZzS+WjzdZZ3OpCyU4dqVnYM6b+uLUUW8 YZqA== MIME-Version: 1.0 X-Received: by 10.152.20.1 with SMTP id j1mr10435202lae.90.1417050158690; Wed, 26 Nov 2014 17:02:38 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Wed, 26 Nov 2014 17:02:38 -0800 (PST) In-Reply-To: <20141126234431.GN99957@funkthat.com> References: <54729224.3060402@freebsd.org> <20141126234431.GN99957@funkthat.com> Date: Wed, 26 Nov 2014 17:02:38 -0800 X-Google-Sender-Auth: PUBPTwq3UqD_vAJT7Mpa-6R5IMY Message-ID: Subject: Re: cu -l /dev/nmdm not setting rows and columns From: Craig Rodrigues To: John-Mark Gurney Content-Type: text/plain; charset=ISO-8859-1 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: Thu, 27 Nov 2014 01:02:41 -0000 On Wed, Nov 26, 2014 at 3:44 PM, John-Mark Gurney wrote: > > So, what exactly is the problem again? > https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-November/003173.html From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 27 11:23:54 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 E8E3226F for ; Thu, 27 Nov 2014 11:23:54 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7EF9D370 for ; Thu, 27 Nov 2014 11:23:54 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MN0jA-1XrlJ308zo-006dWh; Thu, 27 Nov 2014 12:23:37 +0100 Message-ID: <547709B4.8020800@gmx.com> Date: Thu, 27 Nov 2014 12:23:32 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: cu -l /dev/nmdm not setting rows and columns References: <54729224.3060402@freebsd.org> <20141126234431.GN99957@funkthat.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:QgJuwKHYKvFPS4taFDNS265XKcXMYeT0jNTU9azPPiwVDWju2j6 7MbOTvMfJdrWGjD1NbmgD/eEvqwZ/Q6B8xd6d64tXpXvUPfZWb7yV2rZ0FC9hv0nkg/QQhF U84GZ4Im9xdG9aFDt3dkXk6kJtz0padjVagmOLLGUMTdbOOXVToA0tiSGf709++bzBxlZNx Rm7t2kC4i0+8d014eWDaw== X-UI-Out-Filterresults: notjunk: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: Thu, 27 Nov 2014 11:23:55 -0000 On 11/27/14 02:02, Craig Rodrigues wrote: > On Wed, Nov 26, 2014 at 3:44 PM, John-Mark Gurney wrote: > >> >> So, what exactly is the problem again? >> > > https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-November/003173.html Set the correct $TERM and set also rows and columns. Something like this, will suffice: TERM=xterm; export TERM stty rows 80 stty columns 80 Then the system you are connecting to, will know what to send back to your terminal. HTH, Nikos From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 27 12:37:44 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 97087FCE; Thu, 27 Nov 2014 12:37:44 +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 54993D7B; Thu, 27 Nov 2014 12:37:44 +0000 (UTC) Received: from rack1.digiware.nl (unknown [127.0.0.1]) by smtp.digiware.nl (Postfix) with ESMTP id 421A4153418; Thu, 27 Nov 2014 13:37:32 +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 I4Ea3tRjDaM5; Thu, 27 Nov 2014 13:37:04 +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 A1F91153416; Thu, 27 Nov 2014 13:37:03 +0100 (CET) Message-ID: <54771AF2.4020507@digiware.nl> Date: Thu, 27 Nov 2014 13:37:06 +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: Nikos Vassiliadis , Craig Rodrigues Subject: Re: cu -l /dev/nmdm not setting rows and columns References: <54729224.3060402@freebsd.org> <20141126234431.GN99957@funkthat.com> <547709B4.8020800@gmx.com> In-Reply-To: <547709B4.8020800@gmx.com> Content-Type: text/plain; charset=ISO-8859-1 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, 27 Nov 2014 12:37:44 -0000 On 27-11-2014 12:23, Nikos Vassiliadis wrote: > On 11/27/14 02:02, Craig Rodrigues wrote: >> On Wed, Nov 26, 2014 at 3:44 PM, John-Mark Gurney >> wrote: >> >>> >>> So, what exactly is the problem again? >>> >> >> https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-November/003173.html >> > > Set the correct $TERM and set also rows and columns. Something like > this, will suffice: > TERM=xterm; export TERM > stty rows 80 > stty columns 80 > > Then the system you are connecting to, will know what to send back to > your terminal. And then wrap this into a piece of shell init. for tcsh in .tcshrc, but you get the drift: if (@`tty`@ == @/dev/ttyd0@) ( setenv TERM vt220; stty rows 60 ) if (@`tty`@ == @/dev/ttyv6@) /usr/bin/systat -vm 1 if (@`tty`@ == @/dev/ttyv7@) /usr/bin/top Just try it once an check the tty with /usr/bin/tty --WjW From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 27 15:02:37 2014 Return-Path: Delivered-To: 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 5FDEB41D for ; Thu, 27 Nov 2014 15:02:37 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1ABBBF5A for ; Thu, 27 Nov 2014 15:02:33 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sARF2McX028434 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Thu, 27 Nov 2014 07:02:25 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54773CF8.2020306@freebsd.org> Date: Thu, 27 Nov 2014 23:02:16 +0800 From: Julian Elischer 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: virtualization@FreeBSD.org Subject: bhyve failure Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: Thu, 27 Nov 2014 15:02:37 -0000 I added WITNESS to a kernel I've been running and during boot I got this result: vm exit[0] reason VMX rip 0xffffffff8078c1a7 inst_length 7 status 0 exit_reason 2 qualification 0x0000000000000000 inst_type 0 inst_error 0 Abort trap (core dumped) anyone have a decoder ring? julian From owner-freebsd-virtualization@FreeBSD.ORG Thu Nov 27 19:12:24 2014 Return-Path: Delivered-To: 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 DA37BE93; Thu, 27 Nov 2014 19:12:24 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::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 90EF08; Thu, 27 Nov 2014 19:12:24 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id r20so19320134wiv.0 for ; Thu, 27 Nov 2014 11:12:22 -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=3y5Jhl4cRDTcRObsaHz629z/2AnchIFBjSVEFCqwEKU=; b=yw+3an7l8ag4kk5TMAZubPReQjohCBTFU4jSPDfzkn4C4x6f16uCAZNkuYM9Vcf0Rh T+ie4iIJdDkozJFLcf6xMiEl3i1biRXniETgnIz5segdM7qWHZTWrD2TfyAS6i44KvgY nJYojZJDl+Pp8jiUbGRcxjJy/ehhYvWcVjB5ts7B01DEIIlJrMpDY0BbIy5dk0ePosYI SLVRr8KKsRZcdKJRO3vVE3REzBHKhsg0DGymULlIekW/knxp0GSEosCJuZZxyG9faBtk J3eBFtenNwHcKesao9ozcEcK1pf5MMNmda+DzdOrYQWM2KkIsfiAKkOd14GaIeG8QnNV B+Vw== MIME-Version: 1.0 X-Received: by 10.180.98.100 with SMTP id eh4mr20408565wib.54.1417115542364; Thu, 27 Nov 2014 11:12:22 -0800 (PST) Received: by 10.27.12.168 with HTTP; Thu, 27 Nov 2014 11:12:22 -0800 (PST) In-Reply-To: <54773CF8.2020306@freebsd.org> References: <54773CF8.2020306@freebsd.org> Date: Thu, 27 Nov 2014 11:12:22 -0800 Message-ID: Subject: Re: bhyve failure From: Neel Natu To: Julian Elischer 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: Thu, 27 Nov 2014 19:12:24 -0000 Hi Julian, On Thu, Nov 27, 2014 at 7:02 AM, Julian Elischer wrote: > I added WITNESS to a kernel I've been running and during boot I got this > result: > > vm exit[0] > reason VMX > rip 0xffffffff8078c1a7 > inst_length 7 > status 0 > exit_reason 2 That's a triple fault (from sys/amd64/vmm/intel/vmcs.h) #define EXIT_REASON_TRIPLE_FAULT 2 > qualification 0x0000000000000000 > inst_type 0 > inst_error 0 > Abort trap (core dumped) > > anyone have a decoder ring? > A few questions to narrow this down: Did you add WITNESS to the guest kernel or the host kernel when this happened? Is this readily reproducible? Can you share the host and guest revision numbers? best Neel > > julian > _______________________________________________ > 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 28 11:04:23 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 3C71D860 for ; Fri, 28 Nov 2014 11:04:23 +0000 (UTC) Received: from mbox1.develooper.com (mbox1.develooper.com [207.171.7.178]) by mx1.freebsd.org (Postfix) with ESMTP id 2499A6AC for ; Fri, 28 Nov 2014 11:04:22 +0000 (UTC) Received: from mbox1.develooper.com (mbox1.develooper.com [127.0.0.1]) by mbox1.develooper.com (Postfix) with ESMTP id 8D8C61757D9 for ; Fri, 28 Nov 2014 02:43:17 -0800 (PST) Received: (qmail 32080 invoked from network); 28 Nov 2014 10:43:15 -0000 Received: from c-50-161-96-117.hsd1.ca.comcast.net (HELO ?10.0.200.10?) (ask@mail.dev@50.161.96.117) by smtp.develooper.com with ESMTPA; 28 Nov 2014 10:43:15 -0000 From: =?utf-8?Q?Ask_Bj=C3=B8rn_Hansen?= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Unsupported cmd:c4 (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 00 00 00 40 00 00 00 00 01 00 Message-Id: Date: Fri, 28 Nov 2014 02:42:30 -0800 To: freebsd-virtualization@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) X-Mailer: Apple Mail (2.1993) 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, 28 Nov 2014 11:04:23 -0000 Hi everyone, I=E2=80=99ve spent some time off this week upgrading my = build-my-personal-NanoBSD-image tool from a VMware virtual machine to a = physical box running a 32-bit build-box under bhyve. So far so good =E2=80=94 all that has been working really well. My nanobsd image is only used on Soekris and PC Engines boxes and my = production images are really small (some <100MB storage and ~32MB = memory), so I have a crufty kernel config that excluded a bunch of stuff = I (thought I) don=E2=80=99t need. Now I=E2=80=99d like to run my built image under bhyve for testing. = It=E2=80=99s easier for me if the disk comes up as an ada device, so = I=E2=80=99m using ahci-hd instead of virtio-blk. With virtio-blk the = system boots but the device has the =E2=80=9Cwrong" name. With ahci-hd it can=E2=80=99t read my partition for some reason. I=E2=80=99ve tried with both file and zvol backing store. This is the error I=E2=80=99m getting: ada0: ATA-8 SATA 2.x device ada0: Serial Number 123456 ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes) ada0: Command Queueing enabled ada0: 260MB (532480 512 byte sectors: 16H 63S/T 528C) ada0: Previously was known as ad4 Unsupported cmd:c4 (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 c1 1f 08 40 = 00 00 00 00 04 00 (ada0:ahcich0:0:0:0): CAM status: ATA Status Error (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 04 (ABRT ) (ada0:ahcich0:0:0:0): RES: 41 04 00 00 00 40 00 00 00 00 00 (ada0:ahcich0:0:0:0): Retrying command Unsupported cmd:c4 Any suggestion for what I=E2=80=99m doing wrong? Did I compile my kernel = with some idiotic set of not-working options? Ask From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 28 15:37:09 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 08FE36CB for ; Fri, 28 Nov 2014 15:37:09 +0000 (UTC) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CFAB0D4A for ; Fri, 28 Nov 2014 15:37:08 +0000 (UTC) Received: from Julian-MBP3.local (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.14.9/8.14.9) with ESMTP id sASFb3b8032530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 28 Nov 2014 07:37:06 -0800 (PST) (envelope-from julian@freebsd.org) Message-ID: <54789699.7030507@freebsd.org> Date: Fri, 28 Nov 2014 23:36:57 +0800 From: Julian Elischer 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: Neel Natu Subject: Re: bhyve failure References: <54773CF8.2020306@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; 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: Fri, 28 Nov 2014 15:37:09 -0000 On 11/28/14, 3:12 AM, Neel Natu wrote: > Hi Julian, > > On Thu, Nov 27, 2014 at 7:02 AM, Julian Elischer wrote: >> I added WITNESS to a kernel I've been running and during boot I got this >> result: >> >> vm exit[0] >> reason VMX >> rip 0xffffffff8078c1a7 >> inst_length 7 >> status 0 >> exit_reason 2 > That's a triple fault (from sys/amd64/vmm/intel/vmcs.h) > > #define EXIT_REASON_TRIPLE_FAULT 2 > > >> qualification 0x0000000000000000 >> inst_type 0 >> inst_error 0 >> Abort trap (core dumped) >> >> anyone have a decoder ring? >> > A few questions to narrow this down: > > Did you add WITNESS to the guest kernel or the host kernel when this happened? yes I added it to the guest kernel.. I suspect it ay be related to this, especially since there was a kernel module loaded that was not recompiled. I'm trying to ascertain now whether a withness kernel requires special handling for its modules. > > Is this readily reproducible? don't know yet. > > Can you share the host and guest revision numbers? guest is custom sources based on stable-10 on the same day as 10.0 was released.basically whatever svn revision# was on 10.0 but on the stable branch. host is FreeBSD 10.1-BETA1 #0 r271671: Tue Sep 16 09:31:23 PDT 2014 > > best > Neel > >> julian >> _______________________________________________ >> 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 28 16:44: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 8191D21A for ; Fri, 28 Nov 2014 16:44:35 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 430DB69F for ; Fri, 28 Nov 2014 16:44:34 +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 A7EE37CC98 for ; Fri, 28 Nov 2014 16:44:27 +0000 (UTC) Message-ID: <5478A67C.7030904@freebsd.org> Date: Fri, 28 Nov 2014 11:44:44 -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: Unsupported cmd:c4 (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 00 00 00 40 00 00 00 00 01 00 References: In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EnHdR8TRr6G2HbBDfCmoicsbUTBLdfgWx" 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, 28 Nov 2014 16:44:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --EnHdR8TRr6G2HbBDfCmoicsbUTBLdfgWx Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2014-11-28 05:42, Ask Bj=C3=B8rn Hansen wrote: > Hi everyone, >=20 > I=E2=80=99ve spent some time off this week upgrading my build-my-person= al-NanoBSD-image tool from a VMware virtual machine to a physical box run= ning a 32-bit build-box under bhyve. >=20 > So far so good =E2=80=94 all that has been working really well. >=20 > My nanobsd image is only used on Soekris and PC Engines boxes and my pr= oduction images are really small (some <100MB storage and ~32MB memory), = so I have a crufty kernel config that excluded a bunch of stuff I (though= t I) don=E2=80=99t need. >=20 > Now I=E2=80=99d like to run my built image under bhyve for testing. It=E2= =80=99s easier for me if the disk comes up as an ada device, so I=E2=80=99= m using ahci-hd instead of virtio-blk. With virtio-blk the system boots b= ut the device has the =E2=80=9Cwrong" name. >=20 > With ahci-hd it can=E2=80=99t read my partition for some reason. >=20 > I=E2=80=99ve tried with both file and zvol backing store. >=20 > This is the error I=E2=80=99m getting: >=20 > ada0: ATA-8 SATA 2.x device > ada0: Serial Number 123456 > ada0: 300.000MB/s transfers (SATA 2.x, PIO4, PIO 8192bytes) > ada0: Command Queueing enabled > ada0: 260MB (532480 512 byte sectors: 16H 63S/T 528C) > ada0: Previously was known as ad4 > Unsupported cmd:c4 > (ada0:ahcich0:0:0:0): READ_MUL. ACB: c4 00 c1 1f 08 4= 0 00 00 00 00 04 00 > (ada0:ahcich0:0:0:0): CAM status: ATA Status Error > (ada0:ahcich0:0:0:0): ATA status: 41 (DRDY ERR), error: 04 (ABRT ) > (ada0:ahcich0:0:0:0): RES: 41 04 00 00 00 40 00 00 00 00 00 > (ada0:ahcich0:0:0:0): Retrying command > Unsupported cmd:c4 >=20 >=20 > Any suggestion for what I=E2=80=99m doing wrong? Did I compile my kerne= l with some idiotic set of not-working options? >=20 >=20 > Ask >=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 When using zvols, you must set the 'volmode' to 'dev', otherwise GEOM on the host locks the disk and causes all kinds of interesting things to happen. Note: the volmode property is only applied when the device is created, so you might have to 'zfs rename' it to cause it to be recreated --=20 Allan Jude --EnHdR8TRr6G2HbBDfCmoicsbUTBLdfgWx 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) iQIcBAEBAgAGBQJUeKZ/AAoJEJrBFpNRJZKf+EYQAJzI3K/QjmdntfRSjNDhVf/0 5soTK03w8cLIvxcO6GbOZToofXkvfUOPm0ujFo7k7KA4EkQT6zVPMn6LNkjRDZ4G GGxVzgUvAPHohi0Jy8sNuQKSXF48t4LRV9Sa+Ev2i0t1wP9HeTXVy2HwfHaiAVrt XdEil7vDN4LzFaLzJhjW26WzJ06Oh22fr1KMwxaiKrhmLZDulHIpXggp+4bYMd7d V60Nb/viJZat5fpuG0iJT98vYh+c6lKlixiZF3FCyvkdTv7bV/WoVoCFKxx7wBsP al1//tmWNQOalIKoupxSekGYKbxRuzvP/bcs5aLy63q9D1tNZaNk7OD2bGnffPfC 1huO/rEPBkU2EaVOsuXLDiTf95v7SOB7PQNZLR+3p0WyTC+WvoAFLZMbEv8W6oOo ibDTrbeWzDdPFnwV45L6xSGEZ3JPAkljB4ectrByoZAil5vlGGX9QLwg7xSKoXxb hzqbBHeEkKEMItPdbDzzJFyO1LhIymKtGkGFbXj3E62iXyTABSbaohj6TNlcXRlh YA0iB0po7GLinrmqd1cOaBFOeB00q0f5OiARWYMTA1vUpa2fpa/z5PV+IJ1GzQcz Cf/G5aCLmeFwRDQ0l0s3ElUS6JmrJG3v9Le7325xu975a0iSQm8sMjEa3/b6qfV2 MwoWPdUX3jkRj45Ise7b =ReGD -----END PGP SIGNATURE----- --EnHdR8TRr6G2HbBDfCmoicsbUTBLdfgWx-- From owner-freebsd-virtualization@FreeBSD.ORG Fri Nov 28 21:10: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 2C1C8F75 for ; Fri, 28 Nov 2014 21:10:46 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FCF932D for ; Fri, 28 Nov 2014 21:10:45 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0LtZfc-1Y47LN2Ttk-010sRC for ; Fri, 28 Nov 2014 22:10:37 +0100 Message-ID: <5478E4C4.3080203@gmx.com> Date: Fri, 28 Nov 2014 22:10:28 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: bhyve: Unsupported MSI-X configuration: 2/0/0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:DICo6klIvX6+srrSs/a6bDQKuaiu/iS+YSwU44axN0u3GYcbp4Y yWLtvBXTbCXdc4Nx7zox+5PtsquBzs8rSz8BxYHMMc22HWk87oS3GXy0UqlnAcsbrj3p31H SBxMA4EKARhwSo8irIrgyfS1aJdqjG3+2Q6+wU6jpNjqKG0/ugotD8KDVVehYTT4yVgToN9 X+2oEFoeYhCMA8319NUSg== X-UI-Out-Filterresults: notjunk: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: Fri, 28 Nov 2014 21:10:46 -0000 Hi, I am trying to use PCI passthrough to pass the bge device to a guest but I am doing something wrong. I have tried several combinations of pptdevs like "2/0/0 2/0/1 2/0/2 2/0/3" but it always fails on 2/0/0. Any ideas what I could try? > root@moby:~ # pciconf -l > hostb0@pci0:0:0:0: class=0x060000 card=0x064b1025 chip=0x01548086 rev=0x09 hdr=0x00 > pcib1@pci0:0:1:0: class=0x060400 card=0x064b1025 chip=0x01518086 rev=0x09 hdr=0x01 > vgapci1@pci0:0:2:0: class=0x030000 card=0x064b1025 chip=0x01668086 rev=0x09 hdr=0x00 > none0@pci0:0:22:0: class=0x078000 card=0x064b1025 chip=0x1e3a8086 rev=0x04 hdr=0x00 > ehci0@pci0:0:26:0: class=0x0c0320 card=0x064b1025 chip=0x1e2d8086 rev=0x04 hdr=0x00 > hdac0@pci0:0:27:0: class=0x040300 card=0x064b1025 chip=0x1e208086 rev=0x04 hdr=0x00 > pcib2@pci0:0:28:0: class=0x060400 card=0x064b1025 chip=0x1e108086 rev=0xc4 hdr=0x01 > pcib3@pci0:0:28:1: class=0x060400 card=0x064b1025 chip=0x1e128086 rev=0xc4 hdr=0x01 > ehci1@pci0:0:29:0: class=0x0c0320 card=0x064b1025 chip=0x1e268086 rev=0x04 hdr=0x00 > isab0@pci0:0:31:0: class=0x060100 card=0x064b1025 chip=0x1e578086 rev=0x04 hdr=0x00 > ahci0@pci0:0:31:2: class=0x010601 card=0x064b1025 chip=0x1e038086 rev=0x04 hdr=0x00 > none1@pci0:0:31:3: class=0x0c0500 card=0x064b1025 chip=0x1e228086 rev=0x04 hdr=0x00 > vgapci0@pci0:1:0:0: class=0x030000 card=0x06911025 chip=0x114010de rev=0xa1 hdr=0x00 > bge0@pci0:2:0:0: class=0x020000 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 > sdhci_pci0@pci0:2:0:1: class=0x080501 card=0x06471025 chip=0x16bc14e4 rev=0x10 hdr=0x00 > none2@pci0:2:0:2: class=0x088000 card=0x06471025 chip=0x16be14e4 rev=0x10 hdr=0x00 > none3@pci0:2:0:3: class=0x088000 card=0x06471025 chip=0x16bf14e4 rev=0x10 hdr=0x00 > none4@pci0:3:0:0: class=0x028000 card=0xe042105b chip=0x472714e4 rev=0x01 hdr=0x00 > root@moby:~ # Thanks, Nikos From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 01:05: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 63279EC2 for ; Sat, 29 Nov 2014 01:05:43 +0000 (UTC) Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) (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 D6DB5C7A for ; Sat, 29 Nov 2014 01:05:42 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id hs14so1655954lab.11 for ; Fri, 28 Nov 2014 17:05:40 -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=GZ1WZOPPtdtEJg/yIDyH0zcRaPTAEdbRlVTrfsn3V+E=; b=uqkAs0uu+d8bH2FYKirxgLp+JkOid59ATYCp2BpI6Klt9p3L5AQA4dadh8xgqEpVPN BfU6gqoXda50FRjzIN/f9l26dJioMQN21WwhQnmeM3hc3ubh5ukDTSKtlnuE5k34yjnC 57gSTLwBkNkGsW1PZf9PjTzcLwdS9HXSSv7orKTCZG3cCE8x7p0SaSH+wPQQjs1yi0pE iE8Z6Rfj7CHpL48Mbk1iLZTO302oidO7GjgBZd5nJaofRbdBKwrk2gfKOxugXnAlN392 Vdv5gyN1at9Vz3CznnhvYB2RUeO5aVsLvYeQ4s3NxZyPw9tmnNzuoNbZBouX6LjScw9o wY1w== MIME-Version: 1.0 X-Received: by 10.152.7.193 with SMTP id l1mr45929584laa.57.1417223140784; Fri, 28 Nov 2014 17:05:40 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Fri, 28 Nov 2014 17:05:40 -0800 (PST) In-Reply-To: <5478E4C4.3080203@gmx.com> References: <5478E4C4.3080203@gmx.com> Date: Fri, 28 Nov 2014 17:05:40 -0800 X-Google-Sender-Auth: G454sitPcP72_cj2cbnukwOj_x4 Message-ID: Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Craig Rodrigues To: Nikos Vassiliadis Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 29 Nov 2014 01:05:43 -0000 On Fri, Nov 28, 2014 at 1:10 PM, Nikos Vassiliadis wrote: > Hi, > > I am trying to use PCI passthrough to pass the bge device to a guest but I > am doing something wrong. I have tried several combinations of pptdevs like > "2/0/0 2/0/1 2/0/2 2/0/3" but it always fails on 2/0/0. Any ideas what I > could try? > Did you read this: https://wiki.freebsd.org/bhyve/pci_passthru ? After following those instructions, what is the output of pciconf -l -v before and after enabling PCI passthru? On the host and in the guest? -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 05:02:10 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 420EB451; Sat, 29 Nov 2014 05:02:10 +0000 (UTC) Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) (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 149236DE; Sat, 29 Nov 2014 05:02:10 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id eu11so7688335pac.8 for ; Fri, 28 Nov 2014 21:02:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=iwPCFAlmyhZS2EoeKpGdKD/wqUQUkIHoKMvxrycxe74=; b=R4/BtV+s7c8/DMGnoqbMbaEMRwIgPapnJ/A5PaSh5RnHvCYr1Z5gyacE/D+FXEZqeP EyXSgZSa9+0ZLTgADX8iDGCs7KvhivwDDIxaB9E+b9uzAabXvn2mRkx133TchbTVIIpG w5Bw6eXcfA8rrd8FzNvhyoGzNN1ebqeBOaA8EHdjyCJSEyFKHNY8ZZMOATE72BleEVwy J93p5dfC3c/BBkaOG85jg+LmDNgw3MEnVpraqlPQ9uJ0auOBONTBO32ic2X35C7Uav1n m4EsK5/Dde72njZ5QaUgx9WWzko8bWubdqHWm0YE7vhinLfvcdbp0SCbnqKwKeAYqdEf MaPQ== X-Received: by 10.68.211.193 with SMTP id ne1mr79158858pbc.49.1417237329409; Fri, 28 Nov 2014 21:02:09 -0800 (PST) Received: from [192.168.1.3] ([98.248.138.12]) by mx.google.com with ESMTPSA id o5sm11390076pdr.50.2014.11.28.21.02.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Nov 2014 21:02:08 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Anish Gupta In-Reply-To: Date: Fri, 28 Nov 2014 21:02:06 -0800 Message-Id: <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> References: <5478E4C4.3080203@gmx.com> To: Nikos Vassiliadis X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 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: Sat, 29 Nov 2014 05:02:10 -0000 >> bge0@pci0:2:0:0: class=3D0x020000 card=3D0x06471025 = chip=3D0x16b514e4 rev=3D0x10 hdr=3D0x00 >> sdhci_pci0@pci0:2:0:1: class=3D0x080501 card=3D0x06471025 = chip=3D0x16bc14e4 rev=3D0x10 hdr=3D0x00 >> none2@pci0:2:0:2: class=3D0x088000 card=3D0x06471025 = chip=3D0x16be14e4 rev=3D0x10 hdr=3D0x00 >> none3@pci0:2:0:3: class=3D0x088000 card=3D0x06471025 = chip=3D0x16bf14e4 rev=3D0x10 hdr=3D0x00 Passthrough stub driver is part of vmm.ko and if it was present early in = boot, you should see ppt@pciD:B:S:F[Domain:Bus:Slot:Function] in = pciocnf list above. Given that bge driver claimed 2/0/0, most likely = vmm.ko failed to load or probably was not present. Do you have = vmm_load=3D=E2=80=9CYES=E2=80=9D in /boot/loader.conf as mentioned in = https://wiki.freebsd.org/bhyve/pci_passthru? = =20 If you already have loader.conf configured correctly, you can try to = manually load vmm.ko once system is booted and see dmesg for any problem = in loading it like kernel mismatch, missing symbol[One common I usually = encounter is KTRACE define in sys/modules/vmm/Makefile but kernel config = is missing =E2=80=9Coption KTRACE=E2=80=9D] etc. Thanks, Anish > On Nov 28, 2014, at 5:05 PM, Craig Rodrigues = wrote: >=20 > On Fri, Nov 28, 2014 at 1:10 PM, Nikos Vassiliadis = wrote: >=20 >> Hi, >>=20 >> I am trying to use PCI passthrough to pass the bge device to a guest = but I >> am doing something wrong. I have tried several combinations of = pptdevs like >> "2/0/0 2/0/1 2/0/2 2/0/3" but it always fails on 2/0/0. Any ideas = what I >> could try? >>=20 >=20 > Did you read this: https://wiki.freebsd.org/bhyve/pci_passthru ? >=20 > After following those instructions, what is the output of pciconf -l = -v > before and after enabling PCI passthru? > On the host and in the guest? >=20 >=20 > -- > Craig > _______________________________________________ > 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 Sat Nov 29 09:28:59 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 169D6AE4; Sat, 29 Nov 2014 09:28:59 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (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 84E97EDD; Sat, 29 Nov 2014 09:28:58 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id gm9so6722193lab.12 for ; Sat, 29 Nov 2014 01:28:55 -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=nOk/8cDzD87G+NOCc1gE5lBPOJzp7QitMiSZ38qjqEM=; b=yygMI2Y6x6B1LeOnyGMIOJYBX/Mm6Yb5TRmVIpsHP0aXzhb/6m1B00Ka57TnbKk30m CVnHTgZ0CtW/0NAzIqeXRcyWNrvV3CjM6dv/3olqLHIgRFfm1Z2KA3jLzxJvZQFIZlxS l4XiZ0yORrlwWnXDQCa57HSgfFS+7nMxY5Wtu2RBeLhKphl8WxvH1jXzd4OtAUmbHH4q iBRAi4yrNfqnS4h20L/lklGcWnhs5Xxt1g6rmx9GvDAwVoAlGlYDqmciMdQKl2F9beAR aVHJyXH7H4gve469BgNErhiVH6dRD+wriX/oNzOp2h4AVdZaxXh4tTN02Awng7nMDXs5 ji1w== MIME-Version: 1.0 X-Received: by 10.152.88.44 with SMTP id bd12mr32125249lab.88.1417253335677; Sat, 29 Nov 2014 01:28:55 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sat, 29 Nov 2014 01:28:55 -0800 (PST) In-Reply-To: <547364EB.7090505@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> <547364EB.7090505@freebsd.org> Date: Sat, 29 Nov 2014 01:28:55 -0800 X-Google-Sender-Auth: INz4Aba9egH0dYwnkJ6vYYSijMk Message-ID: Subject: Re: RFC: Enabling VIMAGE in GENERIC From: Craig Rodrigues To: Julian Elischer 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: Sat, 29 Nov 2014 09:28:59 -0000 On Mon, Nov 24, 2014 at 9:03 AM, Julian Elischer wrote: > > > also look at the following: (a little dated) > > http://p4web.freebsd.org/@md=d&cd=//depot/projects/vimage/&cdf=//depot/projects/vimage/porting_to_vimage.txt&c=tO0@//depot/projects/vimage/porting_to_vimage.txt?ac=22 This is a useful document. I put it on the wiki: https://wiki.freebsd.org/VIMAGE/porting-to-vimage -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 14:01:46 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 DE2F547E for ; Sat, 29 Nov 2014 14:01:46 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8989BB86 for ; Sat, 29 Nov 2014 14:01:46 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MNZ9u-1Xof7Z0z8s-007C4B; Sat, 29 Nov 2014 15:01:39 +0100 Message-ID: <5479D1BE.2010106@gmx.com> Date: Sat, 29 Nov 2014 15:01:34 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Craig Rodrigues Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 References: <5478E4C4.3080203@gmx.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:43iBU4psmk7sWhtIkhsq+PHxoXBk7ZEgDr0FYuBwBYj+YVFC4gc P4kFwv1120zprFpK9XR6R9tgtjY3LcTaCLjVAXR3bJ7CgIFLV4cmw0/16pmmAyWwE1HKXgF riA8G549uRd2A/R1mxEkEouGs+cC9Wukr4VK7Blow4oiw6w0CJUxAmw9lIiDQ8C+AgowlgV i5su8zclITvy9Nc8W7ORw== X-UI-Out-Filterresults: notjunk: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: Sat, 29 Nov 2014 14:01:47 -0000 On 11/29/14 02:05, Craig Rodrigues wrote: > On Fri, Nov 28, 2014 at 1:10 PM, Nikos Vassiliadis > wrote: > > Hi, > > I am trying to use PCI passthrough to pass the bge device to a guest > but I am doing something wrong. I have tried several combinations of > pptdevs like "2/0/0 2/0/1 2/0/2 2/0/3" but it always fails on 2/0/0. > Any ideas what I could try? > > > Did you read this: https://wiki.freebsd.org/bhyve/pci_passthru ? > > After following those instructions, what is the output of pciconf -l -v > before and after enabling PCI passthru? > On the host and in the guest? Before loading vmm.ko: > hostb0@pci0:0:0:0: class=0x060000 card=0x064b1025 chip=0x01548086 rev=0x09 hdr=0x00 > pcib1@pci0:0:1:0: class=0x060400 card=0x064b1025 chip=0x01518086 rev=0x09 hdr=0x01 > vgapci1@pci0:0:2:0: class=0x030000 card=0x064b1025 chip=0x01668086 rev=0x09 hdr=0x00 > none0@pci0:0:22:0: class=0x078000 card=0x064b1025 chip=0x1e3a8086 rev=0x04 hdr=0x00 > ehci0@pci0:0:26:0: class=0x0c0320 card=0x064b1025 chip=0x1e2d8086 rev=0x04 hdr=0x00 > hdac0@pci0:0:27:0: class=0x040300 card=0x064b1025 chip=0x1e208086 rev=0x04 hdr=0x00 > pcib2@pci0:0:28:0: class=0x060400 card=0x064b1025 chip=0x1e108086 rev=0xc4 hdr=0x01 > pcib3@pci0:0:28:1: class=0x060400 card=0x064b1025 chip=0x1e128086 rev=0xc4 hdr=0x01 > ehci1@pci0:0:29:0: class=0x0c0320 card=0x064b1025 chip=0x1e268086 rev=0x04 hdr=0x00 > isab0@pci0:0:31:0: class=0x060100 card=0x064b1025 chip=0x1e578086 rev=0x04 hdr=0x00 > ahci0@pci0:0:31:2: class=0x010601 card=0x064b1025 chip=0x1e038086 rev=0x04 hdr=0x00 > none1@pci0:0:31:3: class=0x0c0500 card=0x064b1025 chip=0x1e228086 rev=0x04 hdr=0x00 > vgapci0@pci0:1:0:0: class=0x030000 card=0x06911025 chip=0x114010de rev=0xa1 hdr=0x00 > none2@pci0:2:0:0: class=0x020000 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 > none3@pci0:2:0:1: class=0x080501 card=0x06471025 chip=0x16bc14e4 rev=0x10 hdr=0x00 > none4@pci0:2:0:2: class=0x088000 card=0x06471025 chip=0x16be14e4 rev=0x10 hdr=0x00 > none5@pci0:2:0:3: class=0x088000 card=0x06471025 chip=0x16bf14e4 rev=0x10 hdr=0x00 > none6@pci0:3:0:0: class=0x028000 card=0xe042105b chip=0x472714e4 rev=0x01 hdr=0x00 After loading vmm.ko: > hostb0@pci0:0:0:0: class=0x060000 card=0x064b1025 chip=0x01548086 rev=0x09 hdr=0x00 > pcib1@pci0:0:1:0: class=0x060400 card=0x064b1025 chip=0x01518086 rev=0x09 hdr=0x01 > vgapci1@pci0:0:2:0: class=0x030000 card=0x064b1025 chip=0x01668086 rev=0x09 hdr=0x00 > none0@pci0:0:22:0: class=0x078000 card=0x064b1025 chip=0x1e3a8086 rev=0x04 hdr=0x00 > ehci0@pci0:0:26:0: class=0x0c0320 card=0x064b1025 chip=0x1e2d8086 rev=0x04 hdr=0x00 > hdac0@pci0:0:27:0: class=0x040300 card=0x064b1025 chip=0x1e208086 rev=0x04 hdr=0x00 > pcib2@pci0:0:28:0: class=0x060400 card=0x064b1025 chip=0x1e108086 rev=0xc4 hdr=0x01 > pcib3@pci0:0:28:1: class=0x060400 card=0x064b1025 chip=0x1e128086 rev=0xc4 hdr=0x01 > ehci1@pci0:0:29:0: class=0x0c0320 card=0x064b1025 chip=0x1e268086 rev=0x04 hdr=0x00 > isab0@pci0:0:31:0: class=0x060100 card=0x064b1025 chip=0x1e578086 rev=0x04 hdr=0x00 > ahci0@pci0:0:31:2: class=0x010601 card=0x064b1025 chip=0x1e038086 rev=0x04 hdr=0x00 > none1@pci0:0:31:3: class=0x0c0500 card=0x064b1025 chip=0x1e228086 rev=0x04 hdr=0x00 > vgapci0@pci0:1:0:0: class=0x030000 card=0x06911025 chip=0x114010de rev=0xa1 hdr=0x00 > ppt0@pci0:2:0:0: class=0x020000 card=0x06471025 chip=0x16b514e4 rev=0x10 hdr=0x00 > ppt1@pci0:2:0:1: class=0x080501 card=0x06471025 chip=0x16bc14e4 rev=0x10 hdr=0x00 > ppt2@pci0:2:0:2: class=0x088000 card=0x06471025 chip=0x16be14e4 rev=0x10 hdr=0x00 > ppt3@pci0:2:0:3: class=0x088000 card=0x06471025 chip=0x16bf14e4 rev=0x10 hdr=0x00 > ppt4@pci0:3:0:0: class=0x028000 card=0xe042105b chip=0x472714e4 rev=0x01 hdr=0x00 Then I start "bhyve ... -s 10,passthru,2/0/0 ..." and it spits: "Unsupported MSI-X configuration: 2/0/0" and quits. This happens *only* with 2/0/0, that is the bge device. When I try to passthrough this: > none6@pci0:3:0:0: class=0x028000 card=0xe042105b chip=0x472714e4 rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'BCM4313 802.11b/g/n Wireless LAN Controller' > class = network it goes further, bhyve starts and the device is passed to the host but I cannot use it from the VM. Actually my goal is to use the wifi adapter from a VM. The bge device is just testing and I thought I should report it/ask about it. From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 14:44: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 13182DE8 for ; Sat, 29 Nov 2014 14:44:43 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 833C0EFB for ; Sat, 29 Nov 2014 14:44:42 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M97Nh-1XkaG50BbB-00CUkK; Sat, 29 Nov 2014 15:44:40 +0100 Message-ID: <5479DBD8.1090009@gmx.com> Date: Sat, 29 Nov 2014 15:44:40 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Anish Gupta Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> In-Reply-To: <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V03:K0:MACG0XFEE7cdAAk+A8ecvy/6ilmsxZzNC0xa3LK1k8VoauyVF07 Lt8vnL777BLBmxJ17kjA02M0e1ExCeduzduwnMh/qusFG6sXh1UpqyoH4wHef3tAyQilN+N HR3V4sTZrckss4bTbx0GIzjdHZKaoYER4qn538e7YGLLI3GrjelRnEJA8wGrsTzerlftDxv v+G9+Bvi7r8faW+aknx4Q== X-UI-Out-Filterresults: notjunk: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: Sat, 29 Nov 2014 14:44:43 -0000 On 11/29/14 06:02, Anish Gupta wrote: >>> bge0@pci0:2:0:0: class=0x020000 card=0x06471025 >>> chip=0x16b514e4 rev=0x10 hdr=0x00 >>> sdhci_pci0@pci0:2:0:1: class=0x080501 card=0x06471025 >>> chip=0x16bc14e4 rev=0x10 hdr=0x00 >>> none2@pci0:2:0:2: class=0x088000 card=0x06471025 >>> chip=0x16be14e4 rev=0x10 hdr=0x00 >>> none3@pci0:2:0:3: class=0x088000 card=0x06471025 >>> chip=0x16bf14e4 rev=0x10 hdr=0x00 > > Passthrough stub driver is part of vmm.ko and if it was present early in > boot, you should see ppt@pciD:B:S:F[Domain:Bus:Slot:Function] in > pciocnf list above. Given that bge driver claimed 2/0/0, most likely > vmm.ko failed to load or probably was not present. Do you have > vmm_load=“YES” in /boot/loader.conf as mentioned in > https://wiki.freebsd.org/bhyve/pci_passthru? Yes. To make testing easier: I removed everything from loader.conf and I removed a few drivers(bge and a few others) that were built-in the kernel, so the host kernel won't use them and now I am testing with kenv and loading and unloading vmm.ko. I always see the correct ppt devices in the dmesg when vmm.ko is loaded. > > If you already have loader.conf configured correctly, you can try to > manually load vmm.ko once system is booted and see dmesg for any problem > in loading it like kernel mismatch, missing symbol[One common I usually > encounter is KTRACE define in sys/modules/vmm/Makefile but kernel config > is missing “option KTRACE”] etc. Everything seems ok here as well, I get nothing but the ppt devices. One thing I noticed and seems different is this: > ppt0 mem 0xb3430000-0xb343ffff,0xb3440000-0xb344ffff irq 16 at device 0.0 on pci2 > ppt1 mem 0xb3400000-0xb340ffff irq 17 at device 0.1 on pci2 > ppt2 mem 0xb3410000-0xb341ffff irq 17 at device 0.2 on pci2 > ppt3 mem 0xb3420000-0xb342ffff irq 17 at device 0.3 on pci2 so ppt0 (the bge device) has two mem ranges... Another thing I should mention is that "acpidump -t | grep DMAR" reports nothing. It is mentioned in the documentation but I didn't see until now. From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 17:38:23 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 05203445; Sat, 29 Nov 2014 17:38:23 +0000 (UTC) Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e: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 C254B90; Sat, 29 Nov 2014 17:38:22 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id et14so8496473pad.29 for ; Sat, 29 Nov 2014 09:38:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=VaSGUFtiU5uviQBvBQQg4CofXwavvUzHEn28gsy+384=; b=GtyPXe/5pCKKFBCUMlvBYGzhxQqWuZuP8WcX70UiZ+RvQXWQ6fsnLbQXjlDAmsCGvU u4mpbueUIrO3iCYjdraTPjybaZf5y9f/QN5/KchJBSk7ybnflH1TOtLK3WCgOoBtfw41 U6fgjFKHOKxD4bxS92U798JD3WURcaehASOOUcsH9MN4EOKgl4GNT4RKHnj6NJd4Ackq ecUriQwmgJB6Bidj6Cq7X/LddEa+hfiyORD68/9exsIaMyab1uvj4qeVr1p7Cn0Zb6Bp 4Ob0tiZZtyzTEZYdnic8BaNX+Ojc4JHooCoeLz1rQx/kcNxLeyhTMvsYC6a22jRCiDVX CtBA== X-Received: by 10.66.161.197 with SMTP id xu5mr23721362pab.3.1417282702417; Sat, 29 Nov 2014 09:38:22 -0800 (PST) Received: from [192.168.1.3] ([98.248.138.12]) by mx.google.com with ESMTPSA id oc16sm839120pdb.41.2014.11.29.09.38.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 29 Nov 2014 09:38:21 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Anish Gupta In-Reply-To: <5479DBD8.1090009@gmx.com> Date: Sat, 29 Nov 2014 09:38:19 -0800 Message-Id: References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> To: Nikos Vassiliadis X-Mailer: Apple Mail (2.1993) Content-Type: text/plain; charset=utf-8 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: Sat, 29 Nov 2014 17:38:23 -0000 >Another thing I should mention is that "acpidump -t | grep DMAR" reports nothing. It is mentioned in the documentation but I didn't see = until now. DMAR/VT-d has been supported for sometime now by Intel chipset. You want = to check your BIOS set-up to enable VT-d. >Actually my goal is to use the wifi adapter from a VM. The bge device = is just testing and I thought I should report it/ask about it. What is the error you see in VM for enabling wifi adapter? Is the = corresponding driver getting attached to WiFi adapter? >Then I start "bhyve ... -s 10,passthru,2/0/0 ..." and it spits: "Unsupported MSI-X configuration: 2/0/0" and quits. > ppt0@pci0:2:0:0: class=3D0x020000 card=3D0x06471025 = chip=3D0x16b514e4 rev=3D0x10 hdr=3D0x00 I will try to reproduce the problem if I get hold of this device. -Anish > On Nov 29, 2014, at 6:44 AM, Nikos Vassiliadis wrote: >=20 >=20 >=20 > On 11/29/14 06:02, Anish Gupta wrote: >>>> bge0@pci0:2:0:0: class=3D0x020000 card=3D0x06471025 >>>> chip=3D0x16b514e4 rev=3D0x10 hdr=3D0x00 >>>> sdhci_pci0@pci0:2:0:1: class=3D0x080501 card=3D0x06471025 >>>> chip=3D0x16bc14e4 rev=3D0x10 hdr=3D0x00 >>>> none2@pci0:2:0:2: class=3D0x088000 card=3D0x06471025 >>>> chip=3D0x16be14e4 rev=3D0x10 hdr=3D0x00 >>>> none3@pci0:2:0:3: class=3D0x088000 card=3D0x06471025 >>>> chip=3D0x16bf14e4 rev=3D0x10 hdr=3D0x00 >>=20 >> Passthrough stub driver is part of vmm.ko and if it was present early = in >> boot, you should see ppt@pciD:B:S:F[Domain:Bus:Slot:Function] in >> pciocnf list above. Given that bge driver claimed 2/0/0, most likely >> vmm.ko failed to load or probably was not present. Do you have >> vmm_load=3D=E2=80=9CYES=E2=80=9D in /boot/loader.conf as mentioned in >> https://wiki.freebsd.org/bhyve/pci_passthru? >=20 > Yes. To make testing easier: > I removed everything from loader.conf and I removed a few drivers(bge = and a few others) that were built-in the kernel, so the host kernel = won't use them >=20 > and now I am testing with kenv and loading and unloading vmm.ko. I = always see the correct ppt devices in the dmesg when vmm.ko is loaded. >=20 >>=20 >> If you already have loader.conf configured correctly, you can try to >> manually load vmm.ko once system is booted and see dmesg for any = problem >> in loading it like kernel mismatch, missing symbol[One common I = usually >> encounter is KTRACE define in sys/modules/vmm/Makefile but kernel = config >> is missing =E2=80=9Coption KTRACE=E2=80=9D] etc. >=20 > Everything seems ok here as well, I get nothing but the ppt devices. >=20 > One thing I noticed and seems different is this: >> ppt0 mem 0xb3430000-0xb343ffff,0xb3440000-0xb344ffff irq 16 at device = 0.0 on pci2 >> ppt1 mem 0xb3400000-0xb340ffff irq 17 at device 0.1 on pci2 >> ppt2 mem 0xb3410000-0xb341ffff irq 17 at device 0.2 on pci2 >> ppt3 mem 0xb3420000-0xb342ffff irq 17 at device 0.3 on pci2 >=20 > so ppt0 (the bge device) has two mem ranges... >=20 > Another thing I should mention is that "acpidump -t | grep DMAR" > reports nothing. It is mentioned in the documentation but I didn't see = until now. From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 18:45:49 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 A51CBE2D for ; Sat, 29 Nov 2014 18:45:49 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F8CB8CB for ; Sat, 29 Nov 2014 18:45:49 +0000 (UTC) Received: from moby.local ([109.193.238.174]) by mail.gmx.com (mrgmx002) with ESMTPSA (Nemesis) id 0MCtql-1Xlkkb2WVn-009eZH; Sat, 29 Nov 2014 19:45:46 +0100 Message-ID: <547A1454.2030901@gmx.com> Date: Sat, 29 Nov 2014 19:45:40 +0100 From: Nikos Vassiliadis User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Anish Gupta Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> In-Reply-To: Content-Type: multipart/mixed; boundary="------------030009000707060500090907" X-Provags-ID: V03:K0:QU0tL/sfMTcnaxiX1xOtudp5vNe6q78jwDC0DCoQz+FyxX8v/0q coAiTCfvSErnx8Ibj71LmNT1R1x6bKVwG4Zll7ngBYRFsvcxMKTdkMgMGJl/61ZXtQLX4gr r92poDjbsOE7FJu8Yzb0yVH5mC0Fuji50H8YXOab6heFxAgtguiPSU0fiPHiHFFkJzwjttX TRUOb6XQ3PNW4KdH6nD6A== X-UI-Out-Filterresults: notjunk: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: Sat, 29 Nov 2014 18:45:49 -0000 This is a multi-part message in MIME format. --------------030009000707060500090907 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 11/29/14 18:38, Anish Gupta wrote: > >Another thing I should mention is that "acpidump -t | grep DMAR" > reports nothing. It is mentioned in the documentation but I didn't see > until now. > > DMAR/VT-d has been supported for sometime now by Intel chipset. You want > to check your BIOS set-up to enable VT-d. There are very few setting in the BIOS setup and nothing related to VT-d. My CPU and CPU settings are these: > CPU: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz (2394.61-MHz K8-class CPU) > Origin = "GenuineIntel" Id = 0x306a9 Family = 0x6 Model = 0x3a Stepping = 9 > Features=0xbfebfbff > Features2=0x3dbae3bf > AMD Features=0x28100800 > AMD Features2=0x1 > Structured Extended Features=0x281 > VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID > TSC: P-state invariant, performance statistics I have attached the output of "acpidump -t" in case you'd like to take a look. > >Actually my goal is to use the wifi adapter from a VM. The bge device > is just testing and I thought I should report it/ask about it. > What is the error you see in VM for enabling wifi adapter? Is the > corresponding driver getting attached to WiFi adapter? When I load the kernel module, I get this: > [ 542.919615] cfg80211: Calling CRDA to update world regulatory domain > [ 542.932441] wl 0000:00:07.0: can't derive routing for PCI INT A > [ 542.932449] wl 0000:00:07.0: PCI INT A: no GSI > [ 543.002253] wlan0: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.30.223.248 (r487574) After that, there is a wlan0 device but I am not sure whether it works. There are no new kernel warnings or error messages but no matter what I do (scan, create an AP etc) there is zero reaction. But that might a problematic driver that the VM is using. That's on Linux 3.16.something. I have tried to load another driver and there is a complain regarding PCI which is common to both drivers: > [ 1515.692558] bcma-pci-bridge 0000:00:07.0: can't derive routing for PCI INT A > [ 1515.692568] bcma-pci-bridge 0000:00:07.0: PCI INT A: no GSI Didnt test further with this driver. On FreeBSD, I tried to do the same with an ndis windows driver. It didn't get very far because some windows drivers and ndis and amd64 don't like each other very much:) > >Then I start "bhyve ... -s 10,passthru,2/0/0 ..." and it spits: > "Unsupported MSI-X configuration: 2/0/0" > and quits. >> ppt0@pci0:2:0:0: class=0x020000 card=0x06471025 chip=0x16b514e4 >> rev=0x10 hdr=0x00 > > I will try to reproduce the problem if I get hold of this device. Great, thank you. --------------030009000707060500090907 Content-Type: text/plain; charset=us-ascii; name="acpidump-t" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="acpidump-t" LyoKICBSU0QgUFRSOiBPRU09QUNSU1lTLCBBQ1BJX1Jldj0yLjB4ICgyKQoJWFNEVD0weDk2 ZmZlMjEwLCBsZW5ndGg9MzYsIGNrc3VtPTg1CiAqLwovKgogIFhTRFQ6IExlbmd0aD0xNTYs IFJldmlzaW9uPTEsIENoZWNrc3VtPTE0OCwKCU9FTUlEPUFDUlNZUywgT0VNIFRhYmxlIElE PUFDUlBSRENULCBPRU0gUmV2aXNpb249MHgxLAoJQ3JlYXRvciBJRD0sIENyZWF0b3IgUmV2 aXNpb249MHgxMDAwMDEzCglFbnRyaWVzPXsgMHg5NmZmYjAwMCwgMHg5NmZmZDAwMCwgMHg5 NmZmYzAwMCwgMHg5NmZmYTAwMCwgMHg5NmZmOTAwMCwgMHg5NmZmODAwMCwgMHg5NmZlYjAw MCwgMHg5NmZlOTAwMCwgMHg5NmZlNDAwMCwgMHg5NmZlMzAwMCwgMHg5NmZlMTAwMCwgMHg5 NmZlMDAwMCwgMHg5NmZkZjAwMCwgMHg5NmZkZTAwMCwgMHg5NmZkYTAwMCB9CiAqLwovKgog IEZBQ1A6IExlbmd0aD0yNjgsIFJldmlzaW9uPTUsIENoZWNrc3VtPTM4LAoJT0VNSUQ9QUNS U1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEsCglDcmVhdG9y IElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogCUZBQ1M9MHg5NmZiYTAwMCwg RFNEVD0weDk2ZmVjMDAwCglJTlRfTU9ERUw9QVBJQwoJUHJlZmVycmVkX1BNX1Byb2ZpbGU9 TW9iaWxlICgyKQoJU0NJX0lOVD05CglTTUlfQ01EPTB4YjIsIEFDUElfRU5BQkxFPTB4YTAs IEFDUElfRElTQUJMRT0weGExLCBTNEJJT1NfUkVRPTB4MAoJUFNUQVRFX0NOVD0weDgwCglQ TTFhX0VWVF9CTEs9MHg0MDAtMHg0MDMKCVBNMWFfQ05UX0JMSz0weDQwNC0weDQwNQoJUE0y X0NOVF9CTEs9MHg0NTAtMHg0NTAKCVBNX1RNUl9CTEs9MHg0MDgtMHg0MGIKCUdQRTBfQkxL PTB4NDIwLTB4NDJmCglDU1RfQ05UPTB4ODUKCVBfTFZMMl9MQVQ9MTAxIHVzLCBQX0xWTDNf TEFUPTU3IHVzCglGTFVTSF9TSVpFPTEwMjQsIEZMVVNIX1NUUklERT0xNgoJRFVUWV9PRkZT RVQ9MSwgRFVUWV9XSURUSD0zCglEQVlfQUxSTT0xMywgTU9OX0FMUk09MCwgQ0VOVFVSWT0w CglJQVBDX0JPT1RfQVJDSD17TEVHQUNZX0RFVklDRVMsODA0MixOT19BU1BNfQoJRmxhZ3M9 e1dCSU5WRCxDMV9TVVBQT1JURUQsU0xFRVBfQlVUVE9OLFM0X1JUQ19XQUtFLERPQ0tJTkdf U1VQUE9SVEVELFJFU0VUX1JFR0lTVEVSLFBMQVRGT1JNX0NMT0NLLFM0X1JUQ19WQUxJRCxS RU1PVEVfUE9XRVJfT059CglSRVNFVF9SRUc9MHhiMjowWzhdIChJTyksIFJFU0VUX1ZBTFVF PTB4ZmIKICovCi8qCiAgRkFDUzoJTGVuZ3RoPTY0LCBId1NpZz0weDAwMDAwMDAwLCBGaXJt X1dha2VfVmVjPTB4MDAwMDAwMDAKCUdsb2JhbF9Mb2NrPQoJRmxhZ3M9CglWZXJzaW9uPTIK ICovCi8qCiAgRFNEVDogTGVuZ3RoPTQ4MDMwLCBSZXZpc2lvbj0xLCBDaGVja3N1bT0yMDgs CglPRU1JRD1BQ1JTWVMsIE9FTSBUYWJsZSBJRD1BQ1JQUkRDVCwgT0VNIFJldmlzaW9uPTB4 MCwKCUNyZWF0b3IgSUQ9MTAyNSwgQ3JlYXRvciBSZXZpc2lvbj0weDQwMDAwCiAqLwovKgog IFVFRkk6IExlbmd0aD01NjYsIFJldmlzaW9uPTEsIENoZWNrc3VtPTUyLAoJT0VNSUQ9QUNS U1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEsCglDcmVhdG9y IElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogKi8KLyoKICBBU0YhOiBMZW5n dGg9MTY1LCBSZXZpc2lvbj0zMiwgQ2hlY2tzdW09MjMxLAoJT0VNSUQ9QUNSU1lTLCBPRU0g VGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEsCglDcmVhdG9yIElEPTEwMjUs IENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogKi8KLyoKICBIUEVUOiBMZW5ndGg9NTYsIFJl dmlzaW9uPTEsIENoZWNrc3VtPTE3MCwKCU9FTUlEPUFDUlNZUywgT0VNIFRhYmxlIElEPUFD UlBSRENULCBPRU0gUmV2aXNpb249MHgxLAoJQ3JlYXRvciBJRD0xMDI1LCBDcmVhdG9yIFJl dmlzaW9uPTB4NDAwMDAKCUhQRVQgTnVtYmVyPTAKCUFERFI9MHhmZWQwMDAwMDowWzBdIChN ZW1vcnkpCUhXIFJldj0weDEKCUNvbXBhcmF0b3JzPTIKCUNvdW50ZXIgU2l6ZT0xCglMZWdh Y3kgSVJRIHJvdXRpbmcgY2FwYWJsZT17VFJVRX0KCVBDSSBWZW5kb3IgSUQ9MHg4MDg2CglN aW5pbWFsIFRpY2s9MTI4CiAqLwovKgogIEFQSUM6IExlbmd0aD0xNDAsIFJldmlzaW9uPTMs IENoZWNrc3VtPTE0LAoJT0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9F TSBSZXZpc2lvbj0weDEsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0 MDAwMAoJTG9jYWwgQVBJQyBBRERSPTB4ZmVlMDAwMDAKCUZsYWdzPXtQQy1BVH0KCglUeXBl PUxvY2FsIEFQSUMKCUFDUEkgQ1BVPTEKCUZsYWdzPXtFTkFCTEVEfQoJQVBJQyBJRD0wCgoJ VHlwZT1Mb2NhbCBBUElDCglBQ1BJIENQVT0yCglGbGFncz17RU5BQkxFRH0KCUFQSUMgSUQ9 MQoKCVR5cGU9TG9jYWwgQVBJQwoJQUNQSSBDUFU9MwoJRmxhZ3M9e0VOQUJMRUR9CglBUElD IElEPTIKCglUeXBlPUxvY2FsIEFQSUMKCUFDUEkgQ1BVPTQKCUZsYWdzPXtFTkFCTEVEfQoJ QVBJQyBJRD0zCgoJVHlwZT1Mb2NhbCBBUElDCglBQ1BJIENQVT01CglGbGFncz17RElTQUJM RUR9CglBUElDIElEPTAKCglUeXBlPUxvY2FsIEFQSUMKCUFDUEkgQ1BVPTYKCUZsYWdzPXtE SVNBQkxFRH0KCUFQSUMgSUQ9MAoKCVR5cGU9TG9jYWwgQVBJQwoJQUNQSSBDUFU9NwoJRmxh Z3M9e0RJU0FCTEVEfQoJQVBJQyBJRD0wCgoJVHlwZT1Mb2NhbCBBUElDCglBQ1BJIENQVT04 CglGbGFncz17RElTQUJMRUR9CglBUElDIElEPTAKCglUeXBlPUlPIEFQSUMKCUFQSUMgSUQ9 MAoJSU5UIEJBU0U9MAoJQUREUj0weDAwMDAwMDAwZmVjMDAwMDAKCglUeXBlPUlOVCBPdmVy cmlkZQoJQlVTPTAKCUlSUT0wCglJTlRSPTIKCUZsYWdzPXtQb2xhcml0eT1jb25mb3JtaW5n LCBUcmlnZ2VyPWNvbmZvcm1pbmd9CgoJVHlwZT1JTlQgT3ZlcnJpZGUKCUJVUz0wCglJUlE9 OQoJSU5UUj05CglGbGFncz17UG9sYXJpdHk9YWN0aXZlLWhpLCBUcmlnZ2VyPWxldmVsfQog Ki8KLyoKICBNQ0ZHOiBMZW5ndGg9NjAsIFJldmlzaW9uPTEsIENoZWNrc3VtPTEzMCwKCU9F TUlEPUFDUlNZUywgT0VNIFRhYmxlIElEPUFDUlBSRENULCBPRU0gUmV2aXNpb249MHgxLAoJ Q3JlYXRvciBJRD0xMDI1LCBDcmVhdG9yIFJldmlzaW9uPTB4NDAwMDAKCglCYXNlIEFkZHJl c3M9MHgwMDAwMDAwMGYwMDAwMDAwCglTZWdtZW50IEdyb3VwPTB4MDAwMAoJU3RhcnQgQnVz PTAKCUVuZCBCdXM9NjMKICovCi8qCiAgU1NEVDogTGVuZ3RoPTE3OTAsIFJldmlzaW9uPTEs IENoZWNrc3VtPTE5LAoJT0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9F TSBSZXZpc2lvbj0weDEwMDAsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249 MHg0MDAwMAogKi8KLyoKICBCT09UOiBMZW5ndGg9NDAsIFJldmlzaW9uPTEsIENoZWNrc3Vt PTEwNiwKCU9FTUlEPUFDUlNZUywgT0VNIFRhYmxlIElEPUFDUlBSRENULCBPRU0gUmV2aXNp b249MHgxLAoJQ3JlYXRvciBJRD0xMDI1LCBDcmVhdG9yIFJldmlzaW9uPTB4NDAwMDAKICov Ci8qCiAgQVNQVDogTGVuZ3RoPTUyLCBSZXZpc2lvbj03LCBDaGVja3N1bT0xNTIsCglPRU1J RD1BQ1JTWVMsIE9FTSBUYWJsZSBJRD1BQ1JQUkRDVCwgT0VNIFJldmlzaW9uPTB4MSwKCUNy ZWF0b3IgSUQ9MTAyNSwgQ3JlYXRvciBSZXZpc2lvbj0weDQwMDAwCiAqLwovKgogIERCR1A6 IExlbmd0aD01MiwgUmV2aXNpb249MSwgQ2hlY2tzdW09MTcyLAoJT0VNSUQ9QUNSU1lTLCBP RU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEsCglDcmVhdG9yIElEPTEw MjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogKi8KLyoKICBGUERUOiBMZW5ndGg9Njgs IFJldmlzaW9uPTEsIENoZWNrc3VtPTYzLAoJT0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9 QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3Ig UmV2aXNpb249MHg0MDAwMAogKi8KLyoKICBNU0RNOiBMZW5ndGg9ODUsIFJldmlzaW9uPTMs IENoZWNrc3VtPTcyLAoJT0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9F TSBSZXZpc2lvbj0weDEsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0 MDAwMAogKi8KLyoKICBTU0RUOiBMZW5ndGg9MjI3NiwgUmV2aXNpb249MSwgQ2hlY2tzdW09 MjE4LAoJT0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lv bj0weDMwMDAsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAog Ki8KLyoKICBTU0RUOiBMZW5ndGg9MjcwNiwgUmV2aXNpb249MSwgQ2hlY2tzdW09MTg3LAoJ T0VNSUQ9QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDMw MDAsCglDcmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogKi8KLyoK ICBTU0RUOiBMZW5ndGg9ODU4MSwgUmV2aXNpb249MSwgQ2hlY2tzdW09MTgxLAoJT0VNSUQ9 QUNSU1lTLCBPRU0gVGFibGUgSUQ9QUNSUFJEQ1QsIE9FTSBSZXZpc2lvbj0weDEwMDAsCglD cmVhdG9yIElEPTEwMjUsIENyZWF0b3IgUmV2aXNpb249MHg0MDAwMAogKi8K --------------030009000707060500090907-- From owner-freebsd-virtualization@FreeBSD.ORG Sat Nov 29 23:48:25 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 AEF517A9 for ; Sat, 29 Nov 2014 23:48:25 +0000 (UTC) Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::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 2C3CB6AA for ; Sat, 29 Nov 2014 23:48:25 +0000 (UTC) Received: by mail-lb0-f170.google.com with SMTP id w7so7050946lbi.29 for ; Sat, 29 Nov 2014 15:48: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=pZ+0v24WX0JGVB64kkH6eNJrqjZvKHvSKCbyZ6QHIFs=; b=foSmsYqhXQjepH6myoQiIevSUX0obSWLaDmdqeDkZKza2AWV3WI4/K1jnjTu93TJMp SjT28OjJ87BAh833XCmOoSwzqfg+6lj6Gc0HnCp7gREbEN4kekiRDrbQrVdpDEd8NumY 77aSWqCP1Lfj11kvATV4wLUuX+77OfaHDpSWOLQLOGXhys33qvgKdSVSKo7M/l1VJvVN fbIsPTv7dWhiVf7X+02q9WtMdbv0Vc4RYQWoVDCFUFd7jePtZQ8Fu2bAXV77kv+PG9GR OCc+T6w77QLYEazGoSsBmVQ1+5ImOwe1njA7ESgQ+ye0oSAu+WLHwaCJ14hNK+W1jdqI YW1A== MIME-Version: 1.0 X-Received: by 10.152.88.44 with SMTP id bd12mr34637332lab.88.1417304903088; Sat, 29 Nov 2014 15:48:23 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.130.168 with HTTP; Sat, 29 Nov 2014 15:48:23 -0800 (PST) In-Reply-To: <547A1454.2030901@gmx.com> References: <5478E4C4.3080203@gmx.com> <1B9C5228-5549-412C-AAE9-5053C86EDB9D@gmail.com> <5479DBD8.1090009@gmx.com> <547A1454.2030901@gmx.com> Date: Sat, 29 Nov 2014 15:48:23 -0800 X-Google-Sender-Auth: wDXW-RUSIRdfKRoZAOeBYaewpa8 Message-ID: Subject: Re: bhyve: Unsupported MSI-X configuration: 2/0/0 From: Craig Rodrigues To: Nikos Vassiliadis Content-Type: text/plain; charset=ISO-8859-1 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: Sat, 29 Nov 2014 23:48:25 -0000 On Sat, Nov 29, 2014 at 10:45 AM, Nikos Vassiliadis wrote: > There are very few setting in the BIOS setup and nothing related to VT-d. > My CPU and CPU settings are these: > > CPU: Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz (2394.61-MHz K8-class CPU) >> > I'm not sure, but according to this datasheet: http://ark.intel.com/products/65700/Intel-Core-i3-3110M-Processor-3M-Cache-2_40-GHz this CPU does not support VT-d, which is needed for PCI passthru. -- Craig