From owner-freebsd-virtualization@freebsd.org  Wed May 31 01:48:52 2017
Return-Path: <owner-freebsd-virtualization@freebsd.org>
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 831BDBF2EAB
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Wed, 31 May 2017 01:48:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 709D883213
 for <freebsd-virtualization@FreeBSD.org>; Wed, 31 May 2017 01:48:52 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v4V1mqKi041291
 for <freebsd-virtualization@FreeBSD.org>; Wed, 31 May 2017 01:48:52 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 211136] [Hyper-V]mount root may fail because vfs' mount starts
 early than VMBUS
Date: Wed, 31 May 2017 01:48:52 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: honzhan@microsoft.com
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-virtualization@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-211136-27103-OgFolqIiJr@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-211136-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-211136-27103@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-virtualization@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Discussion of various virtualization techniques FreeBSD supports."
 <freebsd-virtualization.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-virtualization/>
List-Post: <mailto:freebsd-virtualization@freebsd.org>
List-Help: <mailto:freebsd-virtualization-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization>, 
 <mailto:freebsd-virtualization-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 May 2017 01:48:52 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211136

--- Comment #5 from Hongjiang <honzhan@microsoft.com> ---
(In reply to David Marker from comment #4)
If you do not use ZFS, the mount failure should not occur on 11-stable if y=
ou
set a relative long waiting time: "vfs.mountroot.timeout=3D30". On Azure, I=
 used
"vfs.mountroot.timeout=3D300" and this error never happen.

If you want to use ZFS, the current workable solution is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D208882.

--=20
You are receiving this mail because:
You are the assignee for the bug.=