>Synopsis: OpenBSD in QEMU KVM: High QEMU CPU usage when OpenBSD is 100%
>idle
>Category: kernel
>Environment:
System : OpenBSD 7.3
Details : OpenBSD 7.3 (GENERIC.MP) #1125: Sat Mar 25 10:36:29 MDT
2023
dera...@amd64.openbsd.org:/usr/sr
> On 05/26/2023 6:06 PM CEST Mike Larkin wrote:
>
> perf top on the linux side to see where qemu is spending it's time?
Sure, I ran `perf top -p $PID` with $PID being the PID of the QEMU process and
copied the screen after a few seconds. Let me know if you intended something
different:
PerfT
On 05/26/2023 8:08 PM CEST Mike Larkin wrote:
> On Fri, May 26, 2023 at 07:16:09PM +0200, br...@mailbox.org wrote:
> > > On 05/26/2023 6:06 PM CEST Mike Larkin wrote:
> > >
> > > perf top on the linux side to see where qemu is spending it's time?
> >
> > Sure, I ran `perf top -p $PID` with $
On Sat, 27 May 2023, Mike Larkin wrote:
On Fri, May 26, 2023 at 08:14:23PM +0200, br...@mailbox.org wrote:
On 05/26/2023 8:08 PM CEST Mike Larkin wrote:
On Fri, May 26, 2023 at 07:16:09PM +0200, br...@mailbox.org wrote:
On 05/26/2023 6:06 PM CEST Mike Larkin wrote:
perf top on the linu
On Sat, 27 May 2023, Mike Larkin wrote:
probably IPI traffic then. not sure what else to say. If a few % host overhead
is too much fot you with a 16 vCPU VM, I'd suggest reducing that.
What is your workload for a 16 vcpu openbsd VM anyway?
I would like to use the OpenBSD VM as my main work
>> > OP: what is your sysctl kern.timecounter ?
>> >
>>
>> kern.timecounter.tick=1
>> kern.timecounter.timestepwarnings=0
>> kern.timecounter.hardware=pvclock0
>> kern.timecounter.choice=i8254(0) pvclock0(1500) acpihpet0(1000)
>> acpitimer0(1000)
>>
>>
>
> You might try changing this and seeing i
