From owner-freebsd-virtualization@FreeBSD.ORG Mon Sep 24 11:07:35 2012 Return-Path: Delivered-To: freebsd-virtualization@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D495F1065673 for ; Mon, 24 Sep 2012 11:07:35 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id BC7968FC1B for ; Mon, 24 Sep 2012 11:07:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q8OB7Z8U086123 for ; Mon, 24 Sep 2012 11:07:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q8OB7ZqS086121 for freebsd-virtualization@FreeBSD.org; Mon, 24 Sep 2012 11:07:35 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 24 Sep 2012 11:07:35 GMT Message-Id: <201209241107.q8OB7ZqS086121@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 Cc: Subject: Current problem reports assigned to freebsd-virtualization@FreeBSD.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2012 11:07:35 -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/170096 virtualization[vimage] Dynamically-attached network interface will c o kern/169991 virtualization[run] [vimage] panic after device plugged in 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/IPFilter + VIMAGE k a kern/147950 virtualization[vimage] [carp] VIMAGE + CARP = kernel crash s kern/143808 virtualization[pf] pf does not work inside jail a kern/141696 virtualization[rum] [vimage] [panic] rum(4)+ vimage = kernel panic 10 problems total. From owner-freebsd-virtualization@FreeBSD.ORG Thu Sep 27 02:38:26 2012 Return-Path: Delivered-To: virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE40E106564A for ; Thu, 27 Sep 2012 02:38:26 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 67ACC8FC0A for ; Thu, 27 Sep 2012 02:38:25 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1008533bkc.13 for ; Wed, 26 Sep 2012 19:38:25 -0700 (PDT) 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=yNc3k7NMDBV4sGMmatC/rWCbS3Q2Y6JaWaAR0i2E0vA=; b=fAZ+5EHu+tYRRgn8GH7Bof70cX8VBziubmUO9HFFUNhZ4f+BjbqoHaWkmeaUDrGdt9 uColx8E0h99sacOOA5AH75SgT2GlS3XS3xrj0Z1TXacN/eSteNf/9iTB8L/8FL6L2CE0 D3MmH8pL+GgODcP4EYjFlr/R3IXEeABkYL+FoJRtoevu9zM32N2zGnyTUYVOBQQKFOn9 nw6UfF3Hfpn3cbNEpN44izqW8h/l6syH4THdTuAvX5pYFCQU54TXPPfpB35aEgyNehU6 npcxnj135xSSK7BSEWTuqtxXWX6sr1hQdItqm3s3NE2+mQd+6RCZUjVqWeys8YACicQa totg== MIME-Version: 1.0 Received: by 10.112.24.233 with SMTP id x9mr1038894lbf.76.1348713504761; Wed, 26 Sep 2012 19:38:24 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 26 Sep 2012 19:38:24 -0700 (PDT) Received: by 10.114.23.230 with HTTP; Wed, 26 Sep 2012 19:38:24 -0700 (PDT) In-Reply-To: <87zk4c2tqq.fsf@rustcorp.com.au> References: <87zk4c2tqq.fsf@rustcorp.com.au> Date: Wed, 26 Sep 2012 19:38:24 -0700 Message-ID: From: Freddie Cash To: virtualization@freebsd.org, "kernel@crater.dragonflybsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Fwd: Proposal for virtio standardization. X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Sep 2012 02:38:27 -0000 Thought this might be of interest to you all, as there are efforts underway to develop virtio drivers for FreeBSD and DragonFlyBSD. ---------- Forwarded message ---------- From: "Rusty Russell" Date: Sep 26, 2012 7:07 PM Subject: Proposal for virtio standardization. To: "Anthony Liguori" , "Adam Litke" , "Amit Shah" , "Avi Kivity" , "Avishay Traeger" , "Jason Wang" , "Michael S. Tsirkin" , "Ohad Ben-Cohen" , "Paolo Bonzini" , "Pawel Moll" , "Sasha Levin" , "Cornelia Huck" Cc: , "LKML" < linux-kernel@vger.kernel.org>, , "qemu-devel" < qemu-devel@nongnu.org> Hi all, I've had several requests for a more formal approach to the virtio draft spec, and (after some soul-searching) I'd like to try that. The proposal is to use OASIS as the standards body, as it's fairly light-weight as these things go. For me this means paperwork and setting up a Working Group and getting the right people involved as Voting members starting with the current contributors; for most of you it just means a new mailing list, though I'll be cross-posting any drafts and major changes here anyway. I believe that a documented standard (aka virtio 1.0) will increase visibility and adoption in areas outside our normal linux/kvm universe. There's been some of that already, but this is the clearest path to accelerate it. Not the easiest path, but I believe that a solid I/O standard is a Good Thing for everyone. Yet I also want to decouple new and experimental development from the standards effort; running code comes first. New feature bits and new device numbers should be reservable without requiring a full spec change. So the essence of my proposal is: 1) I start a Working Group within OASIS where we can aim for virtio spec 1.0. 2) The current spec is textually reordered so the core is clearly bus-independent, with PCI, mmio, etc appendices. 3) Various clarifications, formalizations and cleanups to the spec text, and possibly elimination of old deprecated features. 4) The only significant change to the spec is that we use PCI capabilities, so we can have infinite feature bits. (see http://lists.linuxfoundation.org/pipermail/virtualization/2011-December/019198.html ) 5) Changes to the ring layout and other such things are deferred to a future virtio version; whether this is done within OASIS or externally depends on how well this works for the 1.0 release. Thoughts? Rusty. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html