HDMI can't be used as primary monitor

[jiri]

>Synopsis: selecting HDMI as primary display in BIOS lead in black screen 
>during loading drivers
>Category: driver
>Environment:
System  : OpenBSD 6.2
Details : OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb  2 23:02:19 CET 2018
 
r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
firstly, I was going to use in X a secondary HDMI monitor, but that not 
worked
xrandr shown for moment some resolutions on HDMI-2 but status was disconnected
and during second run of xrandr no resolutions were shown
later I tested connection to HDMI as primary monitor
so I set in BIOS, that HDMI is primary
I had output on HDMI until some driver (Intel ?) has been loaded, then I got 
black screen
Can this be related to this part from dmesg?

inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics 520" rev 0x07
drm0 at inteldrm0
inteldrm0: msi
error: [drm:pid0:i915_firmware_load_error_print] *ERROR* failed to load 
firmware i915/skl_dmc_ver1.bin (-22)
error: [drm:pid0:i915_gem_init_hw] *ERROR* Failed to initialize GuC, error -8 
(ignored)
inteldrm0: 1920x1080, 32bpp
>How-To-Repeat:
set HDMI as primary monitor in BIOS and boot machine
>Fix:
not known to me

dmesg:
OpenBSD 6.2 (GENERIC.MP) #5: Fri Feb  2 23:02:19 CET 2018

r...@syspatch-62-amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 8466038784 (8073MB)
avail mem = 8202440704 (7822MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe0880 (61 entries)
bios0: vendor LENOVO version "R0CET24W (1.12 )" date 05/06/2016
bios0: LENOVO 20GJ003QMC
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP TCPA SSDT UEFI SSDT SSDT HPET LPIT APIC MCFG SSDT SSDT 
SSDT SSDT SSDT DBGP DBG2 SSDT BOOT BATB SLIC SSDT SSDT MSDM DMAR ASF! FPDT UEFI
acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) 
GLAN(S4) XHC_(S4) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) 
PXSX(S4) RP03(S4) [...]
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 2399 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: TSC frequency 24 Hz
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 24MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu2: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu2: 256KB 64b/line 8-way L2 cache
cpu2: smt 1, core 0, package 0
cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz, 2400.00 MHz
cpu3: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT
cpu3: 256KB 64b/line 8-way L2 cache
cpu3: smt 1, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 120 pins
acpimcfg0 at acpi0 addr 0xf800, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (PEG0)
acpiprt2 at acpi0: bus -1 (PEG1)

Re: HDMI can't be used as primary monitor

[Mark Kettenis]

> Date: Thu, 22 Feb 2018 07:50:57 +0100 (CET)
> From: j...@navratil.cz

Please try a -current snapshot.

dhclient.conf - prepend domain-name issue

[Jiri B]

Hi,

I try to configure dhclient.conf to always have my own domain
as first in final /etc/resolv.conf 'search' option line.

But with following configuration there is _no_ white space
between my 'domain-name' and one obtained from lease.

kern.version=OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 17 14:45:09 CET 2018
ji...@build1.brq.afterboot.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP

# grep -Ev '^#' /etc/dhclient.conf
prepend domain-name "example.com";
prepend domain-name-servers 127.0.0.1;

# echo '' > /etc/resolv.conf 
# pkill -HUP -U root -f dhclient
# cat /etc/resolv.conf
# Generated by em0 dhclient
search example.combrq.afterboot.cz
nameserver 127.0.0.1
nameserver 192.168.1.1

# grep domain-name /var/db/dhclient.leases.em0
  option domain-name-servers 192.168.1.1;
   option domain-name "brq.afterboot.cz";

Do I have to put explicitly white space in dhclient.conf?
It seems odd.

Jiri

Re: dhclient.conf - prepend domain-name issue

[Jiri B]

On Thu, Feb 22, 2018 at 03:09:39PM -0500, Jiri B wrote:
> Hi,
> 
> I try to configure dhclient.conf to always have my own domain
> as first in final /etc/resolv.conf 'search' option line.
> 
> But with following configuration there is _no_ white space
> between my 'domain-name' and one obtained from lease.
> 
> kern.version=OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 17 14:45:09 CET 2018
> ji...@build1.brq.afterboot.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> # grep -Ev '^#' /etc/dhclient.conf
> prepend domain-name "example.com";
> prepend domain-name-servers 127.0.0.1;
> 
> # echo '' > /etc/resolv.conf 
> # pkill -HUP -U root -f dhclient
> # cat /etc/resolv.conf
> # Generated by em0 dhclient
> search example.combrq.afterboot.cz
> nameserver 127.0.0.1
> nameserver 192.168.1.1
> 
> # grep domain-name /var/db/dhclient.leases.em0
>   option domain-name-servers 192.168.1.1;
>option domain-name "brq.afterboot.cz";
> 
> Do I have to put explicitly white space in dhclient.conf?
> It seems odd.

Same for 'append', the value needs white space in the beginning
not to have both domains joined into one long string.

Jiri

Re: dhclient.conf - prepend domain-name issue

[Kenneth R Westerback]

On Thu, Feb 22, 2018 at 03:09:39PM -0500, Jiri B wrote:
> Hi,
> 
> I try to configure dhclient.conf to always have my own domain
> as first in final /etc/resolv.conf 'search' option line.
> 
> But with following configuration there is _no_ white space
> between my 'domain-name' and one obtained from lease.
> 
> kern.version=OpenBSD 6.2-current (GENERIC.MP) #0: Sat Feb 17 14:45:09 CET 2018
> ji...@build1.brq.afterboot.cz:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 
> # grep -Ev '^#' /etc/dhclient.conf
> prepend domain-name "example.com";
> prepend domain-name-servers 127.0.0.1;
> 
> # echo '' > /etc/resolv.conf 
> # pkill -HUP -U root -f dhclient
> # cat /etc/resolv.conf
> # Generated by em0 dhclient
> search example.combrq.afterboot.cz
> nameserver 127.0.0.1
> nameserver 192.168.1.1
> 
> # grep domain-name /var/db/dhclient.leases.em0
>   option domain-name-servers 192.168.1.1;
>option domain-name "brq.afterboot.cz";
> 
> Do I have to put explicitly white space in dhclient.conf?
> It seems odd.
> 
> Jiri

The whitespace is required. The 'prepend' and 'append' logic treats
the existing option data and the additional data as uint8_t arrays and
attaches one to the other.

 Ken

Since if_iwm.c r1.224 iwm constantly reports fatal firmware error

[trondd]

>Synopsis:  Since if_iwm.c r1.224 iwm constantly reports fatal firmware 
>error
>Category:  kernel
>Environment:
System  : OpenBSD 6.2
Details : OpenBSD 6.2-current (GENERIC.MP) #1: Tue Jan 23 20:28:22 
EST 2018
 
diena...@portabsd.home.kagu-tsuchi.com:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64
>Description:
Since trying to update on Feb 16, trying snapshots and building
current, I've been getting fatal firmware errors as soon as the iwm device
is brought up.  Last good kernel I have is from Jan 23 as shown in the dmesg.

Rolling back the only commit to if_iwm.c since Jan 23 to r1.223 seems to fix
the problem.

The debug shows the fatal firmware error occuring each time a background scan is
initiated.  Either something with the scan or one of the access points it hits
since the scan doesn't seem to complete based on the fewer number of APs found.

>How-To-Repeat:
$ fw_update -i
Installed: iwm-firmware-0.20170105 vmm-firmware-1.10.2p5 
intel-firmware-20171117p0v0

My hostname.iwm0 is simply:
nwid decepticons
wpakey mykey
dhcp

A working ifconfig output:
$ ifconfig iwm0
iwm0: flags=8843 mtu 1500
lladdr dc:53:60:4a:b1:ea
index 2 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect (HT-MCS2 mode 11n)
status: active
ieee80211: nwid decepticons chan 3 bssid 88:9f:fa:0b:83:46 59% wpakey 
wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
inet 192.168.1.15 netmask 0xff00 broadcast 192.168.1.255

When failing:
$ ifconfig iwm0
iwm0: flags=8843 mtu 1500
lladdr dc:53:60:4a:b1:ea
index 2 priority 4 llprio 3
groups: wlan egress
media: IEEE802.11 autoselect mode 11n (DS1)
status: no network
ieee80211: nwid decepticons wpakey wpaprotos wpa2 wpaakms psk 
wpaciphers ccmp wpagroupcipher ccmp
inet 192.168.1.15 netmask 0xff00 broadcast 192.168.1.255


debug output on broken kernel followed by debug output on working kernel:
iwm0: hw rev 0x210, fw ver 16.242414.0, address dc:53:60:4a:b1:ea
iwm0: begin active scan
iwm0: INIT -> SCAN
iwm0: end active scan
 + 88:9f:fa:0b:83:463   +23 54M   ess  privacy   rsn  "decepticons"
iwm0: SCAN -> AUTH
iwm0: sending auth to 88:9f:fa:0b:83:46 on channel 3 mode 11g
iwm0: AUTH -> ASSOC
iwm0: sending assoc_req to 88:9f:fa:0b:83:46 on channel 3 mode 11g
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: ASSOC -> RUN
iwm0: associated with 88:9f:fa:0b:83:46 ssid "decepticons" channel 3 start MCS 
0 short preamble long slot time HT enabled
iwm0: missed beacon threshold set to 7 beacons, beacon interval is 100 TU
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: RUN -> AUTH
iwm0: sending auth to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: AUTH -> ASSOC
iwm0: sending assoc_req to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: ASSOC -> RUN
iwm0: associated with 88:9f:fa:0b:83:46 ssid "decepticons" channel 3 start MCS 
0 short preamble long slot time HT enabled
iwm0: missed beacon threshold set to 7 beacons, beacon interval is 100 TU
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: RUN -> AUTH
iwm0: sending auth to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: AUTH -> ASSOC
iwm0: sending assoc_req to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: ASSOC -> RUN
iwm0: associated with 88:9f:fa:0b:83:46 ssid "decepticons" channel 3 start MCS 
0 short preamble long slot time HT enabled
iwm0: missed beacon threshold set to 7 beacons, beacon interval is 100 TU
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46
iwm0: sending msg 2/4 of the 4-way handshake to 88:9f:fa:0b:83:46
iwm0: RUN -> AUTH
iwm0: sending auth to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: AUTH -> ASSOC
iwm0: sending assoc_req to 88:9f:fa:0b:83:46 on channel 3 mode 11n
iwm0: received msg 1/4 of the 4-way handshake from 88:9f:fa:0b:83:46

PF divert-packet

[Romain Gabet]

Hi,


I don't know if it's a bug but, if I use "set prio" or "set queue" with 
"divert-packet", the priority isn't reflected to VLAN header or the packets 
isn't queued.

I diverted packets to snort. I use OpenBSD 6.2 (GENERIC.MP).

PS : sorry for my english.

Best regards.

VMD consumes 100% cpu after unpausing guest

[Dave Voutila]

>Synopsis:  VMD consumes 100% cpu after unpausing guest
>Category:  amd64
>Environment:
System  : OpenBSD 6.2
Details : OpenBSD 6.2-current (GENERIC.MP) #10: Wed Feb 21 21:26:27 
MST 2018
 
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP

Architecture: OpenBSD.amd64
Machine : amd64

>Description:

Not sure if this is a known issue, but I couldn't find anything
searching the lists.

Using an Alpine Linux guest vm, I can successfully pause the guest using
`vmctl pause 1` and some time later resume it using `vmctl unpause 1`. 

Unpausing works as the guest comes back to life, I can SSH back in, and
it's fine. However, on the host the vmd process representing that guest
sits at 100% CPU utilization with 1 thread constantly queueing onto a
cpu and running. The guest reports normal load so it must be one of the
2 threads.

Taking a ktrace of that particular thread, and slimming for sake of
email, it's constantly calling clock_gettime and kevent:

CALLfutex(0x7361d183cd0,0x2,1,0,0)  
RET futex   0
CALLkevent(5,0,0,0x7361d17c800,64,0x735f272b7c0)
STRUstruct  timespec
RET kevent  0
CALLclock_gettime(CLOCK_MONOTONIC,0x735f272b860)
STRUstruct  timespec
RET clock_gettime   0
CALLkevent(5,0,0,0x7361d17c800,64,0x735f272b7c0)
STRUstruct  timespec
RET kevent  0
CALLclock_gettime(CLOCK_MONOTONIC,0x735f272b860)
STRUstruct  timespec
RET clock_gettime   0
CALLkevent(5,0,0,0x7361d17c800,64,0x735f272b7c0)
STRUstruct  timespec
RET kevent  0
CALLclock_gettime(CLOCK_MONOTONIC,0x735f272b860)
STRUstruct  timespec
RET clock_gettime   0
CALLkevent(5,0,0,0x7361d17c800,64,0x735f272b7c0)
STRUstruct  timespec
RET kevent  0
CALLclock_gettime(CLOCK_MONOTONIC,0x735f272b860)
STRUstruct  timespec
RET clock_gettime   0
CALLkevent(5,0,0,0x7361d17c800,64,0x735f272b7c0)
STRUstruct  timespec
RET kevent  0
...etc.

VMD reports nothing strange, which I'd expect as the guest vm is
perfectly functional during this period even while that thread
burns up the CPU:

startup
/etc/vm.conf:3: switch "uplink" registered
vm_register: registering vm 1   
/etc/vm.conf:12: vm "alpine" registered (disabled)
vm_priv_brconfig: interface bridge0 description switch1-uplink
vmd_configure: not creating vm alpine (disabled)
config_setconfig: setting config
config_getconfig: retrieving config
config_getconfig: retrieving config
config_getconfig: retrieving config
vm_opentty: vm alpine tty /dev/ttyp5 uid 1000 gid 4 mode 620
vm_register: registering vm 1
vm_priv_ifconfig: interface tap0 description vm1-if0-alpine
vm_priv_ifconfig: switch "uplink" interface bridge0 add tap0
alpine: started vm 1 successfully, tty /dev/ttyp5
loadfile_bios: loaded BIOS image
run_vm: initializing hardware for vm alpine
virtio_init: vm "alpine" vio0 lladdr fe:e1:bb:d1:1b:bd
run_vm: starting vcpu threads for vm alpine
vcpu_reset: resetting vcpu 0 for vm 3
run_vm: waiting on events for VM alpine
i8259_write_datareg: master pic, reset IRQ vector to 0x8
i8259_write_datareg: slave pic, reset IRQ vector to 0x70
vcpu_exit_i8253: channel 0 reset, mode=0, start=65535
virtio_blk_io: device reset
virtio_blk_io: device reset
vcpu_process_com_lcr: set baudrate = 115200
vcpu_process_com_lcr: set baudrate = 115200
i8259_write_datareg: master pic, reset IRQ vector to 0x30
i8259_write_datareg: slave pic, reset IRQ vector to 0x38
vcpu_process_com_lcr: set baudrate = 115200
vcpu_exit_i8253: channel 0 reset, mode=7, start=3977
vcpu_exit_i8253: channel 2 reset, mode=7, start=65535
vcpu_exit_i8253: channel 2 reset, mode=7, start=65535
vcpu_exit_i8253: channel 2 reset, mode=7, start=65535
vcpu_exit_i8253: channel 2 reset, mode=7, start=65535
vcpu_process_com_lcr: set baudrate = 115200
vcpu_process_com_data: guest reading com1 when not ready
vcpu_process_com_data: guest reading com1 when not ready
vcpu_process_com_data: guest reading com1 when not ready
vcpu_process_com_lcr: set baudrate = 115200
virtio_blk_io: device reset
virtio_blk_io: device reset
virtio_net_io: device reset
alpine: paused vm 1 successfully
alpine: unpaused vm 1 successfully.
rtc_update_rega: set non-32KHz timebase not supported
rtc_fire1: RTC clock drift (44s), requesting guest resync
rtc_update_rega: set non-32KHz timebase not supported

>How-To-Repeat:
Pause an actively running linux guest: `vmctl pause 1`
After some time, resume the guest: `vmctl unpause 1`
Observe CPU utilization of matching VMD process.

>Fix:
Unknown. Stopping the guest through either having it halt or 
`vmctl stop ` obviously ends the cpu consumption.

dmesg:
OpenBSD 6.2-current (GENERIC.MP) #10: Wed Feb 21 21:26:27 MST 2018
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 17053851648 (16263MB)
avail mem = 16529985536 (15764MB)
mpath0 at root
scsibus0