From owner-freebsd-virtualization@freebsd.org Mon Apr 25 04:15:46 2016 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 92761B1B40C for ; Mon, 25 Apr 2016 04:15:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 637D91A12 for ; Mon, 25 Apr 2016 04:15:46 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x229.google.com with SMTP id u185so172274136iod.3 for ; Sun, 24 Apr 2016 21:15:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc; bh=c38JuefBOOUsBNrB9H/XZ3B6T0EbUOGjHHmi5U3TxIs=; b=RjtlOfnSmKrxg81ITFAX6cKGAeivJuISj4d3Nj/KnTwRFsbbDCa1KA5UazB3cNs/T1 8G+OmpIRrQCHCxHpR394ke6+77RC7a+juHvlJMJ4JZIdmnXQOa31WAdrrsR2R6tlxs2L Tux1ITJnzLqhkGvOKYYMwrViYmi0wtyyapjrA2x6VoxUfo0zcOPzXTEZL+mi9oNVnJDA CUoMAWn1NwvOvvdEkHGXaG5I0DL+zMLJQLO7KRE4zD58Ec+vES+3ejA/kZ9trXMj1Ql2 HtRnoETzKw4DQ/5gIGMluwyh+FJ6nmVIYMPw8quTJj+KZxAQT4bN3gpoS3bDBcKLoIQR kWpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc; bh=c38JuefBOOUsBNrB9H/XZ3B6T0EbUOGjHHmi5U3TxIs=; b=ApNA/oyaOJtanB+PeCpufafMSTFoMPceOamGnllEJ9Wjp1rdPUGkTveyClBg6NO6Jr JXPKUO49Jkj/sSXwNxk+tc+ZEIss87Mhy0E1PMGd8EXCeGV4zUcu5z+7QGdABZhVI8lM 1iAhvn9Etqc2MrgexnNirjIZJSACzMkcLB8Q2dPZ+xI9L3Z8dskYXXZNAMTejjyFxkOm AaIImbyuHKKjRuIMUlnmJn2rKVuyohHCNRNqYu0mmJdgWSumbIZDxrUTsW86LLWqq/+Q v5M0YeE75k3+yP5t+KsbwYDv/Rn+G9B6PwDmsE9Oa3upDOa3JINjVS4TE3f5aY055Bah gOkQ== X-Gm-Message-State: AOPr4FX2Y+Skf55EEx6fJn/3IuxIavgAasKJW+4SOqm/NAPP7CL0pvX7sPhoYQqCV5yWNDWR6I+FuyP4qzGyeA== MIME-Version: 1.0 X-Received: by 10.107.133.229 with SMTP id p98mr7555952ioi.16.1461557745593; Sun, 24 Apr 2016 21:15:45 -0700 (PDT) Sender: wlosh@bsdimp.com Received: by 10.79.104.197 with HTTP; Sun, 24 Apr 2016 21:15:45 -0700 (PDT) X-Originating-IP: [50.253.99.174] In-Reply-To: <20160424204934.46eebae8@nonamehost.local> References: <20160415114443.660453cb@nonamehost.local> <20160424204934.46eebae8@nonamehost.local> Date: Sun, 24 Apr 2016 22:15:45 -0600 X-Google-Sender-Auth: RI13Xh1IOK9QxJcIGHye4YCUp8E Message-ID: Subject: Re: Heads up From: Warner Losh To: Ivan Klymenko Cc: FreeBSD Current , "freebsd-virtualization@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.21 X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.21 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, 25 Apr 2016 04:15:46 -0000 I'll try virtualbox again, but it booted fine when I tried it before. I'll give bhyve a sping. I haven't tried it in quite some time, but it worked about 9 months ago. But since I don't even know what the errors you are seeing are, I can't tell you that it is similar to some other error reports or something completely new. Warner On Sun, Apr 24, 2016 at 11:49 AM, Ivan Klymenko wrote: > On Fri, 15 Apr 2016 11:44:43 +0300 > Ivan Klymenko wrote: > > > On Thu, 14 Apr 2016 16:42:33 -0600 > > Warner Losh wrote: > > > > > The CAM I/O scheduler has been committed to current. This work is > > > described in > > > https://people.freebsd.org/~imp/bsdcan2015/iosched-v3.pdf though the > > > default scheduler doesn't change the default (old) behavior. > > > > > > One possible issue, however, is that it also enables NCQ Trims on > > > ada SSDs. There are a few rogue drives that claim support for this > > > feature, but actually implement data corrupt instead of queued > > > trims. The list of known rogues is believed to be complete, but > > > some caution is in order. > > > > > > Warner > > > > Hi. > > Thanks for you work. > > But i have problem with VirtualBox if i use the kernel with option > > CAM_NETFLIX_IOSCHED > > http://imgur.com/JpcfW1h > > This problem is not over. > After the update on other hardware from r296979 to r298512 (!!! without > option CAM_NETFLIX_IOSCHED !!!) due to errors in recording the virtual > machine to a virtual disk I lost completely virtual machine with > permanent damage to the integrity of the file system in the inside of > the virtual machine. > > This is a serious bug! > > Who cares not to fall into the same situation - is testing yourself > and needed more testers. > Because there is a suspicion that the problem is also relevant for > bhyve VM. > With me on this no more neither the strength nor the desire nor > time. > > Thanks. >