The problem seems to have been fixed, but the code is still in the review.
For more details, see https://reviews.freebsd.org/D26915#601420
Eugene M. Zheganin <emz at norma.perm.ru> ?2020?11?5??? ??12:35???
> Hello,
>
>
> Guys, does anyone have VM running in AliCloud Chinese provider (one of
> the biggest, if not the biggest one) ? They seem to provide stock
> FreeBSD 11.x images on some Redhat-based Linux with VirtIO which run
> just fine (at least I take a look at their kernel and it seem to be a
> stock GENERIC), but after source uprgading to 12.2 it cannot mountroot,
> because literally no disks are found after thee kernel booting stage.
> This, in turn, is cause by a bunch of repeatable virtio errors, which
> looks like (screenshot provided in the link):
>
>
> virtio_pci1: cannot map I/O space
>
> device_attach: virtio_pci1 attach returned 6
>
>
> (https://enazadev.ru/stub-data/freebsd12-alicloud-cannot-map-io.png)
>
> So not only vtbd0 cannot be attached to, but also a network adater.
> Surprisingly, virtio_console and memory baloon device seems to be working.
>
> I've took a look at various VirtIO cases in the bug tracker and
compiled
> a kernel without netmap (yeah, after some consideration this could help
> only with virtio_net part), but this doesn't help.
>
> Is this some sort of regression that needs to be reported ? Is there
> some kind of known workaround ?
>
> I also have a running 11.3 on a second VM, so I can provide any
> necessary details if needed.
>
>
> Thanks.
>
> Eugene.
>
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>