Hi Peter, Thanks for suggesting that! I re-installed the VM, this time using 0.1.96 instead of 0.1.126 and it worked as soon as I gave it static addressing. As 0.1.96 doesn't contain a driver specifically for Server 2016 I just used the 2012R2 one and I don't appear to have any issues.
Unfortunately I don't really have time to test the drivers one by one until I find where it breaks, but it looks like some others in this thread have already done so, which is useful. Thanks, Jonathan. November 15, 2016 10:14 PM, "Peter Grehan" <gre...@freebsd.org> wrote: > Hi Jonathan, > >> In particular, I used virtio-win-0.1.126.iso with driver net-kvm/windows >> 2k16/amd64 for my attempt with Server 2016 and the 2k12r2/amd64 driver >> for Server 2012 R2. > > I've not had any success with 0.1.126 - it installs, but doesn't appear to > pass packets. I'd > recommend going with 0.1.96 > > later, > > Peter. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"
