From owner-freebsd-virtualization@freebsd.org  Thu Nov 16 11:19:48 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 8551CDD9988
 for <freebsd-virtualization@mailman.ysv.freebsd.org>;
 Thu, 16 Nov 2017 11:19:48 +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 6FBCC769DF
 for <freebsd-virtualization@FreeBSD.org>; Thu, 16 Nov 2017 11:19:48 +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 vAGBJlfg029091
 for <freebsd-virtualization@FreeBSD.org>; Thu, 16 Nov 2017 11:19:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-virtualization@FreeBSD.org
Subject: [Bug 223531] Instant kernel panic on 'kldload virtio_console' on
 oVirt 3.5 VM
Date: Thu, 16 Nov 2017 11:19:48 +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: wosch@FreeBSD.org
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-223531-27103-YrPjSI1Sxm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-223531-27103@https.bugs.freebsd.org/bugzilla/>
References: <bug-223531-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.25
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: Thu, 16 Nov 2017 11:19:48 -0000

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

--- Comment #16 from Wolfram Schneider <wosch@FreeBSD.org> ---
I agree that spaces in filenames are not a good idea.=20

However, a kernel which is not booting due spaces is very bad. I removed the
space check in sys/kern/kern_conf.c and now I can boot my current kernel, a=
nd
upgrade the VM.

Attached a patch with a one line change. It could be that this change has
unknown side effect for devd
(PR #144736, PR #161912). Lets see.

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