From owner-freebsd-virtualization@FreeBSD.ORG Tue Aug 26 15:23:27 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 C7FEF85A for ; Tue, 26 Aug 2014 15:23:27 +0000 (UTC) Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A720338A for ; Tue, 26 Aug 2014 15:23:27 +0000 (UTC) Received: by mail-yk0-f172.google.com with SMTP id 20so2236456yks.3 for ; Tue, 26 Aug 2014 08:23:26 -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 :cc:content-type; bh=98eJojYMjtZewLK0mXaFH/1fjdZjrFefmbR7SjcTwag=; b=M9z06XsZhM67mG1EvyhubFiT0XKAJHBRWPWqjkciFi8ZWpOPaZenxqQC8nkTdf0mQo ZSt7rYl5/6+02oKbtuhVuj0xOokLhzD1nO+tmyj7JuEnB5EMTr35gE6gKSQZQYBbSecR nlb1+FOy0I9vQImuLBBrm2zV+o2uVGc8d0VbrHE60fopleNm7V6yKj00bUgK8/HrLu3P UalHk5Sm4ROP2sLS3z5+ko1YgpMBw62EMkVdrtkzIv2WiS78TngoHkcD3jDZFK+zuRYy 5p35zuL7GGmJ3m40qotsb8knqVz9TDfz/9ttM6KBPXE7EIW0ZKkPj1vM82iwuhjUN5Mr BLqQ== MIME-Version: 1.0 X-Received: by 10.52.61.99 with SMTP id o3mr7998547vdr.46.1409066606613; Tue, 26 Aug 2014 08:23:26 -0700 (PDT) Received: by 10.221.46.133 with HTTP; Tue, 26 Aug 2014 08:23:26 -0700 (PDT) In-Reply-To: <53FC8DD9.4010202@hawara.com> References: <53FB2662.7090501@hawara.com> <53FB856A.4090900@freebsd.org> <53FBAA8A.40908@freebsd.org> <53FC8DD9.4010202@hawara.com> Date: Tue, 26 Aug 2014 17:23:26 +0200 Message-ID: Subject: Re: VirtIo errors inside VM with UFS-in-zvol From: Nikolay Denev To: Marat Bakeev Content-Type: text/plain; charset=UTF-8 Cc: freebsd-virtualization@freebsd.org X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Aug 2014 15:23:27 -0000 On Tue, Aug 26, 2014 at 3:38 PM, Marat Bakeev wrote: > > On 26/08/2014 09:28, Allan Jude wrote: >>> >>> Thanks Peter, >>> >>> That would be volmode=dev, correct? >> >> You want: vfs.zfs.vol.mode=2 >> >> in /boot/loader.conf >> >> It is my understanding that the sysctl must be set BEFORE the pool is >> imported to work correctly. > > What is the difference between property 'volmode=dev', and the sysctl? > When do I need to use the sysctl, and when do one needs to use the > volmode=dev? > > Either of them must be set in the host system, of course? > > _______________________________________________ > 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" To me it looks like you should not use the sysctl if you are using the zvols on the host systems for anything that expects them to be GEOM providers, e.g. mounting as UFS volumes, etc. as this will hide them from GEOM. For now I've set it to "dev" via the zfs property only for the zvols that I either export as iscsi or use for bhyve virts. Flipping the property has the effect of gpt partitions of the zvol disappearing and appearing again in /dev/zvol/..., while the system is running, while as Allan mentioned, setting the sysctl does not seem to affect zvols that are on already imported pool. --Nikolay