Hi Wolfram,
I believe r305900 broke it. I don't have any patch or workaround,
sorry. It wouldn't be too hard for someone interested in
virtualization to fix the issue. Please follow up in the bug :-).
Best,
Conrad
On Wed, Nov 15, 2017 at 7:16 AM, Wolfram Schneider wrote:
> Hi Conrad,
>
> tha
On 15 November 2017 at 10:58, Conrad Meyer 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
Hi Wolfram,
Looks like the same issue as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223531 .
Best,
Conrad
On Wed, Nov 15, 2017 at 1:31 AM, Wolfram Schneider wrote:
> Hi,
>
> I have a virtual machine running with FreeBSD 11-stable at a cloud
> provider. It runs fine. I tried to upgrade to
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
