Date: Wed, 15 Nov 2017 16:16:35 +0100 From: Wolfram Schneider <wosch@freebsd.org> To: cem@freebsd.org, Wolfram Schneider <wosch@freebsd.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: kernel panic: make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0) Message-ID: <CAMWY7CD_TizUU6mB%2Bv7Lb6i6nAOHrEmCwSLAPoN-aKZN8P8w-Q@mail.gmail.com> In-Reply-To: <CAG6CVpXnwbPxzK-WQM9wQ5OV_TvyHbKHr%2BMWVy1znEcutB_uSg@mail.gmail.com> References: <CAMWY7CBUdYqWxM19CTMvE_B2pH6FXV0YPX%2BRxkPURE1t_etZ0w@mail.gmail.com> <CAG6CVpXnwbPxzK-WQM9wQ5OV_TvyHbKHr%2BMWVy1znEcutB_uSg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15 November 2017 at 10:58, Conrad Meyer <cem@freebsd.org> wrote: > Hi Wolfram, > > Looks like the same issue as > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 . Hi Conrad, thanks for the hint. Do you know which commit may broke the driver? Is there any patch or workaround? I do not have access to the physical machine, only full root access to the guest. I don't want to bother with the cloud provider, I'm happy that they offer FreeBSD at all as a default installation. -Wolfram > Best, > Conrad > > On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider <wosch@freebsd.org> wrote: >> Hi, >> >> I have a virtual machine running with FreeBSD 11-stable at a cloud >> provider. It runs fine. I tried to upgrade to FreeBSD 12-current and >> the kernel panics at boot time with: >> >> make_dev_alias_v bad si_name (error=22) si_name=vtcon/ org.qemu.guest_agent.0) >> >> and hangs. Lucky, I still can boot from kernel.old and bring the machine up. >> >> any idea whats wrong here? >> >> -Wolfram -- Wolfram Schneider <wosch@FreeBSD.org> https://wolfram.schneider.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMWY7CD_TizUU6mB%2Bv7Lb6i6nAOHrEmCwSLAPoN-aKZN8P8w-Q>