From owner-freebsd-virtualization@FreeBSD.ORG Sun Sep 7 23:13:35 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 2EF25D19 for ; Sun, 7 Sep 2014 23:13:35 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AE93019E7 for ; Sun, 7 Sep 2014 23:13:34 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id b17so16757599lan.27 for ; Sun, 07 Sep 2014 16:13:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=tSQZZnpO9QyVbmVUy3tvPto1z5aJVbRrVBqamdLU0Pc=; b=P0v1txVqiPllI1NNJETvQ9jHdGRqKXSOUEh3gDd2EY3CS27NhihPLHNXyOrbhih+ql NgIfqeVpBB5af21Z9W21rt0gIDUdzLU+uefQc+EXYFAF3LhatspUwZkqaxWBxJM/cAqK 4gzOt+zH4ryc3NsxBNcaQ/a/DjF5FV/hrrR3lhZ4zmvxdFNwjKCF8PMIl3q+ohHKhhay x2L/doKx/4dZyOvKeVHMuTIolkREFtGcVYYLy+GDCMtSNLuRqlX0yGRtsWbdYMVQSQE8 QtH2DARcf0FW5fhSnkPLKR/yJ9hwgLrTTbKT4s8Mezso7Y9zss/cXEL1aXNzjaNsLNHo bGYw== MIME-Version: 1.0 X-Received: by 10.152.21.229 with SMTP id y5mr15721826lae.9.1410131611600; Sun, 07 Sep 2014 16:13:31 -0700 (PDT) Received: by 10.152.121.100 with HTTP; Sun, 7 Sep 2014 16:13:31 -0700 (PDT) Date: Sun, 7 Sep 2014 19:13:31 -0400 Message-ID: Subject: https://forums.freebsd.org/viewtopic.php?f=3&t=47951 From: Manas Bhatnagar To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Sun, 07 Sep 2014 23:13:35 -0000 Hello, I am running: uname -a FreeBSD ****.** 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I have followed the instructions in the handbook to successfully install and run Debian 7.6.0 64 bit on the host. When trying to run Ubuntu Server 14.04.1 64 bit, after successfully completing the installation, I run into an error where bhyve exits. The VM goes through the boot process and this is the message when it exits: vm exit rdmsr 0x611, cpu 0 Any insight on the error? Thank From owner-freebsd-virtualization@FreeBSD.ORG Sun Sep 7 23:14:29 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBAE8D68 for ; Sun, 7 Sep 2014 23:14:29 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::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 4782719F7 for ; Sun, 7 Sep 2014 23:14:29 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id p9so5128931lbv.14 for ; Sun, 07 Sep 2014 16:14:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=hGF3xjJryK8B9RqLwCvqUhnhmRfqp2Ii+CU/ItiylNA=; b=mr5Y1Zw/GMtErXyXBfeoUwEf4OWugkiNWFcpu0llx/W9v+vvhdELAfEcJ/UnIbvKVX QuCAMLW75HfbQRJq7Tj3FpzyrSYZTKEl65T3r3At8lxogd8fsbZoVjwMjfur6To6kVcc 1BtZZY2qNDGNEBHvWbNKJ3zemJTCgoROPBu+oHeTbhTFznbA62wt/DNsLqVkRdfyBagP yanwibdoyi/H1TCA/egp2rCkAtR/LY0s0r8iyyfza0f0b9vpXoQduBGbegVYbZcPBQDB bULRboCWmIdxocR3A0rxwPX/koSMr9teBpj5pDM/slB42JJIru+MGk0aNORnB9ye5bR6 2owA== MIME-Version: 1.0 X-Received: by 10.112.167.103 with SMTP id zn7mr24018478lbb.63.1410131667183; Sun, 07 Sep 2014 16:14:27 -0700 (PDT) Received: by 10.152.121.100 with HTTP; Sun, 7 Sep 2014 16:14:27 -0700 (PDT) Date: Sun, 7 Sep 2014 19:14:27 -0400 Message-ID: Subject: Unable to boot Ubuntu Server 14.04.1 64 bit on bhyve From: Manas Bhatnagar To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 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: Sun, 07 Sep 2014 23:14:29 -0000 Hello, I am running: uname -a FreeBSD ****.** 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 06:37:44 UTC 2014 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 I have followed the instructions in the handbook to successfully install and run Debian 7.6.0 64 bit on the host. When trying to run Ubuntu Server 14.04.1 64 bit, after successfully completing the installation, I run into an error where bhyve exits. The VM goes through the boot process and this is the message when it exits: vm exit rdmsr 0x611, cpu 0 Any insight on the error? Thanks From owner-freebsd-virtualization@FreeBSD.ORG Sun Sep 7 23:22:20 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1ACF0E3A for ; Sun, 7 Sep 2014 23:22:20 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D052B1AAA for ; Sun, 7 Sep 2014 23:22:19 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 94015121E7; Mon, 8 Sep 2014 09:22:10 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BYF28756 (AUTH peterg@ptree32.com.au); Mon, 8 Sep 2014 09:22:09 +1000 Message-ID: <540CE89F.8040209@freebsd.org> Date: Sun, 07 Sep 2014 16:22:07 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Manas Bhatnagar Subject: Re: Unable to boot Ubuntu Server 14.04.1 64 bit on bhyve 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: Sun, 07 Sep 2014 23:22:20 -0000 Hi, > I am running: > uname -a > FreeBSD ****.** 10.0-RELEASE-p7 FreeBSD 10.0-RELEASE-p7 #0: Tue Jul 8 > 06:37:44 UTC 2014 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 > > I have followed the instructions in the handbook to successfully install > and run Debian 7.6.0 64 bit on the host. > > When trying to run Ubuntu Server 14.04.1 64 bit, after successfully > completing the installation, I run into an error where bhyve exits. The VM > goes through the boot process and this is the message when it exits: > vm exit rdmsr 0x611, cpu 0 > > Any insight on the error? Yes: the Ubuntu kernel is attempting to read the 'package energy status' MSR, which is unsupported in bhyve. In 10-STABLE and CURRENT, there is a new option, "-w", which ignores attempts to read/write unimplemented MSRs. The option made it into 10-STABLE on Apr 8, svn change r264273. You'll have to upgrade to pick up this option. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 8 13:12:55 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E972A2CA for ; Mon, 8 Sep 2014 13:12:55 +0000 (UTC) Received: from potato.growveg.org (potato.growveg.org [62.49.247.163]) (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 A1D7F1B2B for ; Mon, 8 Sep 2014 13:12:55 +0000 (UTC) Received: from john by potato.growveg.org with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1XQyk0-000ISg-39 for freebsd-virtualization@freebsd.org; Mon, 08 Sep 2014 14:12:20 +0100 Date: Mon, 8 Sep 2014 14:12:20 +0100 From: John To: freebsd-virtualization@freebsd.org Subject: Re: bhyve and zfs and speed Message-ID: <20140908131220.GA70743@potato.growveg.org> Reply-To: freebsd-virtualization@freebsd.org References: <20140902133950.GA19480@potato.growveg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: John X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: john@potato.growveg.org X-SA-Exim-Scanned: No (on potato.growveg.org); SAEximRunCond expanded to false 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, 08 Sep 2014 13:12:56 -0000 On Wed, Sep 03, 2014 at 12:15:28AM +0200, Nikolay Denev wrote: > I see you have 108G free memory. Is this due to a recent reboot and > the ARC hasn't grown much yet, or you are limiting it? not doing anything to it - it's running defaults. Two virtual machines are running. > As for ZFS tuning for bhyve, I'm not aware of anything specific, but > you should consider that values you want to put for the zvols for > primarycache and secondarycache. (In your case only primarycache as > you don't have L2ARC). ok, thanks. > Leaving this to the default might be faster but might result in double > caching: Once in the ARC on the host system, and then on the buffer > cache of the UFS guest. ok - will look to see how to turn off double buffering > For MySQL and databases in general, as far as I can remember the > general advice was to run them on zfs datasets with lower reclen, like > 8k for example. > Here you have zvols which default to 8k but the vtbd device reports > 512b sectors, not sure if you try to trick it into using larger values > here wouldn't help. > Also different UFS block sizes for different zvol recordlens might be > interesting test. Thanks again for the advice -- John From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 8 22:58:02 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 35BB28B4 for ; Mon, 8 Sep 2014 22:58:02 +0000 (UTC) Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EC3C6CE for ; Mon, 8 Sep 2014 22:58:01 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id im17so1861854vcb.38 for ; Mon, 08 Sep 2014 15:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=8N93dgoIqmmgL7kjI/IkZE65mtvuDLxoldOj4X4R8O8=; b=ANIvdsLONji4Vc3VL2PpFXRV9QQ60RyAMgmDEVlicEuzU4n57RWhfneYQUnY/x8MNz +53XNoXKcvLWCZ2/dVG6yF9KxLSQ8znwFNBurh+x99/itutwgk7JwSFHPUq3KjAkohhI +n4g0dxBS9PnwURheTlMkosNvll757iRAWLISkXenCnzA4cY3h/ChqtfnyiMIOEixcy8 ZIA48jP3vQa+YoObmXuTbKUwE8fgsrELjcpS9GKCNbpjHvyRx2AXuZaneQnqRipP3vH+ JMsTpT2QFg4VuVHFSecPbxH85oDKlbZJ57LrgSa9u2CsLFZhoItNAXGTHTFsk+JEGpOv tIYw== MIME-Version: 1.0 X-Received: by 10.52.137.2 with SMTP id qe2mr22782208vdb.11.1410215268430; Mon, 08 Sep 2014 15:27:48 -0700 (PDT) Received: by 10.221.46.133 with HTTP; Mon, 8 Sep 2014 15:27:48 -0700 (PDT) Date: Tue, 9 Sep 2014 00:27:48 +0200 Message-ID: Subject: Bhyve virtio-net indirect descriptors From: Nikolay Denev To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 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, 08 Sep 2014 22:58:02 -0000 Hi, Any reason why bhyve is not advertising indirect descriptors for virtio-net? --Nikolay From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 8 23:17:53 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46C29E40 for ; Mon, 8 Sep 2014 23:17:53 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 0896B342 for ; Mon, 8 Sep 2014 23:17:52 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 70E0F125FC; Tue, 9 Sep 2014 09:17:50 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BYF88601 (AUTH peterg@ptree32.com.au); Tue, 9 Sep 2014 09:17:49 +1000 Message-ID: <540E391A.6040701@freebsd.org> Date: Mon, 08 Sep 2014 16:17:46 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Nikolay Denev Subject: Re: Bhyve virtio-net indirect descriptors 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, 08 Sep 2014 23:17:53 -0000 Hi Nikolay, > Any reason why bhyve is not advertising indirect descriptors for virtio-net? Indirect descriptors never seemed to make a lot of sense to me for networking. It requires allocations at the end of the transmit path which could potentially fail, or requires large amounts of preallocation to deal with maximum-sized segments. So, the initial version of bhyve's virtio-net didn't support it since I felt it impacted guest drivers. However, with Chris Torek's contribution of virtio.c, the additional work of dealing with the descriptors is hidden in the virtio api. For transmit it should just work, but there has to be some extra code added for receive. Did you have any particular guests in mind ? later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 10 05:44:32 2014 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0493678D for ; Wed, 10 Sep 2014 05:44:32 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFA2F9CE for ; Wed, 10 Sep 2014 05:44:31 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8A5iVrB032512 for ; Wed, 10 Sep 2014 05:44:31 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 192281] [kern] nmdm with bhyve causes kernel panic Date: Wed, 10 Sep 2014 05:44:32 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: commit-hook@freebsd.org X-Bugzilla-Status: Open X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.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, 10 Sep 2014 05:44:32 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 --- Comment #8 from commit-hook@freebsd.org --- A commit references this bug: Author: grehan Date: Wed Sep 10 05:44:16 UTC 2014 New revision: 271350 URL: http://svnweb.freebsd.org/changeset/base/271350 Log: Fix issue with nmdm and leading zeros in device name. The nmdm code enforces a number between the 'nmdm' and 'A|B' portions of the device name. This is then used as a unit number, and sprintf'd back into the tty name. If leading zeros were used in the name, the created device name is different than the string used for the clone-open (e.g. /dev/nmdm0001A will result in /dev/nmdm1A). Since unit numbers are no longer required with the updated tty code, there seems to be no reason to force the string to be a number. The fix is to allow an arbitrary string between 'nmdm' and 'A|B', within the constraints of devfs names. This allows all existing user of numeric strings to continue to work, and also allows more meaningful names to be used, such as bhyve VM names. Tested on amd64, i386 and ppc64. Reported by: Dave Smith PR: 192281 Reviewed by: neel, glebius Phabric: D729 MFC after: 3 days Changes: head/sys/dev/nmdm/nmdm.c -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 10 13:52:55 2014 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B15BC52; Wed, 10 Sep 2014 13:52:54 +0000 (UTC) Date: Wed, 10 Sep 2014 09:52:51 -0400 From: Glen Barber To: freebsd-virtualization@FreeBSD.org Subject: Does anyone use the FreeBSD VM qcow2 images Message-ID: <20140910135251.GF48287@hub.FreeBSD.org> Reply-To: gjb@FreeBSD.org MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="h6w+13shfCQ8v2Yw" Content-Disposition: inline X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) 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, 10 Sep 2014 13:52:55 -0000 --h6w+13shfCQ8v2Yw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, I'm talking about the images available here: http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ Since mkimg(1) in head/ and stable/10 supports VMDK and VHD formats, I would prefer to remove the need to use qemu-img to generate the VM images. This would mean that the qcow2 format would no longer be produced. If you are using the qcow2 format, please reply off-list. If the qcow2 format is being widely used, they will continue to be produced. If not, they'll go away, and we'll have raw, VMDK, and VHD formats. Thanks. Glen --h6w+13shfCQ8v2Yw Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUEFezAAoJELls3eqvi17QvW0QAIB0TQJ1gqCnPvt8DZXnZr4H 6FbKb8rwmM41HEftTddDgVfN/l9SDt0JvS/FPgcPXoX42yYNfoFAKvbArWpZij1o 0nGyzK509y2Ze+omAB+d3j9+skbL9HHp0FsJtpuiXjQytjMi0yspzPcGUB5Z61MU NBRWnpXYsgrSYUCvVrGPem/JV9G3LdBAJUDT1gi5AJEt7x55tSSdoN9CX+v66GH3 zHtBljZH/xub88Uy7CvAcluGpEvGL02yM8x3LhHhTdwChY6lZbz+w/jtvX3I/l7u 9Gjvq18jm7VkflYH5p1rMiS8SoBTqyR3cVez61t3GH1oFKXeY4C7tEsbvJobHv33 /YB8ZKcjyd70Pxgduh4BeWdzO3P5/nosHKGh07gGDQTu/FNSig3NIb6myGCJvr2O UCfMzRekWhpfpIVLbR4EzR5uBGsYvy1SsH+sE3kT+gtE0z5YxaVYogr5wh89TOhl tEoOgrS/EK8lvDhoN4DyrpJHNyLvxt1xUEEX/qGKhMUkRkbOpMIEU2BiokbUWC48 /+51CvdM5linrw+2twKjITTK42oNVPA6EsMKM504JAxYrvh/b0M23pN4cZXHZocX LOgS0cGiXvEZn/ZMYeFPR+nJZq3m7Zp6MVUKvsMRa6/BVBjhqPWuUcVKx0vMIxCx Lga82E8wyjWcHdplLWk1 =PIaE -----END PGP SIGNATURE----- --h6w+13shfCQ8v2Yw-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 10 17:20:29 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 48269E31; Wed, 10 Sep 2014 17:20:29 +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 96743125; Wed, 10 Sep 2014 17:20:28 +0000 (UTC) Received: by mail-la0-f52.google.com with SMTP id b8so10304396lan.11 for ; Wed, 10 Sep 2014 10:20:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=hN9GgL4EcWiGbRxk3fbhN+PdTPZmJcWTv1O7EOmoVn4=; b=VfITPAj6zAYDCtoLFrXjCOeXazmsdmFXXERfleiPBtVDRMZSlxUxT/Vj8ujZ8e53Je 17c+xtCliFKt/1yyBs5M47V0E+qo28Kfkor7RFL5eHNm5BOKADbTMM0c8aBwauwiRXUq nKJXzafbzMjstyuPCaWxcHCAPHK5F3a21rhC7ROc8tBOGy7UNQtrjYJLaM8GvsxCGbtT 5o+i8xQFWZRf7Sp4hGISXB1HZ9gaDNYKKJ6bawK19gOaBRSasrWBDXuBO5kPjNZgainp XKy+wYMeEwweffmfIpL7ZEJCp1YSRJ/Hzh+GHHU/qE1izqm5fagGkPSFQyG7Hn7RqtSi uNow== X-Received: by 10.152.44.230 with SMTP id h6mr43313249lam.51.1410369626444; Wed, 10 Sep 2014 10:20:26 -0700 (PDT) Received: from kloomba ([95.104.129.68]) by mx.google.com with ESMTPSA id as6sm5828434lbc.17.2014.09.10.10.20.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 10 Sep 2014 10:20:25 -0700 (PDT) Sender: Roman Bogorodskiy Date: Wed, 10 Sep 2014 21:18:29 +0400 From: Roman Bogorodskiy To: Glen Barber Subject: Re: Does anyone use the FreeBSD VM qcow2 images Message-ID: <20140910171827.GA1287@kloomba> References: <20140910135251.GF48287@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="oyUTqETQ0mS9luUI" Content-Disposition: inline In-Reply-To: <20140910135251.GF48287@hub.FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) 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, 10 Sep 2014 17:20:29 -0000 --oyUTqETQ0mS9luUI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Glen Barber wrote: > Hi, >=20 > I'm talking about the images available here: >=20 > http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ >=20 > Since mkimg(1) in head/ and stable/10 supports VMDK and VHD formats, > I would prefer to remove the need to use qemu-img to generate the VM > images. >=20 > This would mean that the qcow2 format would no longer be produced. The qcow2 image format is very popular among Linux KVM/qemu-kvm users, maybe the most popular even. So I think it'd be useful to keep producing these images. Roman Bogorodskiy --oyUTqETQ0mS9luUI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iQEcBAEBAgAGBQJUEIfjAAoJEMltX/4IwiJqrqQH/j+Byc9ykrAbRsk1/GrzkGBN tYUUu6r+981CMsUb1ivyDD/Eq2Yms+0SYNBjsejO3KBmA0rvE35wFMMJSjzGTmr4 Qgg0G9Q/5bilobS6ovDSF5KvZeeMAA400J+Wwh4yFUHMhLTen8A4LKdeDjYwaZKz DDIdHWj6dxknwWbaXBMvBjvgdaDNcixi5egerz/VNGRHkLS6Zw4DNXvqkQ0grHq4 zRKVhoxl16IjHmnzw7dJ1S6Xy4enfS3KXB/A73KqCxtLZBWj4Tfs6OL3jZFXEqs1 vbVmE+aWiXLCsI8i55YTfj2gsLO4lneijSRslbAlR9Prjqs0GqcdXLAf5sy3Oew= =Xvl/ -----END PGP SIGNATURE----- --oyUTqETQ0mS9luUI-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 10 19:49:54 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 319DDDC6; Wed, 10 Sep 2014 19:49:54 +0000 (UTC) Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::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 55D80319; Wed, 10 Sep 2014 19:49:53 +0000 (UTC) Received: by mail-lb0-f169.google.com with SMTP id p9so10499558lbv.14 for ; Wed, 10 Sep 2014 12:49:51 -0700 (PDT) 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=R/RGr7WabmDunYHlg9BYqdJoF2znlUlmWslUshzG7L8=; b=XqSGw1DLCGcRNUcSBISpos/XLSg/CPGilPXh/YkhbIW63ahqARHuoEh14DOVKDoHFx y0TKEKSkQBHFKt2FBVhDvngGmNwzyGwarQ5eoWd8ze1KDkYGecyhSCK5HLSNmFshVXd/ Id9e7yzCgj/HIuYC/L7hKR7DcpZL1P6tb1Z/6TtFdtMpaT/xh2/vG2KrI8vsH+lurxzO 9W3KWTp5YxRJQWIaVVLN4RLC8bhiFiIrXToshpHuAJm3lLRP2V1vr1Z+8SRqfvG/jnci d/Kq6sx3Mof8vZT0ktIBsY/eMpb2xMF0EqtxLzrHRd3SkdWBjQ6OGo/FHRXusEvj7gPz B+eQ== MIME-Version: 1.0 X-Received: by 10.112.149.133 with SMTP id ua5mr41676744lbb.40.1410378591106; Wed, 10 Sep 2014 12:49:51 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.22.72 with HTTP; Wed, 10 Sep 2014 12:49:51 -0700 (PDT) In-Reply-To: <20140910171827.GA1287@kloomba> References: <20140910135251.GF48287@hub.FreeBSD.org> <20140910171827.GA1287@kloomba> Date: Wed, 10 Sep 2014 12:49:51 -0700 X-Google-Sender-Auth: xJ5s_j0hgpnUb8ml3otgcVSi8V0 Message-ID: Subject: Re: Does anyone use the FreeBSD VM qcow2 images From: Craig Rodrigues To: Roman Bogorodskiy Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: Glen Barber , "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, 10 Sep 2014 19:49:54 -0000 On Wed, Sep 10, 2014 at 10:18 AM, Roman Bogorodskiy wrote: > Glen Barber wrote: > > > Hi, > > > > I'm talking about the images available here: > > > > http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ > > > > Since mkimg(1) in head/ and stable/10 supports VMDK and VHD formats, > > I would prefer to remove the need to use qemu-img to generate the VM > > images. > > > > This would mean that the qcow2 format would no longer be produced. > > The qcow2 image format is very popular among Linux KVM/qemu-kvm users, > maybe the most popular even. > > So I think it'd be useful to keep producing these images. > > Hi, That may be true, but I don't think that we as the FreeBSD project need to produce qcow2 images. We also provide raw disk, VMDK , and VDI images. The raw disk and VMDK images can easily be converted to qcow2 via the qemu-img program. For example: http://docs.openstack.org/image-guide/content/ch_converting.html -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Sep 10 20:06:37 2014 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from hub.FreeBSD.org (hub.freebsd.org [IPv6:2001:1900:2254:206c::16:88]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 120B4314; Wed, 10 Sep 2014 20:06:36 +0000 (UTC) Date: Wed, 10 Sep 2014 16:06:33 -0400 From: Glen Barber To: freebsd-virtualization@FreeBSD.org Subject: Re: Does anyone use the FreeBSD VM qcow2 images Message-ID: <20140910200633.GH48287@hub.FreeBSD.org> References: <20140910135251.GF48287@hub.FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="4G+GqPlnVGGS3vR6" Content-Disposition: inline In-Reply-To: <20140910135251.GF48287@hub.FreeBSD.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event User-Agent: Mutt/1.5.23 (2014-03-12) 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, 10 Sep 2014 20:06:37 -0000 --4G+GqPlnVGGS3vR6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 10, 2014 at 09:52:51AM -0400, Glen Barber wrote: > Hi, >=20 > I'm talking about the images available here: >=20 > http://ftp.freebsd.org/pub/FreeBSD/snapshots/VM-IMAGES/ >=20 > [...] >=20 A number of people replied that they do use the qcow2 format, so we'll keep producing them. I was trying to avoid having multiple code paths that do similar things if it wasn't necessary, but that's a non-issue. Thanks. Glen --4G+GqPlnVGGS3vR6 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJUEK9JAAoJELls3eqvi17QYtUQAJUhue5VhY0uUyOzFgKzbc1D r5PHErXZCSXrAE4YVi0926o6r6ovd+0jPDDGm0Onpokbx/ux1fnX01rdmCKEuB0r Q+F00gwa5hnVThgHaaEf0doFbj2zOHM8yWd22Z3WeiA+JN9V0DdbEtkfx0p4IsxN XO8MZwtCD5vNqL0RZPXeCpEOYUDA2dWuNi5jpTr150Ntte0f3NUSAAQmcgjVcLXw Ue5i8MiDRNmZNMmmhvLiz6AE2gY2jFHs/D5Qz9BPV6oqgQGen4ryzQWI6dDpr4tI qoAz5xzzkSksaaYSwM+T3vl216ib4+j4yolKENvAYCs9+r37RyZnT7wdAO/E1q/F +m2G6upYXh6RYvu98X50XrR8CRXOIcPaoyz8p3D+SBUF1noSWcpiLqLqBk7QJrBF pmuK5IK1Owde1xm2RYwjXuBUvpLJGSdjqVBVBHCvLA6VqBanxo01t/30Z/UkWsBK o0YIkjRPg0fu5NrW74PEt4RNI2FYLiG9FWKuE7l9OeYsk2XBCKncF0GKsfHrtg2+ UPfaKwiyFAuo2dGVBJnVpPMrU5cE1zTpeGVBGVjhD0HljAWjBloph3shl7fr6cKB KT3RmP6EkQG3xACqBgh8MhFud5Slc/iAlP1BTjsjK5a7EGBM5Mlsbth4d/B4Czbi B/+LqHyAn56TwuN7h4KC =6eWH -----END PGP SIGNATURE----- --4G+GqPlnVGGS3vR6-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Sep 11 07:35:13 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 8D5BEFB0 for ; Thu, 11 Sep 2014 07:35:13 +0000 (UTC) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Certum Level IV CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 44E42B8B for ; Thu, 11 Sep 2014 07:35:12 +0000 (UTC) Received: from web13j.yandex.ru (web13j.yandex.ru [5.45.198.54]) by forward11.mail.yandex.net (Yandex) with ESMTP id 5ED40E808D1 for ; Thu, 11 Sep 2014 11:35:00 +0400 (MSK) Received: from 127.0.0.1 (localhost [127.0.0.1]) by web13j.yandex.ru (Yandex) with ESMTP id 0AD32D40098; Thu, 11 Sep 2014 11:34:59 +0400 (MSK) Received: from vialan.irkutsk.ru (vialan.irkutsk.ru [195.208.10.123]) by web13j.yandex.ru with HTTP; Thu, 11 Sep 2014 11:34:59 +0400 From: maxim.kos@revich.me To: freebsd-virtualization@freebsd.org Subject: Dynamic memory MIME-Version: 1.0 Message-Id: <1120921410420899@web13j.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 11 Sep 2014 16:34:59 +0900 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r X-Mailman-Approved-At: Thu, 11 Sep 2014 15:05:06 +0000 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, 11 Sep 2014 07:35:13 -0000 Hello. Write using an online translator. As will include support for dynamic memory in FreeBSD 10.0 for Microsoft Hyper-V. If this is not possible, then tell me in which version this feature will be implemented and at least the approximate date of release. In case of knowledge of Russian. Здравствуйте. Пишу с помощью онлайн переводчика. Как включит поддержку динамической памяти в FreeBSD 10.0 для Microsoft Hyper-V. Если это не возможно, то подскажите в какой версии эта возможность будет реализована и хотя бы приблизительная дата выхода релиза. From owner-freebsd-virtualization@FreeBSD.ORG Sat Sep 13 00:40:02 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81493C53 for ; Sat, 13 Sep 2014 00:40:02 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 68905FCA for ; Sat, 13 Sep 2014 00:40:02 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s8D0e25p004855 for ; Sat, 13 Sep 2014 00:40:02 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-virtualization@FreeBSD.org Subject: [Bug 192470] [bhyve] can't boot FreeBSD in bhyve on CURRENT Date: Sat, 13 Sep 2014 00:40:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: lifanov@mail.lifanov.com X-Bugzilla-Status: Issue Resolved X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.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, 13 Sep 2014 00:40:02 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192470 Nikolai Lifanov changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Triage |Issue Resolved Resolution|--- |Works As Intended --- Comment #11 from Nikolai Lifanov --- This issue can be closed. It's not valuable to fix, but anyone with a similar problem can find this bug report. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-virtualization@FreeBSD.ORG Sat Sep 13 21:23:36 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 B55AAE29 for ; Sat, 13 Sep 2014 21:23:36 +0000 (UTC) Received: from fallback7.mail.ru (fallback7.mail.ru [94.100.181.128]) by mx1.freebsd.org (Postfix) with ESMTP id 65437BCC for ; Sat, 13 Sep 2014 21:23:36 +0000 (UTC) Received: from f350.i.mail.ru (f350.i.mail.ru [217.69.140.246]) by fallback7.mail.ru (mPOP.Fallback_MX) with ESMTP id 9566E112F15F1 for ; Sun, 14 Sep 2014 01:23:33 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=inbox.ru; s=mail; h=Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=laHdR7CIGwIW3ouKwjSHISp/q5vhUfniDBgmf91I1Z0=; b=cU7Xr5w51Mx+767davHkiHywPQ7/lrKrdcpkOpR18+gopy9TCXVH7ZPQNmeKTudQCQ3YDOVouNLrKhdmHCYMNFzzhjSYcMpj7UjxiAWfxFkkiTv3cNfYhFwjETqxPvRnWDLo45yM/OYlTFM/WbYFhHrehCD6GMdaYanM62e7LK4=; Received: from [109.225.7.184] (ident=mail) by f350.i.mail.ru with local (envelope-from ) id 1XSumx-0005ws-HP for freebsd-virtualization@freebsd.org; Sun, 14 Sep 2014 01:23:23 +0400 Received: from [109.225.7.184] by e.mail.ru with HTTP; Sun, 14 Sep 2014 01:23:23 +0400 From: =?UTF-8?B?RGVuaXMgTWVuc2hpa292?= To: freebsd-virtualization@freebsd.org Subject: =?UTF-8?B?bm1kbS5j?= Mime-Version: 1.0 X-Mailer: Mail.Ru Mailer 1.0 X-Originating-IP: [109.225.7.184] Date: Sun, 14 Sep 2014 01:23:23 +0400 Reply-To: =?UTF-8?B?RGVuaXMgTWVuc2hpa292?= X-Priority: 3 (Normal) Message-ID: <1410643403.25508279@f350.i.mail.ru> X-Cloud-Ids: X-Mras: Ok X-Spam: undefined Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 21:23:36 -0000 CgpodHRwczovL2J1Z3MuZnJlZWJzZC5vcmcvYnVnemlsbGEvc2hvd19idWcuY2dpP2lkPTE5MjI4 MQoKSW4gd2hhdCBicmFuY2ggSSBjYW4gdXNlIHRoZSBmdW5jdGlvbmFsaXR5IG9mIHRoZSBtb2Rp ZmllZCBubWRtLmMgPyBUaGFuayB5b3UuCgotLSAKRGVuaXMgTWVuc2hpa292 From owner-freebsd-virtualization@FreeBSD.ORG Sat Sep 13 21:27:52 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 CFB71E86 for ; Sat, 13 Sep 2014 21:27:52 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 92957BDF for ; Sat, 13 Sep 2014 21:27:52 +0000 (UTC) Received: from dommail.onthenet.com.au (dommail.OntheNet.com.au [203.13.70.57]) by alto.onthenet.com.au (Postfix) with ESMTPS id 1886C123CF; Sun, 14 Sep 2014 07:27:51 +1000 (EST) Received: from Peters-MacBook-Pro.local (c-69-181-164-196.hsd1.ca.comcast.net [69.181.164.196]) by dommail.onthenet.com.au (MOS 4.4.4-GA) with ESMTP id BYI54872 (AUTH peterg@ptree32.com.au); Sun, 14 Sep 2014 07:27:50 +1000 Message-ID: <5414B6D9.8060109@freebsd.org> Date: Sat, 13 Sep 2014 14:27:53 -0700 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Denis Menshikov Subject: Re: nmdm.c References: <1410643403.25508279@f350.i.mail.ru> In-Reply-To: <1410643403.25508279@f350.i.mail.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2014 21:27:52 -0000 Hi Denis, > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192281 > > In what branch I can use the functionality of the modified nmdm.c ? It's in CURRENT and should be in 10-STABLE very shortly. later, Peter.