Hi all,
I am running bhyve (via TrueNAS Core 13) and have some Ubuntu 20.04 and
22.04 guests.
One of them rather regularly seizes up hard, where I cannot ssh to it,
then after a few minutes works again. This happens repeatedly and on and
off. In the Ubuntu logs I see messages like:
```
cl
some having this issue, but we haven't seen
it
though we do use OpenNTPD across our BSD/*nix guests (windows has its
own
time sync service).
Cheers,
Jason.
From: owner-freebsd-virtualizat...@freebsd.org
On Behalf Of Sean McBride
Sent: Friday, June 16, 2023 5:20 AM
To: freebsd-v
Hi all,
As part of debugging a problem I'm having, I'd like to understand:
What clock source should bhyve guests use? tsc? hpet? acpi_pm? What are
pros/cons of the choices? Does it depend on the guest OS? (for me FreeBSD and
Ubuntu) Should it match the host?
Thanks,
Sean
ixie wrote:
> in the old days i used to have to hard wire it. now it picks the same value i
> used to hard code. ntpd encountered chaos with other values.
>
> kern.timecounter.hardware: TSC-low
>
> i don't know if this has become an urban legend since i last fought it.
>
>
Hi all,
I'm trying to build bhyve from source, with the ultimate goal of fixing
https://reviews.freebsd.org/D39620 in my production TrueNAS Core system.
I've followed the TrueNAS build instructions at
https://github.com/truenas/core-build and although some packages failed
to build, the FreeB
On 12 Dec 2023, at 14:08, Denis Kirjanov wrote:
The patch mentions only the kernel, so you have to rebuild the vmm
module
That's a nice simplification, thanks!
So I've replaced `/boot/kernel/vmm.ko` with the one I built, and
rebooted. Alas it doesn't seem to load. I see in /var/run/dmesg.b
On 12 Dec 2023, at 15:42, Patrick M. Hausen wrote:
> Compile on 13.1-p(latest) if possible
Quite possible. I'm doing the compiling in a VM, so I'll just create another.
I suppose I may as well put TrueNAS in a VM and do my compiling in that. Then
I match up perfectly.
> or if you can stand/af
