Date: Thu, 24 May 2018 11:05:44 +0800 From: Sepherosa Ziehau <sepherosa@gmail.com> To: Yuri Pankov <yuripv@yuripv.net> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: pciconf -l doesn't show any devices on Hyper-V VM Message-ID: <CAMOc5cy3xcVGbtbtVZ%2BUzmzj7scDhWBpX3_aWdTz070qXLpX3g@mail.gmail.com> In-Reply-To: <140b87e9-8e37-e4b8-4adb-e881a1843408@yuripv.net> References: <140b87e9-8e37-e4b8-4adb-e881a1843408@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Gen1 or Gen2? On Gen2 Hyper-V, there is _no_ pcib0 and pci0 at all; unless you uses pci-e pass-through or SR-IOV. Why do you care about the existence of pci bus? On Thu, May 24, 2018 at 9:33 AM, Yuri Pankov <yuripv@yuripv.net> wrote: > Hi, > > Running FreeBSD-12.0-CURRENT-amd64-20180514-r333606 snapshot as a VM on > Hyper-V, `pciconf -l` (and `lspci`, expected) doesn't return any > information. > > Hyper-V Version: 10.0.14393 [SP2] (that's Windows 2016 with Hyper-V role). > > dmesg.boot is attached in case it's useful. > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Tomorrow Will Never Die
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMOc5cy3xcVGbtbtVZ%2BUzmzj7scDhWBpX3_aWdTz070qXLpX3g>