Date: Wed, 16 Nov 2016 09:46:21 +0000 From: freebsd@jonathanprice.org To: "Peter Grehan" <grehan@freebsd.org> Cc: "The Doctor" <doctor@doctor.nl2k.ab.ca>, freebsd-virtualization@freebsd.org Subject: Re: bhyve windows guest unable to ping default gateway or external networks Message-ID: <081abe1ac9091b9412739e57a0cfdc79@mail.jonathanprice.org> In-Reply-To: <00938431-be4a-1729-1c93-a56d7063a76a@freebsd.org> References: <00938431-be4a-1729-1c93-a56d7063a76a@freebsd.org> <4cf1a528d9a4e85d5aa351ca2ff417a9@mail.jonathanprice.org> <20161115150028.GB3776@doctor.nl2k.ab.ca> <d8232456-6bca-2308-a43e-583a365e21f0@jonathanprice.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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" <grehan@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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?081abe1ac9091b9412739e57a0cfdc79>