From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 15 23:17:50 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6E30B11; Mon, 15 Sep 2014 23:17:50 +0000 (UTC) Received: from webmail2.jnielsen.net (webmail2.jnielsen.net [50.114.224.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "webmail2.jnielsen.net", Issuer "freebsdsolutions.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C6CEEF03; Mon, 15 Sep 2014 23:17:49 +0000 (UTC) Received: from [10.10.1.198] (office.betterlinux.com [199.58.199.60]) (authenticated bits=0) by webmail2.jnielsen.net (8.14.9/8.14.9) with ESMTP id s8FNHd6t095345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 15 Sep 2014 17:17:42 -0600 (MDT) (envelope-from lists@jnielsen.net) X-Authentication-Warning: webmail2.jnielsen.net: Host office.betterlinux.com [199.58.199.60] claimed to be [10.10.1.198] From: John Nielsen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Using virtio_random Date: Mon, 15 Sep 2014 17:17:39 -0600 Message-Id: <3A1313AD-5B06-4F17-9C17-B91AA32FEE88@jnielsen.net> To: freebsd-virtualization@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) X-Mailer: Apple Mail (2.1878.6) Cc: Bryan Venteicher 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, 15 Sep 2014 23:17:51 -0000 Hi all- I am happy to see that virtio_random(4) will be included in FreeBSD = 10.1. To try it out, I loaded up BETA1 in a virtual machine with entropy = passthrough enabled. After booting it with the virtio_random module = loaded I see this in dmesg: virtio_pci3: port 0xc0a0-0xc0bf irq 10 at = device 6.0 on pci0 = =20 vtrnd0: on virtio_pci3 = = =20 virtio_pci3: host features: 0x71000000 = = = =20 virtio_pci3: negotiated features: 0 = = =20 So far, so good. (I think? The 'negotiated features: 0' gives me = pause..) Now how do I use the driver as an entropy source (or verify that it's = being used)? I don't see any difference in the output of "sysctl = kern.random" with or without the driver loaded. Is something missing? Thanks, JN