I'd recommend giving a try with 118. I had a lot of trouble getting a Win16
image running. Ultimately, it was 118 and a lot of tries with deleting the
driver software and reinstalling from the virtio iso to get it to work.
I sent a a few emails last month as I was working through the issues. In
the end, I think it was mainly dropping back to 118 and many tries to
convince new driver to install.
On Tue, Nov 15, 2016 at 4:30 PM, Matt Thyer <matt.th...@gmail.com> wrote:
> virtio-win-0.1.102.iso was the last version I've had any success with.
> (I haven't tried with bhyve, only VirtualBox Windows VMs).
> On 16 November 2016 at 08:43, 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.
> > _______________________________________________
> > firstname.lastname@example.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
> > To unsubscribe, send any mail to "freebsd-virtualization-unsubs
> > cr...@freebsd.org"
> email@example.com mailing list
> To unsubscribe, send any mail to "freebsd-virtualization-
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to