I had the same issue if the gcc48 port was installed, but removing
that somehow resolved it for me.
-Dustin
On Mon, Feb 22, 2021 at 12:08 AM The Doctor via freebsd-virtualization
wrote:
>
> On Sun, Feb 21, 2021 at 09:38:29PM -0700, Rebecca Cran wrote:
> > On 2/18/2021 6:22 PM, The Doctor via
On Tue, Sep 1, 2020 at 5:11 PM Jason Tubnor wrote:
>
> On Wed, 2 Sep 2020 at 00:20, Hiroshi Nishida wrote:
> I hit similar bugs in various ways around IPv6 guests in 12.0 with
> lingering problems in 12.1. All issues appeared to be fixed in 12-STABLE
> now, so 12.2 should be good to go. Can
t. stable/fast.
>
> On Tue, Jul 7, 2020 at 6:40 AM Dustin Marquess wrote:
> >
> > Try nvme, I believe that driver supports TRIM and I've had a lot
> > better performance with it over ahci-hd.
> >
> > -Dustin
> >
> > On Mon, Jul 6, 2020 at 12:24 PM
Try nvme, I believe that driver supports TRIM and I've had a lot
better performance with it over ahci-hd.
-Dustin
On Mon, Jul 6, 2020 at 12:24 PM Andrea Venturoli wrote:
>
> Hello.
>
> I'm running zvol-backed Windows guests in bhyve on FreeBSD 12.1.
> Over time, I see the zvol effectively used
I have this weird issue. I have a PC Engines box with a AMD SoC in it.
I'm trying to pass through the USB 3.0 controller to a Windows VM. I added:
hw.vmm.amdvi.enable="1"
pptdevs="0/16/0"
to /boot/loader.conf, rebooted, installed Windows, etc. Everything
works great until I add:
-s
As far as I know, virtio-blk works, but doesn’t support TRIM. I believe
virtio-scsi does, but it seems to require more configuration on the host side
from what I’ve seen. I never got it working with Windows at least.
-Dustin
On Apr 21, 2019, 2:47 PM -0500, Paul Vixie , wrote:
>
>
&g
Using a sparse zvol and either the ahci-hd or nvme drivers should support TRIM.
-Dustin
On Apr 21, 2019, 12:02 PM -0500, Bjoern A. Zeeb
, wrote:
> Hi,
>
> I have been wondering about this with other (commercial) virtualisation
> solutions in the past. If running on a “disk image” ideally I’d
>
passthrough to Windows to run u-blox u-center :).
-Dustin
On Fri, Apr 12, 2019 at 9:57 AM Rodney W. Grimes
wrote:
>
> > On Thu, Apr 11, 2019 at 10:10:03PM -0500, Dustin Marquess wrote:
> > > It's worth a shot at least to see if it works!
> > >
> > >
-net,tap2 \
-s 20,virtio-rnd \
-s 31,lpc \
-l com1,stdio -l bootrom,/usr/local/share/uefi-firmware/BHYVE_UEFI.fd ${VM}
-Dustin
On Thu, Apr 11, 2019 at 5:54 PM The Doctor wrote:
>
> On Thu, Apr 11, 2019 at 05:18:10PM -0500, Dustin Marquess wrote:
> > I'm not sure if 12.0 has bhyve
I'm not sure if 12.0 has bhyve nmve support, but 10 & 2019 both seem
to run MUCH faster when using nvme compared to ahci-hd.
-Dustin
On Thu, Apr 11, 2019 at 4:40 PM The Doctor via freebsd-virtualization
wrote:
>
> Seems to be running slow on FreeBSD 12.0 p3.
>
> Just wondering if there are
It would be interesting to test running it under Xen with FreeBSD as the
dom0.
-Dustin
On Sat, Oct 27, 2018 at 1:04 PM Harry Schmalzbauer
wrote:
> Am 22.10.2018 um 13:26 schrieb Harry Schmalzbauer:
> …
> > Test-Runs:
> > Each hypervisor had only the one bench-guest running, no other
> >
The bhyve ahci driver does work with guests that issue TRIM. virtio-blk sadly
does not.
-Dustin
On May 14, 2018, 10:34 AM -0500, Paul Esson , wrote:
> Hi Folks,
>
> I'm attempting to use a sparse ZVOL from a FreeBSD 11.1-RELEASE host as a
> data disk for a bhyve FreeBSD
I doubt it's best practice, and I'm sure I'm just crazy for doing it,
but personally I try and match the ZVOL blocksize to whatever the
underlaying filesystem's blocksize is. To me that just makes the most
logical sense.
-Dustin
On Mon, Dec 4, 2017 at 5:19 PM, Dustin Wenz
On Wed, Feb 22, 2017 at 3:59 AM, Frank Leonhardt wrote:
> Can anyone help me running Windows 5.1 (XP) as a VM under FreeBSD?
>
> bhyve doesn't support anything older than Vista, and I'm unclear as to
> whether it supports 32-bit versions of that. I tried compiling
I'm running 2016 (both Standard and Essentials) under 12-CURRENT bhyve without
any obvious issues other than it's acting a lot slower than it should be.
However I'm not entirely sure that it's a bhyve issue.
-Dustin
On Sun, Jan 15, 2017 at 4:46 PM -0600, "The Doctor"
Another thing I've seen before is that if there's a lot of broadcast traffic on
the network, that seems to increase CPU on the bhyve process.
-Dustin
On Sun, Jul 24, 2016 at 8:48 PM -0500, "Shane Ambler"
wrote:
On 25/07/2016 02:10, tech-lists wrote:
> Hi,
>
AH-HA! Indeed I am. Is UEFI not supported?
-Dustin
On Thu, Apr 14, 2016 at 4:59 AM, Roger Pau Monné <roger@citrix.com>
wrote:
> On Thu, Apr 14, 2016 at 01:24:46AM -0500, Dustin Marquess wrote:
> > Hello!
> >
> > I'm using a -CURRENT install from a couple of week
I'm using bhyve on my AMD box because of this exact reason. It's
working well enough for me!
-Dustin
On Thu, Feb 4, 2016 at 11:00 AM, Gerd Hafenbrack
wrote:
> On 2016-02-04 13:21, Roger Pau Monné wrote:
>> El 4/2/16 a les 11:59, Gerd Hafenbrack ha escrit:
>>> Hello,
I'm running an 11.0-CURRENT (from exactly a week ago) on a 32-core
(16-module) AMD Bulldozer system.
Guest is NetBSD 7.99.21 HEAD, with timecounter hard-forced to
ACPI-safe instead of hpet (HPET seemed unstable, although HPET is
being used in the host FreeBSD).
I start bhyve using a simple
19 matches
Mail list logo