From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 03:04: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E48267E for ; Sun, 2 Feb 2014 03:04:25 +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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 271BF15C5 for ; Sun, 2 Feb 2014 03:04:25 +0000 (UTC) Received: by mail-pa0-f42.google.com with SMTP id kl14so5868767pab.15 for ; Sat, 01 Feb 2014 19:04:23 -0800 (PST) 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=lgdQbuQJWG47jVGc6CPqwmqNo3ydSym2Y7uV9/Jcr+4=; b=klSnxONhWStGXOeIALiWXrTrzUBPUn9dbxiSo2jkcRE72WmQoT5qFFMM2ukK7xJdfA OZiKJbSn7h0yFW1rQJsieNXsPcm8y8LlgxyhVLUc9HRF6PI+yl4tez058Ss1mQ6UzK9W W4GlWl+bjkV64d8+N85cgok7NUVVfV3Mwbtd4ORfS5d9K1upPH3YIrDLSBqXmra48v/I sQY0eMf7XfHdeA3MA9xgInTMZ+AX5IX7Dv4rxSlqDvo/2hrcGGhJnrjEuFiUGoSlgRxw xwaqnPnwAHWGbNOEYTxmUMgeYGuL0mIsL5+juQUVa7wnZN7L94cBq5C+7isTLnRAH48O jfsg== MIME-Version: 1.0 X-Received: by 10.66.221.199 with SMTP id qg7mr29765109pac.88.1391310263178; Sat, 01 Feb 2014 19:04:23 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 1 Feb 2014 19:04:23 -0800 (PST) Date: Sat, 1 Feb 2014 22:04:23 -0500 Message-ID: Subject: who should I report this to? From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" , qemu-devel@nongnu.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 03:04:25 -0000 Under kvm (ubuntu 12.04.03 LTS) when logged in via VNC and installing 10-RELEASE the installer just boots you during the disk initialization phase. Who should this be reported to? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 03:10:37 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 CE5A0760 for ; Sun, 2 Feb 2014 03:10:37 +0000 (UTC) Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A80451607 for ; Sun, 2 Feb 2014 03:10:37 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id w10so5692165pde.20 for ; Sat, 01 Feb 2014 19:10:37 -0800 (PST) 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=0QG7Q7/S9Zv8uqxFcHRA1WDoJpXBlYhV/UMshUVWicI=; b=Dt9hhLNJrlzMELr9R8rNcH7MWZgt75WuzneWku5AJN29tYJyVviCHg2xIDL8NcsZri xxSkcwt7gP9AKEuK5ymAbF2WwGe62DHPEJJERCtogQ9j+kZu9q86g/etoseumabmNaEw NEWgur0gFzaZIXM/kMpYj1CmpScpCiN0VgxqoJCXSVOUQVb3yzDigTzrkFzXjei0uY2R rBkQ5NJbg0DOyC8Y8LnzTTgashDxeKIo1gFQHFJx/PoH5uhlGKvx+vpSD3wmdpB0or1q +afuyPnrr0H1tcVMFZupvmX0VGkcJNKGtkO+2TOOvN/3x9jOBBAu1xEf8I6/i66xJQud KxXw== MIME-Version: 1.0 X-Received: by 10.68.238.201 with SMTP id vm9mr29213432pbc.18.1391310637385; Sat, 01 Feb 2014 19:10:37 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 1 Feb 2014 19:10:37 -0800 (PST) Date: Sat, 1 Feb 2014 22:10:37 -0500 Message-ID: Subject: some interesting observations on the relative performance of kvm vs. bhyve From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 03:10:37 -0000 I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve seems to be atleast 3 or 4 times faster with disk I/O then kvm using the most stripped down command lines I can come up with. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 03:16:46 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 DD9F891B for ; Sun, 2 Feb 2014 03:16:46 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 9DFDB168B for ; Sun, 2 Feb 2014 03:16:46 +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 7BA4712384; Sun, 2 Feb 2014 13:16:44 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRO16583 (AUTH peterg@ptree32.com.au); Sun, 2 Feb 2014 13:16:43 +1000 Message-ID: <52EDB899.9060703@freebsd.org> Date: Sat, 01 Feb 2014 19:16:41 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: some interesting observations on the relative performance of kvm vs. 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.17 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, 02 Feb 2014 03:16:46 -0000 > I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve > seems to be atleast 3 or 4 times faster with disk I/O then kvm using the > most stripped down command lines I can come up with. I'm guessing that the default cache mode for qemu in that release is "none". You may want to switch it to "writeback", which is what bhyve does by default (it can be changed with AHCI, see bhyve(8)). Lots of info on the web about Qemu block i/o cache modes e.g. http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaat%2Fliaatbpkvmguestcache.htm later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 03:19:19 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2B6CC977; Sun, 2 Feb 2014 03:19:19 +0000 (UTC) Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F048A1695; Sun, 2 Feb 2014 03:19:18 +0000 (UTC) Received: by mail-pb0-f45.google.com with SMTP id un15so5830063pbc.18 for ; Sat, 01 Feb 2014 19:19:18 -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=QBPZdE21ietviO6S3svJIDH3qt0CBey5q+qS5943vPo=; b=EMkoY/Gs7SdeWGgHJegD4xT+UnI7SY0D2jr8h9r5hr4uzCf5A74vXsoZnZzejVZzRs ROXy+YEDWYuPw7yHXA3+EkgHN8Qgl/9Whbex2OAzFGBhofu4lKJIBPyaulvNwsjGSLB1 Ss9ikmNztMSqzH5P/ko62aYRggDdeaPwGv4BwocGV7JwD2ue5ZxaBkDc6VnTTYYtwb08 5wlbyYIRNhmuMyVTa00d/euLQEEUYSdpbKUXhi5jkqYYFLNWP6nNAFSgnw6TXDT4/Rjh bBlABKmJdBbgl+KXFBZCW2xzNR3Uru5IxPCWTQcBS3RqAWPeNgP8DBIMg9PSXOT5P0sc zxUg== MIME-Version: 1.0 X-Received: by 10.66.102.39 with SMTP id fl7mr29246139pab.43.1391311158501; Sat, 01 Feb 2014 19:19:18 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 1 Feb 2014 19:19:18 -0800 (PST) In-Reply-To: <52EDB899.9060703@freebsd.org> References: <52EDB899.9060703@freebsd.org> Date: Sat, 1 Feb 2014 22:19:18 -0500 Message-ID: Subject: Re: some interesting observations on the relative performance of kvm vs. bhyve From: Aryeh Friedman To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 03:19:19 -0000 On Sat, Feb 1, 2014 at 10:16 PM, Peter Grehan wrote: > > I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve > >> seems to be atleast 3 or 4 times faster with disk I/O then kvm using the >> most stripped down command lines I can come up with. >> > > I'm guessing that the default cache mode for qemu in that release is > "none". You may want to switch it to "writeback", which is what bhyve does > by default (it can be changed with AHCI, see bhyve(8)). > Is this also true of emulators/qemu (without kqemu)? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 04:13:16 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 647BDF0; Sun, 2 Feb 2014 04:13:16 +0000 (UTC) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2EB4C1990; Sun, 2 Feb 2014 04:13:16 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id v10so5696653pde.14 for ; Sat, 01 Feb 2014 20:13:15 -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=CeT5dBzvE4q7Zb67gwFq0AtNbp1toSKswJi9DL4yDm0=; b=wRpYA+l5Mo0/hugpvXqBJKx0Bt4aWjCJfq3dI33klCyAo7SPGi+lTn08xstXlcOq8K Rigyd3r1juSbmBT7tuLdRqH6UMYjVJZnpfw13tz2zkCSn8JpA6BnigSGp+bh5+vCWgie 4EwlH826Ei6O4AilDmSIRLrfqWyHaWuSkVDZC+g79DqgXRzO7q4fa9Fb60EizOE8PPOt tPzpoNeFUq3okka29rJCQQy8M5n68yBAanOyJUYxQyWyXTlse1vmlhiYx5XjMgKUXDLD uitKIXTeT5VdUJ7OzDNV2ijseVOCiCzv3ScN1zIvo84C3GIXBbHbDmueioiRIg15XqpS I9GQ== MIME-Version: 1.0 X-Received: by 10.66.145.166 with SMTP id sv6mr30104236pab.31.1391314395336; Sat, 01 Feb 2014 20:13:15 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 1 Feb 2014 20:13:15 -0800 (PST) In-Reply-To: <52EDB899.9060703@freebsd.org> References: <52EDB899.9060703@freebsd.org> Date: Sat, 1 Feb 2014 23:13:15 -0500 Message-ID: Subject: Re: some interesting observations on the relative performance of kvm vs. bhyve From: Aryeh Friedman To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 04:13:16 -0000 On Sat, Feb 1, 2014 at 10:16 PM, Peter Grehan wrote: > > I have 1 host that dual boots FreeBSD and Ubuntu 12.04.3 LTS and bhtyve > >> seems to be atleast 3 or 4 times faster with disk I/O then kvm using the >> most stripped down command lines I can come up with. >> > > I'm guessing that the default cache mode for qemu in that release is > "none". You may want to switch it to "writeback", which is what bhyve does > by default (it can be changed with AHCI, see bhyve(8)). > Does this bring up the same power failure scenario issues mentioned in the link you provided? It seems like the only way to get reasonable performance is to be essentially unsafe in guest writes to the host disk? A question does the ability of FreeBSD to be able to better handle power failure in general better then linux (it seems like every time there is a unscheduled reboot on linux it messes up)? This seems to be at odds with my personal observations of bhyve via petitecloud which I routinely very abruptly start/stop (petitecloud's "stop" is nothing more then killing the hyperv and any cleanup needed) and except for the occasional need for a fsck have not had an issue. But it does not seem to be at odds with OpenStack's experience http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_nova-disaster-recovery-process > Lots of info on the web about Qemu block i/o cache modes e.g. > > > http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaat% > 2Fliaatbpkvmguestcache.htm > > later, > > Peter. > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 05:25:00 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42491706 for ; Sun, 2 Feb 2014 05:25:00 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 197DB1DE8 for ; Sun, 2 Feb 2014 05:25:00 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id y13so5766240pdi.9 for ; Sat, 01 Feb 2014 21:24:59 -0800 (PST) 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=Uy51HhcUvNXPbw6KcNPtRr8zXtxAeo11uDOqMLtjx4Q=; b=ZHaXVu5AuroYpzVSBF+v9oDntG7oF+pRsp2ADBN3SJeM69qGamGOiO30IXKv5bHm5y knvfXvWrSzS8Nzeahd6caon97m7UDbAre5TgAy8aBkw5dkSvky6v3FUYB601ymNIMKrd HcRooY5i2ABy9/vGug3BmyHBi6sfRBbJ97dcZWYS34N7UbhHSu4VtSq1CexlbzdXZrbp aZ86y7r9+R15A3BfGPmu6g37mnXoPmSrMitYL9J4ZcAluZVmI+iuflwS3V+qMUJKHndn Ufy7f5SUCVvxuFYmn4j/HNraTXGI3dF1SBsLOHqjZOccj1w0/3T5Hkxs5tO/S/APDDfW g8XA== MIME-Version: 1.0 X-Received: by 10.66.192.74 with SMTP id he10mr30076027pac.126.1391318699678; Sat, 01 Feb 2014 21:24:59 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 1 Feb 2014 21:24:59 -0800 (PST) Date: Sun, 2 Feb 2014 00:24:59 -0500 Message-ID: Subject: RFC: hyperv disk i/o performance vs. data integrity From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 05:25:00 -0000 Disclaimer: This is more of a thinking out loud then it is an definative set of suggestions on the matter. Also a cleaned up version of this will likely become PetiteCloud's white paper on storage and disaster recovery. I do not make any promises to when any of it might be implemented and/or if it will be implemented in the manner described here. Looking at the link Peter provided in an other thread: http://pic.dhe.ibm.com/infocenter/lnxinfo/v3r0m0/index.jsp?topic=%2Fliaat%2Fliaatbpkvmguestcache.htm I at first did my standard "OpenStack got it wrong and PetiteCloud got it right" reaction to it. I then read deeper and saw that every last modethat offered reasonable performance also was considered to be untrustworthy especially in the case of a power failure. The one exception seems to be if your going straight to physical disk then if you can use "none" and get reasonable performance without the issues associated with abrupt disconnects like power failure or the sudden death of the hyperv process. So it seems we are stuck with sucky disk performance. That is until we make an other interesting observation that TCP offers the guarantee of never been more then a few packets out of sync and being 100% reliable if the network is functioning properly. At first it might not seem that a network would ever be faster then disk. We forget though that we are talking virtualization and not real networks here so there is no reason why we can not form networks between instances on the same host and no matter how inefficent the packet drivers are they are surely faster then any disk if we only consider transport on the host's motherboard and not between hosts. Craig Rodrigues and the FreeNAS team have done a fantastic job already (I have not personally tried FreeNAS yet but I have heard nothing but good things about it) and making it so it can run on a bhyve instance. Given that the following local machine only archicture might make sense to act as a solution to the performance vs. safety problem in the hyperv's: Host +------ Storage (both local and remote) | +------ FreeNAS instance (as little RAM and VCPU's as possible) | +------ Production instances The FreeNAS node would distribute it's storage via iSCSI or the equiv. Setting the rule that all "primary" iSCSI sessions/devices be local (in case vs. on rack or somewhere else in the data center) would eliminate the power failure nightmare that OpenStack seems to have http://docs.openstack.org/admin-guide-cloud/content/ch_introduction-to-openstack-compute.html#section_nova-disaster-recovery-processwithout killing performance (in many cases increasing it). The reason is it is not an issue since we isolated all the remote disk sessions to one instance we have used the "blast wall" capability of virtualization. Namely if FreeNAS blows up we just swap in an other FreeNAS instance with the same devices attached and the using normal OS (host and guest) facilities it should be trivial to reconnect the device to the guest (you will just have to give up the idea of a session that outlives the devices power cycle though) and do basic recovery. Now that we have offloaded the storage from the hyperv all the other aspects of backup/recovery can be done using normal OS facilities instead of the cloud platform. (Real) network storage will need to use a completely different model likely though if you allow it to be passed to the guest OS. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 06:19:16 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 65107F2D for ; Sun, 2 Feb 2014 06:19:16 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id 2226710CD for ; Sun, 2 Feb 2014 06:19:15 +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 3350012268; Sun, 2 Feb 2014 16:19:08 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local (c-67-161-27-37.hsd1.ca.comcast.net [67.161.27.37]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRO19515 (AUTH peterg@ptree32.com.au); Sun, 2 Feb 2014 16:19:06 +1000 Message-ID: <52EDE352.9050805@freebsd.org> Date: Sat, 01 Feb 2014 22:18:58 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: some interesting observations on the relative performance of kvm vs. bhyve References: <52EDB899.9060703@freebsd.org> 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.17 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, 02 Feb 2014 06:19:16 -0000 Hi Aryeh, > Does this bring up the same power failure scenario issues mentioned in > the link you provided? It seems like the only way to get reasonable > performance is to be essentially unsafe in guest writes to the host > disk? Use ZFS and a ZIL to mitigate this. Or UFS with journalling. > A question does the ability of FreeBSD to be able to better > handle power failure in general better then linux (it seems like every > time there is a unscheduled reboot on linux it messes up)? It's not the o/s but the behavior of the filesystem. > This seems > to be at odds with my personal observations of bhyve via petitecloud > which I routinely very abruptly start/stop (petitecloud's "stop" is > nothing more then killing the hyperv and any cleanup needed) and except > for the occasional need for a fsck have not had an issue. It's not the VM stop/crash that's the problem, but the host. Once a write has been marked as complete by the VM, the guest assumes it has been committed to stable storage and can assume e.g. that a database transaction is complete. If the write is being held in the host's buffer cache and power is lost, the write never makes it to stable storage, resulting in data loss/corruption for the guest. This is different than the VM crashing, since the writes in the host's buffer cache aren't lost in that case. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 20:20:22 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB9FD4B1 for ; Sun, 2 Feb 2014 20:20:22 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 82C081A3D for ; Sun, 2 Feb 2014 20:20:22 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id y13so6121080pdi.37 for ; Sun, 02 Feb 2014 12:20:22 -0800 (PST) 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=bjVcQl0whl5wjd1VQ84f98ksd7M4MAqSdS6rjYZsQxs=; b=h+m+ijpjuawtKXJ5CeShIPtiEPHw7Wi0gmYlw3ZQbmt7b/UkRH92VbMfvckGpZDMV4 LKfLcbIt/1A0gCl0wRqNTBG4jRRfOOGyiYbQq4seb4t8a3dCykN1i3HXB78CMaFQQoNk kMBNuuyyx9jW4k1QHnGnow9kA4Hby3nNE2wMM3DTl403ySXvLT9oYaYdijHPLzZRUxkR JzAuJ4yuA+9HYRcQnTRsn1UPzDVUv9kcQFx6l1ohuaONw69/FGZoIAndfX9JLh7we2Mx vT4z3xUzwfbS66+D+cLEQjeF3KymXTyYfetaCGH29RKjaUHuZVpwuJz69cL4bWQKWr6V 0SVA== MIME-Version: 1.0 X-Received: by 10.68.240.36 with SMTP id vx4mr3573607pbc.140.1391372422229; Sun, 02 Feb 2014 12:20:22 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 2 Feb 2014 12:20:22 -0800 (PST) Date: Sun, 2 Feb 2014 15:20:22 -0500 Message-ID: Subject: looking for a quick and dirty remote vnc solution From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 20:20:22 -0000 Use case: 1. I am out of the office (the entire office except for one petitelcoud instance is behind a firewall) without any ability to poke holes (something petitecloud will handle soon) 2. The way to install a non-bhyve hyperv instance (kvm in this case) 3. I am installing an QEMU instance (console via VNC) on one of the hosts (behind the FW) 4. Is there any easy way to connect to the QEMU on the FW'ed host P.S. Since it is pretty obvious that all my work is leading to Linux as a host for PetiteCloud I will be releasing a very rough release (hand build with warnings [but no outright errors]) for testing in an hour or so (over the next few days I will work on making it end user usable). This way we do not violate our no preannounce policy (the reason for this policy is we have found in our consulting work that the minute you preannounce something the client will insist on having it even if you decide it is a bad idea before final release). -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 2 22:22: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C6C432A7 for ; Sun, 2 Feb 2014 22:22:12 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D2FA15A4 for ; Sun, 2 Feb 2014 22:22:12 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so6223315pdj.1 for ; Sun, 02 Feb 2014 14:22:11 -0800 (PST) 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=Oh/KgW8TEu2MTIzo2aYg72VSydGDRalIhgl27RVj4Y0=; b=Zy8H4nIpsTMVv+J/2b5phfOmLMSSpLYa9/dGbpHzuywAx+xG/TdcFaT319lfWgUqKn RzE/5sKqHmCupbe1db3z4Xe3HaEw02ruM6uwDjUObxk4cXhKsudXMclPfHRV6COSGYhz nzBNW+/8F7KfaOdfnkez+fqORfC+9tfRuAk75SMiDnScrUilDTvWGSHsUE4eMlj48nRw Q9FemYn7tTThTr5VuN18/+xcUSm9Wv5gko+rRIIoBexFqRs2DI7gQFljx7Sy+HfckR4x gQzeCgw0F73CdDPbI3w5n9N1o1QTR3E7qGgWtVx0mJ1AVEuHsjhpLW2Eq8ZkoKZ9CDhN SwPA== MIME-Version: 1.0 X-Received: by 10.68.114.163 with SMTP id jh3mr33038269pbb.99.1391379731740; Sun, 02 Feb 2014 14:22:11 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 2 Feb 2014 14:22:11 -0800 (PST) Date: Sun, 2 Feb 2014 17:22:11 -0500 Message-ID: Subject: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 02 Feb 2014 22:22:12 -0000 Even though FreeBSD will always be my preferred OS for both personal and professional use it is sad to say in today's world if you do not support Linux and your run on Unix-like OS's then to everyone out side [insert favorite OS here] you don't exist. This is even more so for a effort like PetiteCloud that needs the widest possible user base to grow (the user base is what will attract apps which will attract more users and so forth). For the above reasons it is obvious that PetiteCloud *MUST* support linux as host or we simply are irrelevant to mainstream cloud computing users. It is likely less painful to do it now then later when we have more devices and drivers and such to have to sort out. Therefore I have posted a developer's snapshot of 0.2.4 with Linux hosting on the normal download link (don't worry the FreeBSD build still works fine). Take a look at the developers section of the site for details of how to install and test it. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 3 01:15:18 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 C619E2CA for ; Mon, 3 Feb 2014 01:15:18 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E9361907 for ; Mon, 3 Feb 2014 01:15:18 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so6319236pdj.1 for ; Sun, 02 Feb 2014 17:15:18 -0800 (PST) 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=o4PUyHKBYkphsUdtZF6hw7L4NtUDC7Zn+wiQ3GysTHw=; b=XHgULstdnrB4E9YJz9Rg+ZOTpEqPyPRwhXHT4tHy8ahlgVyLzX8R4SCHc1LomF5wah MEzXGNHVqrMZdE8rI4d6+3H12EcotM4QVYQX7aJOREEizBQQh1Y6NQ+tuzV09cq6TsIh /utuo4trXI+gZ8j4GLIUice5CKNcO9ItH2xr3JDwa6MY2OtSVSzA6eGHMtMNyGXR0gdT ZoGmDVzm49THvKpqYl2cT4xJ/JfrbqH0kDXLKmnICbJtmX5fWGpbbFSvpaAUBB3iFxd8 k9qLjED8BpbBlY+bwVw85vSBzgdGN7qkQ69pfOZ9+qO1wgKIYIfbr+gJqWrsft/I6mBM y6OA== MIME-Version: 1.0 X-Received: by 10.66.16.131 with SMTP id g3mr4398849pad.138.1391390118262; Sun, 02 Feb 2014 17:15:18 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sun, 2 Feb 2014 17:15:18 -0800 (PST) Date: Sun, 2 Feb 2014 20:15:18 -0500 Message-ID: Subject: OT: How best to market FreeBSD's innate strengths as a cloud host? From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Feb 2014 01:15:18 -0000 After dealing with linux for the last few days the difference between it and FreeBSD are glaring when it comes to suitability as a cloud the host OS of a cloud node/host. Most of these strengths come from it's fundimentally sound design and design process. Namely it is rock solid because it was designed to be rock solid (linux can not say this). This rock solidiness is what is needed for a cloud host because it is often the most likely point of failure in a cloud environment. How do we best market this? This might be just the route that FreeBSD as a whole has been looking for to get onto the radar of Corporate America upper management. One way I see to start is turning freebsd-openstack.orginto the portal we promised when we got it. Right now the only content I see for it is the series of tutorials I mentioned. The only other thing I can think of is a "logo gallery" of companies that use FreeBSD for cloud computing like services (internally or externally) and/or provide them. For example I think NetApp should be on the list (FNWE would be willing but we don't think we are big enough yet to make any difference). Any other content ideas? Also it would be nice to know who all is using FreeBSD for cloud computing so we can see how to populate logo gallery (looking at the logs for petitecloud.org I see some *VERY* big names but am wondering why some of them have not stepped forward) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 3 11:06:56 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 80E6A1E1 for ; Mon, 3 Feb 2014 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6BE5F1A63 for ; Mon, 3 Feb 2014 11:06:56 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s13B6use022825 for ; Mon, 3 Feb 2014 11:06:56 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s13B6tCJ022822 for freebsd-virtualization@FreeBSD.org; Mon, 3 Feb 2014 11:06:55 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Feb 2014 11:06:55 GMT Message-Id: <201402031106.s13B6tCJ022822@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-virtualization@FreeBSD.org Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Feb 2014 11:06:56 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with VIMAGE and PF o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + VIMAGE wh o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning on td 0x o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + VIMAGE o kern/148155 virtualization[vimage] [pf] Kernel panic with PF + VIMAGE kernel opt a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail 7 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 3 17:46:32 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 99AFBD3; Mon, 3 Feb 2014 17:46:32 +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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 69D5210C5; Mon, 3 Feb 2014 17:46:32 +0000 (UTC) Received: by mail-pa0-f49.google.com with SMTP id hz1so7352787pad.36 for ; Mon, 03 Feb 2014 09:46:31 -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=q5LBpaTlK2dJRNO/GTF78ganwdtRFO+rUfg/FmQs5TY=; b=iytgbLajXV9Dw1MNijQopmwPBw4wJXXoe8HFMPwT9amCzFwQBszRJ+EwdRZrN3Dyky qg3rC9R0kPouCtuVyzNKuyLWL/qe83a4J6QhLxV91YMzQP0279yqgni69ValhYYJg71N Yz67+O6M+fyl4c3UeCTmtjua96pk6SR0Y9V645Tu2GvokA0/+Wc+UT3bFBZe8uS54Owz PKOc38AprzAghFQRTObUZJ58BeyO9bJUWyN52odtINAMdTPSR0MyANwiXGmKTPTuCle3 8ADQufyBpzJFNQRAz1WIRlZnu7i1Rhi9pDRxQ6/cSoVVjpGyefWCXs0rAJSq3CKlW9ML vAdA== MIME-Version: 1.0 X-Received: by 10.68.87.98 with SMTP id w2mr38553711pbz.2.1391449591807; Mon, 03 Feb 2014 09:46:31 -0800 (PST) Received: by 10.68.155.38 with HTTP; Mon, 3 Feb 2014 09:46:31 -0800 (PST) In-Reply-To: <201402031106.s13B6tCJ022822@freefall.freebsd.org> References: <201402031106.s13B6tCJ022822@freefall.freebsd.org> Date: Mon, 3 Feb 2014 12:46:31 -0500 Message-ID: Subject: Re: Current problem reports assigned to freebsd-virtualization@FreeBSD.org From: Aryeh Friedman To: FreeBSD bugmaster Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Feb 2014 17:46:32 -0000 By now we have made enough progress in runninng FB as a VM on FB why are we still putting out devlopement instances for various providers. Wouldn't it be easier to just put the raw disk images up (as far I know these will work with all frontend/hyperv [vmrun, petitecloud, raw hyperv calls, etc.] except for openstack [which is not currently supported on FB]) On Mon, Feb 3, 2014 at 6:06 AM, FreeBSD bugmaster wrote: > Note: to view an individual PR, use: > http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). > > The following is a listing of current problems submitted by FreeBSD users. > These represent problem reports covering all versions including > experimental development code and obsolete releases. > > > S Tracker Resp. Description > > -------------------------------------------------------------------------------- > o kern/165252 virtualization[vimage] [pf] [panic] kernel panics with > VIMAGE and PF > o kern/161094 virtualization[vimage] [pf] [panic] kernel panic with pf + > VIMAGE wh > o kern/160541 virtualization[vimage][pf][patch] panic: userret: Returning > on td 0x > o kern/160496 virtualization[vimage] [pf] [patch] kernel panic with pf + > VIMAGE > o kern/148155 virtualization[vimage] [pf] Kernel panic with PF + VIMAGE > kernel opt > a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash > s kern/143808 virtualization[pf] pf does not work inside jail > > 7 problems total. > > _______________________________________________ > 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" > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 3 18:32:26 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 98BADF4D for ; Mon, 3 Feb 2014 18:32:26 +0000 (UTC) Received: from mail.ijs.si (mail.ijs.si [IPv6:2001:1470:ff80::25]) by mx1.freebsd.org (Postfix) with ESMTP id 48D94159C for ; Mon, 3 Feb 2014 18:32:26 +0000 (UTC) Received: from amavis-proxy-ori.ijs.si (localhost [IPv6:::1]) by mail.ijs.si (Postfix) with ESMTP id 3fHyLw0D24zGN53 for ; Mon, 3 Feb 2014 19:32:24 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ijs.si; h= message-id:content-transfer-encoding:content-type:content-type :mime-version:in-reply-to:references:user-agent:date:date :subject:subject:organization:from:from:received:received :received; s=jakla2; t=1391452342; x=1394044343; bh=Kkklq+SArxnQ oI4ZBItV6gI2qyqiazqCSSxy++/HPYc=; b=gaxyNzYvTE60UgE+JUwRjAwxVqh3 KWOzXFIBGMW9BB90JDGj9k30xXHgHaeCwvLFWlzTbY1d8o8kWfjR0ONFh/62YgYE aTYqSDG7N5lUIahUVfxUwhKjE35F6n8L1WCxj7iqzCLvPwGYJ0Ma3gIs7kt+Rtrq nVRNhPs9MuYH1e4= X-Virus-Scanned: amavisd-new at ijs.si Received: from mail.ijs.si ([IPv6:::1]) by amavis-proxy-ori.ijs.si (mail.ijs.si [IPv6:::1]) (amavisd-new, port 10012) with ESMTP id tDsqVJF9rT0w for ; Mon, 3 Feb 2014 19:32:22 +0100 (CET) Received: from mildred.ijs.si (mailbox.ijs.si [IPv6:2001:1470:ff80::143:1]) by mail.ijs.si (Postfix) with ESMTP for ; Mon, 3 Feb 2014 19:32:22 +0100 (CET) Received: from neli.ijs.si (neli.ijs.si [IPv6:2001:1470:ff80:88:21c:c0ff:feb1:8c91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mildred.ijs.si (Postfix) with ESMTPSA id 95B89584 for ; Mon, 3 Feb 2014 19:32:22 +0100 (CET) From: Mark Martinec Organization: J. Stefan Institute To: freebsd-virtualization@freebsd.org Subject: Re: Current problem reports assigned to freebsd-virtualization@FreeBSD.org Date: Mon, 3 Feb 2014 19:32:21 +0100 User-Agent: KMail/1.13.7 (FreeBSD/9.2-STABLE; KDE/4.10.5; amd64; ; ) References: <201402031106.s13B6tCJ022822@freefall.freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201402031932.21874.Mark.Martinec+freebsd@ijs.si> X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 03 Feb 2014 18:32:26 -0000 Aryeh Friedman wrote: > By now we have made enough progress in runninng FB as a VM on FB ... Please avoid shortening FreeBSD as FB. It is confusing for a casual reader as FB is commonly associated with Facebook, and it is unfriendly to search engines. If FreeBSD is too much to type, use FBSD. Mark From owner-freebsd-virtualization@FreeBSD.ORG Mon Feb 3 19:02:01 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 9EF8DE11 for ; Mon, 3 Feb 2014 19:02:01 +0000 (UTC) Received: from mail.grem.de (outcast.grem.de [213.239.217.27]) by mx1.freebsd.org (Postfix) with SMTP id E145B18FB for ; Mon, 3 Feb 2014 19:02:00 +0000 (UTC) Received: (qmail 51854 invoked by uid 89); 3 Feb 2014 19:01:52 -0000 Received: from unknown (HELO bsd64.grem.de) (mg@grem.de@194.97.158.66) by mail.grem.de with ESMTPA; 3 Feb 2014 19:01:52 -0000 Date: Mon, 3 Feb 2014 20:01:52 +0100 From: Michael Gmelin To: Aryeh Friedman Subject: Re: Current problem reports assigned to freebsd-virtualization@FreeBSD.org Message-ID: <20140203200152.6f8ab832@bsd64.grem.de> In-Reply-To: <201402031932.21874.Mark.Martinec+freebsd@ijs.si> References: <201402031106.s13B6tCJ022822@freefall.freebsd.org> <201402031932.21874.Mark.Martinec+freebsd@ijs.si> X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.18; amd64-portbld-freebsd9.1) 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.17 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, 03 Feb 2014 19:02:01 -0000 On Mon, 3 Feb 2014 19:32:21 +0100 Mark Martinec wrote: > Aryeh Friedman wrote: > > By now we have made enough progress in runninng FB as a VM on FB ... > > Please avoid shortening FreeBSD as FB. It is confusing for a casual > reader as FB is commonly associated with Facebook, and it is > unfriendly to search engines. If FreeBSD is too much to type, use > FBSD. > I restrained myself from asking the same, but I agree 100% with Mark, FB == Facebook, FreeBSD == FreeBSD. Also, please don't top post (I know it's hard these days, especially with gmail, but it's FreeBSD etiquette for a reason, see http://www.freebsd.org/doc/en/articles/mailing-list-faq/etiquette.html ). Thank you. -- Michael Gmelin From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 4 03:03:23 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 4CA2B12F for ; Tue, 4 Feb 2014 03:03:23 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F3CB11851 for ; Tue, 4 Feb 2014 03:03:22 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WAWIC-0002wg-Vn for freebsd-virtualization@freebsd.org; Tue, 04 Feb 2014 04:03:20 +0100 Received: from tempe0.bbox.io ([24.249.180.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Feb 2014 04:03:20 +0100 Received: from kevin.bowling by tempe0.bbox.io with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 04 Feb 2014 04:03:20 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-virtualization@freebsd.org From: Kevin Bowling Subject: Re: using -virtualization@ as the preferred support channel for petitecloud? Date: Mon, 03 Feb 2014 20:03:09 -0700 Lines: 16 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: tempe0.bbox.io User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 In-Reply-To: X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 04 Feb 2014 03:03:23 -0000 On 1/29/2014 8:07 PM, Aryeh Friedman wrote: > We are in the process of updating PetiteCloud.org in preparation for our > upcoming release of 0.2.3 (which will include support for Linux as a guest, > though still with FreeBSD as the only host and bhyve the only hypervisor > that currently runs in hardware virtualization mode). We're wondering if > it is ok if we update the resources page to say that all support questions > should go to -virtualization@? > > We've already been doing this unofficially for quite some time, and > PetiteCloud does not currently have a large enough user base to justify a > mailing list of its own. If/when questions about PetiteCloud become too > high volume here, we will then, of course, start our own mailing list. > I would greatly appreciate anything specific to your implementation on it's own list/forum/whatever. From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 4 03:24:04 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 0668A7BC for ; Tue, 4 Feb 2014 03:24:04 +0000 (UTC) Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CED301A88 for ; Tue, 4 Feb 2014 03:24:03 +0000 (UTC) Received: by mail-pd0-f170.google.com with SMTP id p10so7695616pdj.29 for ; Mon, 03 Feb 2014 19:24:03 -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 :content-type; bh=qtQtDrwgZDO5vw64uxqtsal63xY9uxLO9Rc3xhIYB1E=; b=SryiNEvjMPIsLtNxzHBfwwMcqtZ4k2c5xBy7kROCUJvh0zDUibKM22d+dJoAnla7jM ZDPh+wiLc6Nlaqp7sxe++PPWkAlIyD0uH/E+gQkUVDt2sXknJ0xSUXsye3Uq+dhBFSN+ yskLbeeeHfs25oAFA3ufYBjK3XJpLXo8KF8Y+3gZ9Rf+d+BVi9MabVay2hyI49BKWvx8 kaQK/YOVbTlBCMQdeO6mF998KS3SLH+R4d+Skyc/tevZ+YBRtaM3+iCBKeV0Lo3X8A43 ffX9+vHhJ3NxHLBY+34BFUjTWyIEw910VyMaCNX6qdLAQRI8TZf9OD022JczSwYOWcna G8lQ== MIME-Version: 1.0 X-Received: by 10.69.19.139 with SMTP id gu11mr7256691pbd.149.1391484243392; Mon, 03 Feb 2014 19:24:03 -0800 (PST) Received: by 10.68.155.38 with HTTP; Mon, 3 Feb 2014 19:24:03 -0800 (PST) In-Reply-To: References: Date: Mon, 3 Feb 2014 22:24:03 -0500 Message-ID: Subject: Fwd: using -virtualization@ as the preferred support channel for petitecloud? From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 04 Feb 2014 03:24:04 -0000 We will also need to rexamine this as the linux user base grows (right now there are no linux only users I know of)... we will likely still recommend that most of the "high end" (not the normal run of the mil ones) tech support bve directected to virtualization most them will likely include more then just petitecloud ---------- Forwarded message ---------- From: Aryeh Friedman Date: Mon, Feb 3, 2014 at 10:08 PM Subject: Re: using -virtualization@ as the preferred support channel for petitecloud? To: Kevin Bowling We currently do not have enough demand for it (the actual tech support requests have been a total of 1 and that was a bug report) almost everything I post except for announcements is I hopefully useful to all of virtualization and not just petitecloud... once we see more then 1 or 2 tech support requests and/pr pettiecloud spsecific discussions per week we will move On Mon, Feb 3, 2014 at 10:03 PM, Kevin Bowling wrote: > On 1/29/2014 8:07 PM, Aryeh Friedman wrote: > >> We are in the process of updating PetiteCloud.org in preparation for our >> upcoming release of 0.2.3 (which will include support for Linux as a >> guest, >> though still with FreeBSD as the only host and bhyve the only hypervisor >> that currently runs in hardware virtualization mode). We're wondering if >> it is ok if we update the resources page to say that all support questions >> should go to -virtualization@? >> >> We've already been doing this unofficially for quite some time, and >> PetiteCloud does not currently have a large enough user base to justify a >> mailing list of its own. If/when questions about PetiteCloud become too >> high volume here, we will then, of course, start our own mailing list. >> >> > I would greatly appreciate anything specific to your implementation on > it's own list/forum/whatever. > > > _______________________________________________ > 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" > -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 4 04:35:44 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C7ABD57B; Tue, 4 Feb 2014 04:35:44 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9411A1036; Tue, 4 Feb 2014 04:35:44 +0000 (UTC) Received: by mail-pd0-f178.google.com with SMTP id y13so7759309pdi.9 for ; Mon, 03 Feb 2014 20:35:44 -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=OHp+9m2COKa0VpFwQWCwwx6BkMnAm2wAv3Uk16fG/TM=; b=Y1UXdNiCLFIG3tSkoAXpZlr1Px2yIYZ4+l66cxoiWyiIG4M+hA56MYWz6Qr2OZZDVb herETfQcJwzQAWJpar1bAuXOsM6bQtDmik4kKT/4G6l9xA97/fye5htBmxLQYPiqJCeF eu5Fka80Lly7nlzXt41brbOLFhyYJnsvo5zi5FXFXZRwBDx31LDED7/Ym3aicExfGBIu znV1Bl6oR2MpvA69eaNPkHmQ1oY3aqVdP3h409Y+5Jh/oNNvw4EV21F47pmTrNjGbjfg z4aTy0OQ1kZH8Ix6Vpb3CV0ZQiSL1wNjI5L9a0+wdgUOzGmxhmIae9f8Bm+cHmS9NA1F 68tg== MIME-Version: 1.0 X-Received: by 10.69.19.139 with SMTP id gu11mr7560339pbd.149.1391488544347; Mon, 03 Feb 2014 20:35:44 -0800 (PST) Received: by 10.68.155.38 with HTTP; Mon, 3 Feb 2014 20:35:44 -0800 (PST) In-Reply-To: <52EDE352.9050805@freebsd.org> References: <52EDB899.9060703@freebsd.org> <52EDE352.9050805@freebsd.org> Date: Mon, 3 Feb 2014 23:35:44 -0500 Message-ID: Subject: Re: some interesting observations on the relative performance of kvm vs. bhyve From: Aryeh Friedman To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 04 Feb 2014 04:35:44 -0000 Note on cachemodes it seems to make very little real world difference in which one you pick. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Tue Feb 4 17:55:21 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 CEABF9F2 for ; Tue, 4 Feb 2014 17:55:21 +0000 (UTC) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9AD2F1783 for ; Tue, 4 Feb 2014 17:55:20 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id uo5so8777162pbc.13 for ; Tue, 04 Feb 2014 09:55:14 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=06FZO44aOjZh/fzXSxaJL3ChZfZTor3sRE/XtfWWE7c=; b=WiMlidiSaH55PuLcHKX0+NLX65t4oqOVNyRfWsMalf09iZtY79f7zwFsyHq4oMB10I iIyJad8YsQgT6t0s2jWBa8TlB+7QYVg7cw+hbtPxceSse5bjQ7Sn7qNcJtQ9+Xq7vgha traKy8f4lk99Cr9DAWH2DSjCMbiyOeP/X4QniKvNOoqrnK5BfxxkEZoGI2V1Ydd8rjH6 bKuQ/LtStibwDSEvyf1kGN7TnfJreI/RBJujuNLW2OurmdgYxRlFj13xIDq/dV7nEzv4 /gGtYwe+e9yOOijXSAS5letpG4WN/lQ3Kbj9LorzolQ5O4gVyzctqCkxEWgGgBPDYxLH DXag== X-Gm-Message-State: ALoCoQmq1Iu87PNGZcaZO2uXHVxDogNmnybepb9y8Q6k6I/tEE0jBNQ0D6Mbupp6t0UlPBeXALo/ X-Received: by 10.67.5.131 with SMTP id cm3mr45187963pad.92.1391536514768; Tue, 04 Feb 2014 09:55:14 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id un5sm175374717pab.3.2014.02.04.09.55.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Feb 2014 09:55:14 -0800 (PST) Message-ID: <52F12981.4080103@callfortesting.org> Date: Tue, 04 Feb 2014 09:55:13 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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: Tue, 04 Feb 2014 17:55:21 -0000 May I suggest you take this all to a personal blog? Michael On 2/2/14 2:22 PM, Aryeh Friedman wrote: > Even though FreeBSD will always be my preferred OS for both personal and > professional use it is sad to say in today's world if you do not support > Linux and your run on Unix-like OS's then to everyone out side [insert > favorite OS here] you don't exist. This is even more so for a effort like > PetiteCloud that needs the widest possible user base to grow (the user base > is what will attract apps which will attract more users and so forth). For > the above reasons it is obvious that PetiteCloud *MUST* support linux as > host or we simply are irrelevant to mainstream cloud computing users. > > It is likely less painful to do it now then later when we have more devices > and drivers and such to have to sort out. Therefore I have posted a > developer's snapshot of 0.2.4 with Linux hosting on the normal download > link (don't worry the FreeBSD build still works fine). Take a look at the > developers section of the site for details of how to install and test it. > From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 07:03:10 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AD573F76; Wed, 5 Feb 2014 07:03:10 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F400B16A6; Wed, 5 Feb 2014 07:03:09 +0000 (UTC) Received: by mail-lb0-f174.google.com with SMTP id l4so7216256lbv.19 for ; Tue, 04 Feb 2014 23:03:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:cc:content-type; bh=UAd5Ujyisr8TCefy8pdBV+cHpkq2B+5wzFJepEXiU1g=; b=V1zRdOrwTe5lDeCzVarq6iIbVm3l2gum+VoIm6lZVQhMC15WYsazyEaz1giAo8F840 treREdI6z+y5dR6SNpvWFG1u86hlJGj11C46EWZwLenSGEruXAwOD4RKncyyUarxfalK /91ViqYlLfhxfq5uDnSixVpUTfrF/wQLH+V49YsFY+9F3+Y27jJBNe+7Se1s3ff5OcYj r4h/l2qRExwcv0iMbojrMmbuSOuKuetBabdYe1QRJTiszXIhzJvjlfBmmqYSRQBaG6TX pkhkJm9kH+Rsr+QN4S74g1uLMHVAyZZnDsvxGYdssH/d1skU5e7VugXsp2CH4FIen3G/ N2Bg== MIME-Version: 1.0 X-Received: by 10.112.142.161 with SMTP id rx1mr11731206lbb.33.1391583787957; Tue, 04 Feb 2014 23:03:07 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Tue, 4 Feb 2014 23:03:07 -0800 (PST) Date: Tue, 4 Feb 2014 23:03:07 -0800 X-Google-Sender-Auth: Z2KY4I6ox0xgRFuW53n3O3hfNSo Message-ID: Subject: MAC addresses to use for BHyve VM's running under FreeBSD? From: Craig Rodrigues To: George Neville-Neil Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 07:03:10 -0000 Hi, I am running many BHyve VM's and am using tap interfaces with a single bridge. I am configuring the IP addresses of these VM's via DHCP. I need to have separate MAC addresses for each VM. Can anyone recommend a range of MAC addresses to use? I seem to recall that at the 2013 FreeBSD Vendor Summit in Sunnyvale, California, that George mentioned that there might be a Organizational Unique Identifier (OUI) for the FreeBSD project that we can use for BHyve VM's. Is that right? If not, can people recommend a range of addresses to use? VMWare for example has an OUI of 00:50:56 ( http://pubs.vmware.com/vsphere-4-esxi-installable-vcenter/index.jsp?topic=/com.vmware.vsphere.esxi_server_config.doc_41/esx_server_config/advanced_networking/c_setting_up_mac_addresses.html) I'd rather not use that range if I don't have to, since I have a VMWare ESXi server running in the same network. :) -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 07:12: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1F4FCA6 for ; Wed, 5 Feb 2014 07:12: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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 921091739 for ; Wed, 5 Feb 2014 07:12:58 +0000 (UTC) Received: by mail-la0-f53.google.com with SMTP id e16so2027lan.12 for ; Tue, 04 Feb 2014 23:12:56 -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=n2j5t/ZOSSQtWQHRmSX/LMDGpLabGm1wDYjqgkzStC8=; b=fLoeHhO59Cx7LYyQtm2/ZXASHscNMYMCVc/4sC6pb2EVXg8eYZYwSgc52mBpWVs/HJ WXJ1d5TJELck6kZcmh2pXw/Rt6+svuNV6Jo/ZuWH4GbWOJSmGnBll3F8sTRD7Cangqk4 9fVmmBgkzc0p/qZWRYWYoudnUP6dL6YwnZCf1qseqRx07KF23k5ynbMeyZ60MZegwKcN 7jm1BD7/dcIAe6+7oX+U0n3VKzKvYa/vbn1vxTgtvACEJueGzq9zFng7pjF2WJDYRAR6 Lc8ptsizhzhNuj3r3EnUkcpNXlHCR74F4JcljKvboen3pxRyBwdsBqrAsrupaEvpGX2b M/gw== MIME-Version: 1.0 X-Received: by 10.152.9.65 with SMTP id x1mr4126laa.6.1391584376419; Tue, 04 Feb 2014 23:12:56 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Tue, 4 Feb 2014 23:12:56 -0800 (PST) In-Reply-To: References: Date: Tue, 4 Feb 2014 23:12:56 -0800 X-Google-Sender-Auth: fauMNbwsdD8s4DehVEjNX6Ek6UQ Message-ID: Subject: Re: Bhyve and network virtualization From: Craig Rodrigues To: =?ISO-8859-1?Q?Fr=E9d=E9ric_Alix?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 07:12:59 -0000 On Sat, Feb 1, 2014 at 1:03 AM, Fr=E9d=E9ric Alix wrote: > Now, i need a tool for build a virtual network, like crossbow in Illumos. > Well, it is not a graphical tool, but if you are OK with doing things from the command-line, you can create a bridge network device and create tap interfaces for each BHyve VM. Then inside your BHyve VM, you can use the vtnet driver (part of virtio) to access the network. Michael Dexter has written a nice document which explains how to do this and a lot more with BHyve: http://bhyve.org/bhyve-manual.pdf -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 07:36:21 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 9AA49414; Wed, 5 Feb 2014 07:36:21 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 64F2218AA; Wed, 5 Feb 2014 07:36:21 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id q10so25722pdj.10 for ; Tue, 04 Feb 2014 23:36:21 -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=5oitB1e73nNFBo6b5njlN/llFNHdKE421+UgRhT8wOo=; b=ZxIvYPomSpyIWDupGJ4J1+wnfKqBLL+N6xsgaZwxf3rz/NV76rhqyReFy6tNoDQreF qSw0SvJS+BIW3dpb5ZLSxRd61cmj2qm0Tp1lZFz9wIzWHbYTYqHQ/wwzPgAvyA1gZwL1 aErJ4iZhyVlFn7tVNOvsZwQ5KVyR7rsbMHptE780DkbkZRlMNaESLTxxpfw4AXYN4XRc NLEu9nIwU5Mu6pyjRsclkyu3+Ymx/k3XGBFvebrm7TZRtfE25ndMcr8ZvwXJseMDzwoM NIsiQGj5wLAx1AsLI7W7a1ctPavfdryDFtphzsrRApUf39g+lbVowXFftxGVifN/DlkD 2ZAg== MIME-Version: 1.0 X-Received: by 10.68.139.73 with SMTP id qw9mr48524663pbb.121.1391585780936; Tue, 04 Feb 2014 23:36:20 -0800 (PST) Received: by 10.68.155.38 with HTTP; Tue, 4 Feb 2014 23:36:20 -0800 (PST) In-Reply-To: References: Date: Wed, 5 Feb 2014 02:36:20 -0500 Message-ID: Subject: Re: Bhyve and network virtualization From: Aryeh Friedman To: Craig Rodrigues Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 07:36:21 -0000 On Wed, Feb 5, 2014 at 2:12 AM, Craig Rodrigues wrote= : > On Sat, Feb 1, 2014 at 1:03 AM, Fr=E9d=E9ric Alix >wrote: > > > Now, i need a tool for build a virtual network, like crossbow in Illumo= s. > > > > Well, it is not a graphical tool, but if > you are OK with doing things from the command-line, > you can create a bridge network device and create > tap interfaces for each BHyve VM. Then inside your BHyve VM, > you can use the vtnet driver (part of virtio) to access the network. > PC 0.3 is going to focus on networking we should have something simple (and www text based) soon that will include this... Craig I will have some questions in doing this (see my thoughts on storage) --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 08:33:42 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 09C1A332 for ; Wed, 5 Feb 2014 08:33:42 +0000 (UTC) Received: from smtp.free.de (smtp.free.de [91.204.6.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 622BD1D7A for ; Wed, 5 Feb 2014 08:33:41 +0000 (UTC) Received: (qmail 84091 invoked from network); 5 Feb 2014 09:33:32 +0100 Received: from smtp.free.de (HELO orwell.free.de) (k@free.de@[91.204.4.103]) (envelope-sender ) by smtp.free.de (qmail-ldap-1.03) with AES128-SHA encrypted SMTP for ; 5 Feb 2014 09:33:32 +0100 Subject: Re: MAC addresses to use for BHyve VM's running under FreeBSD? Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha512; boundary="Apple-Mail-11-965162304" From: Kai Gallasch In-Reply-To: Date: Wed, 5 Feb 2014 09:33:42 +0100 Content-Transfer-Encoding: 7bit Message-Id: <5975C516-9590-4059-A094-96EDFF1420FC@free.de> References: To: Craig Rodrigues X-Pgp-Agent: GPGMail 1.4.1 X-Mailer: Apple Mail (2.1085) Cc: George Neville-Neil , "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 08:33:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --Apple-Mail-11-965162304 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Am 05.02.2014 um 08:03 schrieb Craig Rodrigues: > Hi, >=20 > I am running many BHyve VM's and am using tap interfaces > with a single bridge. I am configuring the IP addresses > of these VM's via DHCP. >=20 > I need to have separate MAC addresses for each VM. >=20 > Can anyone recommend a range of MAC addresses to use? >=20 > I seem to recall that at the 2013 FreeBSD Vendor Summit in > Sunnyvale, California, that George mentioned that > there might be a Organizational Unique Identifier (OUI) for the = FreeBSD > project that we can use for BHyve VM's. Is that right? >=20 > If not, can people recommend a range of addresses to use? http://standards.ieee.org/develop/regauth/oui/public.html Using "Search the Public MA-L Listing" with search term FreeBSD = reveals.. --- snip --- Here are the results of your search through the public section of the = IEEE Standards OUI database report for freebsd: 58-9C-FC (hex) FreeBSD Foundation 589CFC (base 16) =09 FreeBSD Foundation P.O. Box 20247 Boulder CO 80308-3247 UNITED STATES --- snap --- Regards, K. -- GPG-Key: A593 E38B E968 4DBE 14D6 2115 7065 4D7C 4FB1 F588 Key available from hkps://hkps.pool.sks-keyservers.net --Apple-Mail-11-965162304 content-type: application/pgp-signature; x-mac-type=70674453; name=PGP.sig content-description: Signierter Teil der Nachricht content-disposition: inline; filename=PGP.sig content-transfer-encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJS8fdmAAoJEHBlTXxPsfWI+2EQAKqlt9fwXwjYUI8XPa2Hmxxk sAy2nGxqPWNuBkt2MYwpHaavArq+GWQxXxle9fY29gkgDc/dd5hTmMyLq2uGvcR4 SiqYIsb9KiglXjiuwKImFXwJlL2BnNhhuZ+f4VPCuu5wAjPMeITTgZCDHZyNA0aD oUTihTurOINtOiZllJX9qqr3OPgQ57WIxhw5QErgCiWKQOc5tJ+RubOCanLbtrxT PV8FqyWFHBlMELNsGtU/n1yUjxWXUBTn0Xrse33ndM3iodtkNIpqZBazias9FvbY CvCkg7wtWH8fFE6eIFZxlB/znP1KHTgu7SGx+2bdfe6kxKk6Jb1/wXFK9DSn5JDh rviqYKc++5FizEvZKiYMV9YdyxcKGqceEThsT14+W/kyurEvjN5d54ssWtjntHZP /bZsdgrPNxChS2HDiOiRNMKBfpZ9uVxZNyahtPNc/2uuQDBbEmSYR+cGQcmpG5xJ 1E0v1BBR4x7vE8ujbZzbcBugq2t5PBX6zUM9PPGgPwIXbjrPawES1pbFNwD2j3Xf QP6ZGBTf7ktFyxc9qKe4aVcrj6Z6xaxvHDWTKIyMuVsdNS++iH7kRhBV4n3QCIij z5U2xedM+1jR9gSkDR5ZKcUx8CIBybigFN86FLabqaJast9EMysxK4UBB/oasNLR V2GGKwyPAYdOQNfklQvg =VuSZ -----END PGP SIGNATURE----- --Apple-Mail-11-965162304-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 11:33: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 C7ED1F37; Wed, 5 Feb 2014 11:33:02 +0000 (UTC) Received: from vps.hungerhost.com (vps.hungerhost.com [216.38.53.176]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 908831D77; Wed, 5 Feb 2014 11:33:02 +0000 (UTC) Received: from pool-96-250-5-187.nycmny.fios.verizon.net ([96.250.5.187]:60812 helo=minion.home) by vps.hungerhost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1WB0hw-0008Ez-W5; Wed, 05 Feb 2014 06:31:57 -0500 Content-Type: multipart/signed; boundary="Apple-Mail=_D74EF3B8-0A71-4E83-B864-E3C655B66177"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: MAC addresses to use for BHyve VM's running under FreeBSD? From: George Neville-Neil In-Reply-To: <5975C516-9590-4059-A094-96EDFF1420FC@free.de> Date: Wed, 5 Feb 2014 06:31:56 -0500 Message-Id: <9BF7840E-03C2-47E4-A863-DE07FB1256F1@freebsd.org> References: <5975C516-9590-4059-A094-96EDFF1420FC@free.de> To: Kai Gallasch X-Mailer: Apple Mail (2.1827) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vps.hungerhost.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - freebsd.org X-Get-Message-Sender-Via: vps.hungerhost.com: authenticated_id: gnn@neville-neil.com Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 11:33:02 -0000 --Apple-Mail=_D74EF3B8-0A71-4E83-B864-E3C655B66177 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Feb 5, 2014, at 3:33 , Kai Gallasch wrote: > Am 05.02.2014 um 08:03 schrieb Craig Rodrigues: >> Hi, >>=20 >> I am running many BHyve VM's and am using tap interfaces >> with a single bridge. I am configuring the IP addresses >> of these VM's via DHCP. >>=20 >> I need to have separate MAC addresses for each VM. >>=20 >> Can anyone recommend a range of MAC addresses to use? >>=20 >> I seem to recall that at the 2013 FreeBSD Vendor Summit in >> Sunnyvale, California, that George mentioned that >> there might be a Organizational Unique Identifier (OUI) for the = FreeBSD >> project that we can use for BHyve VM's. Is that right? >>=20 >> If not, can people recommend a range of addresses to use? >=20 > http://standards.ieee.org/develop/regauth/oui/public.html >=20 > Using "Search the Public MA-L Listing" with search term FreeBSD = reveals.. >=20 > --- snip --- >=20 > Here are the results of your search through the public section of the = IEEE Standards OUI database report for freebsd: >=20 > 58-9C-FC (hex) FreeBSD > Foundation > 589CFC (base 16) =09 > FreeBSD > Foundation > P.O. Box 20247 > Boulder CO 80308-3247 > UNITED STATES > --- snap --- >=20 >=20 Correct, that is an address that the Foundation has registered with the = IEEE. If you look at sys/net/ieee_oui.h you will see that I=92ve allocated a = range to bhyve already. Best, George --Apple-Mail=_D74EF3B8-0A71-4E83-B864-E3C655B66177 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlLyISwACgkQYdh2wUQKM9KMeQCfaltXAuTLZ6NnvmuWF7PZTq3L deMAoK4gwbmp2iICjLWWQNx96Xu3qVaP =NUkn -----END PGP SIGNATURE----- --Apple-Mail=_D74EF3B8-0A71-4E83-B864-E3C655B66177-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 12:57:46 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 CE5C7645 for ; Wed, 5 Feb 2014 12:57:46 +0000 (UTC) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9695C151E for ; Wed, 5 Feb 2014 12:57:46 +0000 (UTC) Received: by mail-ig0-f174.google.com with SMTP id hl1so12244462igb.1 for ; Wed, 05 Feb 2014 04:57:46 -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=y4ayVK2k12W6N/az+keIAu+mp+wwRDt2olpMMAhNf2Y=; b=R4h1IMeZjA5vfXmClimw9GTAuFlJra5qkkaFv7ARB8nyA0dMI5heV9Hq4fHWaVVrem /0yf7NP0Y87P5XmyHr6PSues4YOkYqs8yuBnBwtjPBqncSV70JH2kAd2g/abUd1h5AQ5 vJpG5MUo8Ssy0jm/ps2q1nozAH0mvtL2aURacQJy9x87XZfX+kaGUooInv2EAaw0N3vS iLQ+oQ0/LgBZ0IFc0r6/0X5obHIELRzhPbZDYLET9XwwxijFaN/mIjIlqkWvytUTNZ1h T4cuakc8yxd/Ij58Z1i+PAyXqIq3ZJ4USLXTS+7ef26ZnlRG4IRRCqRxc90d+Akeit+E wwfA== MIME-Version: 1.0 X-Received: by 10.50.141.234 with SMTP id rr10mr22463127igb.11.1391605065536; Wed, 05 Feb 2014 04:57:45 -0800 (PST) Sender: admdwrf@gmail.com Received: by 10.42.23.13 with HTTP; Wed, 5 Feb 2014 04:57:45 -0800 (PST) In-Reply-To: References: Date: Wed, 5 Feb 2014 13:57:45 +0100 X-Google-Sender-Auth: dxIJjK4Uts1P2eZbCbthAGyGoN0 Message-ID: Subject: Re: Bhyve and network virtualization From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Alix?= To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 12:57:47 -0000 Thank you :) With crossbow, no GUI too. I always prefer cmd line thant gui :p Thank you for the document. Actually, i am testing the vde2 port ( http://www.freebsdports.info/ports/net/vde2.html). It's very interesting too for build a virtual network. -- fax 2014-02-05 Craig Rodrigues : > On Sat, Feb 1, 2014 at 1:03 AM, Fr=E9d=E9ric Alix wrote: > >> Now, i need a tool for build a virtual network, like crossbow in Illumos= . >> > > Well, it is not a graphical tool, but if > you are OK with doing things from the command-line, > you can create a bridge network device and create > tap interfaces for each BHyve VM. Then inside your BHyve VM, > you can use the vtnet driver (part of virtio) to access the network. > > Michael Dexter has written a nice document which explains how to do this > and a lot more with BHyve: http://bhyve.org/bhyve-manual.pdf > > -- > Craig > From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 17:46:20 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 3BE52610 for ; Wed, 5 Feb 2014 17:46:20 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EFCDB1502 for ; Wed, 5 Feb 2014 17:46:19 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id s15HkIrJ094456; Wed, 5 Feb 2014 12:46:18 -0500 (EST) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <52F278EA.3020509@pix.net> Date: Wed, 05 Feb 2014 12:46:18 -0500 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: MAC addresses to use for BHyve VM's running under FreeBSD? References: <9BF7840E-03C2-47E4-A863-DE07FB1256F1@freebsd.org> In-Reply-To: <9BF7840E-03C2-47E4-A863-DE07FB1256F1@freebsd.org> Content-Type: multipart/mixed; boundary="------------050005050101010709030301" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 17:46:20 -0000 This is a multi-part message in MIME format. --------------050005050101010709030301 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit > On Feb 5, 2014, at 3:33 , Kai Gallasch wrote: > >> Am 05.02.2014 um 08:03 schrieb Craig Rodrigues: >>> Hi, >>> >>> I am running many BHyve VM's and am using tap interfaces >>> with a single bridge. I am configuring the IP addresses >>> of these VM's via DHCP. >>> >>> I need to have separate MAC addresses for each VM. >>> >>> Can anyone recommend a range of MAC addresses to use? >>> >>> I seem to recall that at the 2013 FreeBSD Vendor Summit in >>> Sunnyvale, California, that George mentioned that >>> there might be a Organizational Unique Identifier (OUI) for the FreeBSD >>> project that we can use for BHyve VM's. Is that right? >>> >>> If not, can people recommend a range of addresses to use? >> >> http://standards.ieee.org/develop/regauth/oui/public.html >> >> Using "Search the Public MA-L Listing" with search term FreeBSD reveals.. >> >> --- snip --- >> >> Here are the results of your search through the public section of the IEEE Standards OUI database report for freebsd: >> >> 58-9C-FC (hex) FreeBSD >> Foundation >> 589CFC (base 16) >> FreeBSD >> Foundation >> P.O. Box 20247 >> Boulder CO 80308-3247 >> UNITED STATES >> --- snap --- >> >> > > Correct, that is an address that the Foundation has registered with the IEEE. > > If you look at sys/net/ieee_oui.h you will see that I’ve allocated a range to bhyve already. At work, we modified the bhyverun command to seed the hostname of them machine running the hypervisor as part of the "generate a MAC address" routine. That means that for virtual machine "foo", you now get different MACs on server "bar" and server "baz". Without this patch, you're likely to get identical MAC addresses for virtual machine "foo" on different servers. I personally also have my virtual machines set bit 2 in the first octet of the MAC address, so it falls into the "locally administered" catagory of MAC addresses. My gut feel is that using the FreeBSD OUI bhyve range, *AND* setting the locally administered bit in the MAC address is the way to go. -Kurt --------------050005050101010709030301 Content-Type: text/plain; charset=UTF-8; x-mac-type="0"; x-mac-creator="0"; name="pci_virtio_net.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="pci_virtio_net.diff" diff --git a/usr.sbin/bhyve/pci_virtio_net.c b/usr.sbin/bhyve/pci_virtio_net.c --- a/usr.sbin/bhyve/pci_virtio_net.c +++ b/usr.sbin/bhyve/pci_virtio_net.c @@ -579,27 +579,36 @@ pci_vtnet_init(struct vmctx *ctx, struct close(sc->vsc_tapfd); sc->vsc_tapfd = -1; } } } /* * The default MAC address is the standard NetApp OUI of 00-a0-98, - * followed by an MD5 of the PCI slot/func number and dev name + * followed by an MD5 of the PCI slot/func number, hostname, and + * vmname. The "locally administered" bit is also set in the + * resulting MAC address. */ if (!mac_provided) { - snprintf(nstr, sizeof(nstr), "%d-%d-%s", pi->pi_slot, - pi->pi_func, vmname); + char hostname[MAXHOSTNAMELEN]; + int rc; + + rc = gethostname(hostname, sizeof hostname - 1); + if (rc < 0) + hostname[0] = 0; + hostname[MAXHOSTNAMELEN-1] = 0; + snprintf(nstr, sizeof(nstr), "%d-%d-%s-%s", pi->pi_slot, + pi->pi_func, hostname, vmname); MD5Init(&mdctx); MD5Update(&mdctx, nstr, strlen(nstr)); MD5Final(digest, &mdctx); - sc->vsc_config.mac[0] = 0x00; + sc->vsc_config.mac[0] = 0x00 | 0x2; /* locally administered */ sc->vsc_config.mac[1] = 0xa0; sc->vsc_config.mac[2] = 0x98; sc->vsc_config.mac[3] = digest[0]; sc->vsc_config.mac[4] = digest[1]; sc->vsc_config.mac[5] = digest[2]; } /* initialize config space */ --------------050005050101010709030301-- From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 17:59:19 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 ED418BAB for ; Wed, 5 Feb 2014 17:59:19 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A4E431616 for ; Wed, 5 Feb 2014 17:59:19 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WB6kl-0005RR-OC for freebsd-virtualization@freebsd.org; Wed, 05 Feb 2014 18:59:15 +0100 Received: from tempe0.bbox.io ([24.249.180.233]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Feb 2014 18:59:15 +0100 Received: from kevin.bowling by tempe0.bbox.io with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 05 Feb 2014 18:59:15 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-virtualization@freebsd.org From: Kevin Bowling Subject: Re: Bhyve and network virtualization Date: Wed, 05 Feb 2014 10:59:04 -0700 Lines: 35 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: tempe0.bbox.io User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Thunderbird/27.0 In-Reply-To: X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 17:59:20 -0000 Has anyone used VALE with bhyve yet? It's in 10.0-RELEASE http://info.iet.unipi.it/~luigi/vale/ On 2/5/2014 5:57 AM, Frédéric Alix wrote: > Thank you :) > With crossbow, no GUI too. > I always prefer cmd line thant gui :p > Thank you for the document. Actually, i am testing the vde2 port ( > http://www.freebsdports.info/ports/net/vde2.html). > It's very interesting too for build a virtual network. > > > -- > fax > > > 2014-02-05 Craig Rodrigues : > >> On Sat, Feb 1, 2014 at 1:03 AM, Frédéric Alix wrote: >> >>> Now, i need a tool for build a virtual network, like crossbow in Illumos. >>> >> >> Well, it is not a graphical tool, but if >> you are OK with doing things from the command-line, >> you can create a bridge network device and create >> tap interfaces for each BHyve VM. Then inside your BHyve VM, >> you can use the vtnet driver (part of virtio) to access the network. >> >> Michael Dexter has written a nice document which explains how to do this >> and a lot more with BHyve: http://bhyve.org/bhyve-manual.pdf >> >> -- >> Craig >> From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 19:28:23 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 5255E2EB for ; Wed, 5 Feb 2014 19:28:23 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 22D951E24 for ; Wed, 5 Feb 2014 19:28:23 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 276F3B972; Wed, 5 Feb 2014 14:28:22 -0500 (EST) From: John Baldwin To: freebsd-virtualization@freebsd.org, Aryeh Friedman Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) Date: Wed, 05 Feb 2014 13:00:20 -0500 Message-ID: <5330814.Xk97r20mZI@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) In-Reply-To: <52F12981.4080103@callfortesting.org> References: <52F12981.4080103@callfortesting.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 05 Feb 2014 14:28:22 -0500 (EST) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 19:28:23 -0000 On Tuesday, February 04, 2014 09:55:13 AM Michael Dexter wrote: > May I suggest you take this all to a personal blog? I agree. You can use a blog on petitecloud.org if you wish, but the purpose of this list is discussing virtualization techniques FreeBSD supports including jails/vimage, hypervisors (bhyve), and accelerated guest support (e.g. Xen HVM and Hyper-V drivers). An occasional note about petitecloud may be warranted, but the current volume is excessive. Also, this list is not suitable for use as a support forum for a commercial product. It is certainly appropriate for bug reports in the aforementioned list of topics (e.g. bhyve bugs or bhyve performance testing results) that may come out of "downstream" bug reports. -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 19:57:20 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 1957394B for ; Wed, 5 Feb 2014 19:57:20 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 78BED1223 for ; Wed, 5 Feb 2014 19:57:19 +0000 (UTC) Received: by mail-la0-f43.google.com with SMTP id pv20so720953lab.16 for ; Wed, 05 Feb 2014 11:57:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=OzavNnbxCfat4S/+l113to7drPK3v1T2Bu2t1eiRZNY=; b=Ub3NRZJmDq2j9gZbD5s4IqYBYcYH4z1BA7zZh858X6VAV9W6LLeFh8SBK4f2ekkw/c wKM7d/ffrSiKMDaHKVweeAiE87hKdhGTN4FXOGUolIivbYXCkWRyO6l/ZEZsQTvD5DeY I4JjqetrDQrwR++g88YeP47vAvm3l6FswG5stnA00b1OQdcwI5AC/frjANLGE/V/zuUP ApF9wFKh48HD0q7jIUbsPSwHQC1aRTNYDwBgw49jy1K9Lbv18hku5eww7hYpIhoFbIFG 29UH4vZfyCRb4nuC+cU7/RNYJv+gk9NucuR8S5J14YCMOf1Q3pD2sQ/cxzErgNQOiOPq 3HSw== MIME-Version: 1.0 X-Received: by 10.112.148.197 with SMTP id tu5mr66771lbb.79.1391630237441; Wed, 05 Feb 2014 11:57:17 -0800 (PST) Sender: crodr001@gmail.com Received: by 10.112.30.211 with HTTP; Wed, 5 Feb 2014 11:57:17 -0800 (PST) In-Reply-To: <52F278EA.3020509@pix.net> References: <9BF7840E-03C2-47E4-A863-DE07FB1256F1@freebsd.org> <52F278EA.3020509@pix.net> Date: Wed, 5 Feb 2014 11:57:17 -0800 X-Google-Sender-Auth: TdUP9A8IXfLpFzD4NRmjbm_hZ74 Message-ID: Subject: Re: MAC addresses to use for BHyve VM's running under FreeBSD? From: Craig Rodrigues To: Kurt Lidl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 19:57:20 -0000 On Wed, Feb 5, 2014 at 9:46 AM, Kurt Lidl wrote: > On Feb 5, 2014, at 3:33 , Kai Gallasch wrote: >> >> Am 05.02.2014 um 08:03 schrieb Craig Rodrigues: >>> >>>> Hi, >>>> >>>> I am running many BHyve VM's and am using tap interfaces >>>> with a single bridge. I am configuring the IP addresses >>>> of these VM's via DHCP. >>>> >>>> I need to have separate MAC addresses for each VM. >>>> >>>> Can anyone recommend a range of MAC addresses to use? >>>> >>>> I seem to recall that at the 2013 FreeBSD Vendor Summit in >>>> Sunnyvale, California, that George mentioned that >>>> there might be a Organizational Unique Identifier (OUI) for the FreeBSD >>>> project that we can use for BHyve VM's. Is that right? >>>> >>>> If not, can people recommend a range of addresses to use? >>>> >>> >>> http://standards.ieee.org/develop/regauth/oui/public.html >>> >>> Using "Search the Public MA-L Listing" with search term FreeBSD reveals.. >>> >>> --- snip --- >>> >>> Here are the results of your search through the public section of the >>> IEEE Standards OUI database report for freebsd: >>> >>> 58-9C-FC (hex) FreeBSD >>> Foundation >>> 589CFC (base 16) >>> FreeBSD >>> Foundation >>> P.O. Box 20247 >>> Boulder CO 80308-3247 >>> UNITED STATES >>> --- snap --- >>> >>> >>> >> Correct, that is an address that the Foundation has registered with the >> IEEE. >> >> If you look at sys/net/ieee_oui.h you will see that I've allocated a >> range to bhyve already. >> > > At work, we modified the bhyverun command to seed the hostname > of them machine running the hypervisor as part of the "generate a MAC > address" routine. That means that for virtual machine "foo", > you now get different MACs on server "bar" and server "baz". > Without this patch, you're likely to get identical MAC addresses > for virtual machine "foo" on different servers. > > I personally also have my virtual machines set bit 2 in > the first octet of the MAC address, so it falls into the > "locally administered" catagory of MAC addresses. My gut feel > is that using the FreeBSD OUI bhyve range, *AND* setting the > locally administered bit in the MAC address is the way to go. > b > George, Thanks for allocating that range of MAC addresses. We shoud probably document that MAC address range in one of the BHyve man pages. Kurt, Your change is definitely useful. It changes the behavior of BHyve with respect to MAC addresses, but it is a very useful change. Have you submitted your change to Peter and Neel to see if they can evaluate if it can be made part of BHyve in the FreeBSD src tree? -- Craig From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 20:42:59 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 29F18609 for ; Wed, 5 Feb 2014 20:42:59 +0000 (UTC) Received: from volt.iem.pw.edu.pl (volt.iem.pw.edu.pl [194.29.146.3]) by mx1.freebsd.org (Postfix) with SMTP id B640B1763 for ; Wed, 5 Feb 2014 20:42:58 +0000 (UTC) Received: from iem.pw.edu.pl (localhost [127.0.0.1]) (Authenticated sender: kaczorem) by volt.iem.pw.edu.pl (Postfix) with ESMTPA id CDD50A66494 for ; Wed, 5 Feb 2014 21:42:57 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 05 Feb 2014 21:42:57 +0100 From: kaczorem To: freebsd-virtualization@freebsd.org Subject: Disks are not shown on Adaptec 5805 (added via passthrough to the VM) Message-ID: <76a98a271ebb61b01a1f2bcc6c4da479@iem.pw.edu.pl> X-Sender: kaczorem@localhost User-Agent: Roundcube Webmail/1.0-beta X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 20:42:59 -0000 Hello, I created a virtual machine with installed FreeBSD on ESXi 5.5. I added controller Adaptec 5805 to the VM via passthrough. FreeBSD detects aac controller but does not show disks. (it does not matter whether JBODs or logical volumes are configured on Adaptec) I did some tests and ex. it works well on Ubuntu - I can use all disks on controller which was added via passhrough to the virtual machine with Ubuntu. Everything works well under "physical" FreeBSD. logs: aac0: mem 0xfd200000-0xfd3fffff irq 18 at device 0.0 on pci3 aac0: Enabling 64-bit address support aac0: Enable Raw I/O aac0: Enable 64-bit array aac0: New comm. interface enabled aac0: Adaptec 5805, aac driver 2.1.9-1 aacp0 on aac0 aacp1 on aac0 aacp2 on aac0 (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Retrying command (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Retrying command (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Retrying command (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Retrying command (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Retrying command (probe2:aacp2:0:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00 (probe2:aacp2:0:0:0): CAM status: CCB request completed with an error (probe2:aacp2:0:0:0): Error 5, Retries exhausted ses0 at aacp2 bus 0 scbus4 target 0 lun 0 ses0: Fixed Enclosure Services SCSI-5 device ses0: 3.300MB/s transfers (8bit) ses0: SCSI-3 ENC Device regards, From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 21:02:16 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1CD38526; Wed, 5 Feb 2014 21:02:16 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D2CBD1964; Wed, 5 Feb 2014 21:02:15 +0000 (UTC) Received: from smarthost.fisglobal.com ([10.132.206.192]) by ltcfislmsgpa01.fnfis.com (8.14.5/8.14.5) with ESMTP id s15L2Eag019014 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 5 Feb 2014 15:02:14 -0600 Received: from THEMADHATTER (10.242.181.54) by smarthost.fisglobal.com (10.132.206.192) with Microsoft SMTP Server id 14.3.174.1; Wed, 5 Feb 2014 15:02:12 -0600 From: Sender: Devin Teske To: "'Craig Rodrigues'" , "'George Neville-Neil'" References: In-Reply-To: Subject: RE: MAC addresses to use for BHyve VM's running under FreeBSD? Date: Wed, 5 Feb 2014 13:02:06 -0800 Message-ID: <09da01cf22b5$885cecd0$9916c670$@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQKZhVDonEQDk15t88paxz5njic4opkSWrEg Content-Language: en-us X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-02-05_07:2014-02-05,2014-02-05,1970-01-01 signatures=0 Cc: dteske@FreeBSD.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 21:02:16 -0000 > -----Original Message----- > From: Craig Rodrigues [mailto:rodrigc@FreeBSD.org] > Sent: Tuesday, February 4, 2014 11:03 PM > To: George Neville-Neil > Cc: freebsd-virtualization@freebsd.org > Subject: MAC addresses to use for BHyve VM's running under FreeBSD? > > Hi, > > I am running many BHyve VM's and am using tap interfaces with a single > bridge. I am configuring the IP addresses of these VM's via DHCP. > > I need to have separate MAC addresses for each VM. > > Can anyone recommend a range of MAC addresses to use? > > I seem to recall that at the 2013 FreeBSD Vendor Summit in Sunnyvale, > California, that George mentioned that there might be a Organizational > Unique Identifier (OUI) for the FreeBSD project that we can use for BHyve > VM's. Is that right? > > If not, can people recommend a range of addresses to use? > [Devin Teske] I read a bunch of RFCs on how manufacturers form their MAC addresses. There is a range of values that will indicate "privately administered" MAC to networking equipment. In my testing over 6 years, I've found that these "privately administered" MAC addresses are not only treated well (read: no issues), but in some cases they hold their DHCP leases far longer than those without this special bit set. In my vimage script: http://druidbsd.sourceforge.net/download.shtml#vimage I have the following formula: # # Set the MAC address of the new interface using a sensible # algorithm to prevent conflicts on the network. # # MAC LAYOUT LP:LL:LB:BB:BB:BB # # Where: # P 2, 6, A, or E but usually 2 # NOTE: Indicates "privately administered" MAC # L ng_bridge(4) link number (1-65535) # B Same as bridged interface # So if we think of a MAC address as 6 octets, there are three goals that this formula/layout is addressing: Goal 1: Set the P nibble to a value of 2, 6, A, or E to indicate that the MaC address is one that is "privately administered" Goal 2: Allow up to 65530** unique MAC addresses to be formed from one single bridged interface. ** This number comes from stress-testing the ng_bridge(4) interface. In a lab, we were able to generate 65530 peers, all visible with ifconfig(8) and ngctl(8). Goal 3: Make the child MAC address look as similar to the parent MAC while satisfying goal 1 and goal 2. It is Goal #2 that gives us the layout requirement to have 2 octets (4 nibbles, aka 16 bits) to store a numeric identifier for a unique MAC address. It is goal #3 that gives us the layout requirement to copy (unmodified) bits from the bridge interface into the child MAC address. However, it is Goal #1 (of utmost importance in our needs) to force the second nibble of the first octet (high order; P in the layout) to a certain value. It was my own personal preference to simply split the 4 nibbles for child identifier so I could group the nibbles from the parent MAC. Resulting in the layout: LP:LL:LB:BB:BB Again, where the disjoint LL:LL represents a number 0-65535 for the LINK or CHILD identifier (first peer is 0, second is 1, so-on), P is locked at 2 (but could easily expand to also use 6, A, or E), and B:BB:BB are bits from the bridge's MAC. For code on calculating it all, see the above link -- written in shell script using bit- wise masking. I think it needless to say that we went overboard... a single system could potentially run 262,120 vimages (dup the vimage rc.d 3x and change the privately administered MAC nibble ``P'' from 2 to 6, then A, then E; each gaining up to 65530 new privately administered MAC address space). -- Devin _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. From owner-freebsd-virtualization@FreeBSD.ORG Wed Feb 5 23:48: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 82A12B09 for ; Wed, 5 Feb 2014 23:48:52 +0000 (UTC) Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 52627187D for ; Wed, 5 Feb 2014 23:48:52 +0000 (UTC) Received: by mail-pb0-f49.google.com with SMTP id up15so1011504pbc.22 for ; Wed, 05 Feb 2014 15:48:52 -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=+QJ2rguw1b8M2+NmhUjB62/mYd6Wrg5NhtrAdBrzLek=; b=sq2INCYtl4YTL7h5d+bGVhgId+bHpRuRJv1K+WusF6uApwf7FhGVtD/KI4QMfaoGPZ 6EP/AkWK5RNyAmF2QcSoATsbSwh+95jLp/Ab1rXzHTU0VXyGgdTF738ZtW7lnPR1buVA RN+NSQrfJ2M/+BViKx1P71v7SfjynBsfsg2uMosVcHNBNxJuDKRrXqKygdo2C+D623D5 ybgZ1DbOlZdZhEK0EIytxfJeLxHiHeXTXelNijZdYViVM0hJO3JTRYGn1AcvdU4wQygV ekGlbHrAKxSKP4raudO+KEOMP93Jf23AQciu648iqnRdyp+FBuHKv1bx4haFHO/w59Jv knTg== MIME-Version: 1.0 X-Received: by 10.69.20.139 with SMTP id hc11mr6568986pbd.63.1391644131925; Wed, 05 Feb 2014 15:48:51 -0800 (PST) Received: by 10.68.155.38 with HTTP; Wed, 5 Feb 2014 15:48:51 -0800 (PST) In-Reply-To: References: Date: Wed, 5 Feb 2014 18:48:51 -0500 Message-ID: Subject: Re: Bhyve and network virtualization From: Aryeh Friedman To: Kevin Bowling Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 05 Feb 2014 23:48:52 -0000 On Wed, Feb 5, 2014 at 12:59 PM, Kevin Bowling wrote: > Has anyone used VALE with bhyve yet? It's in 10.0-RELEASE > http://info.iet.unipi.it/~luigi/vale/ > > Just a general question on virtual network how encapsulatable (ability to wrap standardized wrappers around them) to do the different things... the reason for this is when I added the support for whatever networking solution(s) we choose I want to add them in the same way we did hypervisors (a stripped down plugin model [which will be expanded in future versions to be more complete])... does anyone see any reason why this model could not be used? -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 00:55:08 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E77A4258; Thu, 6 Feb 2014 00:55:07 +0000 (UTC) Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9E5B41DC8; Thu, 6 Feb 2014 00:55:07 +0000 (UTC) Received: by mail-oa0-f44.google.com with SMTP id g12so1490210oah.3 for ; Wed, 05 Feb 2014 16:55:07 -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=1EI5qRcEepao4pHrMcq6zEXXZ8tVI5e8KD6S23RFZuU=; b=FKNMZ2uHaLE8XG556wvno9H9g1bFYRFNafJYq/WS4jkPIVzzHhI6RBZGgNTGz0+0yw FXXQgGcbBuoX+gMBNN7WHTPVqeHtKADpVxTpnjzw4/SKn+zeWMMZ6Ztxplyz6AA3Kten Gd5bnywQ/7+IT6Xix2oCllN/sRciF6hu7TOpJrSBBc3XhQxA8UzRrF94WvHtPu0qLZ+u SGriiciwhFkwxVTqVTtFdXm7lyS55f935xJNMVynZOqjNjKKl8nvyqRBTvkCc+p7vBFi QAlwRWDcydyIji854nm/L+AyLOKJ4wWDfW/W6B7b4NATh+cjsonCMb+4NKb2yG5a+S+c rkBw== MIME-Version: 1.0 X-Received: by 10.182.153.41 with SMTP id vd9mr63255obb.87.1391648106884; Wed, 05 Feb 2014 16:55:06 -0800 (PST) Received: by 10.60.137.233 with HTTP; Wed, 5 Feb 2014 16:55:06 -0800 (PST) In-Reply-To: <5330814.Xk97r20mZI@ralph.baldwin.cx> References: <52F12981.4080103@callfortesting.org> <5330814.Xk97r20mZI@ralph.baldwin.cx> Date: Wed, 5 Feb 2014 19:55:06 -0500 Message-ID: Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) From: Aryeh Friedman To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 00:55:08 -0000 On Wed, Feb 5, 2014 at 1:00 PM, John Baldwin wrote: > On Tuesday, February 04, 2014 09:55:13 AM Michael Dexter wrote: > > May I suggest you take this all to a personal blog? > > I agree. You can use a blog on petitecloud.org if you wish, but the > purpose > of this list is discussing virtualization techniques FreeBSD supports > including > jails/vimage, hypervisors (bhyve), and accelerated guest support (e.g. Xen > HVM > and Hyper-V drivers). An occasional note about petitecloud may be > warranted, > but the current volume is excessive. Also, this list is not suitable for > use > as a support forum for a commercial product. It is certainly appropriate > for > bug reports in the aforementioned list of topics (e.g. bhyve bugs or bhyve > performance testing results) that may come out of "downstream" bug reports. > 1. We'll be creating our own mailing list as soon as we can solve these technical issues: a. Mailman (under apache22) seems to insist on being on port 80. We have no machine that is on the public internet that has 80 not used by tomcat. Any ideas on how to fix this? (Both machines are at RootBSD and have 9.2-RELEASE on them.) b. The way our internal build system works, updating petitecloud.org also triggers a snapshot release of PetiteCloud and it is currently in a state that is not releasable (massive security issues on the Linux end [FreeBSD has no such issues]) 2. You seem to be under the impression that PetiteCloud is a commercial product. It is in fact 100% Free Open Source (BSD license) and Open Knowledge. We do plan to sell products that are ENABLED by PetiteCloud but are NOT REQUIRED by PetiteCloud in any way. (Thus there will be no "enterprise edition", "secret sauce", high-priced "training", etc.) Also we eventually plan, once there is enough interest, to form a foundation on the FreeBSD/Apache model and transfer PetiteCloud completely over to it. The reason for this is that we do not see any "honest" way to make money from PetiteCloud itself, but only from various types of products it enables. We will also encourage anyone who wants to build products or open source (also hopefully open knowledge) projects on top of PetiteCloud (even if they are direct competitors of our commerical products) 3. Yes the comments on why we now have support for a non-FreeBSD host (as well as for FreeBSD, our preferred OS) really belong on a different forum. Since we have not yet created said forum, for the temporary technical reasons mentioned above, -virtualization@ seemed the only appropriate place to post our announcement, since the actual announcement was only a CFT and 100% of our users are FreeBSD. 4. Currently the only available place to discuss cloud computing at all on FreeBSD is -virtualization@. A -cloud@ list might make more sense if there was one. We would strongly urge the creation of such a list, because we consider FreeBSD to be, without question, the best operating system for truly stable and robust cloud computing, and we would strongly encourage the FreeBSD Foundation to emphasize this in its advocacy. In the meantime, please note that PetiteCloud is not yet a full-fledged cloud platform, but currently is little more than just a front end for various hypervisors including bhyve (our preferred hypervisor 5.. We would appreciate clarification on what kinds of announcements are appropriate here. For example, we've been posting calls for testing of new versions of PetiteCloud for almost five months with no objection from anyone (except for an early question from Michael Dexter about how truly open-source we were) until we added support for a non-FreeBSD host. May we continue to post CFT's that contain FreeBSD-related issues (including making sure we didn't break anything related to our FreeBSD support when adding features required by other OS's). 6. Since we purposely do not collect user email addresses at any point in the download and/or install, we will have no other quick way, besides -virtualization@ itself, to tell users where to ask questions about PetiteCloud now that -virtualization@ is no longer the correct place to send things. Thus we will need to make at least one more purely administrative/support oriented post before the move is complete 7. Miscellaneous a. We will sending the $50 we had offered to give someone on -emulation@ to the FreeBSD foundation, earmarked for work on virtualization and cloud computing. (The person to whom we offered the $50, for a solution to a problem we had been struggling with, told us to keep it.) b. As soon the appropriate person at the FreeBSD foundation contacts us, we will arrange to transfer freebsd-openstack.org to the foundation, if the FreeBSD foundation desires to be in charge of such a portal. We do want to keep editorial control until we can put a basic content management system in place and populate it with some initial content. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 09:05:24 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 419B2F03 for ; Thu, 6 Feb 2014 09:05:24 +0000 (UTC) Received: from ext.mellstrand.net (ext.mellstrand.net [IPv6:2001:2040:4:2::51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9D8B117AA for ; Thu, 6 Feb 2014 09:05:23 +0000 (UTC) Received: by ext.mellstrand.net Thu, 6 Feb 2014 09:05:20 GMT From: Mats Mellstrand Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Subject: vm_create: Device not configured Message-Id: Date: Thu, 6 Feb 2014 10:05:23 +0100 To: freebsd-virtualization@freebsd.org Mime-Version: 1.0 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 09:05:24 -0000 Hi I'm sure I'm doing something wrong, but I can=B4t figure out what. I'm following the instructions from = http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt First some facts: My host FreeBSD 10.0-STABLE #7 r260986: Tue Jan 21 19:29:18 CET 2014 mats@xxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz (3392.37-MHz K8-class = CPU) Origin =3D "GenuineIntel" Id =3D 0x306a9 Family =3D 0x6 Model =3D = 0x3a Stepping =3D 9 = Features=3D0xbfebfbff = Features2=3D0x7fbae3ff AMD Features=3D0x28100800 AMD Features2=3D0x1 Standard Extended Features=3D0x281 TSC: P-state invariant, performance statistics real memory =3D 17179869184 (16384 MB) avail memory =3D 16297574400 (15542 MB) [snip] # kldstat Id Refs Address Size Name 1 20 0xffffffff80200000 160c130 kernel 2 1 0xffffffff8180d000 23db68 zfs.ko 3 2 0xffffffff81a4b000 6638 opensolaris.ko 4 1 0xffffffff81c12000 34d3 ums.ko 5 1 0xffffffff81c16000 2f142 pf.ko 6 1 0xffffffff81c46000 16ef79 vmm.ko 7 1 0xffffffff81db5000 553f if_tap.ko Using the image from http://people.freebsd.org/~neel/bhyve/release.iso When running the script http://people.freebsd.org/~neel/bhyve/vmrun.sh # sh -xv vmrun.sh vml=20 [snip] + BOOTDISK=3D./release.iso + installer_opt=3D'-s 31:0,virtio-blk,./release.iso' + /usr/sbin/bhyveload -m 512M -d ./release.iso vml vm_create: Device not configured + [ 1 -ne 0 ] + break exit 99 + exit 99 /mm From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 12:11:37 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 A513E2F7 for ; Thu, 6 Feb 2014 12:11:37 +0000 (UTC) Received: from ext.mellstrand.net (ext.mellstrand.net [IPv6:2001:2040:4:2::51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 065281C66 for ; Thu, 6 Feb 2014 12:11:36 +0000 (UTC) Received: by ext.mellstrand.net Thu, 6 Feb 2014 12:11:34 GMT Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Subject: Re: vm_create: Device not configured From: Mats Mellstrand In-Reply-To: Date: Thu, 6 Feb 2014 13:11:38 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <4EA3BFD4-9491-4C22-A9A4-4CD13287AD7E@exmandato.se> References: To: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 12:11:37 -0000 Hi=20 Some more info I put the line vmm_load=3D"YES"=20 in loader.conf. Still the same problem, but I see module_register_init: MOD_LOAD (vmm, 0xffffffff81c47b60, 0) error 6 in the dmesg output The device /dev/vmm is not created (as I think it should?) /mm On 6 feb 2014, at 10:05, Mats Mellstrand wrote: > Hi >=20 > I'm sure I'm doing something wrong, but I can=B4t figure out what. >=20 > I'm following the instructions from = http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt >=20 > First some facts: >=20 > My host >=20 > FreeBSD 10.0-STABLE #7 r260986: Tue Jan 21 19:29:18 CET 2014 > mats@xxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 > CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz (3392.37-MHz K8-class = CPU) > Origin =3D "GenuineIntel" Id =3D 0x306a9 Family =3D 0x6 Model =3D = 0x3a Stepping =3D 9 > = Features=3D0xbfebfbff > = Features2=3D0x7fbae3ff > AMD Features=3D0x28100800 > AMD Features2=3D0x1 > Standard Extended Features=3D0x281 > TSC: P-state invariant, performance statistics > real memory =3D 17179869184 (16384 MB) > avail memory =3D 16297574400 (15542 MB) > [snip] >=20 > # kldstat >=20 > Id Refs Address Size Name > 1 20 0xffffffff80200000 160c130 kernel > 2 1 0xffffffff8180d000 23db68 zfs.ko > 3 2 0xffffffff81a4b000 6638 opensolaris.ko > 4 1 0xffffffff81c12000 34d3 ums.ko > 5 1 0xffffffff81c16000 2f142 pf.ko > 6 1 0xffffffff81c46000 16ef79 vmm.ko > 7 1 0xffffffff81db5000 553f if_tap.ko >=20 >=20 > Using the image from http://people.freebsd.org/~neel/bhyve/release.iso >=20 > When running the script = http://people.freebsd.org/~neel/bhyve/vmrun.sh >=20 > # sh -xv vmrun.sh vml=20 >=20 > [snip] > + BOOTDISK=3D./release.iso > + installer_opt=3D'-s 31:0,virtio-blk,./release.iso' > + /usr/sbin/bhyveload -m 512M -d ./release.iso vml > vm_create: Device not configured > + [ 1 -ne 0 ] > + break >=20 > exit 99 > + exit 99 >=20 >=20 > /mm >=20 >=20 >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to = "freebsd-virtualization-unsubscribe@freebsd.org" >=20 From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 13:39:08 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 A988D3E0 for ; Thu, 6 Feb 2014 13:39:08 +0000 (UTC) Received: from ext.mellstrand.net (ext.mellstrand.net [IPv6:2001:2040:4:2::51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2EADB161A for ; Thu, 6 Feb 2014 13:39:07 +0000 (UTC) Received: by ext.mellstrand.net Thu, 6 Feb 2014 13:39:05 GMT Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Subject: Re: vm_create: Device not configured From: Mats Mellstrand In-Reply-To: <4EA3BFD4-9491-4C22-A9A4-4CD13287AD7E@exmandato.se> Date: Thu, 6 Feb 2014 14:39:09 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <8654B538-C9BA-49F9-A08A-29199D5E043F@exmandato.se> References: <4EA3BFD4-9491-4C22-A9A4-4CD13287AD7E@exmandato.se> To: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 13:39:08 -0000 Hi again Problem solved. I had to enable VTX in BIOS /mm On 6 feb 2014, at 13:11, Mats Mellstrand wrote: > Hi=20 >=20 > Some more info >=20 > I put the line >=20 > vmm_load=3D"YES"=20 >=20 > in loader.conf. Still the same problem, but I see >=20 > module_register_init: MOD_LOAD (vmm, 0xffffffff81c47b60, 0) error 6 >=20 > in the dmesg output >=20 > The device /dev/vmm is not created (as I think it should?) >=20 > /mm >=20 >=20 > On 6 feb 2014, at 10:05, Mats Mellstrand wrote: >=20 >> Hi >>=20 >> I'm sure I'm doing something wrong, but I can=B4t figure out what. >>=20 >> I'm following the instructions from = http://people.freebsd.org/~neel/bhyve/bhyve_instructions.txt >>=20 >> First some facts: >>=20 >> My host >>=20 >> FreeBSD 10.0-STABLE #7 r260986: Tue Jan 21 19:29:18 CET 2014 >> mats@xxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/GENERIC amd64 >> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 >> CPU: Intel(R) Xeon(R) CPU E3-1240 V2 @ 3.40GHz (3392.37-MHz K8-class = CPU) >> Origin =3D "GenuineIntel" Id =3D 0x306a9 Family =3D 0x6 Model =3D = 0x3a Stepping =3D 9 >> = Features=3D0xbfebfbff >> = Features2=3D0x7fbae3ff >> AMD Features=3D0x28100800 >> AMD Features2=3D0x1 >> Standard Extended Features=3D0x281 >> TSC: P-state invariant, performance statistics >> real memory =3D 17179869184 (16384 MB) >> avail memory =3D 16297574400 (15542 MB) >> [snip] >>=20 >> # kldstat >>=20 >> Id Refs Address Size Name >> 1 20 0xffffffff80200000 160c130 kernel >> 2 1 0xffffffff8180d000 23db68 zfs.ko >> 3 2 0xffffffff81a4b000 6638 opensolaris.ko >> 4 1 0xffffffff81c12000 34d3 ums.ko >> 5 1 0xffffffff81c16000 2f142 pf.ko >> 6 1 0xffffffff81c46000 16ef79 vmm.ko >> 7 1 0xffffffff81db5000 553f if_tap.ko >>=20 >>=20 >> Using the image from = http://people.freebsd.org/~neel/bhyve/release.iso >>=20 >> When running the script = http://people.freebsd.org/~neel/bhyve/vmrun.sh >>=20 >> # sh -xv vmrun.sh vml=20 >>=20 >> [snip] >> + BOOTDISK=3D./release.iso >> + installer_opt=3D'-s 31:0,virtio-blk,./release.iso' >> + /usr/sbin/bhyveload -m 512M -d ./release.iso vml >> vm_create: Device not configured >> + [ 1 -ne 0 ] >> + break >>=20 >> exit 99 >> + exit 99 >>=20 >>=20 >> /mm >>=20 >>=20 >>=20 >>=20 >>=20 >>=20 >> _______________________________________________ >> freebsd-virtualization@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization >> To unsubscribe, send any mail to = "freebsd-virtualization-unsubscribe@freebsd.org" >>=20 >=20 > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to = "freebsd-virtualization-unsubscribe@freebsd.org" >=20 From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 15:21:34 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 D23655CA; Thu, 6 Feb 2014 15:21:34 +0000 (UTC) Received: from mail-qc0-x22d.google.com (mail-qc0-x22d.google.com [IPv6:2607:f8b0:400d:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7EC171200; Thu, 6 Feb 2014 15:21:34 +0000 (UTC) Received: by mail-qc0-f173.google.com with SMTP id i8so3327381qcq.18 for ; Thu, 06 Feb 2014 07:21:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:date:message-id:subject:from:to:cc :content-type; bh=D3wkB2CF+2wAHNQqy/rxEXtcV8Vqh61fkQVLSac+0hM=; b=F9fx9QFSJ6dZayKPYylrK55k5dFm5yIyv1oM84S9iDBFvl7pmIj18YoLcu0hEbUjfj DjCiiUrwaDvkQ4pqcoe8zifO+UpCgo2Yd+yPJPPPSiDjaV80GLK2nuXIBlH9FTg1sjsS B5wZyKu7bDIh6P/iC4XNv6a12e1WW21Ka21cQZoZZKO3tpxi2mIE51nQqsVfMBZFvMAi gP27+V2xxx+P2e0tDfdLVkCSiKmhA/bn6bP/M8G8m44mt22cNyJdoMRWIilpTdi1es2l 112aaWXEenV3fLbgXueCCzEqg+tubXAtj3OJ6rgYS9xDKX+jsaWJDeGROpFZrLK5cGT1 wn/A== MIME-Version: 1.0 X-Received: by 10.140.32.200 with SMTP id h66mr12644168qgh.49.1391699775290; Thu, 06 Feb 2014 07:16:15 -0800 (PST) Sender: shteryana@gmail.com Received: by 10.224.128.73 with HTTP; Thu, 6 Feb 2014 07:16:15 -0800 (PST) Date: Thu, 6 Feb 2014 17:16:15 +0200 X-Google-Sender-Auth: 7VjaghsUkbCxgiz69xjkLCAgKTU Message-ID: Subject: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE ) From: Shteryana Shopova To: freebsd-virtualization@freebsd.org Content-Type: multipart/mixed; boundary=001a1139b126bd9b0304f1be5a0a Cc: nox@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: syrinx@FreeBSD.org List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 15:21:35 -0000 --001a1139b126bd9b0304f1be5a0a Content-Type: text/plain; charset=UTF-8 Hi all, Sorry for top posting but I'm new to the list and came across this thread while playing with bhyve these days. To apply the patch - #cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/ compile and install the module. I've been running kqemu under current with the attached patch (plain text below in case the attachment is removed) for a couple of months now and the module is loaded successfully - root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu kqemu version 0x00010300 kqemu: KQEMU installed, max_locked_mem=4120624kB. root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014 The original commit that broke kqemu-kmod is from March 9th, 2013, so the patch should be applicable to 10-STABLE too. Reports on success/failures welcome. cheers, Shteryana P.S. Example on getting a headless VM with vbox - #VBoxManage createvm --name MyServer --ostype Windows7 --register #VBoxManage createhd --filename "MyServer.vdi" --size 200000 #VBoxManage storagectl MyServer --name "IDE Controller" --add ide --controller PIIX3 #VBoxManage storageattach MyServer --storagectl "IDE Controller" --port 0 --device 1 --type hdd --medium "MyServer.vdi" #VBoxManage storageattach MyServer --storagectl "IDE Controller" --port 1 --device 0 --type dvddrive --medium /home/myserver/install.iso #VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on --bridgeadapter1 em0 --nictype1 82540EM #VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd #VBoxHeadless -n -m 5901 -s "MyServer" The VM is then accessible via vncviewer to the IP of the original machine port 5901 --- kqemu-freebsd.c.orig 2014-02-06 16:03:15.881335406 +0200 +++ kqemu-freebsd.c 2014-02-06 16:04:25.951329106 +0200 @@ -109,7 +109,12 @@ vm_offset_t va; vm_paddr_t pa; +#if __FreeBSD_version >= 1000030 + va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK); +#else va = kmem_alloc(kernel_map, PAGE_SIZE); +#endif + if (va == 0) { kqemu_log("kqemu_alloc_zeroed_page: NULL\n"); return NULL; --001a1139b126bd9b0304f1be5a0a Content-Type: application/octet-stream; name=patch-unit3minorfix Content-Disposition: attachment; filename=patch-unit3minorfix Content-Transfer-Encoding: base64 X-Attachment-Id: f_hrc5g75v0 LS0tIGtxZW11LWZyZWVic2QuYy5vcmlnCTIwMTQtMDItMDYgMTY6MDM6MTUuODgxMzM1NDA2ICsw MjAwCisrKyBrcWVtdS1mcmVlYnNkLmMJMjAxNC0wMi0wNiAxNjowNDoyNS45NTEzMjkxMDYgKzAy MDAKQEAgLTEwOSw3ICsxMDksMTIgQEAKICAgICB2bV9vZmZzZXRfdCB2YTsKICAgICB2bV9wYWRk cl90IHBhOwogCisjaWYgX19GcmVlQlNEX3ZlcnNpb24gPj0gMTAwMDAzMAorICAgIHZhID0ga21l bV9tYWxsb2Moa2VybmVsX21hcCwgUEFHRV9TSVpFLCBNX1dBSVRPSyk7CisjZWxzZQogICAgIHZh ID0ga21lbV9hbGxvYyhrZXJuZWxfbWFwLCBQQUdFX1NJWkUpOworI2VuZGlmCisKICAgICBpZiAo dmEgPT0gMCkgewogCWtxZW11X2xvZygia3FlbXVfYWxsb2NfemVyb2VkX3BhZ2U6IE5VTExcbiIp OwogCXJldHVybiBOVUxMOwo= --001a1139b126bd9b0304f1be5a0a-- From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 16:21:49 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 57803253 for ; Thu, 6 Feb 2014 16:21:49 +0000 (UTC) Received: from hydra.pix.net (hydra.pix.net [IPv6:2001:470:e254::4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 19A5817E9 for ; Thu, 6 Feb 2014 16:21:48 +0000 (UTC) Received: from torb.pix.net (torb.pix.net [IPv6:2001:470:e254:10:12dd:b1ff:febf:eca9]) (authenticated bits=0) by hydra.pix.net (8.14.5/8.14.5) with ESMTP id s16GLlov004104; Thu, 6 Feb 2014 11:21:47 -0500 (EST) (envelope-from lidl@pix.net) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98 at mail.pix.net Message-ID: <52F3B69B.6030706@pix.net> Date: Thu, 06 Feb 2014 11:21:47 -0500 From: Kurt Lidl User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) References: In-Reply-To: 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.17 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, 06 Feb 2014 16:21:49 -0000 > 1. We'll be creating our own mailing list as soon as we can solve these > technical issues: > > a. Mailman (under apache22) seems to insist on being on port 80. > We have no machine that is on the public internet that has 80 not used by > tomcat. Any ideas on how to fix this? (Both machines are at RootBSD and > have 9.2-RELEASE on them.) This part is easy. You run a reverse proxy on your external IP address, and then you have it pass stuff for one virtual host to the server running tomcat, and have it pass requests for the mailman host to the server running apache22. Those "servers" could just be processes on the same machine, bound to different ports, or they could be complete virtual machines. It's entirely up to you as to how to implement and run it to best serve your interests. -Kurt From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 17:36:37 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 B702D489 for ; Thu, 6 Feb 2014 17:36:37 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8B59E109F for ; Thu, 6 Feb 2014 17:36:37 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id fp1so1579163pdb.24 for ; Thu, 06 Feb 2014 09:36:37 -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=HJLkXs9xH1tAsuPdbKdvRrXiHR0igOu1nDtix20wSzs=; b=PJ9zoIt8u9XAcZPMMShE7+sWtC9cP//K7nEM6GR0F78nN05weWXG45wlhamjoG6pUN yTSnrw6gFAg19Zxw23ddeAIleS+ehngwM2IIQ10WdNj9sFZ4KVb1eRZ6p1vcVgdSx8UW Jhxxb3FJQcY3JekQTfKBSs8KXq7y9sRtZ5Atih+lIurpTrPKfj7IQTyTd5Fq+pXzTY67 D5WlK03kY7V6IDhCBV5CTx3XzESgLoC8ktog7v0OvENeQF66gGg+f/1Cd5dDEWZh24yk XXfaIRfwa7xVHn4cMgNCnmsiSA1BLMLD4PWR9OmMVziB1CIXGXkK1eUaX/EN6YNBeLfL +jHw== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr13835718pbc.42.1391708197212; Thu, 06 Feb 2014 09:36:37 -0800 (PST) Received: by 10.68.155.38 with HTTP; Thu, 6 Feb 2014 09:36:37 -0800 (PST) In-Reply-To: <52F3B69B.6030706@pix.net> References: <52F3B69B.6030706@pix.net> Date: Thu, 6 Feb 2014 12:36:37 -0500 Message-ID: Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) From: Aryeh Friedman To: Kurt Lidl Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 17:36:37 -0000 On Thu, Feb 6, 2014 at 11:21 AM, Kurt Lidl wrote: > 1. We'll be creating our own mailing list as soon as we can solve these >> >> technical issues: >> >> a. Mailman (under apache22) seems to insist on being on port >> 80. >> We have no machine that is on the public internet that has 80 not used by >> tomcat. Any ideas on how to fix this? (Both machines are at RootBSD and >> have 9.2-RELEASE on them.) >> > > This part is easy. > > You run a reverse proxy on your external IP address, and then you have > it pass stuff for one virtual host to the server running tomcat, > and have it pass requests for the mailman host to the server running > apache22. > > Those "servers" could just be processes on the same machine, bound to > different ports, or they could be complete virtual machines. It's > entirely up to you as to how to implement and run it to best serve > your interests. Due to scheduling reasons we decided to spin up a third instance at RootBSD dedicated to mail and our non open source work. We should have everything set up and ready to go in the next few days. But since I am always looking out for new tricks, thanks. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 18:00:38 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 52182FEA; Thu, 6 Feb 2014 18:00:38 +0000 (UTC) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 0B01112CB; Thu, 6 Feb 2014 18:00:34 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 2A4DA1E007B8; Thu, 6 Feb 2014 19:00:31 +0100 (CET) Received: from enceladus10.kn-bremen.de (noident@localhost [127.0.0.1]) by enceladus10.kn-bremen.de (8.14.5/8.14.5) with ESMTP id s16HxJn1069878; Thu, 6 Feb 2014 18:59:19 +0100 (CET) (envelope-from nox@enceladus10.kn-bremen.de) Received: (from nox@localhost) by enceladus10.kn-bremen.de (8.14.5/8.14.5/Submit) id s16HxJSi069877; Thu, 6 Feb 2014 18:59:19 +0100 (CET) (envelope-from nox) From: Juergen Lock Date: Thu, 6 Feb 2014 18:59:19 +0100 To: Shteryana Shopova Subject: Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE ) Message-ID: <20140206175919.GA67849@enceladus10.kn-bremen.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: nox@FreeBSD.org, freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 18:00:38 -0000 On Thu, Feb 06, 2014 at 05:16:15PM +0200, Shteryana Shopova wrote: > Hi all, > > Sorry for top posting but I'm new to the list and came across this > thread while playing with bhyve these days. To apply the patch - > > #cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/ > > compile and install the module. > > I've been running kqemu under current with the attached patch (plain > text below in case the attachment is removed) for a couple of months > now and the module is loaded successfully - > > root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu > kqemu version 0x00010300 > kqemu: KQEMU installed, max_locked_mem=4120624kB. > root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v > FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014 > > The original commit that broke kqemu-kmod is from March 9th, 2013, so > the patch should be applicable to 10-STABLE too. Reports on > success/failures welcome. > > cheers, > Shteryana > > P.S. Example on getting a headless VM with vbox - > > #VBoxManage createvm --name MyServer --ostype Windows7 --register > #VBoxManage createhd --filename "MyServer.vdi" --size 200000 > #VBoxManage storagectl MyServer --name "IDE Controller" --add ide > --controller PIIX3 > #VBoxManage storageattach MyServer --storagectl "IDE Controller" > --port 0 --device 1 --type hdd --medium "MyServer.vdi" > #VBoxManage storageattach MyServer --storagectl "IDE Controller" > --port 1 --device 0 --type dvddrive --medium > /home/myserver/install.iso > #VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on > --bridgeadapter1 em0 --nictype1 82540EM > #VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd > #VBoxHeadless -n -m 5901 -s "MyServer" > > The VM is then accessible via vncviewer to the IP of the original > machine port 5901 > > --- kqemu-freebsd.c.orig 2014-02-06 16:03:15.881335406 +0200 > +++ kqemu-freebsd.c 2014-02-06 16:04:25.951329106 +0200 > @@ -109,7 +109,12 @@ > vm_offset_t va; > vm_paddr_t pa; > > +#if __FreeBSD_version >= 1000030 > + va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK); > +#else > va = kmem_alloc(kernel_map, PAGE_SIZE); > +#endif > + > if (va == 0) { > kqemu_log("kqemu_alloc_zeroed_page: NULL\n"); > return NULL; Oh well kqemu isn't even used by vbox, it's for emulaotors/qemu when built with the KQEMU knob and run with -enable-kqemu or -kernel-kqemu, and fixing _that_ needs most likely more changes than this. (I.e. I think I tried something similar and only got a panic. And also qemu uses kqemu-kmod-devel, kqemu-kmod is only left for people still using even older qemu forks.) Sorry... Juergen From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 19:00:56 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 7EFE5FD3; Thu, 6 Feb 2014 19:00:56 +0000 (UTC) Received: from mail-qa0-x236.google.com (mail-qa0-x236.google.com [IPv6:2607:f8b0:400d:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D07371900; Thu, 6 Feb 2014 19:00:55 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id i13so3504611qae.27 for ; Thu, 06 Feb 2014 11:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+ah69YB46PGH6fxp1WWtoPgRoB4HdgNOleGw6Dd4XpE=; b=Yazee+8MDsvTavrcX35OfwAaTOUS8mCKVp3p0SxgwbkIwOpcJQlXJJGu/ZcUU6jXT6 pbO80xkBKoBSOfWq9DuQL/vA+i1o/7P/OcCzSnM4BOcsbH5LGVBGiVgK6kXHsM1e2TiL quAcM1TevMAFF13rygp7qxEv4tUDSb5a7OeV2F8SjwhP2BOA1Wm7MyZ8gMp3YanDQch0 Uc+ozVCY8CC+ecMo8nOqxLKAGlx/FmEeanYqXDw2s0jwKwl9bWK46H4WZZ7sje2UE+QN O8EBf8arBVNX+A+9ood5bnvhmWFCmjJLoLDeKLsUKhxb3gOA9K2jlZYzNVQUCw4LHBRw BxWw== MIME-Version: 1.0 X-Received: by 10.140.32.200 with SMTP id h66mr14163254qgh.49.1391713254909; Thu, 06 Feb 2014 11:00:54 -0800 (PST) Sender: shteryana@gmail.com Received: by 10.224.128.73 with HTTP; Thu, 6 Feb 2014 11:00:54 -0800 (PST) In-Reply-To: <20140206175919.GA67849@enceladus10.kn-bremen.de> References: <20140206175919.GA67849@enceladus10.kn-bremen.de> Date: Thu, 6 Feb 2014 21:00:54 +0200 X-Google-Sender-Auth: jfwIEspnq0r7jVWY1-7-pVfWMKg Message-ID: Subject: Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE ) From: Shteryana Shopova To: Juergen Lock X-Mailman-Approved-At: Thu, 06 Feb 2014 19:12:25 +0000 Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: nox@freebsd.org, freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: syrinx@FreeBSD.org List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Feb 2014 19:00:56 -0000 On Thu, Feb 6, 2014 at 7:59 PM, Juergen Lock wrote: > On Thu, Feb 06, 2014 at 05:16:15PM +0200, Shteryana Shopova wrote: >> Hi all, >> >> Sorry for top posting but I'm new to the list and came across this >> thread while playing with bhyve these days. To apply the patch - >> >> #cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/ >> >> compile and install the module. >> >> I've been running kqemu under current with the attached patch (plain >> text below in case the attachment is removed) for a couple of months >> now and the module is loaded successfully - >> >> root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu >> kqemu version 0x00010300 >> kqemu: KQEMU installed, max_locked_mem=4120624kB. >> root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v >> FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014 >> >> The original commit that broke kqemu-kmod is from March 9th, 2013, so >> the patch should be applicable to 10-STABLE too. Reports on >> success/failures welcome. >> >> cheers, >> Shteryana >> >> P.S. Example on getting a headless VM with vbox - >> >> #VBoxManage createvm --name MyServer --ostype Windows7 --register >> #VBoxManage createhd --filename "MyServer.vdi" --size 200000 >> #VBoxManage storagectl MyServer --name "IDE Controller" --add ide >> --controller PIIX3 >> #VBoxManage storageattach MyServer --storagectl "IDE Controller" >> --port 0 --device 1 --type hdd --medium "MyServer.vdi" >> #VBoxManage storageattach MyServer --storagectl "IDE Controller" >> --port 1 --device 0 --type dvddrive --medium >> /home/myserver/install.iso >> #VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on >> --bridgeadapter1 em0 --nictype1 82540EM >> #VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd >> #VBoxHeadless -n -m 5901 -s "MyServer" >> >> The VM is then accessible via vncviewer to the IP of the original >> machine port 5901 >> >> --- kqemu-freebsd.c.orig 2014-02-06 16:03:15.881335406 +0200 >> +++ kqemu-freebsd.c 2014-02-06 16:04:25.951329106 +0200 >> @@ -109,7 +109,12 @@ >> vm_offset_t va; >> vm_paddr_t pa; >> >> +#if __FreeBSD_version >= 1000030 >> + va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK); >> +#else >> va = kmem_alloc(kernel_map, PAGE_SIZE); >> +#endif >> + >> if (va == 0) { >> kqemu_log("kqemu_alloc_zeroed_page: NULL\n"); >> return NULL; > > Oh well kqemu isn't even used by vbox, it's for emulaotors/qemu when Well, the VirtualBox off topic was caused by someone saying in an earlier thread "me and Dee (personally and not as the petitecloud development team) would be willing to give $50 to anyone who can get kqemu running on 10 and/or show how to get vbox to work headless" > built with the KQEMU knob and run with -enable-kqemu or -kernel-kqemu, > and fixing _that_ needs most likely more changes than this. (I.e. I > think I tried something similar and only got a panic. And also qemu Did you really try it? Can you explain then why it works for me with both kqemu-kmod-devel and kqemu-kmod? Can you please explain why this commit - http://svnweb.freebsd.org/base?view=revision&revision=248084 - is (ir-)relevant to the patch proposed? > uses kqemu-kmod-devel, kqemu-kmod is only left for people still using > even older qemu forks.) > > Sorry... > Juergen cheers, Shteryana Shopova From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 19:22:22 2014 Return-Path: Delivered-To: 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 CFDC182D for ; Thu, 6 Feb 2014 19:22:22 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A83631B18 for ; Thu, 6 Feb 2014 19:22:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B96D2B9B3 for ; Thu, 6 Feb 2014 14:22:21 -0500 (EST) From: John Baldwin To: virtualization@freebsd.org Subject: FreeBSD/i386 guest support in bhyve Date: Thu, 6 Feb 2014 14:21:59 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <201402050439.s154d4Uq036793@svn.freebsd.org> In-Reply-To: <201402050439.s154d4Uq036793@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201402061421.59699.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 06 Feb 2014 14:22:21 -0500 (EST) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 19:22:22 -0000 On Tuesday, February 04, 2014 11:39:04 pm John Baldwin wrote: > Author: jhb > Date: Wed Feb 5 04:39:03 2014 > New Revision: 261504 > URL: http://svnweb.freebsd.org/changeset/base/261504 > > Log: > Add support for FreeBSD/i386 guests under bhyve. FYI, this commit added support for FreeBSD/i386 guests under bhyve. I have not tried any other i386 guest OSs, though if grub2-bhyve is capable of booting a 32-bit guest those might work. -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 19:29: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C4A1ABBF for ; Thu, 6 Feb 2014 19:29:14 +0000 (UTC) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 91BA91B99 for ; Thu, 6 Feb 2014 19:29:14 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id w10so2088750pde.6 for ; Thu, 06 Feb 2014 11:29:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vhltDxK6uviabVljeRExLJEXdBzSrzzPclYzTcS8qdw=; b=MQ8jvToV4YO9fIGp+UcE9fe1smg6JyWs9VBwmJ4HigCbWnmgQm19uyabrtjMvwmlgy 1/jNbn5sfxELcXiFv8/kAjW1RCMM2owkH1pV0UQqr0B464rwB2P/WAb027pLGKYdfEco T35KDWanExJKy9F5kRZNMubJD1Yz1YpObBJz2kb5jB4Onq/Wo3Kc3JrIt4a7aqvx7pr7 02bcROhT8eYY9DWh6XLz277gvpLG3SjM3nJoeoZ5hXoc/xrg8Zuke47/WByp4vft08Nq Ug44GLYotHsXemnZHCcJlzSFDUWIMMW1RLCzDFTy3YWjGR2qkh7W8gX7+GcXO4Y02wsJ z3cA== X-Gm-Message-State: ALoCoQnOo7bNgdeSaCojQNz2T45j4Mg/+TAzE6NC/dst2JQZuDDNFqani4INNRn+B3NntS5STXVT X-Received: by 10.67.4.169 with SMTP id cf9mr2544548pad.45.1391714553914; Thu, 06 Feb 2014 11:22:33 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id iu7sm6001580pbc.45.2014.02.06.11.22.32 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Feb 2014 11:22:33 -0800 (PST) Message-ID: <52F3E0F9.8040504@callfortesting.org> Date: Thu, 06 Feb 2014 11:22:33 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-virtualization@freebsd.org, Aryeh Friedman Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) References: <52F3B69B.6030706@pix.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 19:29:14 -0000 On 2/6/14 9:36 AM, Aryeh Friedman wrote: > Due to scheduling reasons we decided to spin up a third instance at RootBSD > dedicated to mail and our non open source work. We should have everything > set up and ready to go in the next few days. But since I am always looking > out for new tricks, thanks. This news does not, under any circumstances belong on a technical list relating to virtualization technologies in FreeBSD as per the project's published guidelines: http://www.freebsd.org/doc/en/articles/mailing-list-faq/etiquette.html#idp62859952 There are countless resources on the Internet to help you debug your systems and development work but this is not one of them. It is great that you have found bhyve useful and we all look forward to your bug reports, patches and success stories. So far you have inundated this list with broken download URL's, misnamed software archives, non-resolving hosts, proposals of marketing materials and my personal favorite, a request for a bhyve developer to sign an NDA to see these. Please hesitate before you write and determine if this is the correct list and your post is in accordance with the above policies. Michael Dexter bhyve volunteer From owner-freebsd-virtualization@FreeBSD.ORG Thu Feb 6 20:14:34 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 94A9CFD8; Thu, 6 Feb 2014 20:14:34 +0000 (UTC) Received: from smtp.kn-bremen.de (gelbbaer.kn-bremen.de [78.46.108.116]) by mx1.freebsd.org (Postfix) with ESMTP id 3AF9510E8; Thu, 6 Feb 2014 20:14:32 +0000 (UTC) Received: by smtp.kn-bremen.de (Postfix, from userid 10) id 003261E007B8; Thu, 6 Feb 2014 21:14:31 +0100 (CET) Received: from enceladus10.kn-bremen.de (noident@localhost [127.0.0.1]) by enceladus10.kn-bremen.de (8.14.5/8.14.5) with ESMTP id s16KCcMK074814; Thu, 6 Feb 2014 21:12:38 +0100 (CET) (envelope-from nox@enceladus10.kn-bremen.de) Received: (from nox@localhost) by enceladus10.kn-bremen.de (8.14.5/8.14.5/Submit) id s16KCclE074813; Thu, 6 Feb 2014 21:12:38 +0100 (CET) (envelope-from nox) From: Juergen Lock Date: Thu, 6 Feb 2014 21:12:38 +0100 To: Shteryana Shopova Subject: Re: kqemu patch for CURRENT/10-STABLE (was Re: Linux on BHyVe in 10.0-RELEASE ) Message-ID: <20140206201238.GA74665@enceladus10.kn-bremen.de> References: <20140206175919.GA67849@enceladus10.kn-bremen.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: nox@FreeBSD.org, Juergen Lock , freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 06 Feb 2014 20:14:34 -0000 On Thu, Feb 06, 2014 at 09:00:54PM +0200, Shteryana Shopova wrote: > On Thu, Feb 6, 2014 at 7:59 PM, Juergen Lock wrote: > > On Thu, Feb 06, 2014 at 05:16:15PM +0200, Shteryana Shopova wrote: > >> Hi all, > >> > >> Sorry for top posting but I'm new to the list and came across this > >> thread while playing with bhyve these days. To apply the patch - > >> > >> #cp patch-unit3minorfix /usr/ports/emulators/kqemu-kmod/files/ > >> > >> compile and install the module. > >> > >> I've been running kqemu under current with the attached patch (plain > >> text below in case the attachment is removed) for a couple of months > >> now and the module is loaded successfully - > >> > >> root@demetra:/usr/ports/emulators/kqemu-kmod # dmesg | tail -n 10 | grep kqemu > >> kqemu version 0x00010300 > >> kqemu: KQEMU installed, max_locked_mem=4120624kB. > >> root@demetra:/usr/ports/emulators/kqemu-kmod # uname -v > >> FreeBSD 11.0-CURRENT #6 r260863: Sun Jan 19 02:57:49 EET 2014 > >> > >> The original commit that broke kqemu-kmod is from March 9th, 2013, so > >> the patch should be applicable to 10-STABLE too. Reports on > >> success/failures welcome. > >> > >> cheers, > >> Shteryana > >> > >> P.S. Example on getting a headless VM with vbox - > >> > >> #VBoxManage createvm --name MyServer --ostype Windows7 --register > >> #VBoxManage createhd --filename "MyServer.vdi" --size 200000 > >> #VBoxManage storagectl MyServer --name "IDE Controller" --add ide > >> --controller PIIX3 > >> #VBoxManage storageattach MyServer --storagectl "IDE Controller" > >> --port 0 --device 1 --type hdd --medium "MyServer.vdi" > >> #VBoxManage storageattach MyServer --storagectl "IDE Controller" > >> --port 1 --device 0 --type dvddrive --medium > >> /home/myserver/install.iso > >> #VBoxManage modifyvm MyServer --nic1 bridged --cableconnected1 on > >> --bridgeadapter1 em0 --nictype1 82540EM > >> #VBoxManage modifyvm MyServer --memory 1024 --acpi on --boot1 dvd > >> #VBoxHeadless -n -m 5901 -s "MyServer" > >> > >> The VM is then accessible via vncviewer to the IP of the original > >> machine port 5901 > >> > >> --- kqemu-freebsd.c.orig 2014-02-06 16:03:15.881335406 +0200 > >> +++ kqemu-freebsd.c 2014-02-06 16:04:25.951329106 +0200 > >> @@ -109,7 +109,12 @@ > >> vm_offset_t va; > >> vm_paddr_t pa; > >> > >> +#if __FreeBSD_version >= 1000030 > >> + va = kmem_malloc(kernel_map, PAGE_SIZE, M_WAITOK); > >> +#else > >> va = kmem_alloc(kernel_map, PAGE_SIZE); > >> +#endif > >> + > >> if (va == 0) { > >> kqemu_log("kqemu_alloc_zeroed_page: NULL\n"); > >> return NULL; > > > > Oh well kqemu isn't even used by vbox, it's for emulaotors/qemu when > > Well, the VirtualBox off topic was caused by someone saying in an earlier thread > > "me and > Dee (personally and not as the petitecloud development team) would be > willing to give $50 to anyone who can get kqemu running on 10 and/or show > how to get vbox to work headless" > > > > built with the KQEMU knob and run with -enable-kqemu or -kernel-kqemu, > > and fixing _that_ needs most likely more changes than this. (I.e. I > > think I tried something similar and only got a panic. And also qemu > > Did you really try it? Can you explain then why it works for me with > both kqemu-kmod-devel and kqemu-kmod? > Can you please explain why this commit - > http://svnweb.freebsd.org/base?view=revision&revision=248084 - is > (ir-)relevant to the patch proposed? > > > uses kqemu-kmod-devel, kqemu-kmod is only left for people still using > > even older qemu forks.) > > > > Sorry... > > Juergen > > cheers, > Shteryana Shopova The commit does look relevant but testing your patch on a 10.0-RC1 vbox guest (it's what I had available) with the RC1 iso like so: # kldload kqemu % qemu-system-x86_64 -cdrom /dev/cd0 -m 512 -curses -enable-kqemu panics like this: ---------------------------------------------------------- 10rc1amd64mbr2 dumped core - see /var/crash/vmcore.1 Thu Feb 6 20:58:44 CET 2014 FreeBSD 10rc1amd64mbr2 10.0-RC1 FreeBSD 10.0-RC1 #0 r259068: Sat Dec 7 17:45:20 UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 panic: page fault GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x208 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80b06f77 stack pointer = 0x28:0xfffffe023ad436e0 frame pointer = 0x28:0xfffffe023ad43760 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 905 (qemu-system-x86_64) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff808e7d30 at kdb_backtrace+0x60 #1 0xffffffff808af815 at panic+0x155 #2 0xffffffff80c8e552 at trap_fatal+0x3a2 #3 0xffffffff80c8e829 at trap_pfault+0x2c9 #4 0xffffffff80c8dfb6 at trap+0x5e6 #5 0xffffffff80c75252 at calltrap+0x8 #6 0xffffffff808fad2c at vmem_alloc+0x5c #7 0xffffffff80b0f788 at kmem_malloc+0x38 #8 0xffffffff81a15739 at kqemu_alloc_zeroed_page+0x29 #9 0xffffffff81a12288 at mon_alloc_page+0x18 Uptime: 13m13s Dumping 391 out of 8169 MB:..5%..13%..21%..33%..41%..54%..62%..74%..82%..95% Reading symbols from /boot/modules/kqemu.ko...done. Loaded symbols for /boot/modules/kqemu.ko #0 doadump (textdump=) at pcpu.h:219 219 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump (textdump=) at pcpu.h:219 #1 0xffffffff808af490 in kern_reboot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:447 #2 0xffffffff808af854 in panic (fmt=) at /usr/src/sys/kern/kern_shutdown.c:754 #3 0xffffffff80c8e552 in trap_fatal (frame=, eva=) at /usr/src/sys/amd64/amd64/trap.c:882 #4 0xffffffff80c8e829 in trap_pfault (frame=0xfffffe023ad43630, usermode=0) at /usr/src/sys/amd64/amd64/trap.c:699 #5 0xffffffff80c8dfb6 in trap (frame=0xfffffe023ad43630) at /usr/src/sys/amd64/amd64/trap.c:463 #6 0xffffffff80c75252 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:232 #7 0xffffffff80b06f77 in uma_zalloc_arg (zone=0x0, udata=0x0, flags=8194) at /usr/src/sys/vm/uma_core.c:2115 #8 0xffffffff808fad2c in vmem_alloc (vm=, size=, flags=8194, addrp=0xfffffe023ad437a8) at uma.h:336 #9 0xffffffff80b0f788 in kmem_malloc (vmem=0xfffff80002000000, size=4096, flags=2) at /usr/src/sys/vm/vm_kern.c:314 #10 0xffffffff81a15739 in kqemu_alloc_zeroed_page () from /boot/modules/kqemu.ko #11 0xfffffe023ad43838 in ?? () #12 0x00000000f0000000 in ?? () #13 0xffffffff81a12288 in mon_alloc_page () from /boot/modules/kqemu.ko #14 0x0000000000000000 in ?? () Current language: auto; currently minimal (kgdb) ------------------------------------------------------------------------ ps -axl UID PID PPID CPU PRI NI VSZ RSS MWCHAN STAT TT TIME COMMAND 0 0 0 0 -92 0 0 0 - DLs - 0:00.01 [kernel] 0 1 0 0 20 0 9428 0 wait DLs - 0:00.01 [init] 0 2 0 0 -16 0 0 0 waiting_ DL - 0:00.00 [sctp_iterator] 0 3 0 0 -16 0 0 0 ccb_scan DL - 0:00.00 [xpt_thrd] 0 4 0 0 -16 0 0 0 psleep DL - 0:00.00 [pagedaemon] 0 5 0 0 -16 0 0 0 psleep DL - 0:00.00 [vmdaemon] 0 6 0 0 155 0 0 0 pgzero DL - 0:00.00 [pagezero] 0 7 0 0 -16 0 0 0 psleep DL - 0:00.00 [bufdaemon] 0 8 0 0 -16 0 0 0 vlruwt DL - 0:00.00 [vnlru] 0 9 0 0 16 0 0 0 syncer DL - 0:00.00 [syncer] 0 10 0 0 -16 0 0 0 audit_wo DL - 0:00.00 [audit] 0 11 0 0 155 0 0 0 - RL - 0:02.97 [idle] 0 12 0 0 -84 0 0 0 - WL - 0:00.09 [intr] 0 13 0 0 -8 0 0 0 - DL - 0:00.03 [geom] 0 14 0 0 -16 0 0 0 - RL - 0:00.00 [rand_harvestq] 0 15 0 0 -68 0 0 0 - DL - 0:00.01 [usb] 0 16 0 0 20 0 0 0 sdflush DL - 0:00.00 [softdepflush] 0 111 1 0 52 0 12264 0 pause Ds - 0:00.00 [adjkerntz] 0 466 1 0 20 0 13584 0 select Ds - 0:00.00 [devd] 0 575 1 0 20 0 14424 0 select Ds - 0:00.00 [syslogd] 0 702 1 0 20 0 60816 0 select Ds - 0:00.00 [sshd] 0 705 1 0 20 0 23980 0 select Ds - 0:00.00 [sendmail] 25 708 1 0 52 0 23980 0 pause Ds - 0:00.00 [sendmail] 0 712 1 0 20 0 16520 0 nanslp Ds - 0:00.00 [cron] 0 729 1 0 52 0 16628 0 select Ds - 0:00.00 [moused] 0 771 1 0 23 0 47656 0 wait Ds - 0:00.00 [login] 0 772 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 773 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 774 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 775 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 776 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 777 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 0 778 1 0 52 0 14420 0 ttyin Ds+ - 0:00.00 [getty] 1000 779 771 0 20 0 16988 0 ttyin D+ - 0:00.01 [sh] 0 830 702 0 20 0 86084 0 select Ds - 0:00.00 [sshd] 1000 833 830 0 20 0 86084 0 select D - 0:00.05 [sshd] 1000 834 833 0 24 0 16988 0 wait Ds - 0:00.00 [sh] 1000 867 834 0 24 0 30716 0 pause D - 0:00.17 [zsh] 1000 905 867 0 24 0 830672 0 - R+ - 0:00.00 [qemu-system-x86_ ------------------------------------------------------------------------ vmstat -s 327710 cpu context switches 44086 device interrupts 60750 software interrupts 255005 traps 10264404 system calls 16 kernel threads created 729 fork() calls 160 vfork() calls 0 rfork() calls 0 swap pager pageins 0 swap pager pages paged in 0 swap pager pageouts 0 swap pager pages paged out 591 vnode pager pageins 4413 vnode pager pages paged in 0 vnode pager pageouts 0 vnode pager pages paged out 0 page daemon wakeups 0 pages examined by the page daemon 0 pages reactivated 27914 copy-on-write faults 154 copy-on-write optimized faults 102913 zero fill pages zeroed 0 zero fill pages prezeroed 1 intransit blocking page faults 143560 total VM faults taken 489 page faults requiring I/O 0 pages affected by kernel thread creation 26989 pages affected by fork() 6483 pages affected by vfork() 0 pages affected by rfork() 0 pages cached 175031 pages freed 0 pages freed by daemon 0 pages freed by exiting processes 4115 pages active 3862 pages inactive 0 pages in VM cache 64069 pages wired down 1962428 pages free 4096 bytes per page 119708 total name lookups cache hits (87% pos + 5% neg) system 0% per-directory deletions 0%, falsehits 0%, toolong 0% ------------------------------------------------------------------------ vmstat -m Type InUse MemUse HighUse Requests Size(s) USBdev 5 1K - 5 32,64,128 cdev 9 3K - 9 256 entropy 1026 65K - 1033 32,64,4096 CAM SIM 4 1K - 4 256 filedesc 39 78K - 906 2048 sigio 1 1K - 1 64 filecaps 0 0K - 2 64 kdtrace 110 21K - 978 64,256 kenv 72 11K - 80 16,32,64,128 kqueue 0 0K - 84 256,2048 proc-args 23 2K - 513 16,32,64,128,256 kbdmux 6 18K - 6 16,512,1024,2048 hhook 2 1K - 2 256 ithread 61 11K - 61 32,128,256 LED 2 1K - 2 16,128 KTRACE 100 13K - 100 128 CAM XPT 24 2K - 75 32,64,128,256,1024 scsi_cd 0 0K - 25 16,1024 linker 162 29K - 172 16,32,64,128,256,512,1024,2048,4096 lockf 20 3K - 447 64,128 loginclass 2 1K - 20 64 devbuf 16680 35084K - 16736 16,32,64,128,256,512,1024,2048,4096 temp 11 1K - 925 16,32,64,128,256,1024,2048 ip6ndp 4 1K - 5 64,128 module 476 60K - 476 128 mtx_pool 2 16K - 2 pmchooks 1 1K - 1 128 pgrp 22 3K - 112 128 session 19 3K - 23 128 proc 2 32K - 2 subproc 85 179K - 952 512,4096 cred 50 8K - 7266 64,256 plimit 14 4K - 266 256 uidinfo 4 5K - 10 128,4096 ac97 2 1K - 2 16,512 CAM DEV 6 12K - 13 2048 pci_link 8 1K - 8 16,128 sysctl 0 0K - 188 16,32,64 sysctloid 1948 97K - 1985 16,32,64,128 sysctltmp 0 0K - 142 16,32,64,128 tidhash 1 32K - 1 callout 2 1416K - 2 umtx 150 19K - 150 128 p1003.1b 1 1K - 1 16 SWAP 2 957K - 2 64 bus 970 79K - 3051 16,32,64,128,256,1024 bus-sc 33 54K - 1595 16,32,64,128,256,512,1024,2048,4096 devstat 6 13K - 6 32,4096 eventhandler 92 8K - 92 64,128 kobj 330 1320K - 474 4096 Per-cpu 1 1K - 1 32 DEVFS3 97 25K - 113 256 DEVFS1 77 39K - 84 512 rman 105 13K - 494 16,32,128 sbuf 0 0K - 532 16,32,64,128,256,512,1024,2048,4096 DEVFS 15 1K - 16 16,128 taskqueue 15 3K - 15 16,32,256 Unitno 20 2K - 184 32,64 vmem 3 136K - 5 1024,2048,4096 ioctlops 1 1K - 46822 16,32,64,128,256,512,1024 select 12 2K - 12 128 iov 0 0K - 349776 16,64,128,256,512 msg 4 30K - 4 2048,4096 sem 4 106K - 4 2048,4096 shm 1 20K - 1 tty 18 18K - 18 1024 pts 1 1K - 1 256 mbuf_tag 0 0K - 9 32 shmfd 1 8K - 1 soname 3 1K - 5080 16,32,128 pcb 15 1173K - 79 16,32,128,1024,2048 biobuf 0 0K - 1 2048 vfscache 1 2048K - 1 cl_savebuf 0 0K - 21 64 vfs_hash 1 1024K - 1 vnodes 1 1K - 1 256 mount 16 1K - 99 16,32,64,128,256 vnodemarker 0 0K - 63 512 BPF 2 1K - 2 128 ifnet 3 5K - 3 128,2048 ifaddr 35 13K - 35 32,64,128,256,512,2048,4096 ether_multi 40 3K - 46 16,32,64 clone 7 1K - 7 128 arpcom 1 1K - 1 16 lltable 10 4K - 11 256,512 routetbl 37 6K - 148 32,64,128,256,512 igmp 2 1K - 2 256 in_multi 2 1K - 2 256 sctp_a_it 0 0K - 3 16 sctp_vrf 1 1K - 1 64 sctp_ifa 5 1K - 5 128 sctp_ifn 2 1K - 2 128 sctp_iter 0 0K - 3 256 hostcache 1 28K - 1 syncache 1 64K - 1 in6_multi 25 3K - 25 32,256 mld 2 1K - 2 128 NFS FHA 1 2K - 1 2048 rpc 2 1K - 2 256 audit_evclass 187 6K - 228 32 pagedep 1 256K - 147 256 inodedep 1 1024K - 2510 512 bmsafemap 1 8K - 1333 256 newblk 1 2048K - 3703 256 indirdep 0 0K - 14 128 freefrag 0 0K - 142 128 freeblks 0 0K - 1165 256 freefile 0 0K - 1166 64 diradd 0 0K - 1308 128 mkdir 0 0K - 92 128 dirrem 0 0K - 1178 128 newdirblk 0 0K - 47 64 freework 1 1K - 1467 64,128 freedep 0 0K - 11 64 jaddref 0 0K - 1400 128 jremref 0 0K - 1266 128 jnewblk 0 0K - 3702 128 jfreefrag 0 0K - 142 128 jseg 0 0K - 101 128 jsegdep 0 0K - 6510 64 sbdep 0 0K - 20 64 savedino 0 0K - 1216 256 jblocks 2 1K - 2 128,256 ufs_dirhash 36 7K - 42 16,32,64,128,256,512 ufs_quota 1 1024K - 1 ufs_mount 3 13K - 3 512,4096 vm_pgdata 2 1025K - 2 128 pfs_nodes 21 6K - 21 256 GEOM 63 19K - 525 16,32,64,128,256,512,1024,2048 feeder 12 1K - 14 32,128 atkbddev 2 1K - 2 64 CAM CCB 34 68K - 46 2048 mixer 1 4K - 1 4096 raid_data 0 0K - 78 32,128,256 acpiintr 1 1K - 1 64 md_nvidia_data 0 0K - 13 512 acpica 2073 233K - 25623 16,32,64,128,256,1024,4096 md_sii_data 0 0K - 13 512 CAM path 8 1K - 34 32 CAM periph 6 2K - 21 16,32,64,128,256 acpitask 1 8K - 1 apmdev 1 1K - 1 128 madt_table 0 0K - 1 4096 ata_pci 1 1K - 1 64 acpisem 17 3K - 17 128 CAM queue 13 4K - 48 16,32,512 acpidev 24 2K - 24 64 CAM dev queue 4 1K - 4 32 io_apic 1 2K - 1 2048 MCA 1 1K - 1 128 nexusdev 3 1K - 3 16 isadev 9 2K - 9 128 isofs_mount 0 0K - 1 256 isofs_node 0 0K - 30 256 USB 6 5K - 6 16,128,512,4096 kqemu 3 10245K - 3 32,4096 ------------------------------------------------------------------------ vmstat -z ITEM SIZE LIMIT USED FREE REQ FAIL SLEEP UMA Kegs: 384, 0, 95, 5, 95, 0, 0 UMA Zones: 768, 0, 95, 0, 95, 0, 0 UMA Slabs: 80, 0, 1310, 40, 1945, 0, 0 UMA RCntSlabs: 88, 0, 170, 10, 170, 0, 0 UMA Hash: 256, 0, 9, 6, 9, 0, 0 4 Bucket: 32, 0, 9, 116, 833, 0, 0 8 Bucket: 64, 0, 6, 180, 114, 0, 0 16 Bucket: 128, 0, 11, 144, 31, 35, 0 32 Bucket: 256, 0, 120, 15, 641, 99, 0 64 Bucket: 512, 0, 213, 3, 737, 712, 0 128 Bucket: 1024, 0, 119, 1, 611, 10, 0 vmem btag: 56, 0, 9195, 106, 9195, 131, 0 VM OBJECT: 256, 0, 2386, 179, 13622, 0, 0 RADIX NODE: 144, 0, 4899, 2310, 34336, 49, 0 MAP: 240, 0, 3, 61, 3, 0, 0 KMAP ENTRY: 128, 0, 6, 149, 6, 0, 0 MAP ENTRY: 128, 0, 767, 256, 29243, 0, 0 VMSPACE: 448, 0, 23, 13, 890, 0, 0 fakepg: 104, 0, 0, 0, 0, 0, 0 mt_zone: 4112, 0, 343, 0, 343, 0, 0 16: 16, 0, 1053, 202, 58756, 0, 0 32: 32, 0, 1138, 112, 3946, 0, 0 64: 64, 0, 10676, 5010, 375287, 0, 0 128: 128, 0, 3418, 6223, 30064, 0, 0 256: 256, 0, 422, 3913, 13602, 0, 0 512: 512, 0, 210, 2262, 3459, 0, 0 1024: 1024, 0, 35, 61, 1469, 0, 0 2048: 2048, 0, 98, 8, 1147, 0, 0 4096: 4096, 0, 414, 5, 1556, 0, 0 SLEEPQUEUE: 80, 0, 76, 79, 76, 0, 0 uint64 pcpu: 8, 0, 1332, 76, 1332, 0, 0 Files: 80, 0, 72, 78, 10087, 0, 0 TURNSTILE: 136, 0, 76, 64, 76, 0, 0 rl_entry: 40, 0, 30, 170, 30, 0, 0 umtx pi: 96, 0, 0, 0, 0, 0, 0 MAC labels: 40, 0, 0, 0, 0, 0, 0 PROC: 1208, 0, 38, 7, 905, 0, 0 THREAD: 1168, 0, 70, 5, 71, 0, 0 cpuset: 72, 0, 42, 123, 42, 0, 0 audit_record: 1248, 0, 0, 0, 0, 0, 0 mbuf_packet: 256, 3255315, 256, 84, 9612, 335, 0 mbuf: 256, 3255315, 2, 128, 5907, 0, 0 mbuf_cluster: 2048, 508644, 335, 1, 335, 0, 0 mbuf_jumbo_page: 4096, 254321, 0, 2, 7, 0, 0 mbuf_jumbo_9k: 9216, 226062, 0, 0, 0, 0, 0 mbuf_jumbo_16k: 16384, 169544, 0, 0, 0, 0, 0 mbuf_ext_refcnt: 4, 0, 0, 0, 0, 0, 0 g_bio: 248, 0, 0, 3552, 94445, 0, 0 ttyinq: 160, 0, 135, 65, 495, 0, 0 ttyoutq: 256, 0, 72, 63, 264, 0, 0 ata_request: 336, 0, 0, 33, 22961, 0, 0 vtnet_tx_hdr: 24, 0, 0, 0, 0, 0, 0 FPU_save_area: 512, 0, 0, 0, 0, 0, 0 VNODE: 472, 0, 2316, 1052, 3514, 0, 0 VNODEPOLL: 112, 0, 0, 0, 0, 0, 0 BUF TRIE: 144, 0, 345, 52629, 2625, 0, 0 NAMEI: 1024, 0, 0, 16, 29932, 0, 0 S VFS Cache: 108, 0, 1959, 71, 5122, 0, 0 STS VFS Cache: 148, 0, 0, 0, 0, 0, 0 L VFS Cache: 328, 0, 0, 0, 0, 0, 0 LTS VFS Cache: 368, 0, 0, 0, 0, 0, 0 DIRHASH: 1024, 0, 54, 14, 59, 0, 0 NCLNODE: 528, 0, 0, 0, 0, 0, 0 Mountpoints: 816, 0, 2, 13, 3, 0, 0 pipe: 744, 0, 3, 12, 492, 0, 0 procdesc: 128, 0, 0, 0, 0, 0, 0 ksiginfo: 112, 0, 38, 1012, 37529, 0, 0 itimer: 352, 0, 0, 0, 0, 0, 0 KNOTE: 128, 0, 0, 155, 86, 0, 0 socket: 696, 261425, 15, 15, 1013, 0, 0 ipq: 56, 15904, 0, 0, 0, 0, 0 udp_inpcb: 392, 261430, 2, 28, 145, 0, 0 udpcb: 16, 261542, 2, 249, 145, 0, 0 tcp_inpcb: 392, 261430, 4, 26, 17, 0, 0 tcpcb: 1024, 261428, 4, 12, 17, 0, 0 tcptw: 88, 27810, 0, 135, 1, 0, 0 syncache: 160, 15375, 0, 75, 1, 0, 0 hostcache: 136, 15370, 1, 86, 1, 0, 0 tcpreass: 40, 31800, 0, 200, 431, 0, 0 sackhole: 32, 0, 0, 0, 0, 0, 0 sctp_ep: 1408, 261426, 0, 0, 0, 0, 0 sctp_asoc: 2352, 40000, 0, 0, 0, 0, 0 sctp_laddr: 48, 80012, 0, 166, 4, 0, 0 sctp_raddr: 728, 80000, 0, 0, 0, 0, 0 sctp_chunk: 136, 400026, 0, 0, 0, 0, 0 sctp_readq: 104, 400026, 0, 0, 0, 0, 0 sctp_stream_msg_out: 104, 400026, 0, 0, 0, 0, 0 sctp_asconf: 40, 400000, 0, 0, 0, 0, 0 sctp_asconf_ack: 48, 400060, 0, 0, 0, 0, 0 ripcb: 392, 261430, 0, 0, 0, 0, 0 unpcb: 240, 261440, 9, 55, 846, 0, 0 rtentry: 200, 0, 17, 63, 17, 0, 0 selfd: 56, 0, 27, 115, 32990, 0, 0 SWAPMETA: 288, 1017289, 0, 0, 0, 0, 0 FFS inode: 168, 0, 2275, 1083, 3441, 0, 0 FFS1 dinode: 128, 0, 0, 0, 0, 0, 0 FFS2 dinode: 256, 0, 2275, 1085, 3441, 0, 0 ------------------------------------------------------------------------ vmstat -i interrupt total rate irq1: atkbd0 1271 90 irq15: ata1 22961 1640 irq19: em0 14275 1019 irq21: pcm0 ahci0 5579 398 cpu0:timer 66166 4726 Total 110252 7875 ------------------------------------------------------------------------ pstat -T 72/261421 files 0M/6958M swap space ------------------------------------------------------------------------ pstat -s Device 512-blocks Used Avail Capacity /dev/ada0s1b 14251224 0 14251224 0% ------------------------------------------------------------------------ iostat iostat: kvm_read(_tk_nin): invalid address (0x0) iostat: disabling TTY statistics ada0 cd0 pass0 cpu KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 40.75 462 18.38 2.00 1567 3.06 0.00 0 0.00 2 0 3 0 95 ------------------------------------------------------------------------ ipcs -a Message Queues: T ID KEY MODE OWNER GROUP CREATOR CGROUP CBYTES QNUM QBYTES LSPID LRPID STIME RTIME CTIME Shared Memory: T ID KEY MODE OWNER GROUP CREATOR CGROUP NATTCH SEGSZ CPID LPID ATIME DTIME CTIME Semaphores: T ID KEY MODE OWNER GROUP CREATOR CGROUP NSEMS OTIME CTIME ------------------------------------------------------------------------ ipcs -T msginfo: msgmax: 16384 (max characters in a message) msgmni: 40 (# of message queues) msgmnb: 2048 (max characters in a message queue) msgtql: 40 (max # of messages in system) msgssz: 8 (size of a message segment) msgseg: 2048 (# of message segments in system) shminfo: shmmax: 536870912 (max shared memory segment size) shmmin: 1 (min shared memory segment size) shmmni: 192 (max number of shared memory identifiers) shmseg: 128 (max shared memory segments per process) shmall: 131072 (max amount of shared memory in pages) seminfo: semmni: 50 (# of semaphore identifiers) semmns: 340 (# of semaphores in system) semmnu: 150 (# of undo structures in system) semmsl: 340 (max # of semaphores per id) semopm: 100 (max # of operations per semop call) semume: 50 (max # of undo entries per process) semusz: 632 (size in bytes of undo structure) semvmx: 32767 (semaphore maximum value) semaem: 16384 (adjust on exit max value) ------------------------------------------------------------------------ nfsstat Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 0 0 0 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 0 0 0 0 0 0 0 0 BioRLHits Misses BioD Hits Misses DirE Hits Misses Accs Hits Misses 0 0 0 0 0 0 0 0 Server Info: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit 0 0 0 0 0 Server Ret-Failed 0 Server Faults 0 Server Cache Stats: Inprog Idem Non-idem Misses 0 0 0 0 Server Write Gathering: WriteOps WriteRPC Opsaved 0 0 0 ------------------------------------------------------------------------ [...] ------------------------------------------------------------------------ fstat fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 13 at 0x200007fffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 7 at 0x200007fffffffff fstat: can't read file 8 at 0x4000000001fffff fstat: can't read file 10 at 0x780000ffff fstat: can't read file 13 at 0x200007fffffffff fstat: can't read file 14 at 0x4000000001fffff fstat: can't read file 16 at 0x780000ffff fstat: can't read file 19 at 0x200007fffffffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff fstat: can't read file 4 at 0x780000ffff fstat: can't read file 1 at 0x200007fffffffff fstat: can't read file 2 at 0x4000000001fffff USER CMD PID FD MOUNT INUM MODE SZ|DV R/W nox qemu-system-x86_64 905 root / 2 drwxr-xr-x 1024 r nox qemu-system-x86_64 905 wd / 561834 drwxr-xr-x 512 r nox qemu-system-x86_64 905 text / 573033 -rwxr-xr-x 2100864 r nox qemu-system-x86_64 905 ctty /dev 79 crw--w---- pts/0 rw nox qemu-system-x86_64 905 0 /dev 79 crw--w---- pts/0 rw nox qemu-system-x86_64 905 6 /dev 79 crw--w---- pts/0 rw nox zsh 867 root / 2 drwxr-xr-x 1024 r nox zsh 867 wd / 561834 drwxr-xr-x 512 r nox zsh 867 text / 562100 -r-xr-xr-x 652256 r nox zsh 867 ctty /dev 79 crw--w---- pts/0 rw nox zsh 867 0 /dev 79 crw--w---- pts/0 rw nox zsh 867 6 /dev 79 crw--w---- pts/0 rw nox zsh 867 12 /dev 79 crw--w---- pts/0 rw nox sh 834 root / 2 drwxr-xr-x 1024 r nox sh 834 wd / 561834 drwxr-xr-x 512 r nox sh 834 text / 561795 -r-xr-xr-x 141600 r nox sh 834 ctty /dev 79 crw--w---- pts/0 rw nox sh 834 0 /dev 79 crw--w---- pts/0 rw nox sh 834 6 /dev 79 crw--w---- pts/0 rw nox sshd 833 root / 2 drwxr-xr-x 1024 r nox sshd 833 wd / 2 drwxr-xr-x 1024 r nox sshd 833 text / 481810 -r-xr-xr-x 291992 r nox sshd 833 0 /dev 15 crw-rw-rw- null rw nox sshd 833 6 /dev 15 crw-rw-rw- null rw root sshd 830 root / 2 drwxr-xr-x 1024 r root sshd 830 wd / 2 drwxr-xr-x 1024 r root sshd 830 text / 481810 -r-xr-xr-x 291992 r root sshd 830 0 /dev 15 crw-rw-rw- null r nox sh 779 root / 2 drwxr-xr-x 1024 r nox sh 779 wd / 561834 drwxr-xr-x 512 r nox sh 779 text / 561795 -r-xr-xr-x 141600 r nox sh 779 ctty /dev 41 crw------- ttyv0 rw nox sh 779 0 /dev 41 crw------- ttyv0 rw nox sh 779 6 /dev 41 crw------- ttyv0 rw root getty 778 root / 2 drwxr-xr-x 1024 r root getty 778 wd / 2 drwxr-xr-x 1024 r root getty 778 text / 490119 -r-xr-xr-x 27952 r root getty 778 ctty /dev 48 crw------- ttyv7 rw root getty 778 0 /dev 48 crw------- ttyv7 rw root getty 777 root / 2 drwxr-xr-x 1024 r root getty 777 wd / 2 drwxr-xr-x 1024 r root getty 777 text / 490119 -r-xr-xr-x 27952 r root getty 777 ctty /dev 47 crw------- ttyv6 rw root getty 777 0 /dev 47 crw------- ttyv6 rw root getty 776 root / 2 drwxr-xr-x 1024 r root getty 776 wd / 2 drwxr-xr-x 1024 r root getty 776 text / 490119 -r-xr-xr-x 27952 r root getty 776 ctty /dev 46 crw------- ttyv5 rw root getty 776 0 /dev 46 crw------- ttyv5 rw root getty 775 root / 2 drwxr-xr-x 1024 r root getty 775 wd / 2 drwxr-xr-x 1024 r root getty 775 text / 490119 -r-xr-xr-x 27952 r root getty 775 ctty /dev 45 crw------- ttyv4 rw root getty 775 0 /dev 45 crw------- ttyv4 rw root getty 774 root / 2 drwxr-xr-x 1024 r root getty 774 wd / 2 drwxr-xr-x 1024 r root getty 774 text / 490119 -r-xr-xr-x 27952 r root getty 774 ctty /dev 44 crw------- ttyv3 rw root getty 774 0 /dev 44 crw------- ttyv3 rw root getty 773 root / 2 drwxr-xr-x 1024 r root getty 773 wd / 2 drwxr-xr-x 1024 r root getty 773 text / 490119 -r-xr-xr-x 27952 r root getty 773 ctty /dev 43 crw------- ttyv2 rw root getty 773 0 /dev 43 crw------- ttyv2 rw root getty 772 root / 2 drwxr-xr-x 1024 r root getty 772 wd / 2 drwxr-xr-x 1024 r root getty 772 text / 490119 -r-xr-xr-x 27952 r root getty 772 ctty /dev 42 crw------- ttyv1 rw root getty 772 0 /dev 42 crw------- ttyv1 rw root login 771 root / 2 drwxr-xr-x 1024 r root login 771 wd / 561834 drwxr-xr-x 512 r root login 771 text / 493211 -r-sr-xr-x 24728 r root login 771 ctty /dev 41 crw------- ttyv0 rw root login 771 0 /dev 41 crw------- ttyv0 rw root moused 729 root / 2 drwxr-xr-x 1024 r root moused 729 wd / 2 drwxr-xr-x 1024 r root moused 729 text / 481610 -r-xr-xr-x 37848 r root moused 729 0 /dev 15 crw-rw-rw- null rw root cron 712 root / 2 drwxr-xr-x 1024 r root cron 712 wd / 882826 drwxr-x--- 512 r root cron 712 text / 481720 -r-xr-xr-x 41008 r root cron 712 0 /dev 15 crw-rw-rw- null rw smmsp sendmail 708 root / 2 drwxr-xr-x 1024 r smmsp sendmail 708 wd / 882842 drwxrwx--- 512 r smmsp sendmail 708 text / 490295 -r-xr-sr-x 676048 r smmsp sendmail 708 0 /dev 15 crw-rw-rw- null r root sendmail 705 root / 2 drwxr-xr-x 1024 r root sendmail 705 wd / 882845 drwxr-xr-x 512 r root sendmail 705 text / 490295 -r-xr-sr-x 676048 r root sendmail 705 0 /dev 15 crw-rw-rw- null r root sshd 702 root / 2 drwxr-xr-x 1024 r root sshd 702 wd / 2 drwxr-xr-x 1024 r root sshd 702 text / 481810 -r-xr-xr-x 291992 r root sshd 702 0 /dev 15 crw-rw-rw- null rw root syslogd 575 root / 2 drwxr-xr-x 1024 r root syslogd 575 wd / 2 drwxr-xr-x 1024 r root syslogd 575 text / 481625 -r-xr-xr-x 39632 r root syslogd 575 0 /dev 15 crw-rw-rw- null rw root syslogd 575 6 /dev 15 crw-rw-rw- null rw root syslogd 575 12 /dev 15 crw-rw-rw- null rw root syslogd 575 18 / 882910 -rw------- 3 w root devd 466 root / 2 drwxr-xr-x 1024 r root devd 466 wd / 2 drwxr-xr-x 1024 r root devd 466 text / 963141 -r-xr-xr-x 1062424 r root devd 466 0 /dev 15 crw-rw-rw- null rw root devd 466 6 /dev 15 crw-rw-rw- null rw root adjkerntz 111 root / 2 drwxr-xr-x 1024 r root adjkerntz 111 wd / 2 drwxr-xr-x 1024 r root adjkerntz 111 text / 963139 -r-xr-xr-x 9160 r root adjkerntz 111 0 /dev 15 crw-rw-rw- null rw root init 1 root / 2 drwxr-xr-x 1024 r root init 1 wd / 2 drwxr-xr-x 1024 r root init 1 text / 963119 -r-xr-xr-x 938256 r root kernel 0 root / 2 drwxr-xr-x 1024 r root kernel 0 wd / 2 drwxr-xr-x 1024 r ------------------------------------------------------------------------ dmesg Table 'FACP' at 0xdfff00f0 Table 'APIC' at 0xdfff0240 APIC: Found table at 0xdfff0240 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-RC1 #0 r259068: Sat Dec 7 17:45:20 UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 Preloaded elf kernel "/boot/kernel/kernel" at 0xffffffff817f2000. Calibrating TSC clock ... TSC clock: 3399310247 Hz CPU: Intel(R) Xeon(R) CPU E3-1245 v3 @ 3.40GHz (3399.31-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x306c3 Family = 0x6 Model = 0x3c Stepping = 3 Features=0x783fbff Features2=0x209 AMD Features=0x28100800 AMD Features2=0x1 real memory = 9126805504 (8704 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009bfff, 634880 bytes (155 pages) 0x0000000000100000 - 0x00000000001fffff, 1048576 bytes (256 pages) 0x000000000181f000 - 0x00000000dffeffff, 3732738048 bytes (911313 pages) 0x0000000100000000 - 0x000000021221ffff, 4599185408 bytes (1122848 pages) avail memory = 8279642112 (7896 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: APIC: CPU 0 has ACPI ID 0 x86bios: IVT 0x000000-0x0004ff at 0xfffff80000000000 x86bios: SSEG 0x001000-0x001fff at 0xfffffe01f0fac000 x86bios: EBDA 0x09f000-0x09ffff at 0xfffff8000009f000 x86bios: ROM 0x0a0000-0x0fefff at 0xfffff800000a0000 XEN: CPU 0 has VCPU ID 0 ULE: setup cpu 0 ACPI: RSDP 0xe0000 00024 (v02 VBOX ) ACPI: XSDT 0xdfff0030 0003C (v01 VBOX VBOXXSDT 00000001 ASL 00000061) ACPI: FACP 0xdfff00f0 000F4 (v04 VBOX VBOXFACP 00000001 ASL 00000061) ACPI: DSDT 0xdfff0470 01B96 (v01 VBOX VBOXBIOS 00000002 INTL 20130823) ACPI: FACS 0xdfff0200 00040 ACPI: APIC 0xdfff0240 00054 (v02 VBOX VBOXAPIC 00000001 ASL 00000061) ACPI: SSDT 0xdfff02a0 001CC (v01 VBOX VBOXCPUT 00000002 INTL 20130823) MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level ioapic0 irqs 0-23 on motherboard cpu0 BSP: ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0x0fffffff lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x000000f0 pmc: 0x00010400 wlan: <802.11 Link Layer> snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 Hardware, Intel IvyBridge+ RNG: RDRAND is not present Hardware, VIA Nehemiah Padlock RNG: VIA Padlock RNG not present kbd: new array size 4 kbd1 at kbdmux0 mem: CPU supports MTRRs but not enabled null: nfslock: pseudo-device Falling back to random adaptor random: initialized VESA: INT 0x10 vector 0xc000:0x0022 VESA: information block 0000 56 45 53 41 00 02 20 7e 00 c0 01 00 00 00 22 00 0010 00 02 90 00 03 00 35 7e 00 c0 48 7e 00 c0 69 7e 0020 00 c0 00 01 01 01 02 01 03 01 04 01 05 01 06 01 0030 07 01 0d 01 0e 01 0f 01 10 01 11 01 12 01 13 01 0040 14 01 15 01 16 01 17 01 18 01 19 01 1a 01 1b 01 0050 40 01 41 01 42 01 43 01 44 01 45 01 46 01 47 01 0060 48 01 49 01 4a 01 4b 01 4c 01 ff ff 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0090 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0100 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0110 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0120 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0130 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0140 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0150 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0160 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0170 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0180 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0190 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01a0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01c0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 36 mode(s) found VESA: v2.0, 9216k memory, flags:0x1, mode table:0xfffffe01f0fe4022 (2000022) VESA: VirtualBox VESA BIOS VESA: Oracle Corporation Oracle VM VirtualBox VBE Adapter Oracle VM VirtualBox Version 4.3.6 io: VMBUS: load hptnr: R750/DC7280 controller driver v1.0 hpt27xx: RocketRAID 27xx controller driver v1.1 hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 acpi0: on motherboard ACPI: All ACPI Tables successfully acquired ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 ACPI: Executed 1 blocks of module-level executable AML code acpi0: Power Button (fixed) acpi0: Sleep Button (fixed) cpu0: on acpi0 cpu0: switching to generic Cx mode attimer0: port 0x40-0x43,0x50-0x53 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 ioapic0: routing intpin 2 (ISA IRQ 0) to lapic 0 vector 49 Event timer "i8254" frequency 1193182 Hz quality 100 ACPI timer: 1/3 1/14 1/2 1/13 1/2 1/14 1/2 1/13 1/16 1/14 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 9 10 11 Validation 0 11 N 0 5 9 10 11 After Disable 0 255 N 0 5 9 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 9 10 11 Validation 0 11 N 0 5 9 10 11 After Disable 0 255 N 0 5 9 10 11 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 5 9 10 11 Validation 0 10 N 0 5 9 10 11 After Disable 0 255 N 0 5 9 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 5 9 10 11 Validation 0 9 N 0 5 9 10 11 After Disable 0 255 N 0 5 9 10 11 pcib0: port 0xcf8-0xcff on acpi0 pcib0: decoding 4 range 0-0xcf7 pcib0: decoding 4 range 0xd00-0xffff pcib0: decoding 3 range 0xa0000-0xbffff pcib0: decoding 3 range 0xe0000000-0xffdfffff pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x1237, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0000, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7000, revid=0x00 domain=0, bus=0, slot=1, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0200, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x7111, revid=0x01 domain=0, bus=0, slot=1, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) pcib0: allocated type 4 (0x1f0-0x1f7) for rid 10 of pci0:0:1:1 pcib0: allocated type 4 (0x3f6-0x3f6) for rid 14 of pci0:0:1:1 pcib0: allocated type 4 (0x170-0x177) for rid 18 of pci0:0:1:1 pcib0: allocated type 4 (0x376-0x376) for rid 1c of pci0:0:1:1 map[20]: type I/O Port, range 32, base 0xd000, size 4, enabled pcib0: allocated type 4 (0xd000-0xd00f) for rid 20 of pci0:0:1:1 found-> vendor=0x80ee, dev=0xbeef, revid=0x00 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Prefetchable Memory, range 32, base 0xe0000000, size 24, enabled pcib0: allocated type 3 (0xe0000000-0xe0ffffff) for rid 10 of pci0:0:2:0 pcib0: matched entry for 0.2.INTA pcib0: slot 2 INTA hardwired to IRQ 18 found-> vendor=0x8086, dev=0x100e, revid=0x02 domain=0, bus=0, slot=3, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0230, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0xff (63750 ns), maxlat=0x00 (0 ns) intpin=a, irq=10 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf0000000, size 17, enabled pcib0: allocated type 3 (0xf0000000-0xf001ffff) for rid 10 of pci0:0:3:0 map[18]: type I/O Port, range 32, base 0xd010, size 3, enabled pcib0: allocated type 4 (0xd010-0xd017) for rid 18 of pci0:0:3:0 pcib0: matched entry for 0.3.INTA pcib0: slot 3 INTA hardwired to IRQ 19 found-> vendor=0x80ee, dev=0xcafe, revid=0x00 domain=0, bus=0, slot=4, func=0 class=08-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 map[10]: type I/O Port, range 32, base 0xd020, size 5, enabled pcib0: allocated type 4 (0xd020-0xd03f) for rid 10 of pci0:0:4:0 map[14]: type Memory, range 32, base 0xf0400000, size 22, enabled pcib0: allocated type 3 (0xf0400000-0xf07fffff) for rid 14 of pci0:0:4:0 map[18]: type Prefetchable Memory, range 32, base 0xf0800000, size 14, enabled pcib0: allocated type 3 (0xf0800000-0xf0803fff) for rid 18 of pci0:0:4:0 pcib0: matched entry for 0.4.INTA pcib0: slot 4 INTA hardwired to IRQ 20 found-> vendor=0x8086, dev=0x2415, revid=0x01 domain=0, bus=0, slot=5, func=0 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type I/O Port, range 32, base 0xd100, size 8, enabled pcib0: allocated type 4 (0xd100-0xd1ff) for rid 10 of pci0:0:5:0 map[14]: type I/O Port, range 32, base 0xd200, size 6, enabled pcib0: allocated type 4 (0xd200-0xd23f) for rid 14 of pci0:0:5:0 pcib0: matched entry for 0.5.INTA pcib0: slot 5 INTA hardwired to IRQ 21 found-> vendor=0x106b, dev=0x003f, revid=0x00 domain=0, bus=0, slot=6, func=0 class=0c-03-10, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Memory, range 32, base 0xf0804000, size 12, enabled pcib0: allocated type 3 (0xf0804000-0xf0804fff) for rid 10 of pci0:0:6:0 pcib0: matched entry for 0.6.INTA pcib0: slot 6 INTA hardwired to IRQ 22 found-> vendor=0x8086, dev=0x7113, revid=0x08 domain=0, bus=0, slot=7, func=0 class=06-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=9 pcib0: matched entry for 0.7.INTA pcib0: slot 7 INTA hardwired to IRQ 23 found-> vendor=0x8086, dev=0x2829, revid=0x02 domain=0, bus=0, slot=13, func=0 class=01-06-01, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0010, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 3 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xd240, size 3, enabled pcib0: allocated type 4 (0xd240-0xd247) for rid 10 of pci0:0:13:0 map[18]: type I/O Port, range 32, base 0xd250, size 3, enabled pcib0: allocated type 4 (0xd250-0xd257) for rid 18 of pci0:0:13:0 map[20]: type I/O Port, range 32, base 0xd260, size 4, enabled pcib0: allocated type 4 (0xd260-0xd26f) for rid 20 of pci0:0:13:0 map[24]: type Memory, range 32, base 0xf0806000, size 13, enabled pcib0: allocated type 3 (0xf0806000-0xf0807fff) for rid 24 of pci0:0:13:0 pcib0: matched entry for 0.13.INTA pcib0: slot 13 INTA hardwired to IRQ 21 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xd000-0xd00f at device 1.1 on pci0 ata0: at channel 0 on atapci0 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 50 ata1: at channel 1 on atapci0 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 51 vgapci0: mem 0xe0000000-0xe0ffffff irq 18 at device 2.0 on pci0 em0: port 0xd010-0xd017 mem 0xf0000000-0xf001ffff irq 19 at device 3.0 on pci0 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 0 vector 52 em0: bpf attached em0: Ethernet address: 08:00:27:1f:ac:04 em0: Link is up 1000 Mbps Full Duplex pci0: at device 4.0 (no driver attached) pcm0: port 0xd100-0xd1ff,0xd200-0xd23f irq 21 at device 5.0 on pci0 ioapic0: routing intpin 21 (PCI IRQ 21) to lapic 0 vector 53 pcm0: pcm0: Codec features 6 bit master volume, no 3D Stereo Enhancement pcm0: Primary codec extended features variable rate PCM, variable rate mic, reserved 5 pcm0: ac97 codec dac ready count: 0 pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "cd": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "line1": pcm0: Mixer "phin": pcm0: Mixer "phout": pcm0: Mixer "video": ohci0: mem 0xf0804000-0xf0804fff irq 22 at device 6.0 on pci0 ioapic0: routing intpin 22 (PCI IRQ 22) to lapic 0 vector 54 usbus0 on ohci0 ohci0: usbpf: Attached pci0: at device 7.0 (no driver attached) ahci0: port 0xd240-0xd247,0xd250-0xd257,0xd260-0xd26f mem 0xf0806000-0xf0807fff irq 21 at device 13.0 on pci0 ahci0: AHCI v1.10 with 1 3Gbps ports, Port Multiplier not supported ahci0: Caps: 64bit NCQ SS 3Gbps 32cmd CCC 1ports ahcich0: at channel 0 on ahci0 ahcich0: Caps: acpi_acad0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 ioapic0: routing intpin 1 (ISA IRQ 1) to lapic 0 vector 55 atkbd0: [GIANT-LOCKED] psm0: unable to allocate IRQ psmcpnp0: irq 12 on acpi0 psm0: current command byte:0045 psm0: irq 12 on atkbdc0 ioapic0: routing intpin 12 (ISA IRQ 12) to lapic 0 vector 56 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4-00, 5 buttons psm0: config:00000000, flags:00000008, packet size:4 psm0: syncmask:08, syncbits:00 ppc0: using extended I/O port range ACPI: Enabled 1 GPEs in block 00 to 07 acpi0: wakeup code va 0xfffffe023ac90000 pa 0x4000 ahc_isa_identify 0: ioport 0xc00 alloc failed ahc_isa_identify 1: ioport 0x1c00 alloc failed ahc_isa_identify 2: ioport 0x2c00 alloc failed ahc_isa_identify 3: ioport 0x3c00 alloc failed ahc_isa_identify 4: ioport 0x4c00 alloc failed ahc_isa_identify 5: ioport 0x5c00 alloc failed ahc_isa_identify 6: ioport 0x6c00 alloc failed ahc_isa_identify 7: ioport 0x7c00 alloc failed ahc_isa_identify 8: ioport 0x8c00 alloc failed ahc_isa_identify 9: ioport 0x9c00 alloc failed ahc_isa_identify 10: ioport 0xac00 alloc failed ahc_isa_identify 11: ioport 0xbc00 alloc failed ahc_isa_identify 12: ioport 0xcc00 alloc failed ahc_isa_identify 13: ioport 0xdc00 alloc failed ahc_isa_identify 14: ioport 0xec00 alloc failed ex_isa_identify() pcib0: allocated type 3 (0xa0000-0xa07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa0800-0xa0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1000-0xa17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa1800-0xa1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2000-0xa27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa2800-0xa2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3000-0xa37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa3800-0xa3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4000-0xa47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa4800-0xa4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5000-0xa57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa5800-0xa5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6000-0xa67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa6800-0xa6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7000-0xa77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa7800-0xa7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8000-0xa87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa8800-0xa8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9000-0xa97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xa9800-0xa9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa000-0xaa7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaa800-0xaafff) for rid 0 of orm0 pcib0: allocated type 3 (0xab000-0xab7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xab800-0xabfff) for rid 0 of orm0 pcib0: allocated type 3 (0xac000-0xac7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xac800-0xacfff) for rid 0 of orm0 pcib0: allocated type 3 (0xad000-0xad7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xad800-0xadfff) for rid 0 of orm0 pcib0: allocated type 3 (0xae000-0xae7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xae800-0xaefff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf000-0xaf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xaf800-0xaffff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0000-0xb07ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb0800-0xb0fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1000-0xb17ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb1800-0xb1fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2000-0xb27ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb2800-0xb2fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3000-0xb37ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb3800-0xb3fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4000-0xb47ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb4800-0xb4fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5000-0xb57ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb5800-0xb5fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6000-0xb67ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb6800-0xb6fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7000-0xb77ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb7800-0xb7fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8000-0xb87ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb8800-0xb8fff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9000-0xb97ff) for rid 0 of orm0 pcib0: allocated type 3 (0xb9800-0xb9fff) for rid 0 of orm0 pcib0: allocated type 3 (0xba000-0xba7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xba800-0xbafff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb000-0xbb7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbb800-0xbbfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc000-0xbc7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbc800-0xbcfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd000-0xbd7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbd800-0xbdfff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe000-0xbe7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbe800-0xbefff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf000-0xbf7ff) for rid 0 of orm0 pcib0: allocated type 3 (0xbf800-0xbffff) for rid 0 of orm0 isa_probe_children: disabling PnP devices atkbdc: atkbdc0 already exists; skipping it attimer: attimer0 already exists; skipping it sc: sc0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 pcib0: allocated type 4 (0x3c0-0x3df) for rid 0 of vga0 pcib0: allocated type 3 (0xa0000-0xbffff) for rid 0 of vga0 atrtc0: at port 0x70 irq 8 on isa0 pcib0: allocated type 4 (0x70-0x71) for rid 0 of atrtc0 atrtc0: registered as a time-of-day clock (resolution 1000000us, adjustment 0.500000000s) ioapic0: routing intpin 8 (ISA IRQ 8) to lapic 0 vector 57 Event timer "RTC" frequency 32768 Hz quality 0 pcib0: allocated type 4 (0x3f0-0x3f5) for rid 0 of fdc0 pcib0: allocated type 4 (0x3f7-0x3f7) for rid 1 of fdc0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: cannot reserve I/O port range ppc0 failed to probe at irq 7 on isa0 pcib0: allocated type 4 (0x3f8-0x3ff) for rid 0 of uart0 uart0 failed to probe at port 0x3f8-0x3ff irq 4 on isa0 pcib0: allocated type 4 (0x2f8-0x2ff) for rid 0 of uart1 uart1 failed to probe at port 0x2f8-0x2ff irq 3 on isa0 wbwd0 failed to probe on isa0 isa_probe_children: probing PnP devices Device configuration finished. procfs registered lapic: Divisor 2, Frequency 500006494 Hz Timecounters tick every 10.000 msec vlan: initialized, using hash tables with chaining tcp_init: net.inet.tcp.tcbhashsize auto tuned to 65536 lo0: bpf attached hptnr: no controller detected. hpt27xx: no controller detected. hptrr: no controller detected. pcm0: measured ac97 link rate at 36783 Hz usbus0: 12Mbps Full Speed USB v1.0 ata0: reset tp1 mask=00 ostat0=ff ostat1=ff ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ugen0.1: at usbus0 uhub0: on usbus0 ata1: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata1: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=00 stat1=00 devices=0x10000 ahcich0: AHCI reset... ahcich0: SATA connect time=0us status=00000123 ahcich0: AHCI reset: device found ahcich0: AHCI reset: device ready after 0ms ada0 at ahcich0 bus 0 scbus2 target 0 lun 0 ada0: ATA-6 SATA 2.x device ada0: Serial Number VBaac259e0-35cb4216 ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled GEOM: new disk ada0 ada0: 15150MB (31028816 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 cd0 at ata1 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: Serial Number VB2-01700376 cd0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) cd0: cd present [372330 x 2048 byte records] pass0 at ata1 bus 0 scbus1 target 0 lun 0 pass0: Removable CD-ROM SCSI-0 device pass0: Serial Number VB2-01700376 pass0: 33.300MB/s transfers (UDMA2, ATAPI 12bytes, PIO 65534bytes) pass1 at ahcich0 bus 0 scbus2 target 0 lun 0 pass1: ATA-6 SATA 2.x device pass1: Serial Number VBaac259e0-35cb4216 pass1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) pass1: Command Queueing enabled acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times GEOM: new disk cd0 random: unblocking device. Netvsc initializing... TSC timecounter discards lower 1 bit(s) Timecounter "TSC-low" frequency 1699655123 Hz quality 800 uhub0: 8 ports with 8 removable, self powered Trying to mount root from ufs:/dev/ada0s1a [rw]... start_init: trying /sbin/init Setting hostuuid: bb51a26c-8bc6-40ce-98c9-a03d018978be. Setting hostid: 0x1cbba4ff. Entropy harvesting: interrupts ethernet point_to_point swi. Starting file system checks: /dev/ada0s1a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0s1a: clean, 1451445 free (1029 frags, 181302 blocks, 0.1% fragmentation) Mounting local file systems:. Writing entropy file:. Setting hostname: 10rc1amd64mbr2. Starting Network: lo0 em0. lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 em0: flags=8843 metric 0 mtu 1500 options=9b ether 08:00:27:1f:ac:04 inet 10.0.0.44 netmask 0xff000000 broadcast 10.255.255.255 inet6 fe80::a00:27ff:fe1f:ac04%em0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active Starting devd. add net default: gateway 10.9 add net fe80::: gateway ::1 add net ff02::: gateway ::1 add net ::ffff:0.0.0.0: gateway ::1 add net ::0.0.0.0: gateway ::1 Creating and/or trimming log files. Starting syslogd. No core dumps found. ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/gcc46 32-bit compatibility ldconfig path: /usr/lib32 NFS access cache time=60 Clearing /tmp (X related). Updating motd:. Mounting late file systems:. Configuring syscons: blanktime. Performing sanity check on sshd configuration. Starting sshd. Starting sendmail_submit. Starting sendmail_msp_queue. Starting cron. Starting default moused. Starting background file system checks in 60 seconds. Thu Feb 6 20:45:00 CET 2014 Feb 6 20:45:11 10rc1amd64mbr2 su: nox to root on /dev/ttyv0 kqemu version 0x00010400 kqemu: KQEMU installed, max_locked_mem=4182744kB. Feb 6 20:52:29 10rc1amd64mbr2 su: nox to root on /dev/ttyv0 Feb 6 20:53:17 10rc1amd64mbr2 su: nox to root on /dev/ttyv0 Feb 6 20:55:28 10rc1amd64mbr2 su: nox to root on /dev/pts/0 Feb 6 20:56:01 10rc1amd64mbr2 su: nox to root on /dev/pts/0 cd9660: RockRidge Extension Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x208 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff80b06f77 stack pointer = 0x28:0xfffffe023ad436e0 frame pointer = 0x28:0xfffffe023ad43760 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 905 (qemu-system-x86_64) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: #0 0xffffffff808e7d30 at kdb_backtrace+0x60 #1 0xffffffff808af815 at panic+0x155 #2 0xffffffff80c8e552 at trap_fatal+0x3a2 #3 0xffffffff80c8e829 at trap_pfault+0x2c9 #4 0xffffffff80c8dfb6 at trap+0x5e6 #5 0xffffffff80c75252 at calltrap+0x8 #6 0xffffffff808fad2c at vmem_alloc+0x5c #7 0xffffffff80b0f788 at kmem_malloc+0x38 #8 0xffffffff81a15739 at kqemu_alloc_zeroed_page+0x29 #9 0xffffffff81a12288 at mon_alloc_page+0x18 Uptime: 13m13s Dumping 391 out of 8169 MB:..5%..13%..21%..33%..41%..54%..62%..74%..82%..95% ------------------------------------------------------------------------ kernel config options CONFIG_AUTOGENERATED ident GENERIC machine amd64 cpu HAMMER makeoptions WITH_CTF=1 makeoptions DEBUG=-g options XENHVM options USB_DEBUG options ATH_ENABLE_11N options AH_AR5416_INTERRUPT_MITIGATION options AH_SUPPORT_AR5416 options IEEE80211_SUPPORT_MESH options IEEE80211_AMPDU_AGE options IEEE80211_DEBUG options SC_PIXEL_MODE options VESA options AHD_REG_PRETTY_PRINT options AHC_REG_PRETTY_PRINT options ATA_STATIC_ID options SMP options KDB_TRACE options KDB options INCLUDE_CONFIG_FILE options DDB_CTF options KDTRACE_HOOKS options KDTRACE_FRAME options MAC options PROCDESC options CAPABILITIES options CAPABILITY_MODE options AUDIT options HWPMC_HOOKS options KBD_INSTALL_CDEV options PRINTF_BUFR_SIZE=128 options _KPOSIX_PRIORITY_SCHEDULING options SYSVSEM options SYSVMSG options SYSVSHM options STACK options KTRACE options SCSI_DELAY=5000 options COMPAT_FREEBSD7 options COMPAT_FREEBSD6 options COMPAT_FREEBSD5 options COMPAT_FREEBSD4 options COMPAT_FREEBSD32 options GEOM_LABEL options GEOM_RAID options GEOM_PART_GPT options PSEUDOFS options PROCFS options CD9660 options MSDOSFS options NFS_ROOT options NFSLOCKD options NFSD options NFSCL options MD_ROOT options QUOTA options UFS_GJOURNAL options UFS_DIRHASH options UFS_ACL options SOFTUPDATES options FFS options SCTP options TCP_OFFLOAD options INET6 options INET options PREEMPTION options SCHED_ULE options NEW_PCIB options GEOM_PART_MBR options GEOM_PART_EBR_COMPAT options GEOM_PART_EBR options GEOM_PART_BSD device isa device mem device io device uart_ns8250 device cpufreq device acpi device pci device fdc device ahci device ata device mvs device siis device ahc device ahd device esp device hptiop device isp device mpt device mps device sym device trm device adv device adw device aic device bt device isci device scbus device ch device da device sa device cd device pass device ses device amr device arcmsr device ciss device dpt device hptmv device hptnr device hptrr device hpt27xx device iir device ips device mly device twa device tws device aac device aacp device aacraid device ida device mfi device mlx device twe device atkbdc device atkbd device psm device kbdmux device vga device splash device sc device agp device cbb device pccard device cardbus device uart device ppc device ppbus device lpt device ppi device puc device bxe device de device em device igb device ixgbe device le device ti device txp device vx device miibus device ae device age device alc device ale device bce device bfe device bge device cas device dc device et device fxp device gem device hme device jme device lge device msk device nfe device nge device pcn device re device rl device sf device sge device sis device sk device ste device stge device tl device tx device vge device vr device wb device xl device cs device ed device ex device ep device fe device sn device xe device wlan device wlan_wep device wlan_ccmp device wlan_tkip device wlan_amrr device an device ath device ath_pci device ath_hal device ath_rate_sample device ipw device iwi device iwn device malo device mwl device ral device wi device wpi device loop device random device padlock_rng device rdrand_rng device ether device vlan device tun device md device gif device faith device firmware device bpf device uhci device ohci device ehci device xhci device usb device ukbd device umass device sound device snd_cmi device snd_csa device snd_emu10kx device snd_es137x device snd_hda device snd_ich device snd_via8233 device mmc device mmcsd device sdhci device virtio device virtio_pci device vtnet device virtio_blk device virtio_scsi device virtio_balloon device hyperv device xenpci device vmx ------------------------------------------------------------------------ ddb capture buffer ddb: ddb_capture: kvm_nlist From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 03:02:26 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 60E8EB03 for ; Fri, 7 Feb 2014 03:02:26 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 35E4415C4 for ; Fri, 7 Feb 2014 03:02:26 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id z10so2527618pdj.5 for ; Thu, 06 Feb 2014 19:02:25 -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=CpozFJeuDIt/O4UCP+Ynp29ZXAB6y13UvhT9wP+Qn3Y=; b=eDQMDRGHhB96oMuk1vnOgY9Idxrp0gXHjOKd/xmbpMsbjHPcxd5n8jatle16kETaiV ReC8KJJ1qh3KPCLF7rPW/5BzR1Bg0zgKFcDHEEM/61ES5IQFo4sKrR0SsoWXSZqDF7c9 vrFPIXv74JxKo8DT7EqiqMmsmxIPvxO1FtP3O2k5X+Rb207Z5oBI79Nn/Mi3WQQIntTW r5LQj7zMg0FEz9gXJiiUG6joEFTgP9+J+PYudrQwXy7y5KK47zF2I0f5eBO5ARaTzWDA RCCo3FCO86dIs0so2Mvf0EaouMH5k/SvkWbS4C1n//c9dtGrlROPDXHUI8FdA/75w1fs 0rxQ== MIME-Version: 1.0 X-Received: by 10.68.230.137 with SMTP id sy9mr16580182pbc.126.1391742145325; Thu, 06 Feb 2014 19:02:25 -0800 (PST) Received: by 10.68.155.38 with HTTP; Thu, 6 Feb 2014 19:02:25 -0800 (PST) In-Reply-To: <52F3E0F9.8040504@callfortesting.org> References: <52F3B69B.6030706@pix.net> <52F3E0F9.8040504@callfortesting.org> Date: Thu, 6 Feb 2014 22:02:25 -0500 Message-ID: Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) From: Aryeh Friedman To: Michael Dexter Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 03:02:26 -0000 Michael Dexter wrote: > Please hesitate before you write and determine if this is the > correct list and your post is in accordance with the above > policies. 1. We still have not received any guidance on what sort of CFT's (if any) are allowed on -virtualization@ for open-source projects that aim to be FreeBSD ports. 1. The actual message you were taking issue with above was primarily a public thanks to someone for giving us a possible solution to a problem we had. I also made the off-topic "announcement" you objected to for the purpose of updating the -virtualization@ list on our progress in creating our own alternative to using -virtualization@ as our preferred communication channel as requested by you and John Baldwin. > and my personal favorite, a request for a bhyve developer to sign > an NDA to see these. The NDA request was NOT posted on the -virtualization@ list; that was in a private email from Aryeh Friedman to Peter Grehan and him alone, way back in early August 2013. Peter immediately rejected all private communication and directed Aryeh to post everything to the -virtualization@ list. We concluded that Peter was right that everything should be open knowledge. Anyhow, we agree that -virtualization@ should not be the place for discussion of cloud computing because it crosses so many disciplines it does not fully fit into any currently-existing FreeBSD list. For that reason, we again suggest making a -cloud@ list. Until then, -virtualization@seems to us to be the closest-to-suitable option, though far from a perfect fit. From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 05:53:30 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 854E55FF for ; Fri, 7 Feb 2014 05:53:30 +0000 (UTC) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 523341360 for ; Fri, 7 Feb 2014 05:53:29 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id uo5so2787945pbc.41 for ; Thu, 06 Feb 2014 21:53:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PFNCCTl22N9iBUjV80MXSIrDkejKjASx+Oqwm5Jsw6I=; b=DGrjwueVBNM/H7arv6FS3mdCTbgIawaJpKBqL52mKZfcLzEP15vUBd+vLOtPa3GSZ+ p7EvawBpBMjYhaIYQHKnjGtQBwqA5YzLxvkcnZUTjIxL3bd398SRNkXFOWAC9xWiITrr Nxi/z8h4X/jYTbzzwj879kNBwdvelQdP2kRevKKAYmlZixXchmMBCP3+gUliK95HFtws 6UnhFK5rPhW5N9KSQcnLHVPWir/V8ZxQBLOha0A6SKAAq94INX+aXYc77uA0zRCVl2hs mZBoS1lNWunrcqJ8LvhrhLznV8lHJQDWyANeozIhy/OXRAK3erUAB7NhWIAr8ObtCc1M m6jg== X-Gm-Message-State: ALoCoQlHwEjgzQCJMN6s1OduI6/5xkbyeyXSfQjIyVEHFstCL4nrijYGDFisA39kbihWeseqVGtf X-Received: by 10.66.66.234 with SMTP id i10mr5496047pat.127.1391752403128; Thu, 06 Feb 2014 21:53:23 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id kc9sm9685945pbc.25.2014.02.06.21.53.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Feb 2014 21:53:22 -0800 (PST) Message-ID: <52F474CF.7000805@callfortesting.org> Date: Thu, 06 Feb 2014 21:53:19 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) References: <52F3B69B.6030706@pix.net> <52F3E0F9.8040504@callfortesting.org> In-Reply-To: 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.17 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, 07 Feb 2014 05:53:30 -0000 On 2/6/14 7:02 PM, Aryeh Friedman wrote: > We still have not received any guidance on what sort of CFT's (if any) > are allowed on -virtualization@ for open-source projects that aim to be > FreeBSD ports. That's not how it works. Read past list corespondent to get a feel for the tone of the list. Some lists are extremely loose and some are very firm such as one-way security announcements. If you have a doubt or a question, politely ask it and you will find that people are astonishingly helpful. Tell them how it's going to be and they will at best ignore but possibly shun or flame you. The BSD developers are the finest people I have found on this planet and I highly suggest you appreciate what they provide all of us in exchange for either an implied approval, the occasional thanks, the occasional beer or best of all, a meaningful bug report or patch. Please consider this: BSD Unix contains millions of lines of quality code that took millions of person hours to produce. Statistically, there is no dent that any of us can make on it that is warrants arrogance. Companies have come and gone who thought they could laugh their way to the bank by forking it with some multi-person-year diff that they thought the community would never catch up with. bhyve, pf and ZFS show that the community will ALWAYS be ahead of the game and that some companies grasp the value of sharing key technologies like bhyve and ZFS. The community and your role will best function if its extremely simple rules are followed in the context of its extremely reasonable and generous license. In short, do your homework and you will be very glad you did because it will open many doors for you and earn the trust of amazing developers, administrators and users around the world. This is my personal opinion but it is based on over 20 years of BSD Unix use and a dozen years of active community participation. Pause. Listen. Listen some more. Ask questions. Help out and receive priceless help from some of the best developers on the planet. Michael From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 16:53:10 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1EC1F8FB for ; Fri, 7 Feb 2014 16:53:10 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E943F1227 for ; Fri, 7 Feb 2014 16:53:09 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 04248B941 for ; Fri, 7 Feb 2014 11:53:09 -0500 (EST) From: John Baldwin To: virtualization@freebsd.org Subject: Enable bvmconsole and bvmdebug on i386? Date: Fri, 7 Feb 2014 11:38:42 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201402071138.42103.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 07 Feb 2014 11:53:09 -0500 (EST) X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 16:53:10 -0000 I was able to test bvmconsole and bvmdebug on an i386 guest today. The only change required was to copy the entries from files.amd64 to files.i386. Are there any objections to committing that? -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 18:03:43 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3876427A; Fri, 7 Feb 2014 18:03:43 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8C8018C1; Fri, 7 Feb 2014 18:03:42 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id i17so6646079qcy.11 for ; Fri, 07 Feb 2014 10:03:42 -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=EdCnexWVpRVtXvk67FgVDUpfdyxMmLQ1Xyc0wC410jg=; b=iRw+yygY5SiDfd+OErF3Mr2gXvWImrOXSPEc9tDoYvBPWmJonGK1gxtkz2PcThWgie /ZQyx5zu1gbJUaHscdQwaUDtxbASXo3bERvEJjj6O6aZpAwf1m8HqrJQDoXJgX0qGDw8 Sza8yX8CSyyYk+Hji0td3Fr8eq4MxtNCX1V3hvKH1mGfQWZV20DUOVf+QArH2DM4h80T 4SoA8HorbcJrdD7TXBqFLCUsKWDrMf9bZpjhzeGCx0fiEzv6CC88q/0bruuwZheXmF9G KPXtPdqrQeSjqXEA6jV5f/nzXYrZUM/LSH2PZjy4EiZp6LCvjeulaOZpU/gwVtHQoOZT WDLA== MIME-Version: 1.0 X-Received: by 10.224.97.7 with SMTP id j7mr24767422qan.81.1391796222053; Fri, 07 Feb 2014 10:03:42 -0800 (PST) Received: by 10.140.87.71 with HTTP; Fri, 7 Feb 2014 10:03:41 -0800 (PST) In-Reply-To: <201402071138.42103.jhb@freebsd.org> References: <201402071138.42103.jhb@freebsd.org> Date: Fri, 7 Feb 2014 10:03:41 -0800 Message-ID: Subject: Re: Enable bvmconsole and bvmdebug on i386? From: Neel Natu To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 18:03:43 -0000 Hi John, On Fri, Feb 7, 2014 at 8:38 AM, John Baldwin wrote: > I was able to test bvmconsole and bvmdebug on an i386 guest today. The only > change required was to copy the entries from files.amd64 to files.i386. Are > there any objections to committing that? > None at all. best Neel > -- > John Baldwin > _______________________________________________ > 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 Feb 7 18:35:40 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 9A8EB2F8 for ; Fri, 7 Feb 2014 18:35:40 +0000 (UTC) Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 55F4F1BEF for ; Fri, 7 Feb 2014 18:35:40 +0000 (UTC) Received: by mail-vc0-f176.google.com with SMTP id la4so2915842vcb.21 for ; Fri, 07 Feb 2014 10:35:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:from:date:message-id:subject:to:content-type; bh=4NeFkv0mktvWYX+pwWyceOxbxUPJAz76dc7zAJ2yudM=; b=Qr3dupuxKP5QPPogaCr//GWi14Ni7KM6gTZ51wjrdshKi/yBwUiBdqLE61RYnLTzKr IAfQX+sSdm5N/ATSgEhRXczjckvnSa7b8DVpy8LTl8PTvZOTQkoNpVAZqY7sNVN5SeAT m0BIYBPXNVdUhmnOcihH+m0eJGSlyRIpeliTt+qLx5rDKSC+bd1qrmCaz0Mn08w2atCA Ho1MuJBYb807emsWk+HlI5ZvwXnzDDhcpppTgAnTNMgGBCzO68AafWtO0tah7KmTYUB5 CSAZ+crnbpWFurVB9GP+BIfNmxXi/h5YsA/q1t3fuKgTFzo1Zw/LPKx4qZTJCotFuKDl D/gQ== X-Received: by 10.52.106.107 with SMTP id gt11mr9792635vdb.7.1391798139432; Fri, 07 Feb 2014 10:35:39 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.58.188.35 with HTTP; Fri, 7 Feb 2014 10:35:19 -0800 (PST) From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Fri, 7 Feb 2014 19:35:19 +0100 X-Google-Sender-Auth: ynhHLtaVEmmgc6vAWBxMNn5AWr4 Message-ID: Subject: Report of my virtual network lab migrated from virtualbox to bhyve To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 18:35:40 -0000 Hi, just a report of my migration to bhyve. I was using VirtualBox for generate full-meshed network lab of multiple VM (essentially nanobsd based) and have migrated my script to bhyve. My original script is resumed to this kind of usage: ./lab-script.sh -i FreeBSD-image-disk -n number-of-vm -l number-of-LAN For example I can easly generate this kind of topology: ./BSDRP-lab-bhyve.sh -i nanobsd-serial.img -n 4 -l 2 VM 1 have the following NIC: - vtnet0 connected to VM 2. - vtnet1 connected to VM 3. - vtnet2 connected to VM 4. - vtnet3 connected to LAN number 1 - vtnet4 connected to LAN number 2 VM 2 have the following NIC: - vtnet0 connected to VM 1. - vtnet1 connected to VM 3. - vtnet2 connected to VM 4. - vtnet3 connected to LAN number 1 - vtnet4 connected to LAN number 2 VM 3 have the following NIC: - vtnet0 connected to VM 1. - vtnet1 connected to VM 2. - vtnet2 connected to VM 4. - vtnet3 connected to LAN number 1 - vtnet4 connected to LAN number 2 VM 4 have the following NIC: - vtnet0 connected to VM 1. - vtnet1 connected to VM 2. - vtnet2 connected to VM 3. - vtnet3 connected to LAN number 1 - vtnet4 connected to LAN number 2 First remark comparing the disk format: With an original nanobsd disk image of 488MB. - Virtualbox format disk size: 133M - bhyve raw disk size: 488M Second remark regarding the difference between bhyve and virtualbox with disk image management: I'm using the "Linked clone" feature of virtualbox: This avoid to duplicate full guest disk. Here is with the example of 10 VM: - Virtualbox consumed disk space: 133M + 10x133K = about 135M in total - bhyve consumed disk space: 488M x 10 = 4880M in total => Hard drive space is not expensive today, but there is a huge difference (I didn't compare perfs). Third remark regarding memory usage on host (reported by top) with each VM configured for 256M of RAM (the guest report 70M of used memory) in SIZE/RES : . Virtualbox consumed RAM: 490/308M x 10 + 125/20M (VBoxSVC) + 80/11M (VBoxXPCOMIPCD) = total of 5100/4010M - bhyve consumed RAM: 283/22M x 10 = total of 2830/220M => Wow... bhyve memory usage is lot's lower than with Virtualbox ! Forth remark regarding network card emulation: Virtualbox permits to emulate em(4) NIC that supports altq(4) but bhyve emulate only vtnet(4) that didn't have altq(4) support. => I can't use bhyve for simulating network lab with altq(4) Fifth remark regarding network card virtualization: Virtualbox permits to generate "internal only" NIC between VM, but bhyve supports only tap. Can you add epair(4) support into bhyve roadmap ? => I have to create a huge number of bridge/tap interfaces on the host just for internal VM Ethernet links. And a simple user can't create bridge/tap interfaces. Sixth remark regarding the use of nmdm device for serial redirection: Often, I have to start a connection to the nmdm device for "un-pausing" the starting of the bhyve guest. And once I connect to the nmdm dev, this error is displayed (on head): Assertion failed: (error == 0), function init_pci, file /src/usr.sbin/bhyve/pci_emul.c, line 1047. Seventh remark regarding user: I didn't have to use Virtualbox as root (just to be in the virtualbox group), but it's mandatory with bhyve. And final remark: FreeBSD booting speed is very impressive with bhyve ! My bhyve and virtualbox scripts (and qemu) used are online here: http://bsdrp.net/documentation/examples/how_to_build_a_bsdrp_router_lab Regards, Olivier From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 19:13: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 C0AB137F for ; Fri, 7 Feb 2014 19:13:53 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 921691FEA for ; Fri, 7 Feb 2014 19:13:53 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7702BB917; Fri, 7 Feb 2014 14:13:52 -0500 (EST) From: John Baldwin To: Aryeh Friedman Subject: Re: CFT: Very rough draft of PetiteCloud 0.2.4 (Linux as a host) Date: Fri, 7 Feb 2014 14:11:05 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <5330814.Xk97r20mZI@ralph.baldwin.cx> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201402071411.05413.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 07 Feb 2014 14:13:52 -0500 (EST) Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 19:13:53 -0000 On Wednesday, February 05, 2014 7:55:06 pm Aryeh Friedman wrote: > On Wed, Feb 5, 2014 at 1:00 PM, John Baldwin wrote: > > > On Tuesday, February 04, 2014 09:55:13 AM Michael Dexter wrote: > > > May I suggest you take this all to a personal blog? > > > > I agree. You can use a blog on petitecloud.org if you wish, but the purpose > > of this list is discussing virtualization techniques FreeBSD supports including > > jails/vimage, hypervisors (bhyve), and accelerated guest support (e.g. Xen HVM > > and Hyper-V drivers). An occasional note about petitecloud may be warranted, > > but the current volume is excessive. Also, this list is not suitable for use > > as a support forum for a commercial product. It is certainly appropriate for > > bug reports in the aforementioned list of topics (e.g. bhyve bugs or bhyve > > performance testing results) that may come out of "downstream" bug reports. > > 2. You seem to be under the impression that PetiteCloud is a > commercial product. It is in fact 100% Free Open Source (BSD license) and > Open Knowledge. Even derivative open source projects tend to provide their own fora for bug reports, etc. (see, for example, PC-BSD and pfSense). If a bug reported in their system is the result of a bug in FreeBSD then it ends up being logged as a FreeBSD issue as well, but the latter part is what occurs on FreeBSD lists. > 4. Currently the only available place to discuss cloud computing at > all on FreeBSD is -virtualization@. A -cloud@ list might make more sense if > there was one. We would strongly urge the creation of such a list, because > we consider FreeBSD to be, without question, the best operating system for > truly stable and robust cloud computing, and we would strongly encourage > the FreeBSD Foundation to emphasize this in its advocacy. In the meantime, > please note that PetiteCloud is not yet a full-fledged cloud platform, but > currently is little more than just a front end for various hypervisors > including bhyve (our preferred hypervisor I suspect that the your posts would be just as on or off-topic on cloud@ as they would be on virtualization. I do not think we need an extra mailing list at this time. > 5.. We would appreciate clarification on what kinds of announcements > are appropriate here. For example, we've been posting calls for testing of > new versions of PetiteCloud for almost five months with no objection from > anyone (except for an early question from Michael Dexter about how truly > open-source we were) until we added support for a non-FreeBSD host. May we > continue to post CFT's that contain FreeBSD-related issues (including > making sure we didn't break anything related to our FreeBSD support when > adding features required by other OS's). I think CFTs are fine for now. However, I think you should strive to setup your own lists for support and general petitecloud-specific discussion on petitecloud.org itself. This is the model that other projects built on FreeBSD use. > b. As soon the appropriate person at the FreeBSD foundation > contacts us, we will arrange to transfer freebsd-openstack.org to the > foundation, if the FreeBSD foundation desires to be in charge of such a > portal. We do want to keep editorial control until we can put a basic > content management system in place and populate it with some initial > content. You own this domain so you are free to do with it as you wish as far as I am concerned. If you wish to work with the Foundation you can e-mail their board to discuss that further. -- John Baldwin From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 19:38:16 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 24330741 for ; Fri, 7 Feb 2014 19:38:16 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CBAAF11A8 for ; Fri, 7 Feb 2014 19:38:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s17JcCYo021120; Fri, 7 Feb 2014 12:38:12 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s17JcC3G021117; Fri, 7 Feb 2014 12:38:12 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 7 Feb 2014 12:38:12 -0700 (MST) From: Warren Block To: =?ISO-8859-15?Q?Olivier_Cochard-Labb=E9?= Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 07 Feb 2014 12:38:12 -0700 (MST) Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 19:38:16 -0000 On Fri, 7 Feb 2014, Olivier Cochard-Labbé wrote: > First remark comparing the disk format: With an original nanobsd disk image > of 488MB. > - Virtualbox format disk size: 133M > - bhyve raw disk size: 488M Can bhyve use sparse files for disk images? Thank you for posting the comparison! From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 19:38:42 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 5059B786 for ; Fri, 7 Feb 2014 19:38:42 +0000 (UTC) Received: from alto.onthenet.com.au (alto.OntheNet.com.au [203.13.68.12]) by mx1.freebsd.org (Postfix) with ESMTP id D2E1C11AE for ; Fri, 7 Feb 2014 19:38:41 +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 3FA3812420; Sat, 8 Feb 2014 05:38:40 +1000 (EST) Received: from Peter-Grehans-MacBook-Pro-2.local ([64.245.0.210]) by dommail.onthenet.com.au (MOS 4.2.4-GA) with ESMTP id BRR37078 (AUTH peterg@ptree32.com.au); Sat, 8 Feb 2014 05:38:39 +1000 Message-ID: <52F5363D.8040102@freebsd.org> Date: Fri, 07 Feb 2014 11:38:37 -0800 From: Peter Grehan User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Olivier_Cochard-Labb=E9?= Subject: Re: Report of my virtual network lab migrated from virtualbox to 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.17 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, 07 Feb 2014 19:38:42 -0000 Hi Olivier, > just a report of my migration to bhyve. Yeah !!! > First remark comparing the disk format: With an original nanobsd disk image > of 488MB. > - Virtualbox format disk size: 133M > - bhyve raw disk size: 488M If you create a sparse file for the bhyve raw disk (e.g. with truncate -s), du will show the actual blocks used rather than the total size. > Second remark regarding the difference between bhyve and virtualbox with > disk image management: > I'm using the "Linked clone" feature of virtualbox: This avoid to duplicate > full guest disk. Here is with the example of 10 VM: > - Virtualbox consumed disk space: 133M + 10x133K = about 135M in total > - bhyve consumed disk space: 488M x 10 = 4880M in total > => Hard drive space is not expensive today, but there is a huge difference > (I didn't compare perfs). bhyve doesn't support any VM sparse disk formats - it currently relies on the underlying filesystem for this (sparse files, ZFS compression/dedup etc). This can perform better than VM sparse formats, in both i/o speed and also space usage, at the expense of having to do a conversion to/from a flat file if you are importing/exporting. That being said, I'm sure bhyve will gather direct support for these at some point. > Third remark regarding memory usage on host (reported by top) with each VM > configured for 256M of RAM (the guest report 70M of used memory) in > SIZE/RES : > . Virtualbox consumed RAM: 490/308M x 10 + 125/20M (VBoxSVC) + 80/11M > (VBoxXPCOMIPCD) = total of 5100/4010M > - bhyve consumed RAM: 283/22M x 10 = total of 2830/220M > => Wow... bhyve memory usage is lot's lower than with Virtualbox ! To be fair to vbox, the memory usage reported for bhyve is only the pages that have been touched by the bhyve process in it's mmap() of guest memory. This may be less than that actually in use. We need to export the pages in use in the kernel vmspace that represents guest memory. > Forth remark regarding network card emulation: > Virtualbox permits to emulate em(4) NIC that supports altq(4) but bhyve > emulate only vtnet(4) that didn't have altq(4) support. > => I can't use bhyve for simulating network lab with altq(4) There is an em(4) emulation slowly being worked on. It should also be possible to add altq functionality to FreeBSD's virtio net driver. > Fifth remark regarding network card virtualization: > Virtualbox permits to generate "internal only" NIC between VM, but bhyve > supports only tap. Can you add epair(4) support into bhyve roadmap ? > => I have to create a huge number of bridge/tap interfaces on the host just > for internal VM Ethernet links. And a simple user can't create bridge/tap > interfaces. For internal-only networks, there will most likely be a user-space ethernet switch (ala VDE) that bhyve network interfaces can be pointed at. > Sixth remark regarding the use of nmdm device for serial redirection: > Often, I have to start a connection to the nmdm device for "un-pausing" the > starting of the bhyve guest. And once I connect to the nmdm dev, this error > is displayed (on head): > Assertion failed: (error == 0), function init_pci, file > /src/usr.sbin/bhyve/pci_emul.c, line 1047. Yeah, there are some issues with nmdm's simulated modem control :( Looking into this. > Seventh remark regarding user: I didn't have to use Virtualbox as root > (just to be in the virtualbox group), but it's mandatory with bhyve. Fixing this is on the roadmap. > And final remark: FreeBSD booting speed is very impressive with bhyve ! This may be a useful side-effect of the separate loader process. It runs in user-space with Unix process i/o as opposed to a BIOS loader which has to run in polled-mode. later, Peter. From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 20:03: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 C18EEFEF for ; Fri, 7 Feb 2014 20:03:20 +0000 (UTC) Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 804C613C9 for ; Fri, 7 Feb 2014 20:03:20 +0000 (UTC) Received: by mail-qc0-f176.google.com with SMTP id e16so6821259qcx.35 for ; Fri, 07 Feb 2014 12:03:19 -0800 (PST) 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=78D1VQfzMK+L+1vdybsG+uUpmiOiwdqg3kWvHRnjPNs=; b=EjUU7CKbFtIJjwqSoWLTgJpyBghEEqDMO9oOG8XQnvl61PnGb3XIXjZe/OHoRDzJUz FZcXuCnkWUadr4OJ593Vvi1ppnTJG7FnDu4CEJkrTbpapoLcPR0kVTVSanlrZCtgqlyX qZVR9LIuWk4vl2YQA3VEML5WKHA1Cz7kaAK7uwR8FaOo/VdQWygEhnKNxAdBkLPGTaDs fwYA2d6rLpq1ainI+GITY5imm7FcItfhv2JLGkxdYD/7PPn+MZxTBQEtyEmG4+uUnh1T BvSFRmnnrp6GHsB2qJVml+EpgOje63dosTvaJZoqGLQeOvimpiT/JP7WkpCEMz3qc+X2 D2Kg== MIME-Version: 1.0 X-Received: by 10.224.16.72 with SMTP id n8mr25909874qaa.76.1391803399662; Fri, 07 Feb 2014 12:03:19 -0800 (PST) Received: by 10.224.42.7 with HTTP; Fri, 7 Feb 2014 12:03:19 -0800 (PST) Date: Fri, 7 Feb 2014 21:03:19 +0100 Message-ID: Subject: Networking issues From: ickler@gmail.com To: freebsd-virtualization@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 20:03:20 -0000 Hello virtualization-lovers, I am very dedicated to FreeBSD since 7.2 and welcome the new bhyve hypervisor. :) So I set everything up, launched the guest and set up the network. The problem now is, I can reach the host IP, but not the default gateway. Did I forget to set something up? The system is a hosted root box. My current setup (i changed the IP's except the last octet): ---snip--- host: # ifconfig re0: flags=8943 metric 0 mtu 1500 options=82099 ether 30:85:a9:ed:01:22 inet 192.168.0.137 netmask 0xffffffe0 broadcast 192.168.0.159 inet6 fe80::3285:a9ff:feed:122%re0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active bridge0: flags=8843 metric 0 mtu 1500 ether 02:0d:2a:df:6e:00 nd6 options=1 id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200 root id 00:00:00:00:00:00 priority 32768 ifcost 0 port 0 member: tap0 flags=143 ifmaxaddr 0 port 4 priority 128 path cost 2000000 member: re0 flags=143 ifmaxaddr 0 port 1 priority 128 path cost 20000 tap0: flags=8943 metric 0 mtu 1500 options=80000 ether 00:bd:fe:79:0e:00 nd6 options=29 media: Ethernet autoselect status: active Opened by PID 16910 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 5.9.157.129 UGS 0 293321 re0 192.168.0.128/27 link#1 U 0 30 re0 192.168.0.137 link#1 UHS 0 0 lo0 127.0.0.1 link#2 UH 0 1606 lo0 ---snip--- ---snip--- guest: # ifconfig vtnet0: flags=8943 metric 0 mtu 1500 options=80028 ether 00:a0:98:18:c4:69 inet 192.168.0.154 netmask 0xffffffe0 broadcast 192.168.0.159 inet6 fe80::2a0:98ff:fe18:c469%vtnet0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet 10Gbase-T status: active lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 # netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 5.9.157.129 UGS 0 418 vtnet0 192.168.0.128/27 link#1 U 0 24 vtnet0 192.168.0.154 link#1 UHS 0 0 lo0 127.0.0.1 link#2 UH 0 24 lo0 ---snip--- ping host -> guest works # ping 192.168.0.154 PING 192.168.0.154 (192.168.0.154): 56 data bytes 64 bytes from 192.168.0.154: icmp_seq=0 ttl=64 time=0.083 ms 64 bytes from 192.168.0.154: icmp_seq=1 ttl=64 time=0.094 ms ping guest -> host works # ping 192.168.0.137 PING 192.168.0.137 (192.168.0.137): 56 data bytes 64 bytes from 192.168.0.137: icmp_seq=0 ttl=64 time=0.398 ms 64 bytes from 192.168.0.137: icmp_seq=1 ttl=64 time=0.069 ms ping 173.194.70.102 (google.com) from guest - doesn't work... # ping 173.194.70.102 PING 173.194.70.102 (173.194.70.102): 56 data bytes --- 173.194.70.102 ping statistics --- 3 packets transmitted, 0 packets received, 100.0% packet loss tcpdump listening on the host: # tcpdump -N -vv -i bridge0 tcpdump: WARNING: bridge0: no IPv4 address assigned tcpdump: listening on bridge0, link-type EN10MB (Ethernet), capture size 65535 bytes 19:58:19.139767 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has static tell 192.168.0.137, length 46 ---^ same on tap0 What's wrong with that setup? Did I forget to set a proper route? Or is it a MAC address issue? Thanks in advance, Sebastian From owner-freebsd-virtualization@FreeBSD.ORG Fri Feb 7 20:46:19 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 27127A3A; Fri, 7 Feb 2014 20:46:19 +0000 (UTC) Received: from torment.daemoninthecloset.org (torment.daemoninthecloset.org [94.242.209.234]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BF186171B; Fri, 7 Feb 2014 20:46:18 +0000 (UTC) Received: from sage.daemoninthecloset.org (unknown [70.114.209.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "sage.daemoninthecloset.org", Issuer "daemoninthecloset.org" (verified OK)) by torment.daemoninthecloset.org (Postfix) with ESMTPS id 47E5542C26A2; Fri, 7 Feb 2014 21:36:17 +0100 (CET) X-Virus-Scanned: amavisd-new at daemoninthecloset.org X-Virus-Scanned: amavisd-new at daemoninthecloset.org Date: Fri, 7 Feb 2014 14:36:07 -0600 (CST) From: Bryan Venteicher To: Peter Grehan Message-ID: <1819242235.9011.1391805367191.JavaMail.root@daemoninthecloset.org> In-Reply-To: <52F5363D.8040102@freebsd.org> References: <52F5363D.8040102@freebsd.org> Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.51.1.6] X-Mailer: Zimbra 8.0.2_GA_5569 (ZimbraWebClient - GC32 (Mac)/8.0.2_GA_5569) Thread-Topic: Report of my virtual network lab migrated from virtualbox to bhyve Thread-Index: ZfiA/M7OfrIIhNHfwXxX33JYFlHElA== Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 07 Feb 2014 20:46:19 -0000 ----- Original Message ----- > Hi Olivier, > > just a report of my migration to bhyve. > > Yeah !!! > > > First remark comparing the disk format: With an original nanobsd disk image > > of 488MB. > > - Virtualbox format disk size: 133M > > - bhyve raw disk size: 488M > > If you create a sparse file for the bhyve raw disk (e.g. with truncate > -s), du will show the actual blocks used rather than the total size. > > > Second remark regarding the difference between bhyve and virtualbox with > > disk image management: > > I'm using the "Linked clone" feature of virtualbox: This avoid to duplicate > > full guest disk. Here is with the example of 10 VM: > > - Virtualbox consumed disk space: 133M + 10x133K = about 135M in total > > - bhyve consumed disk space: 488M x 10 = 4880M in total > > => Hard drive space is not expensive today, but there is a huge difference > > (I didn't compare perfs). > > bhyve doesn't support any VM sparse disk formats - it currently relies > on the underlying filesystem for this (sparse files, ZFS > compression/dedup etc). This can perform better than VM sparse formats, > in both i/o speed and also space usage, at the expense of having to do a > conversion to/from a flat file if you are importing/exporting. > > That being said, I'm sure bhyve will gather direct support for these > at some point. > > > Third remark regarding memory usage on host (reported by top) with each VM > > configured for 256M of RAM (the guest report 70M of used memory) in > > SIZE/RES : > > . Virtualbox consumed RAM: 490/308M x 10 + 125/20M (VBoxSVC) + 80/11M > > (VBoxXPCOMIPCD) = total of 5100/4010M > > - bhyve consumed RAM: 283/22M x 10 = total of 2830/220M > > => Wow... bhyve memory usage is lot's lower than with Virtualbox ! > > To be fair to vbox, the memory usage reported for bhyve is only the > pages that have been touched by the bhyve process in it's mmap() of > guest memory. This may be less than that actually in use. We need to > export the pages in use in the kernel vmspace that represents guest > memory. > > > Forth remark regarding network card emulation: > > Virtualbox permits to emulate em(4) NIC that supports altq(4) but bhyve > > emulate only vtnet(4) that didn't have altq(4) support. > > => I can't use bhyve for simulating network lab with altq(4) > > There is an em(4) emulation slowly being worked on. It should also be > possible to add altq functionality to FreeBSD's virtio net driver. > You have to recompile the driver with VTNET_LEGACY_TX defined to disable multiqueue support. > > Fifth remark regarding network card virtualization: > > Virtualbox permits to generate "internal only" NIC between VM, but bhyve > > supports only tap. Can you add epair(4) support into bhyve roadmap ? > > => I have to create a huge number of bridge/tap interfaces on the host just > > for internal VM Ethernet links. And a simple user can't create bridge/tap > > interfaces. > > For internal-only networks, there will most likely be a user-space > ethernet switch (ala VDE) that bhyve network interfaces can be pointed at. > > > Sixth remark regarding the use of nmdm device for serial redirection: > > Often, I have to start a connection to the nmdm device for "un-pausing" the > > starting of the bhyve guest. And once I connect to the nmdm dev, this error > > is displayed (on head): > > Assertion failed: (error == 0), function init_pci, file > > /src/usr.sbin/bhyve/pci_emul.c, line 1047. > > Yeah, there are some issues with nmdm's simulated modem control :( > Looking into this. > > > Seventh remark regarding user: I didn't have to use Virtualbox as root > > (just to be in the virtualbox group), but it's mandatory with bhyve. > > Fixing this is on the roadmap. > > > And final remark: FreeBSD booting speed is very impressive with bhyve ! > > This may be a useful side-effect of the separate loader process. It > runs in user-space with Unix process i/o as opposed to a BIOS loader > which has to run in polled-mode. > > later, > > Peter. > > _______________________________________________ > 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 Feb 8 10:45: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 B1A8BA63 for ; Sat, 8 Feb 2014 10:45:52 +0000 (UTC) Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 82AFC1034 for ; Sat, 8 Feb 2014 10:45:52 +0000 (UTC) Received: by mail-pd0-f169.google.com with SMTP id v10so4174096pde.14 for ; Sat, 08 Feb 2014 02:45:52 -0800 (PST) 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=Zu0LyfNFLxpJi7PM3ppu4JIupLzl1JFv6+glYkGDyVI=; b=DMlweWdxgA6kqJqOli9tF59A6qYnsJ9lLYbMIR68jHLUskZkZqq6MSNVlmen9TkMVB 2uvlGpE38lOfF5Y++8+Iz2e5oarHG6ymSctVpDQ8aDUxVoJrgG7BCvdK+RjG71QQJyWk o68PQg6cqOvU6IHNKU9hfd4FV54zF41hD9korx+ZzBNcN0//5C0rSUj7SZVvdMPD3Qr3 Xwf5J4ey/pwpMoFhXIfhinwNzrBugeVYKoI3jmSHwzOJLTp80U2dVgZ2FnvIH8W7EBdG M8/v4HVAnhhwDBceKmM3oRVslUcsrYleyRlrkGKH2VwK73gglJwNdKg0ZmqxqptkjY56 js3Q== MIME-Version: 1.0 X-Received: by 10.66.16.131 with SMTP id g3mr13549679pad.138.1391856352077; Sat, 08 Feb 2014 02:45:52 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 02:45:52 -0800 (PST) Date: Sat, 8 Feb 2014 05:45:52 -0500 Message-ID: Subject: NOTICE to all PetiteCloud users From: Aryeh Friedman To: "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 10:45:52 -0000 We have moved all support over to internal mailing lists. Please http://lists.petitecloud.nyclocal.net/listinfo.cgi to subscribe -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 11:20: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9BDBC8F3; Sat, 8 Feb 2014 11:20:23 +0000 (UTC) Received: from mail-vb0-x232.google.com (mail-vb0-x232.google.com [IPv6:2607:f8b0:400c:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 42B0D1295; Sat, 8 Feb 2014 11:20:23 +0000 (UTC) Received: by mail-vb0-f50.google.com with SMTP id w8so3522964vbj.9 for ; Sat, 08 Feb 2014 03:20:22 -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:from:date:message-id :subject:to:cc:content-type; bh=yGyJfpMujdBeqv+S+bVckgsCyCjwmr5+edeVz+Fy8tM=; b=hna9T2LJSz+J4Itl3aj6fyI4cj7vQGhqIc+OjAU83uaSM/PB+wM2OcuxVaUeBXdw9G 33tzkqpGk4AO61XAajmZHh1AtfRGXcui/OepWnTX6RFxQstS89Y/efsqLj+lwBGxoItt pb9xWmCJg5T+lCRileB/0okz8WguDtGt58tKD+kNVJd8x5o8lfJ77zVb8gxm/15ZgSpY 9U+MVV/Rl34kATOwOQmEQiboDinwIONYupEciAGPETnW0AjNdtRJ0juBDoNvSrYCaZRp 3DGrcHOCcS5zXukM8suy8+Vpya9yMMgm6oWhH3F4C48jAnNpxCZt4+VcOkyvjqWb4W2U GgNg== X-Received: by 10.58.181.71 with SMTP id du7mr602554vec.25.1391858422073; Sat, 08 Feb 2014 03:20:22 -0800 (PST) MIME-Version: 1.0 Sender: cochard@gmail.com Received: by 10.58.188.35 with HTTP; Sat, 8 Feb 2014 03:20:02 -0800 (PST) In-Reply-To: <52F5363D.8040102@freebsd.org> References: <52F5363D.8040102@freebsd.org> From: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Date: Sat, 8 Feb 2014 12:20:02 +0100 X-Google-Sender-Auth: tyEqtF1eAk2O0dedjpRGt6DRiT8 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve To: Peter Grehan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 11:20:23 -0000 On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote: > > > If you create a sparse file for the bhyve raw disk (e.g. with truncate > -s), du will show the actual blocks used rather than the total size. But can I truncate an already existing image disk (downloaded nanobsd image as example) ? > There is an em(4) emulation slowly being worked on. It should also be > possible to add altq functionality to FreeBSD's virtio net driver. Adding altq(4) to vtnet(4) should be a better idea. > For internal-only networks, there will most likely be a user-space > ethernet switch (ala VDE) that bhyve network interfaces can be pointed at. Great: Why not the high-perf netmap VALE switch ? Because with a dummy TCP iperf bench between bhyve guests report only 254 Mbits/sec. Regards, From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 11:37:14 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 4963DD0E; Sat, 8 Feb 2014 11:37:14 +0000 (UTC) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0E97A13CA; Sat, 8 Feb 2014 11:37:14 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id lf10so4241942pab.18 for ; Sat, 08 Feb 2014 03:37:13 -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=G++wG3iuPdY+qK4D8bQHEdjwJMP8e6CbcRsN2Pajw60=; b=Psp/+A6W+BG4Jn9RBB2dD4TWs61qYJKaY0O5uM14pK1EToqt4DDA4MJK2wQgYC0akz O5vZITiEVqpo0sn1NDGKj/UaEymde45z6eCVm+ZSaYv+ZBODUZtb9hjDwngjW5035lel 9HtZ5zms5pJTxP4QSN3RpuvpsQn7jP9Ly3JNyHjhBd/Q8KFFic8REN4eI5nD0iDyuKyl VoLXDk2TpJIsgVNqvzJg/Hsv9pRnJ1T4oDItf8tmDbWJDErD4Zus780NsrOB+ZKcrwwB Mh6PHhxt7bLalrj9oAA5Ts/59IEKpA6ATi6ODU10j4xd4AzaIfyV152P3gcIHGJIhjNN 8tGg== MIME-Version: 1.0 X-Received: by 10.66.141.231 with SMTP id rr7mr13480886pab.41.1391859432915; Sat, 08 Feb 2014 03:37:12 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 03:37:12 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 06:37:12 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: "freebsd-virtualization@freebsd.org" X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 11:37:14 -0000 On Sat, Feb 8, 2014 at 6:20 AM, Olivier Cochard-Labb=E9 wrote: > On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote: > > > > > > > If you create a sparse file for the bhyve raw disk (e.g. with truncate > > -s), du will show the actual blocks used rather than the total size. > > > But can I truncate an already existing image disk (downloaded nanobsd ima= ge > as example) ? > You can increase the size but not lower it. If your using raw format you just scp it over and it will work fine. (bhyve only supports raw format) --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 11:39:29 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 7E6AFE45; Sat, 8 Feb 2014 11:39:29 +0000 (UTC) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B2FD13E1; Sat, 8 Feb 2014 11:39:29 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id kp14so4243414pab.6 for ; Sat, 08 Feb 2014 03:39:29 -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=1l3lf3N5nkXhzBFtwMwJnqyjWbo8YEsZYlS9UN4fQxM=; b=vrK9NIdVwyVFKyxkkGSsgRu1Bm2QR8DbP29MpmPYsjElysUPNNPT9T92DHC/Avlmh+ VpDx4OND8EA1B0t92d1UK568lFxVSZqxoJizj052GVNBHxkV2hTR8M3DRYiBcThRL8Ds 2vqE+YL0ClkHD1LGQ/uZifB5IE6/wSdH2sQIpM1xo4HdAtYVZ6y0vXOkpMmZ+B84xzv4 /R912cH/JYoqEMiaEpmML4qkYICzsT43V7MyyjI0VcFCzRxeK31lAGvnp7zvXTMWt6dB Rm1TIKz7OKFpqHnQQ5EWYXSEgHP6jEW8GAlHp+xlOs6zpz5n8wdD1lYvuzwZr6lVEQRh SxqA== MIME-Version: 1.0 X-Received: by 10.66.121.164 with SMTP id ll4mr4603193pab.129.1391859568925; Sat, 08 Feb 2014 03:39:28 -0800 (PST) Received: by 10.70.92.71 with HTTP; Sat, 8 Feb 2014 03:39:28 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 05:39:28 -0600 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Adam Vande More To: =?ISO-8859-1?Q?Olivier_Cochard=2DLabb=E9?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 11:39:29 -0000 On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labb=E9 wrote: > On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote: > > > > > > > If you create a sparse file for the bhyve raw disk (e.g. with truncate > > -s), du will show the actual blocks used rather than the total size. > > > But can I truncate an already existing image disk (downloaded nanobsd ima= ge > as example) ? There is this: https://github.com/masover/sparsify I think this or something like it used to be in ports too. --=20 Adam From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 11:42:55 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 0689D14B for ; Sat, 8 Feb 2014 11:42:55 +0000 (UTC) Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C4CAA14C1 for ; Sat, 8 Feb 2014 11:42:54 +0000 (UTC) Received: by mail-pd0-f177.google.com with SMTP id x10so4193403pdj.22 for ; Sat, 08 Feb 2014 03:42:54 -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=rKCjzVKcGuqoCcJvlPNdact5RHB8kqA6QxjmuxeLGMQ=; b=Mf+mcne4pDyDsKK2Bc4DyWH2L/02x8NnA04E3me2F2h2x/JQXUO/RVwO9XU99KSoAa mjwnWR21UI/wbxqSKK9uKqOeW8zBNuw92rX5S2oGh5t6NyZwEjXhnrHoIHwIhRo8s+36 LBoX0+WDqPpBz+9hb5udC10pqmoyAwSFvC4Dt7Rt/xrE4SMs6jW/JulB61WmdSv43JGV zA8vRaEQZJMTwr/Cwqs/nl9cUk5oeTeFjvBEtyNOYhIKmTeSukkLUkRE44qqAkN9zD8g YLb3d+8u26s8Muz0O2NTn3Nl94E/nXm98MlslPz1YtkT54IJ1IJAe9jJ7EqHKvaHy2Fu Iw0w== MIME-Version: 1.0 X-Received: by 10.66.221.199 with SMTP id qg7mr13865983pac.88.1391859774393; Sat, 08 Feb 2014 03:42:54 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 03:42:54 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 06:42:54 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 11:42:55 -0000 On Sat, Feb 8, 2014 at 6:39 AM, Adam Vande More wrot= e: > On Sat, Feb 8, 2014 at 5:20 AM, Olivier Cochard-Labb=E9 >wrote: > > > On Fri, Feb 7, 2014 at 8:38 PM, Peter Grehan wrote= : > > > > > > > > > > > If you create a sparse file for the bhyve raw disk (e.g. with trunca= te > > > -s), du will show the actual blocks used rather than the total size. > > > > > > But can I truncate an already existing image disk (downloaded nanobsd > image > > as example) ? > > > There is this: https://github.com/masover/sparsify > > I think this or something like it used to be in ports too. > bhyve (as far I know) disks must be one solid file (md backed) or a /dev block device... therefore it is unlikely the above would work --=20 Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 12:34:39 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 805CA79F for ; Sat, 8 Feb 2014 12:34:39 +0000 (UTC) Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4B70C183A for ; Sat, 8 Feb 2014 12:34:39 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id v10so4246077pde.13 for ; Sat, 08 Feb 2014 04:34:39 -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=pevHgN+vH9gnOpm8nbsDCMCPMyEHngHYN0Byn4w8Rl4=; b=fO+qJlgjbG18miHUjBP3mmoPyO9w71I3fD4vMGlXNMZd8Vv3OyfqYUMRziryUs9+IB WFG/cIl203+lQaP9+0XHa9FlpbHaKBay8oIft7DDuGWySEuwHXNni8HPvTO/vwZAVNzv TTkcAoBX535r1zQAASx16jDSw9n2tyrfdXeEV3FHSRUOPWzX9k3XnnlUsdvCL3sjSVtQ d8OGoUTYgY40+cvYaYbhskGyoKFgpyuXgAj4GsHe0701vqhQDKdhptLq33Da/4S0NQ1R 737VmZuXKgv9O+UEUbzrd/1lu8ka9uwtL0iGVQEdyabQqHc1ccBeiDmZVbqj+nUMozau MR0A== MIME-Version: 1.0 X-Received: by 10.66.49.74 with SMTP id s10mr14131267pan.0.1391862878901; Sat, 08 Feb 2014 04:34:38 -0800 (PST) Received: by 10.70.92.71 with HTTP; Sat, 8 Feb 2014 04:34:38 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 06:34:38 -0600 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Adam Vande More To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 12:34:39 -0000 On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman wrote: > > bhyve (as far I know) disks must be one solid file (md backed) or a /dev > block device... therefore it is unlikely the above would work > The reported size would be identical so I don't see what the problem is. -- Adam From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 12:51:37 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 22B3EA3A for ; Sat, 8 Feb 2014 12:51:37 +0000 (UTC) Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E61FC1960 for ; Sat, 8 Feb 2014 12:51:36 +0000 (UTC) Received: by mail-pb0-f50.google.com with SMTP id rq2so4368910pbb.23 for ; Sat, 08 Feb 2014 04:51:36 -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=mvOTc2lmMW9YOVUD2eyziEpccp2/bMTJ0qhqvr9F320=; b=La5Nxdxn1Tz+L2pSau0qdoQtgI2lZHYkacNFOWapFJX6gxo4bi/ZhMv/JnTnshw3lB aOfrVaHC0NQv4+q1aFw/PBrLRzwu8g4cOBDHlLmf4djgBpOm0vzsV+dKBSadHujmori1 42fMtAPZq09KxREUrTTciTlH0JR4RwJr4Sw4i/8tRpUYWlsr4yOmbimfNoFzm7vIArd3 XcHE6hV3033AvZQ9R3hRl5zdZOavyAwuESaTy5mvEFFFkrna07lHWD8yrf8Vc6NicZzW dEpzO1n4OQeIXQ1dBrjJz5zdQT5+sErKhHT/l38O4c4CBG5GfQKN3J/Kmx5AMUbUsurr sBGQ== MIME-Version: 1.0 X-Received: by 10.66.192.74 with SMTP id he10mr14008781pac.126.1391863896534; Sat, 08 Feb 2014 04:51:36 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 04:51:36 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 07:51:36 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 12:51:37 -0000 On Sat, Feb 8, 2014 at 7:34 AM, Adam Vande More wrote: > > On Sat, Feb 8, 2014 at 5:42 AM, Aryeh Friedman wrote: >> >> bhyve (as far I know) disks must be one solid file (md backed) or a /dev >> block device... therefore it is unlikely the above would work >> > > The reported size would be identical so I don't see what the problem is. > bhyve blindly read/writes into the middle of the file without consulting the filesystem and thus bypassing any things like sparse fill in.... namely all you gain is a few seconds of startup time (matter of fact I think truncate might use sparse allocation [i.e. attempting to read into the middle with guest OS control will result in potentially seeing host data]) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:01:25 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 27C647C9 for ; Sat, 8 Feb 2014 20:01:25 +0000 (UTC) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E8DC81A22 for ; Sat, 8 Feb 2014 20:01:24 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id rd3so4554889pab.16 for ; Sat, 08 Feb 2014 12:01:24 -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=kowxfhgJe+zjd92AYtqQG+wS1lvOD6IEAVOYnj+gX6M=; b=fK2F9okK/Lf2hIEc1SbWoq65ek0yRIR+qQUFovDJJuR9+bocEyLiRh0A2kmIa68Gig YiEbAj0unbFIMxrQH/X/4jsCHG9PMKM3TvdEmanBl5ZerfsOYplOAXpitnvNXgMujutM KaaxG1ZKBEmS4atgzqFG8tbFo480Ko+ncE2JnS96UlWJ7QvPz0xyFfbtcvZgJf0PaC5q K38k9+/jVJoyrf4hvfFvASG3RBJJvlhEx5bGprH/0nm7WyBse+F3U9slFaAnQXsU2OT6 HWVdkDZh4objaNJ3WqWnN09HRX4Ee7MEkjk7tS+ndRQPrf3HeU+FIZmLQjr/kMTL28cX OtTQ== MIME-Version: 1.0 X-Received: by 10.66.27.201 with SMTP id v9mr16131165pag.136.1391889684471; Sat, 08 Feb 2014 12:01:24 -0800 (PST) Received: by 10.70.92.71 with HTTP; Sat, 8 Feb 2014 12:01:24 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 14:01:24 -0600 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Adam Vande More To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:01:25 -0000 On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman wrote: > > bhyve blindly read/writes into the middle of the file without consulting > the filesystem and thus bypassing any things like sparse fill in.... namely > all you gain is a few seconds of startup time (matter of fact I think > truncate might use sparse allocation [i.e. attempting to read into the > middle with guest OS control will result in potentially seeing host data]) > If this is true then there is a *critical* security issue. Using sparse files isn't to gain performance, it's to conserve disk space. Using md devices backed by sparse images would accomplish this. If the sparsify app works on FreeBSD, then there should be no problem using those type of volumes. -- Adam From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:14: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7EA92E6D for ; Sat, 8 Feb 2014 20:14:06 +0000 (UTC) Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4A79E1B0D for ; Sat, 8 Feb 2014 20:14:06 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id um1so4599093pbc.5 for ; Sat, 08 Feb 2014 12:14: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=VBMa6D5KFaiwvdGBnvLTLd9ePuzgSprQ88th6ng0Anc=; b=fG+dHcHbYolLe3WZVK4o3w0qER37yLiP/69g5QLNgm4DcZrEwEk7aitQBccLnMs97s fW8dBAwcHF7PvN2xjBO0VpcJsLqm6NL8rEAUombOvXpGbpprMZeQCJHI+SYHjCPrIk5N rRhL14xLQ8JUbBcTsF4PnDFItosvvEQSITIJxwM4w+BgnvLRKaduKganXUQ64U1vnxUf NLxQnOsol0fV6QugQCCFce7VXgtxXVmnNoZm/NAQ9c9c6BUWW8h5wUC2KUN4Cg+pLApU BwK7D12A8VBBoqxBRw/qtZgVwvyJb5qZLWSY2SU78Vl1ZfDG0Flc6GCgbgzdhEKnQS2l pFQg== MIME-Version: 1.0 X-Received: by 10.69.19.139 with SMTP id gu11mr27999427pbd.149.1391890445893; Sat, 08 Feb 2014 12:14:05 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 12:14:05 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 15:14:05 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:14:06 -0000 On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote: > > On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman wrote: >> >> bhyve blindly read/writes into the middle of the file without consulting >> the filesystem and thus bypassing any things like sparse fill in.... namely >> all you gain is a few seconds of startup time (matter of fact I think >> truncate might use sparse allocation [i.e. attempting to read into the >> middle with guest OS control will result in potentially seeing host data]) >> > > If this is true then there is a *critical* security issue. > > Using sparse files isn't to gain performance, it's to conserve disk space. > Using md devices backed by sparse images would accomplish this. If the > sparsify app works on FreeBSD, then there should be no problem using those > type of volumes. > > It sounds almost identical to the qcow2 security issue being discussed on qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve then in considering that it's default format is raw (should ahci-hdd be the default?). devel/qemu (not sure about -dev) uses qcow2 as a default and when playing with it on other OS's I found that it seemed to default to that also. It is my understand that most of the open source cloud platforms use qcow2 as their default also (I remember this from an attempt to install openstack grizzly last summer... I have not checked havana though... can any of the freebsd-openstack confirm this?). -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:19:05 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AB2CE13C for ; Sat, 8 Feb 2014 20:19:05 +0000 (UTC) Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 757C11B52 for ; Sat, 8 Feb 2014 20:19:05 +0000 (UTC) Received: by mail-pd0-f174.google.com with SMTP id z10so4489884pdj.19 for ; Sat, 08 Feb 2014 12:19: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=1mEEThoEdt37Ba2I49ckZUd5eV+1bykflg7UDxAfpn0=; b=HXehL0HR/IJVevWH8dnfaYPD5u0HiPF0xfI0J4zBH7Zc2liLeKpia37Y8wTVy1K8iP WL1Fs/PNE6pDiYwEP/vRDllVKQKJ9b9O2o1GDu18AAju2UCzD6Ibq4XDlGV+cE92aozP 5qqbe1IsVH+oxViWwsDBxJezrCbxuduo1Arljv/mnw8+52gzl9zvmpMRm0yOqMjzXOgC aAShJr6ykt71JFCvfhPFtCG3RXRFXxFIBrhYiagD3iE0ROmiW0R0Ugjh55io5jT84z0S wgEigZZgRp549fyKGoVP/4OHXK60aDDbWivQWdbH5kwk83jmtu7XCToR8CSAYZJ+QwEu 1Kfg== MIME-Version: 1.0 X-Received: by 10.66.192.74 with SMTP id he10mr15974952pac.126.1391890744898; Sat, 08 Feb 2014 12:19:04 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 12:19:04 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 15:19:04 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:19:05 -0000 On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman wrote: > > > > On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote: > >> >> On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman wrote: >>> >>> bhyve blindly read/writes into the middle of the file without consulting >>> the filesystem and thus bypassing any things like sparse fill in.... namely >>> all you gain is a few seconds of startup time (matter of fact I think >>> truncate might use sparse allocation [i.e. attempting to read into the >>> middle with guest OS control will result in potentially seeing host data]) >>> >> >> If this is true then there is a *critical* security issue. >> >> Using sparse files isn't to gain performance, it's to conserve disk >> space. Using md devices backed by sparse images would accomplish this. If >> the sparsify app works on FreeBSD, then there should be no problem using >> those type of volumes. >> >> > It sounds almost identical to the qcow2 security issue being discussed on > qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve then > in considering that it's default format is raw (should ahci-hdd be the > default?). devel/qemu (not sure about -dev) uses qcow2 as a default and > when playing with it on other OS's I found that it seemed to default to > that also. It is my understand that most of the open source cloud > platforms use qcow2 as their default also (I remember this from an attempt > to install openstack grizzly last summer... I have not checked havana > though... can any of the freebsd-openstack confirm this?). > Forgot to mention that the host OS's disk scheduling also gives a brief window of opportunity during the time after the inode is made and the old contents wiped due to the size of the file -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:24:45 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 89A3A1A4 for ; Sat, 8 Feb 2014 20:24:45 +0000 (UTC) Received: from mail-pa0-x22b.google.com (mail-pa0-x22b.google.com [IPv6:2607:f8b0:400e:c03::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 53C961BE0 for ; Sat, 8 Feb 2014 20:24:45 +0000 (UTC) Received: by mail-pa0-f43.google.com with SMTP id rd3so4588997pab.30 for ; Sat, 08 Feb 2014 12:24:45 -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=LSR/PujOdkOWAYdygmQV/IBuKYF84b06DeapZHkQfz0=; b=Sgb8rZcldcUnOAJrquDZ0vQaFVKWIOOR/+BoT0nD0xsB3fMVVTBaVdWkzx7S1K1HUg Yuu3AZqX7dLVYAP4NL7TLtt/FlTFHC/OGf1e6EukWaCHz/kETLe822nQSiXCIBfyooVM PyxX/Li9h+QmXcsQuso3Wl2tAZbqrqBvYxw0Nst4yxaXnKDwMQa/FLYIDWDtiH/HT+Rh BLnyNsizxLrC9MilFlkm1o2rslsj4DnCoEQEe/4cJyCAa7RosR+a0Xk25jixcJ7QeYuQ kggPZgt/hhSIHsolwIbxl28dqp1K9nbHM3bk78dwn9N2Ipiqk5e07/RzsInClLc/O8c4 hmaw== MIME-Version: 1.0 X-Received: by 10.68.240.36 with SMTP id vx4mr28075024pbc.140.1391891084975; Sat, 08 Feb 2014 12:24:44 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 12:24:44 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 15:24:44 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:24:45 -0000 On Sat, Feb 8, 2014 at 3:19 PM, Aryeh Friedman wrote: > > > > On Sat, Feb 8, 2014 at 3:14 PM, Aryeh Friedman wrote: > >> >> >> >> On Sat, Feb 8, 2014 at 3:01 PM, Adam Vande More wrote: >> >>> >>> On Sat, Feb 8, 2014 at 6:51 AM, Aryeh Friedman >> > wrote: >>>> >>>> bhyve blindly read/writes into the middle of the file without >>>> consulting the filesystem and thus bypassing any things like sparse fill >>>> in.... namely all you gain is a few seconds of startup time (matter of fact >>>> I think truncate might use sparse allocation [i.e. attempting to read into >>>> the middle with guest OS control will result in potentially seeing host >>>> data]) >>>> >>> >>> If this is true then there is a *critical* security issue. >>> >>> Using sparse files isn't to gain performance, it's to conserve disk >>> space. Using md devices backed by sparse images would accomplish this. If >>> the sparsify app works on FreeBSD, then there should be no problem using >>> those type of volumes. >>> >>> >> It sounds almost identical to the qcow2 security issue being discussed on >> qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve >> then in considering that it's default format is raw (should ahci-hdd be the >> default?). devel/qemu (not sure about -dev) uses qcow2 as a default and >> when playing with it on other OS's I found that it seemed to default to >> that also. It is my understand that most of the open source cloud >> platforms use qcow2 as their default also (I remember this from an attempt >> to install openstack grizzly last summer... I have not checked havana >> though... can any of the freebsd-openstack confirm this?). >> > > Forgot to mention that the host OS's disk scheduling also gives a brief > window of opportunity during the time after the inode is made and the old > contents wiped due to the size of the file > > My short memory must be going the main point I meant to make in the second reply is as far I know *ALL* hypervisors have the same blind read/write (remember they see what ever is acting as the disk as (from the VM's POV) a real disk and in order to maintain that illusion blind writes/reads are necessary) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:36:18 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 A96E5426 for ; Sat, 8 Feb 2014 20:36:18 +0000 (UTC) Received: from mail-pb0-f47.google.com (mail-pb0-f47.google.com [209.85.160.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B4281C88 for ; Sat, 8 Feb 2014 20:36:18 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp16so4634981pbb.6 for ; Sat, 08 Feb 2014 12:36:12 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=b6/B4fDWR25aGuxV8itClUoxslJBEPbWV4B/NL106Ro=; b=CuhkKGq2zCgQ0tg/cXetPVQC/KDd6UT0UUP/MOSo6sDw6T/l/fuOsfFBdXN+V0ejwM iI04+MffncZJuV9XumVX6gp0tKvjwT7OdjKcWoumG33aMo+OxV6/T7+dGUx3s5zvQoOp EeEj7mzdnLCq3y4lgA+Hq3mH4YAYNKK0idVcP4GzoYAk02mogg/t275Pma2AmWxJsEhC +bATtRocv1LxEhzf5M6cKYVSkcswG0EHR/OHcd0ewtd41jn2b4oPkCVJtAT0J6y9WifS oiKi76WZORrd4HN4BPyPxxjaZsE9nTbeiJ9PMbaTcuJ+8L2iS3e9Vx3eIbYLwUJlR8IM CKYg== X-Gm-Message-State: ALoCoQnDk4khqZGj2oKTw9qL8c7SVnRYApghOMRDWeWuNyyHsdHQWtFj7vf2imhrrtsG8Hkx1lRA X-Received: by 10.66.136.71 with SMTP id py7mr16307211pab.2.1391891772481; Sat, 08 Feb 2014 12:36:12 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id dr1sm26435235pbc.18.2014.02.08.12.36.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Feb 2014 12:36:11 -0800 (PST) Message-ID: <52F6953D.2010400@callfortesting.org> Date: Sat, 08 Feb 2014 12:36:13 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "freebsd-virtualization@freebsd.org" Subject: CFT: bhyve AMD snapshot Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:36:18 -0000 Hello all, I have built and uploaded a bhyve SVM project branch snapshot of r261578 (February 4th, 2014, MFC @ r259205) that can be found at: http://mirrors.nycbug.org/pub/bhyve/r261578-svm/ Those with Barcelona class (http://en.wikipedia.org/wiki/AMD_10h) AMD hardware are invited to give this. So far I have had luck with my humble Athlon(tm) II Neo N36L Dual-Core Processor (1297.87-MHz K8-class CPU). All the best, Michael Dexter bhyve volunteer From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:54:26 2014 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B8986A9 for ; Sat, 8 Feb 2014 20:54:26 +0000 (UTC) Received: from mail-pb0-x229.google.com (mail-pb0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CC7271DA2 for ; Sat, 8 Feb 2014 20:54:25 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id up15so4692953pbc.0 for ; Sat, 08 Feb 2014 12:54:25 -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=zMmJ3TOm6TUvDYDAacDbN3U6XEezqOg3nPE14h2lgic=; b=0gggyY9y4CWKnjAYCqeguYsjL9YCBXBkpkWOEj+qxsAHn4Z2bnz89MJ9f0WNMGxRUH 0qCgNUNnzUZnK89SSim9ZC3fV3sEpwW0h3LmjR73UhGs/iOwitIc9gLG7neYgUzadMuG WZ6zXmJDwoOcUJ8AXwQ2prEG2w0QdCMQcGqH2sqaN3jJvOO5D9GtRbDU/ZkLegjLiJXO A6aqEc/eAJP6HS1fIf3dIDyZX5zQan+fxPdfHSAfl3i7QknGejnYW8ucle7a6I7XPahY jvJzCgPPhEx7U8S6ALuQdialSZh4bmMFWcy0hCJSkV4MQFzNG002RIxwVzYG3sulPm9N v1hg== MIME-Version: 1.0 X-Received: by 10.68.176.65 with SMTP id cg1mr28176620pbc.145.1391892865428; Sat, 08 Feb 2014 12:54:25 -0800 (PST) Received: by 10.70.92.71 with HTTP; Sat, 8 Feb 2014 12:54:25 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 14:54:25 -0600 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Adam Vande More To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:54:26 -0000 On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote: > > > It sounds almost identical to the qcow2 security issue being discussed on > qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve then > in considering that it's default format is raw (should ahci-hdd be the > default?). devel/qemu (not sure about -dev) uses qcow2 as a default and > when playing with it on other OS's I found that it seemed to default to > that also. It is my understand that most of the open source cloud > platforms use qcow2 as their default also (I remember this from an attempt > to install openstack grizzly last summer... I have not checked havana > though... can any of the freebsd-openstack confirm this?). > I don't consider it a huge win because the possibility of using an insecure device precludes it. Someone high on the tree bhyve needs to confirm or deny this otherwise it is unsafe to recommend bhyve or petitecloud. No offense intended, I really hope it succeeds and will likely use it if it does. I cannot use anything which leaves the host open. I am also unclear on how bhyve bypasses GEOM which *should* prevent any of the symptoms discussed. -- Adam From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 20:57:28 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 57254863 for ; Sat, 8 Feb 2014 20:57:28 +0000 (UTC) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 22D5F1DB6 for ; Sat, 8 Feb 2014 20:57:28 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id md12so4672782pbc.30 for ; Sat, 08 Feb 2014 12:57:27 -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=dLYF0ElwfAo3QZPumirbPzejxGUi7a3gibebxBqEaKI=; b=tJiz5EnPcpWttSD0c/gt17/u7/HNUfsJQ9F+jgk+c3DW2mnCRNOW9b8Yf5Jma1bpU1 PkpGuXYiYlIpnL+s4eqZ8VUXnssAr0O8NZbLrJmrL5VmTZgZcUGpVtcz7H2VVYTVLNer APZskkyuOMIJdmSd9xmGLmrwyBnR3DhClpUWApcq57lT4MLSoFDdTkYtQwm9pmBomF0n 0ByVSnWtxJbLaJcGBRLYGSmehWKutri/4/nVXwA4cWNcEaw/tyGeKzQrdsX4Otb0PuPf 711ezGuteigLWQYLNPRdRlISXxQ+SW34IUEAcmMbgNVSTl/f9sjoy1qO08KLKtoHJfKt E2Qw== MIME-Version: 1.0 X-Received: by 10.68.64.196 with SMTP id q4mr23767623pbs.100.1391893047725; Sat, 08 Feb 2014 12:57:27 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 12:57:27 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 15:57:27 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 20:57:28 -0000 On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote: > > On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote: > >> >> It sounds almost identical to the qcow2 security issue being discussed on >> qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve >> then in considering that it's default format is raw (should ahci-hdd be the >> default?). devel/qemu (not sure about -dev) uses qcow2 as a default and >> when playing with it on other OS's I found that it seemed to default to >> that also. It is my understand that most of the open source cloud >> platforms use qcow2 as their default also (I remember this from an attempt >> to install openstack grizzly last summer... I have not checked havana >> though... can any of the freebsd-openstack confirm this?). >> > > I don't consider it a huge win because the possibility of using an > insecure device precludes it. Someone high on the tree bhyve needs to > confirm or deny this otherwise it is unsafe to recommend bhyve > or petitecloud. No offense intended, I really hope it succeeds and will > likely use it if it does. I cannot use anything which leaves the host > open. I am also unclear on how bhyve bypasses GEOM which *should* prevent > any of the symptoms discussed. > The point was that raw has no issue and this is the default for both bhyve and petitecloud (to avoid certain list politics I didn't mention it by name before). Sparse is the issue and thus qemu, openstack and cloudstack (as well as likely vbox) are a problem. -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 21:07:56 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 C22D8A84 for ; Sat, 8 Feb 2014 21:07:56 +0000 (UTC) Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8CF4B1F5A for ; Sat, 8 Feb 2014 21:07:56 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so4625041pab.38 for ; Sat, 08 Feb 2014 13:07:56 -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=QgugwZcOvr5+64c4uFVxjuLj36cyJOBfH1Xzo9Ag2/k=; b=w16o4F3j2pou1yfV3rEAlVgGQuw5M5wxorcnKPK72Fc+k5FTQ0YPg3oktMHIFkawlT 5+WhJHYDuZKHbnkzAjkxnblW+CeuQmdrK56NkEFiz9JPXwxtC/cJzjia/DaQxOnhO+Y8 uU1Lq4eaihSFyjPjC0Im825VVTTW7VoSrmD5vzi9K7TnVgMo9oa2i0x2DT3HpzEQ590M FSEPqcLrbbRGFgQ7PXZIrtKy7OMzCwBgBuiuNZbVaVGYk5FyCDEN8CHZhbhxbjfaQufg bUHRmUyIl9RSJBGq1QULZ4BvnKjwLgfLc6aXyHWfXBz476q5JMhdSnVYsXVbb7cr9oH2 kTtw== MIME-Version: 1.0 X-Received: by 10.66.27.72 with SMTP id r8mr16036753pag.62.1391893676145; Sat, 08 Feb 2014 13:07:56 -0800 (PST) Received: by 10.70.92.71 with HTTP; Sat, 8 Feb 2014 13:07:56 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 15:07:56 -0600 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Adam Vande More To: Aryeh Friedman Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 21:07:56 -0000 On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman wrote: > > > > On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote: > >> >> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote: >> >>> >>> It sounds almost identical to the qcow2 security issue being discussed >>> on qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve >>> then in considering that it's default format is raw (should ahci-hdd be the >>> default?). devel/qemu (not sure about -dev) uses qcow2 as a default and >>> when playing with it on other OS's I found that it seemed to default to >>> that also. It is my understand that most of the open source cloud >>> platforms use qcow2 as their default also (I remember this from an attempt >>> to install openstack grizzly last summer... I have not checked havana >>> though... can any of the freebsd-openstack confirm this?). >>> >> >> I don't consider it a huge win because the possibility of using an >> insecure device precludes it. Someone high on the tree bhyve needs to >> confirm or deny this otherwise it is unsafe to recommend bhyve >> or petitecloud. No offense intended, I really hope it succeeds and will >> likely use it if it does. I cannot use anything which leaves the host >> open. I am also unclear on how bhyve bypasses GEOM which *should* prevent >> any of the symptoms discussed. >> > > The point was that raw has no issue and this is the default for both bhyve > and petitecloud (to avoid certain list politics I didn't mention it by name > before). Sparse is the issue and thus qemu, openstack and cloudstack (as > well as likely vbox) are a problem. > Yes but bhyve *supports* other backing devices than raw correct? Then this really bad. I don't want a politics game either, just saying you won't get adoption until security is clear. I have no problem with you mentioning petitecloud. Indeed I think you should but others may disagree. In your opinion are ZVOL's a good option? -- Adam From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 21:57: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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 92B82AA2 for ; Sat, 8 Feb 2014 21:57:46 +0000 (UTC) Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5945A12A8 for ; Sat, 8 Feb 2014 21:57:46 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id lf10so4595685pab.18 for ; Sat, 08 Feb 2014 13:57:46 -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=oMR+ga09H/NysvlrtnmJy0ZoA1xUD+6DcwL5XozCi5Q=; b=W51m+ES3gRZK5r2Pjqie8GqsMoAcq3BzV6qn7LfhaAE1vD7EGJHEfrKIDQvIRYazU0 7CW/ZKFv/OIjcRwfXXODPkIzxWv4Twpimi+0Um3wE4otZfQoD3lirzNR6F68g63xTgSi TnHBzxaPMIWwSfyW38v9rRhjUAJpp4S7/rjRZOGqX3AyKTb9t62ZRxnnuQvKiqux/G/9 tlidQ9Cxcn9mmiV6nzEeuGyCio69fq1uVSESVowPcjpsLVxnPXXI78tPmzz/hDWyBpKJ Ij5hQbOhwnAKXmm3uwt/j8kfVf/laF1euirJEXBwVaw0bWX2Pxst+q+QltIeYoUezkYP vVKg== MIME-Version: 1.0 X-Received: by 10.66.226.46 with SMTP id rp14mr16255053pac.133.1391896665998; Sat, 08 Feb 2014 13:57:45 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 13:57:45 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 16:57:45 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 21:57:46 -0000 On Sat, Feb 8, 2014 at 4:07 PM, Adam Vande More wrote: > > On Sat, Feb 8, 2014 at 2:57 PM, Aryeh Friedman wrote: > >> >> >> >> On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote: >> >>> >>> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman >> > wrote: >>> >>>> >>>> It sounds almost identical to the qcow2 security issue being discussed >>>> on qemu-devel@qemu.org recently. This might be a *HUGE* win for >>>> bhyve then in considering that it's default format is raw (should ahci-hdd >>>> be the default?). devel/qemu (not sure about -dev) uses qcow2 as a >>>> default and when playing with it on other OS's I found that it seemed to >>>> default to that also. It is my understand that most of the open source >>>> cloud platforms use qcow2 as their default also (I remember this from an >>>> attempt to install openstack grizzly last summer... I have not checked >>>> havana though... can any of the freebsd-openstack confirm this?). >>>> >>> >>> I don't consider it a huge win because the possibility of using an >>> insecure device precludes it. Someone high on the tree bhyve needs to >>> confirm or deny this otherwise it is unsafe to recommend bhyve >>> or petitecloud. No offense intended, I really hope it succeeds and will >>> likely use it if it does. I cannot use anything which leaves the host >>> open. I am also unclear on how bhyve bypasses GEOM which *should* prevent >>> any of the symptoms discussed. >>> >> >> The point was that raw has no issue and this is the default for both >> bhyve and petitecloud (to avoid certain list politics I didn't mention it >> by name before). Sparse is the issue and thus qemu, openstack and >> cloudstack (as well as likely vbox) are a problem. >> > > Yes but bhyve *supports* other backing devices than raw correct? Then > this really bad. > > I don't want a politics game either, just saying you won't get adoption > until security is clear. I have no problem with you mentioning > petitecloud. Indeed I think you should but others may disagree. In your > opinion are ZVOL's a good option? > Starting tomorrow (now that I got the evil empire OS out of the way) I am going to be adding both networking and storage... in that order but I plan to handle some "low hanging" things in storage before getting deep into networking like allowing any block device to be used (it is up to the host admin how they want to attach it all petitecloud will need is a /dev/ entry or a backing file [some remote storage solutions do present this way not just disk image files])... we do not preannounce features normally but since this is security related we felt it was important to answer with specific plans (no specific due date though since that is our primary reason for not preannouncing is avoiding missing promised dates)... long term see the draft of a white paper I posted a week or so here -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 22:39:11 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 1ADA795D for ; Sat, 8 Feb 2014 22:39:11 +0000 (UTC) Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D8F1D1584 for ; Sat, 8 Feb 2014 22:39:10 +0000 (UTC) Received: by mail-pb0-f47.google.com with SMTP id rp16so4694862pbb.6 for ; Sat, 08 Feb 2014 14:39:10 -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=HF9IL7RtD1Gpsd9g8Q7p8PdWS8tYENCNelJ/1Bo6Ni4=; b=MslBg0P8nFk9UoxFIKUHWHaZVIZ8lXO0T81Rs1aG8r+JRWNDB9cc1kxZoU29muh3PN QBdKpVaJixqTWi4lR5NW6fEpTBvQbzQL6prSs+FwvUQMJ69CLTA7kcmMDr86Ze7G1JGT mDrCzT4DbFTOAFCvIEqtgSrw3Wbo8z51A4aVZQCn7TR5YM1M5jL9B/CY61kaTeUBL7w4 UMTu92uqGv/M2/7UNN//Se+nvfTDBd81CloH86nuiNQYCvXAsJVDodPjep7QN/qaMLSd /BruDV817w5OUE89ATkyi3g1P0SyaBmXf/a5bwQjm2pzuxoc9O2ef+Vd9eLkQEjDMPlD X2tg== MIME-Version: 1.0 X-Received: by 10.68.201.97 with SMTP id jz1mr28606314pbc.26.1391899150391; Sat, 08 Feb 2014 14:39:10 -0800 (PST) Received: by 10.68.155.38 with HTTP; Sat, 8 Feb 2014 14:39:10 -0800 (PST) In-Reply-To: References: <52F5363D.8040102@freebsd.org> Date: Sat, 8 Feb 2014 17:39:10 -0500 Message-ID: Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve From: Aryeh Friedman To: Adam Vande More Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 22:39:11 -0000 On Sat, Feb 8, 2014 at 3:57 PM, Aryeh Friedman wrote: > > > > On Sat, Feb 8, 2014 at 3:54 PM, Adam Vande More wrote: > >> >> On Sat, Feb 8, 2014 at 2:14 PM, Aryeh Friedman wrote: >> >>> >>> It sounds almost identical to the qcow2 security issue being discussed >>> on qemu-devel@qemu.org recently. This might be a *HUGE* win for bhyve >>> then in considering that it's default format is raw (should ahci-hdd be the >>> default?). devel/qemu (not sure about -dev) uses qcow2 as a default and >>> when playing with it on other OS's I found that it seemed to default to >>> that also. It is my understand that most of the open source cloud >>> platforms use qcow2 as their default also (I remember this from an attempt >>> to install openstack grizzly last summer... I have not checked havana >>> though... can any of the freebsd-openstack confirm this?). >>> >> >> I don't consider it a huge win because the possibility of using an >> insecure device precludes it. Someone high on the tree bhyve needs to >> confirm or deny this otherwise it is unsafe to recommend bhyve >> or petitecloud. No offense intended, I really hope it succeeds and will >> likely use it if it does. I cannot use anything which leaves the host >> open. I am also unclear on how bhyve bypasses GEOM which *should* prevent >> any of the symptoms discussed. >> > > The point was that raw has no issue and this is the default for both bhyve > and petitecloud (to avoid certain list politics I didn't mention it by name > before). Sparse is the issue and thus qemu, openstack and cloudstack (as > well as likely vbox) are a problem. > > I should say in all the sparse format cases I do not consider it a flaw (per se) that they picked because if your not considering sceurity qcow2 is a very good format. If PetiteCloud had not started with bhyve as our first hypervisor instead of say qemu it is almost certain we would of fallen into the same trap. It is easy to over look the obvious also like for example until this thread I didn't see how image format could effect security (assuming that it was not crypted of course) -- Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 23:18:06 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 AE819D78 for ; Sat, 8 Feb 2014 23:18:06 +0000 (UTC) Received: from mail-pb0-f46.google.com (mail-pb0-f46.google.com [209.85.160.46]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 72BCE17D1 for ; Sat, 8 Feb 2014 23:18:06 +0000 (UTC) Received: by mail-pb0-f46.google.com with SMTP id um1so4708028pbc.19 for ; Sat, 08 Feb 2014 15:18:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rYdQNCM8qHQblWxPhns11GQml5gEKDAGIJRB0WLwubU=; b=fut/Y3d96C3IaXlqm9yAp0OBcFx8P4Rz54ED4x6VVWQ0aGKrbmsIM2WV+xsfL9X7do i3uZmUy1u0P2ZMgt/dpeKoxcx5nwOFAt56AuuvFCMw76ryvH6rZ40NQxjXjbY60h4F9N uMRk7me28A4gjd12liPk+6bumW8KyJNMiOrJ3ajMxDQ8QcVWS7ohLJhaE9supU/gX67O UcX/O8DTD5Y5ly4TZlqbqJcTlwu9KxKWEIuyTJIdnriw7FLCveIt2JyxOt1idBpBDaff DkMN8rKwinYvtK2NFSQ8xyrUSaYNMwBJHRmoknQWp9PVrD2JvBhA9jG3a+7Rjz3zbcZH 5xWQ== X-Gm-Message-State: ALoCoQmClAyYF/O+so2bSpUPj+zmPbSq2QxjCbegZk6NY2lJeRDYWVPzraeAdlOni/SmuWgkg8e0 X-Received: by 10.68.75.9 with SMTP id y9mr28517991pbv.61.1391901480092; Sat, 08 Feb 2014 15:18:00 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id fk4sm69982667pab.23.2014.02.08.15.17.57 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Feb 2014 15:17:58 -0800 (PST) Message-ID: <52F6BB25.7000209@callfortesting.org> Date: Sat, 08 Feb 2014 15:17:57 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman , Adam Vande More Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve References: <52F5363D.8040102@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 23:18:06 -0000 On 2/8/14 1:57 PM, Aryeh Friedman wrote: > Starting tomorrow (now that I got the evil empire OS out of the way) I am > going to be adding both networking and storage... in that order but I plan > to handle some "low hanging" things in storage before getting deep into > networking like allowing any block device to be used (it is up to the host > admin how they want to attach it all petitecloud will need is a /dev/ entry > or a backing file [some remote storage solutions do present this way not > just disk image files])... we do not preannounce features normally but > since this is security related we felt it was important to answer with > specific plans (no specific due date though since that is our primary > reason for not preannouncing is avoiding missing promised dates)... long > term see the draft of a white paper I posted a week or so here May I again suggest you take this type of message to a personal blog or the mailing list you suggested? http://lists.petitecloud.nyclocal.net/listinfo.cgi Your personal plans apply to you alone and not the FreeBSD operating system or its virtualization subsystems. You have posted 31 out of the 83 messages to date in February with the next closest person coming in at six messages and a total of 10 from the key bhyve developers on a list for all FreeBSD virtualization technologies. Please reconsider this strategy else a complaint will be registered with the list administrators. Michael Dexter bhyve volunteer From owner-freebsd-virtualization@FreeBSD.ORG Sat Feb 8 23:28:19 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 CF7EBC6 for ; Sat, 8 Feb 2014 23:28:19 +0000 (UTC) Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 937E6187D for ; Sat, 8 Feb 2014 23:28:19 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id g10so4613692pdj.30 for ; Sat, 08 Feb 2014 15:28:13 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=CxhyiYlxzjzh49O1rH9pEviLIBkO6e2UR8/k8qzx7Rs=; b=BDsbCQOygw5a5jZLliN5rI2++BWDayaGZyjpOz1hdXDfpMifpLCmV63B8ilgaG4lDR 9d2aoi4vEBVrARsUa1TxaQCWrl8jqrWvaz6ysLzegvE8WC1C6ISzOG0xx1fw6pJKUxC+ XMZYpA6NbZxJXruh620GiaZhRLBHBOwtX2pFXV9luXsrAcHjWEh2+N7DGOL79geH/lw0 Tk8wTGDuQdzvy3a8nLSOJIC4Zpydi3WOiYb5GKO1G3u6YjvJyNx8sc5XEFXMfb8RmCK1 7Ga03aOaGTZBjSvGeaxKI8I5T40k06AlSXxIbgYrGh+W0DxS+iTMy0ZI/IUZQjjPVNDI MAHQ== X-Gm-Message-State: ALoCoQm58z3ENCLMZhh4inJJYsrpQ84EHGPUBBA5I14AZxC24SDD0NvpTR9IngaW1NokfNxGoyYO X-Received: by 10.66.26.10 with SMTP id h10mr16595292pag.24.1391902093253; Sat, 08 Feb 2014 15:28:13 -0800 (PST) Received: from Michaels-MacBook-Pro.local (c-98-246-202-204.hsd1.or.comcast.net. [98.246.202.204]) by mx.google.com with ESMTPSA id yz5sm70210843pac.9.2014.02.08.15.28.12 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Feb 2014 15:28:12 -0800 (PST) Message-ID: <52F6BD8B.7080205@callfortesting.org> Date: Sat, 08 Feb 2014 15:28:11 -0800 From: Michael Dexter User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Aryeh Friedman , Adam Vande More Subject: Re: Report of my virtual network lab migrated from virtualbox to bhyve References: <52F5363D.8040102@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD virtualization X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.17 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, 08 Feb 2014 23:28:19 -0000 For the curious, Aryeh posted 67 out of January's 276 messages to the list with the next highest poster coming in at 21. This is not the proper use of this list. Michael Dexter bhyve volunteer