Date: Mon, 25 Jun 2018 13:50:16 +0200 From: Andrea Bolognani <abologna@redhat.com> To: Mark Rutland <mark.rutland@arm.com>, Ruslan Bukin <ruslan.bukin@cl.cam.ac.uk> Cc: freebsd-arm@freebsd.org, "Robert N. M. Watson" <robert.watson@cl.cam.ac.uk> Subject: Re: virtio-net issues on aarch64 QEMU/KVM Message-ID: <e048c5398832a2376ee3d55f654d60dbf0c52acd.camel@redhat.com> In-Reply-To: <20180615163512.55o5ldr6dwwl5jdl@lakrids.cambridge.arm.com> References: <1501165794.4378.8.camel@redhat.com> <20170804132950.GA9477@remoulade> <20180615115602.GA29619@bsdpad.com> <20180615161023.GA34414@bsdpad.com> <20180615163512.55o5ldr6dwwl5jdl@lakrids.cambridge.arm.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2018-06-15 at 17:35 +0100, Mark Rutland wrote: > On Fri, Jun 15, 2018 at 05:10:23PM +0100, Ruslan Bukin wrote: > > I committed the fix: > > https://lists.freebsd.org/pipermail/svn-src-head/2018-June/114969.html > > Great; thanks for tackling this! I just tried booting the latest -CURRENT qcow2 image (2018-Jun-18) and I can confirm virtio-net works on aarch64 as well. Thanks for looking into it! Additionally, the issue preventing SMT guests to boot seems to have been fixed too, since I could go all the way to 4 vCPUs whereas I was limited to 1 before :) -- Andrea Bolognani / Red Hat / Virtualization
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e048c5398832a2376ee3d55f654d60dbf0c52acd.camel>