I tried the install CD for the latest HEAD-201807121210Z. It can see both the NICs, but they don't work. Trying to configure them with DHCP, it looks as if the NIC is sending a DISCOVERY but timing out never receiving anything back (I doubt that it is actually sending anything on the wire). Then it constantly throws this on the console: "wm0: device timeout (lost interrupt)".
On Sat, Jul 14, 2018 at 8:34 PM Farid Joubbi <[email protected]> wrote: > I have a working configuration for NetBSD on bhyve. It's not a problem > with vm-bhyve https://github.com/churchers/vm-bhyve > > NetBSD 7.1.2 does not initiate the bge0 nor wm0 at all under bhyve, as I > wrote earlier. > It seems to run perfectly fine other than that. > The "normal" vioif0 works fine. > > I tried NetBSD 8.0 RC2. > It finds both NICs! All of a sudden I feel hope ;-) > Unfortunately I can only get link-local addresses on both NICs. > And I also get this printed on the console every now and then: "bge0: > watchdog timeout -- resetting". > > I will try and get it to NetBSD-current and see. > > > On Tue, Jul 10, 2018 at 5:30 AM Travis Paul <[email protected]> wrote: > >> >> >> > On 9 Jul 2018, at 5:58 AM, Farid Joubbi <[email protected]> wrote: >> > >> > Thanks for the reply. >> > After reading it, I realize that the learning curve for me to >> understand what is going on is a bit too steep. >> > I know only some basic C programming from university courses several >> years ago. >> > This kind of learning was not what I had in mind when I figured that I >> want to run a new NetBSD installation this summer... ;-( >> >> FWIW, NetBSD runs fine on Bhyve without PCI passthru. I'm running a few >> NetBSD 7 and 8 VMs on FreeBSD 11. >> >> I can share some commands to get a NetBSD system up if you're interested >> but I'm not using PCI passthru so I can't assist there. >> >> Best, >> Travis >> >
