Hey All,
I'm in the process of reorganizing my bhyve setup on my development
laptop. I'd like to have rename the tap devices to match the name of
the VM so that it's easier to keep track of. Otherwise, I have to keep
a spreadsheet of (tap3 -> win10-vm, tap4 -> fbsd-vm).
It appears bhyve doesn't a
Hi Andriy,
The hardware is AMD.
Ryzen ?
But what I see suggests that at this point a Local APIC timer interrupt gets
delivered to the thread. And that causes all the mess as the thread holding the
spinlock gets preempted.
Does this ring a bell to anyone?
I have seen something similar t
First, about the setup. It's a FreeBSD/amd64 head guest on a FreeBSD/amd64 head
host. The hardware is AMD. The hypervisor is bhyve.
Under a certain specific load, that involves a lot of page faults and IPI-s, I
see the guest system getting stuck. This is pretty consistent. Typically I
find a
