search

pgj / freebsd-wifibox

wifibox: Use Linux to drive your wireless card on FreeBSD
BSD 2-Clause "Simplified" License
159 stars 12 forks source link

the bhyve process the load up to 700% #56

Closed Elimelech closed 1 year ago

Elimelech commented 1 year ago

Description

If I set the cpus value to something other than 1, then the processor is loaded at 100%, the bhyve process in top shows the load up to 700%. Why is that?

Host operating system

If I set the cpus value to something other than 1, then the processor is loaded at 100%, the bhyve process in top shows the load up to 700%.
Why is that?
root@F3ja:/usr/home/luba # uname -a
FreeBSD F3ja 13.2-RELEASE FreeBSD 13.2-RELEASE releng/13.2-n254617-525ecfdad597 GENERIC amd64

Wireless NIC

root@F3ja:/usr/home/luba # pciconf -lv
hostb0@pci0:0:0:0:      class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1630 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne Root Complex'
    class      = bridge
    subclass   = HOST-PCI
amdiommu0@pci0:0:0:2:   class=0x080600 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1631 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne IOMMU'
    class      = base peripheral
    subclass   = IOMMU
hostb1@pci0:0:1:0:      class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1632 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir PCIe Dummy Host Bridge'
    class      = bridge
    subclass   = HOST-PCI
hostb2@pci0:0:2:0:      class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1632 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir PCIe Dummy Host Bridge'
    class      = bridge
    subclass   = HOST-PCI
pcib1@pci0:0:2:2:       class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x1634 subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne PCIe GPP Bridge'
    class      = bridge
    subclass   = PCI-PCI
pcib2@pci0:0:2:4:       class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x1634 subvendor=0x1022 subdevice=0x1453
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne PCIe GPP Bridge'
    class      = bridge
    subclass   = PCI-PCI
hostb3@pci0:0:8:0:      class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1632 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir PCIe Dummy Host Bridge'
    class      = bridge
    subclass   = HOST-PCI
pcib3@pci0:0:8:1:       class=0x060400 rev=0x00 hdr=0x01 vendor=0x1022 device=0x1635 subvendor=0x1022 subdevice=0x1635
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir Internal PCIe GPP Bridge to Bus'
    class      = bridge
    subclass   = PCI-PCI
intsmb0@pci0:0:20:0:    class=0x0c0500 rev=0x51 hdr=0x00 vendor=0x1022 device=0x790b subvendor=0x1022 subdevice=0x790b
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'FCH SMBus Controller'
    class      = serial bus
    subclass   = SMBus
isab0@pci0:0:20:3:      class=0x060100 rev=0x51 hdr=0x00 vendor=0x1022 device=0x790e subvendor=0x1022 subdevice=0x790e
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'FCH LPC Bridge'
    class      = bridge
    subclass   = PCI-ISA
hostb4@pci0:0:24:0:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166a subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 0'
    class      = bridge
    subclass   = HOST-PCI
hostb5@pci0:0:24:1:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166b subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 1'
    class      = bridge
    subclass   = HOST-PCI
hostb6@pci0:0:24:2:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166c subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 2'
    class      = bridge
    subclass   = HOST-PCI
hostb7@pci0:0:24:3:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166d subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 3'
    class      = bridge
    subclass   = HOST-PCI
hostb8@pci0:0:24:4:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166e subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 4'
    class      = bridge
    subclass   = HOST-PCI
hostb9@pci0:0:24:5:     class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x166f subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 5'
    class      = bridge
    subclass   = HOST-PCI
hostb10@pci0:0:24:6:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1670 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 6'
    class      = bridge
    subclass   = HOST-PCI
hostb11@pci0:0:24:7:    class=0x060000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1671 subvendor=0x0000 subdevice=0x0000
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Cezanne Data Fabric; Function 7'
    class      = bridge
    subclass   = HOST-PCI
ppt0@pci0:1:0:0:        class=0x028000 rev=0x00 hdr=0x00 vendor=0x10ec device=0xb852 subvendor=0x103c subdevice=0x88e3
    vendor     = 'Realtek Semiconductor Co., Ltd.'
    class      = network
nvme0@pci0:2:0:0:       class=0x010802 rev=0x00 hdr=0x00 vendor=0x1c5c device=0x174a subvendor=0x1c5c subdevice=0x174a
    vendor     = 'SK hynix'
    device     = 'Gold P31/PC711 NVMe Solid State Drive'
    class      = mass storage
    subclass   = NVM
vgapci0@pci0:3:0:0:     class=0x030000 rev=0xc1 hdr=0x00 vendor=0x1002 device=0x15e7 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Barcelo'
    class      = display
    subclass   = VGA
hdac0@pci0:3:0:1:       class=0x040300 rev=0x00 hdr=0x00 vendor=0x1002 device=0x1637 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD/ATI]'
    device     = 'Renoir Radeon High Definition Audio Controller'
    class      = multimedia
    subclass   = HDA
none0@pci0:3:0:2:       class=0x108000 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15df subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 17h (Models 10h-1fh) Platform Security Processor'
    class      = encrypt/decrypt
xhci0@pci0:3:0:3:       class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1639 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne USB 3.1'
    class      = serial bus
    subclass   = USB
xhci1@pci0:3:0:4:       class=0x0c0330 rev=0x00 hdr=0x00 vendor=0x1022 device=0x1639 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Renoir/Cezanne USB 3.1'
    class      = serial bus
    subclass   = USB
none1@pci0:3:0:5:       class=0x048000 rev=0x01 hdr=0x00 vendor=0x1022 device=0x15e2 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'ACP/ACP3X/ACP6x Audio Coprocessor'
    class      = multimedia
hdac1@pci0:3:0:6:       class=0x040300 rev=0x00 hdr=0x00 vendor=0x1022 device=0x15e3 subvendor=0x103c subdevice=0x89fc
    vendor     = 'Advanced Micro Devices, Inc. [AMD]'
    device     = 'Family 17h/19h HD Audio Controller'
    class      = multimedia
    subclass   = HDA

Wifibox version

root@F3ja:/usr/home/luba # pkg info wifibox 
wifibox-1.2.2
Name           : wifibox
Version        : 1.2.2
Installed on   : Mon Apr  3 16:57:30 2023 EEST
Origin         : net/wifibox
Architecture   : FreeBSD:13:*
Prefix         : /usr/local
Categories     : net
Licenses       : NA
Maintainer     : pali.gabor@gmail.com
WWW            : https://github.com/pgj/freebsd-wifibox
Comment        : Wireless card driver via virtualized Linux
Annotations    :
        flavor         : default
        repo_type      : binary
        repository     : FreeBSD
Flat size      : 243B
Description    :
Wifibox deploys a Linux guest to drive a wireless networking card on
the FreeBSD host system with the help of PCI pass-through.  There have
been guides on the Internet to suggest the use of such techniques to
improve the wireless networking experience on FreeBSD, of which
Wifibox tries to implement as a single easy-to-use software package.

WWW: https://github.com/pgj/freebsd-wifibox

Disk image type and version

root@F3ja:/usr/home/luba # pkg info wifibox-alpine wifibox-alpine-20230326 Name : wifibox-alpine Version : 20230326 Installed on : Mon Apr 3 16:57:29 2023 EEST Origin : net/wifibox-alpine Architecture : FreeBSD:13:amd64 Prefix : /usr/local Categories : net Licenses : BSD2CLAUSE Maintainer : pali.gabor@gmail.com WWW : https://github.com/pgj/freebsd-wifibox-alpine Comment : Wifibox guest based on Alpine Linux Options : APP_HOSTAPD : off APP_WPA_SUPPLICANT: on COMP_GZIP : off COMP_LZ4 : off COMP_LZO : off COMP_XZ : on COMP_ZSTD : off FW_ATH10K : on FW_ATH11K : on FW_ATMEL : off FW_B43 : off FW_B43LEGACY : off FW_BRCM : on FW_IPW2100 : off FW_IPW2200 : off FW_IWL3945 : off FW_IWL4965 : off FW_IWLWIFI : on FW_MARVELL : on FW_MEDIATEK : on FW_RT61 : on FW_RTLWIFI : on FW_RTW88 : on FW_RTW89 : on FW_TI : off UDS_PASSTHRU : on XX_DRIVER_WL : off XX_FORWARDING : off XX_MDNS : off XX_TCPDUMP : off Annotations : FreeBSD_version: 1301000 flavor : default repo_type : binary repository : FreeBSD Flat size : 100MiB Description : The implementation of the Wifibox embedded wireless router is based on the use of a Linux-based guest operating system which can communicate with the host's wireless network card on behalf of the host. In order to meet the requirements, this has to be a system with a low resource footprint and easy to manage. This is derived from Alpine Linux, which is an actively maintained, security-oriented, lightweight distribution, based on musl libc and BusyBox.

WWW: https://github.com/pgj/freebsd-wifibox-alpine

Changes to the default configuration files

Include relevant sections from all the configuration files that contain local changes and may help to reproduce the problem.

Logs

Apr 11 08:02:16 wifibox syslog.info syslogd started: BusyBox v1.35.0
Apr 11 08:02:16 wifibox daemon.info supervise-daemon[786]: Supervisor command line: supervise-daemon wpa_supplicant --start --respawn-delay 2 --respawn-max 5 --respawn-period 1800 /sbin/wpa_supplicant -- -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf 
Apr 11 08:02:16 wifibox daemon.info supervise-daemon[790]: Child command line: /sbin/wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/wpa_supplicant.conf 
Apr 11 08:02:22 wifibox daemon.info supervise-daemon[948]: Supervisor command line: supervise-daemon uds_passthru --start --respawn-delay 2 --respawn-max 5 --respawn-period 1800 /sbin/uds_passthru -- 
Apr 11 08:02:22 wifibox daemon.info supervise-daemon[952]: Child command line: /sbin/uds_passthru 
Apr 11 08:02:22 wifibox daemon.info : starting pid 955, tty '': '/sbin/openrc default'
Apr 11 08:02:22 wifibox daemon.debug uds_passthru[952]: Configuration: network=10.0.0.1:255.255.255.0, sockets=[path=/var/run/wpa_supplicant/wlan0,user=root,group=0,mode=770,port=1200 path=/var/run/wpa_supplicant/p2p-dev-wlan0,user=root,group=0,mode=770,port=1201]
Apr 11 08:02:22 wifibox daemon.info uds_passthru[952]: Associating 10.0.0.1:1200 (10.0.0.1:255.255.255.0) with /var/run/wpa_supplicant/wlan0 (/tmp/tmp.BJLpMC/tmp.kONNJg)
Apr 11 08:02:22 wifibox daemon.warn uds_passthru[952]: /var/run/wpa_supplicant/p2p-dev-wlan0 is not available, skipping.
Apr 11 08:02:22 wifibox daemon.info uds_passthru[952]: Waiting for PID 964 to stop.
Apr 11 08:02:22 wifibox cron.info crond[1012]: crond (busybox 1.35.0) started, log level 8
Apr 11 08:02:22 wifibox daemon.info udhcpd[1065]: started, v1.35.0
Apr 11 08:02:22 wifibox daemon.err udhcpd[1065]: can't open '/var/lib/misc/udhcpd.leases': No such file or directory
Apr 11 08:02:22 wifibox daemon.info : starting pid 1072, tty '/dev/ttyS0': '/sbin/getty -L ttyS0 115200 vt100'
Apr 11 08:02:25 wifibox daemon.info udhcpd[1065]: sending OFFER to 10.0.0.2
Apr 11 08:02:27 wifibox daemon.info udhcpd[1065]: sending ACK to 10.0.0.2
Apr 11 08:15:00 wifibox cron.info crond[1012]: USER root pid 1081 cmd run-parts /etc/periodic/15min
Apr 11 08:30:00 wifibox cron.info crond[1012]: USER root pid 1082 cmd run-parts /etc/periodic/15min
Apr 11 08:45:00 wifibox cron.info crond[1012]: USER root pid 1084 cmd run-parts /etc/periodic/15min
Apr 11 09:00:00 wifibox cron.info crond[1012]: USER root pid 1085 cmd run-parts /etc/periodic/15min
Apr 11 09:00:00 wifibox cron.info crond[1012]: USER root pid 1086 cmd run-parts /etc/periodic/hourly
Apr 11 09:15:00 wifibox cron.info crond[1012]: USER root pid 1087 cmd run-parts /etc/periodic/15min
Apr 11 09:30:00 wifibox cron.info crond[1012]: USER root pid 1088 cmd run-parts /etc/periodic/15min
Apr 11 09:45:00 wifibox cron.info crond[1012]: USER root pid 1089 cmd run-parts /etc/periodic/15min
Apr 11 10:00:00 wifibox cron.info crond[1012]: USER root pid 1090 cmd run-parts /etc/periodic/15min
Apr 11 10:00:00 wifibox cron.info crond[1012]: USER root pid 1091 cmd run-parts /etc/periodic/hourly
Apr 11 10:15:00 wifibox cron.info crond[1012]: USER root pid 1092 cmd run-parts /etc/periodic/15min

[    0.000000] Linux version 5.15.104-0-lts (pgj@wifibox-dev) (gcc (Alpine 12.2.1_git20220924-r4) 12.2.1 20220924, GNU ld (GNU Binutils) 2.39) #1-Alpine Sun, 26 Mar 2023 00:13:40 +0000
[    0.000000] Command line: console=ttyS0 BOOT_IMAGE=(host)/usr/local/share/wifibox/vmlinuz modules=squashfs root=/dev/vda rootfstype=squashfs clocksource=hpet tsc=unstable
[    0.000000] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
[    0.000000] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
[    0.000000] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
[    0.000000] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
[    0.000000] signal: max sigframe size: 1360
[    0.000000] BIOS-provided physical RAM map:
[    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ffff] usable
[    0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000163fffff] usable
[    0.000000] NX (Execute Disable) protection: active
[    0.000000] SMBIOS 2.6 present.
[    0.000000] DMI: FreeBSD BHYVE/BHYVE, BIOS 13.0 11/10/2020
[    0.000000] tsc: Fast TSC calibration using PIT
[    0.000000] tsc: Detected 1996.109 MHz processor
[    0.000004] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[    0.000006] e820: remove [mem 0x000a0000-0x000fffff] usable
[    0.000008] last_pfn = 0x16400 max_arch_pfn = 0x400000000
[    0.000055] Disabled
[    0.000056] x86/PAT: MTRRs disabled, skipping PAT initialization too.
[    0.000070] CPU MTRRs all blank - virtualized system.
[    0.000071] x86/PAT: Configuration [0-7]: WB  WT  UC- UC  WB  WT  UC- UC  
[    0.000075] Using GB pages for direct mapping
[    0.000110] ACPI: Early table checksum verification disabled
[    0.000111] ACPI: RSDP 0x00000000000F2400 000024 (v02 BHYVE )
[    0.000114] ACPI: XSDT 0x00000000000F2470 00004C (v01 BHYVE  BVXSDT   00000001 BASL 20220504)
[    0.000117] ACPI: FACP 0x00000000000F24C0 000114 (v05 BHYVE  BVFACP   00000001 BASL 20220504)
[    0.000120] ACPI: DSDT 0x00000000000F2750 000A5C (v02 BHYVE  BVDSDT   00000001 INTL 20201113)
[    0.000121] ACPI: FACS 0x00000000000F26C0 000040
[    0.000123] ACPI: FACS 0x00000000000F26C0 000040
[    0.000124] ACPI: APIC 0x00000000000F25E0 00005A (v01 BHYVE  BVAPIC   00000001 BASL 20220504)
[    0.000125] ACPI: HPET 0x00000000000F2640 000038 (v01 BHYVE  BVHPET   00000001 BASL 20220504)
[    0.000126] ACPI: MCFG 0x00000000000F2680 00003C (v01 BHYVE  BVMCFG   00000001 BASL 20220504)
[    0.000128] ACPI: SPCR 0x00000000000F2700 000050 (v01 BHYVE  BVSPCR   00000001 BASL 20220504)
[    0.000129] ACPI: Reserving FACP table memory at [mem 0xf24c0-0xf25d3]
[    0.000130] ACPI: Reserving DSDT table memory at [mem 0xf2750-0xf31ab]
[    0.000130] ACPI: Reserving FACS table memory at [mem 0xf26c0-0xf26ff]
[    0.000131] ACPI: Reserving FACS table memory at [mem 0xf26c0-0xf26ff]
[    0.000131] ACPI: Reserving APIC table memory at [mem 0xf25e0-0xf2639]
[    0.000132] ACPI: Reserving HPET table memory at [mem 0xf2640-0xf2677]
[    0.000132] ACPI: Reserving MCFG table memory at [mem 0xf2680-0xf26bb]
[    0.000133] ACPI: Reserving SPCR table memory at [mem 0xf2700-0xf274f]
[    0.000144] system APIC only can use physical flat
[    0.000144] Setting APIC routing to physical flat.
[    0.000158] Zone ranges:
[    0.000159]   DMA      [mem 0x0000000000001000-0x0000000000ffffff]
[    0.000160]   DMA32    [mem 0x0000000001000000-0x00000000163fffff]
[    0.000161]   Normal   empty
[    0.000162] Movable zone start for each node
[    0.000162] Early memory node ranges
[    0.000163]   node   0: [mem 0x0000000000001000-0x000000000009ffff]
[    0.000164]   node   0: [mem 0x0000000000100000-0x00000000163fffff]
[    0.000165] Initmem setup node 0 [mem 0x0000000000001000-0x00000000163fffff]
[    0.000169] On node 0, zone DMA: 1 pages in unavailable ranges
[    0.000190] On node 0, zone DMA: 96 pages in unavailable ranges
[    0.000710] On node 0, zone DMA32: 7168 pages in unavailable ranges
[    0.001052] ACPI: PM-Timer IO Port: 0x408
[    0.001054] system APIC only can use physical flat
[    0.001055] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.001077] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-31
[    0.001079] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
[    0.001080] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level)
[    0.001082] ACPI: Using ACPI (MADT) for SMP configuration information
[    0.001083] ACPI: HPET id: 0x80860701 base: 0xfed00000
[    0.001085] ACPI: SPCR: SPCR table version 1
[    0.001086] ACPI: SPCR: console: uart,io,0x3f8,115200
[    0.001091] [mem 0x16400000-0xffffffff] available for PCI devices
[    0.001092] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns
[    0.002488] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.002490] pcpu-alloc: [0] 0 
[    0.002494] Built 1 zonelists, mobility grouping on.  Total pages: 89456
[    0.002496] Kernel command line: console=ttyS0 BOOT_IMAGE=(host)/usr/local/share/wifibox/vmlinuz modules=squashfs root=/dev/vda rootfstype=squashfs clocksource=hpet tsc=unstable
[    0.002509] tsc: Marking TSC unstable due to boot parameter
[    0.002511] Unknown kernel command line parameters "BOOT_IMAGE=(host)/usr/local/share/wifibox/vmlinuz modules=squashfs", will be passed to user space.
[    0.002559] Dentry cache hash table entries: 65536 (order: 7, 524288 bytes, linear)
[    0.002586] Inode-cache hash table entries: 32768 (order: 6, 262144 bytes, linear)
[    0.002593] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.002881] Memory: 337768K/364156K available (8193K kernel code, 1465K rwdata, 1572K rodata, 724K init, 1768K bss, 26128K reserved, 0K cma-reserved)
[    0.002896] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.002920] NR_IRQS: 4352, nr_irqs: 256, preallocated irqs: 16
[    0.003160] Console: colour EGA 80x25
[    0.034933] printk: console [ttyS0] enabled
[    0.035203] ACPI: Core revision 20210730
[    0.035526] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 113919999973 ns
[    0.036120] APIC: Switch to symmetric I/O mode setup
[    0.037590] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[    0.042182] Calibrating delay loop (skipped), value calculated using timer frequency.. 3992.21 BogoMIPS (lpj=1996109)
[    0.042851] pid_max: default: 32768 minimum: 301
[    0.043153] LSM: Security Framework initializing
[    0.043194] Mount-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[    0.043659] Mountpoint-cache hash table entries: 1024 (order: 1, 8192 bytes, linear)
[    0.044377] Last level iTLB entries: 4KB 512, 2MB 512, 4MB 256
[    0.044751] Last level dTLB entries: 4KB 2048, 2MB 2048, 4MB 1024, 1GB 0
[    0.045182] CPU: AMD Ryzen 7 5825U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0)
[    0.045749] Spectre V1 : Mitigation: usercopy/swapgs barriers and __user pointer sanitization
[    0.046182] Spectre V2 : Kernel not compiled with retpoline; no mitigation available!
[    0.046182] Spectre V2 : Vulnerable
[    0.047181] Spectre V2 : Spectre v2 / SpectreRSB mitigation: Filling RSB on context switch
[    0.047703] Speculative Store Bypass: Vulnerable
[    0.048375] Performance Events: PMU not available due to virtualization, using software events only.
[    0.149316] devtmpfs: initialized
[    0.149590] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.150181] futex hash table entries: 256 (order: 0, 6144 bytes, linear)
[    0.150410] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.150829] thermal_sys: Registered thermal governor 'step_wise'
[    0.150829] thermal_sys: Registered thermal governor 'user_space'
[    0.151183] cpuidle: using governor menu
[    0.152562] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.153041] ACPI: bus type PCI registered
[    0.153181] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[    0.153618] PCI: Using configuration type 1 for base access
[    0.153972] PCI: Using configuration type 1 for extended access
[    0.154451] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.155400] ACPI: Added _OSI(Module Device)
[    0.155671] ACPI: Added _OSI(Processor Device)
[    0.155955] ACPI: Added _OSI(3.0 _SCP Extensions)
[    0.156181] ACPI: Added _OSI(Processor Aggregator Device)
[    0.156526] ACPI: Added _OSI(Linux-Dell-Video)
[    0.156811] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[    0.157181] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics)
[    0.157659] ACPI: 1 ACPI AML tables successfully acquired and loaded
[    0.158258] ACPI: Interpreter enabled
[    0.158497] ACPI: PM: (supports S0 S5)
[    0.158739] ACPI: Using IOAPIC for interrupt routing
[    0.159063] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[    0.159206] ACPI: Enabled 1 GPEs in block 00 to 07
[    0.160531] ACPI: PCI Root Bridge [PC00] (domain 0000 [bus 00])
[    0.160910] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.161205] PCI host bridge to bus 0000:00
[    0.161469] pci_bus 0000:00: root bus resource [io  0x0000-0x0cf7 window]
[    0.162182] pci_bus 0000:00: root bus resource [io  0x0d00-0x1fff window]
[    0.162614] pci_bus 0000:00: root bus resource [io  0x2000-0x27bf window]
[    0.163043] pci_bus 0000:00: root bus resource [mem 0xc0000000-0xc02fffff window]
[    0.163181] pci_bus 0000:00: root bus resource [mem 0x800000000-0x81fffffff window]
[    0.163666] pci_bus 0000:00: root bus resource [bus 00]
[    0.164319] pci 0000:00:00.0: [1275:1275] type 00 class 0x060000
[    0.165314] pci 0000:00:04.0: [1af4:1001] type 00 class 0x010000
[    0.165769] pci 0000:00:04.0: reg 0x10: [io  0x2700-0x277f]
[    0.166160] pci 0000:00:04.0: reg 0x14: [mem 0xc0130000-0xc0131fff]
[    0.166620] pci 0000:00:04.1: [1af4:1009] type 00 class 0x010000
[    0.167252] pci 0000:00:04.1: reg 0x10: [io  0x2000-0x21ff]
[    0.167645] pci 0000:00:04.1: reg 0x14: [mem 0xc0132000-0xc0133fff]
[    0.168625] pci 0000:00:04.2: [1af4:1009] type 00 class 0x010000
[    0.169076] pci 0000:00:04.2: reg 0x10: [io  0x2200-0x23ff]
[    0.169219] pci 0000:00:04.2: reg 0x14: [mem 0xc0134000-0xc0135fff]
[    0.170381] pci 0000:00:04.3: [1af4:1009] type 00 class 0x010000
[    0.170835] pci 0000:00:04.3: reg 0x10: [io  0x2400-0x25ff]
[    0.171219] pci 0000:00:04.3: reg 0x14: [mem 0xc0136000-0xc0137fff]
[    0.172047] pci 0000:00:05.0: [8086:100f] type 00 class 0x020000
[    0.172251] pci 0000:00:05.0: reg 0x10: [mem 0xc0100000-0xc011ffff]
[    0.172685] pci 0000:00:05.0: reg 0x14: [mem 0xc0120000-0xc012ffff]
[    0.173218] pci 0000:00:05.0: reg 0x18: [io  0x2780-0x2787]
[    0.173974] pci 0000:00:06.0: [10ec:b852] type 00 class 0x028000
[    0.174275] pci 0000:00:06.0: reg 0x10: [io  0x2600-0x26ff]
[    0.174739] pci 0000:00:06.0: reg 0x18: [mem 0xc0000000-0xc00fffff 64bit]
[    0.175554] pci 0000:00:06.0: PME# supported from D0 D3hot D3cold
[    0.176469] pci 0000:00:1f.0: [8086:7000] type 00 class 0x060100
[    0.177236] pci_bus 0000:00: on NUMA node 0
[    0.177278] ACPI: PCI: Interrupt link LNKA configured for IRQ 5
[    0.177694] ACPI: PCI: Interrupt link LNKB configured for IRQ 6
[    0.178104] ACPI: PCI: Interrupt link LNKC configured for IRQ 7
[    0.178217] ACPI: PCI: Interrupt link LNKD configured for IRQ 10
[    0.178634] ACPI: PCI: Interrupt link LNKE configured for IRQ 11
[    0.179212] ACPI: PCI: Interrupt link LNKF configured for IRQ 0
[    0.179589] ACPI: PCI: Interrupt link LNKF disabled
[    0.179928] ACPI: PCI: Interrupt link LNKG configured for IRQ 0
[    0.180181] ACPI: PCI: Interrupt link LNKG disabled
[    0.180522] ACPI: PCI: Interrupt link LNKH configured for IRQ 0
[    0.180897] ACPI: PCI: Interrupt link LNKH disabled
[    0.181239] vgaarb: loaded
[    0.181426] pps_core: LinuxPPS API ver. 1 registered
[    0.181743] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.182183] PTP clock support registered
[    0.182484] NetLabel: Initializing
[    0.182705] NetLabel:  domain hash size = 128
[    0.183181] NetLabel:  protocols = UNLABELED CIPSOv4 CALIPSO
[    0.183547] NetLabel:  unlabeled traffic allowed by default
[    0.183910] PCI: Using ACPI for IRQ routing
[    0.184182] PCI: pci_cache_line_size set to 64 bytes
[    0.184269] e820: reserve RAM buffer [mem 0x16400000-0x17ffffff]
[    0.184277] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
[    0.184672] hpet0: 8 comparators, 32-bit 16.777216 MHz counter
[    0.187187] clocksource: Switched to clocksource hpet
[    0.187530] pnp: PnP ACPI init
[    0.187844] system 00:02: [io  0x04d0-0x04d1] has been reserved
[    0.188245] system 00:02: [io  0x0400-0x0407] has been reserved
[    0.188624] system 00:02: [mem 0xe0000000-0xefffffff] has been reserved
[    0.189074] pnp: PnP ACPI: found 8 devices
[    0.194203] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    0.194793] NET: Registered PF_INET protocol family
[    0.195144] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.195689] tcp_listen_portaddr_hash hash table entries: 256 (order: 0, 4096 bytes, linear)
[    0.196217] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.196724] TCP established hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.197222] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.197696] TCP: Hash tables configured (established 4096 bind 4096)
[    0.198106] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.198538] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[    0.199002] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.199469] pci_bus 0000:00: resource 4 [io  0x0000-0x0cf7 window]
[    0.199863] pci_bus 0000:00: resource 5 [io  0x0d00-0x1fff window]
[    0.200271] pci_bus 0000:00: resource 6 [io  0x2000-0x27bf window]
[    0.200664] pci_bus 0000:00: resource 7 [mem 0xc0000000-0xc02fffff window]
[    0.201098] pci_bus 0000:00: resource 8 [mem 0x800000000-0x81fffffff window]
[    0.201620] pci 0000:00:1f.0: Activating ISA DMA hang workarounds
[    0.202016] PCI: CLS 64 bytes, default 64
[    0.202377] Initialise system trusted keyrings
[    0.202906] workingset: timestamp_bits=62 max_order=17 bucket_order=0
[    0.203667] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.204047] 9p: Installing v9fs 9p2000 file system support
[    0.211441] Key type asymmetric registered
[    0.211706] Asymmetric key parser 'x509' registered
[    0.212130] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[    0.212617] ACPI: button: Power Button [PWRF]
[    0.213147] virtio-pci 0000:00:04.0: virtio_pci: leaving for legacy driver
[    0.213728] virtio-pci 0000:00:04.1: virtio_pci: leaving for legacy driver
[    0.214298] virtio-pci 0000:00:04.2: virtio_pci: leaving for legacy driver
[    0.214846] virtio-pci 0000:00:04.3: virtio_pci: leaving for legacy driver
[    0.215427] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.215893] 00:03: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[    0.216564] 00:04: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
[    0.217117] 00:05: ttyS2 at I/O 0x3e8 (irq = 4, base_baud = 115200) is a 16550A
[    0.217692] 00:06: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
[    0.218385] Non-volatile memory driver v1.3
[    0.219138] loop: module loaded
[    0.219617] virtio_blk virtio0: [vda] 196624 512-byte logical blocks (101 MB/96.0 MiB)
[    0.221105] e1000: Intel(R) PRO/1000 Network Driver
[    0.221439] e1000: Copyright (c) 1999-2006 Intel Corporation.
[    0.527822] e1000 0000:00:05.0 eth0: (PCI:33MHz:32-bit) 00:a0:98:8a:05:71
[    0.528242] e1000 0000:00:05.0 eth0: Intel(R) PRO/1000 Network Connection
[    0.528757] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[    0.529385] i8042: Warning: Keylock active
[    0.530064] serio: i8042 KBD port at 0x60,0x64 irq 1
[    0.530435] serio: i8042 AUX port at 0x60,0x64 irq 12
[    0.531063] rtc_cmos 00:07: registered as rtc0
[    0.531397] rtc_cmos 00:07: alarms up to one day, y3k, 114 bytes nvram
[    0.531911] Initializing XFRM netlink socket
[    0.532203] NET: Registered PF_INET6 protocol family
[    0.532696] Segment Routing with IPv6
[    0.532939] In-situ OAM (IOAM) with IPv6
[    0.533203] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    0.533648] NET: Registered PF_PACKET protocol family
[    0.533970] 9pnet: Installing 9P2000 support
[    0.534987] registered taskstats version 1
[    0.535244] Loading compiled-in X.509 certificates
[    0.535589] printk: console [netcon0] enabled
[    0.535859] netconsole: network logging started
[    0.536149] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    0.536849] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    0.537431] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    0.537961] cfg80211: failed to load regulatory.db
[    0.539289] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[    0.540070] devtmpfs: mounted
[    0.540343] Freeing unused kernel image (initmem) memory: 724K
[    0.540708] Write protecting the kernel read-only data: 12288k
[    0.541331] Freeing unused kernel image (text/rodata gap) memory: 2044K
[    0.541789] Freeing unused kernel image (rodata/data gap) memory: 476K
[    0.542191] Run /sbin/init as init process
[    0.542463]   with arguments:
[    0.542463]     /sbin/init
[    0.542463]   with environment:
[    0.542464]     HOME=/
[    0.542464]     TERM=linux
[    0.542464]     BOOT_IMAGE=(host)/usr/local/share/wifibox/vmlinuz
[    0.542465]     modules=squashfs
[    0.707060] rtw89core: loading out-of-tree module taints kernel.
[    0.720315] rtw89_8852be 0000:00:06.0: can't derive routing for PCI INT A
[    0.720317] rtw89_8852be 0000:00:06.0: PCI INT A: not connected
[    0.750084] rtw89_8852be 0000:00:06.0: Firmware version 0.29.29.0, cmd version 0, type 5
[    0.750087] rtw89_8852be 0000:00:06.0: Firmware version 0.29.29.0, cmd version 0, type 3
[    1.022269] rtw89_8852be 0000:00:06.0: chip rfe_type is 1

Additional context

Add any other context about the problem here that might help the investigation.

Have you tried to turn it on and off?

Elimelech commented 1 year ago

2023-03-22T14:33:22+0200 WARN No passthru device is configured 2023-03-22T14:33:22+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T14:35:51+0200 WARN No bhyve PPT device could be found 2023-03-22T14:35:53+0200 WARN No passthru device is configured 2023-03-22T14:35:53+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T14:39:49+0200 WARN No bhyve PPT device could be found 2023-03-22T14:39:50+0200 WARN No passthru device is configured 2023-03-22T14:39:50+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T14:42:23+0200 WARN No passthru device is configured 2023-03-22T14:42:23+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T15:04:40+0200 WARN No passthru device is configured 2023-03-22T15:04:40+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T15:07:33+0200 WARN No passthru device is configured 2023-03-22T15:07:33+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T15:11:20+0200 WARN No bhyve PPT device could be found 2023-03-22T15:11:21+0200 WARN No passthru device is configured 2023-03-22T15:11:21+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:18:14+0200 WARN No passthru device is configured 2023-03-22T20:18:15+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:20:51+0200 WARN No bhyve PPT device could be found 2023-03-22T20:20:51+0200 WARN No passthru device is configured 2023-03-22T20:20:51+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:22+0200 WARN Guest is already run by PID 19011, left intact 2023-03-22T20:22:22+0200 WARN Unix Domain Sockets are already forwarded, skipping 2023-03-22T20:22:42+0200 WARN No bhyve PPT device could be found 2023-03-22T20:22:46+0200 WARN No passthru device is configured 2023-03-22T20:22:46+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:46+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:47+0200 WARN No passthru device is configured 2023-03-22T20:22:47+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:47+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:48+0200 WARN No passthru device is configured 2023-03-22T20:22:48+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:48+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:49+0200 WARN No passthru device is configured 2023-03-22T20:22:49+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:49+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:50+0200 WARN No passthru device is configured 2023-03-22T20:22:50+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:50+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:51+0200 WARN No passthru device is configured 2023-03-22T20:22:51+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:51+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:52+0200 WARN No passthru device is configured 2023-03-22T20:22:52+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:52+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:54+0200 WARN No passthru device is configured 2023-03-22T20:22:54+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:54+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:55+0200 WARN No passthru device is configured 2023-03-22T20:22:55+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:55+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:56+0200 WARN No passthru device is configured 2023-03-22T20:22:56+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:56+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:57+0200 WARN No passthru device is configured 2023-03-22T20:22:57+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:57+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:58+0200 WARN No passthru device is configured 2023-03-22T20:22:58+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:58+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:22:59+0200 WARN No passthru device is configured 2023-03-22T20:22:59+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:22:59+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:00+0200 WARN No passthru device is configured 2023-03-22T20:23:00+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:00+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:01+0200 WARN No passthru device is configured 2023-03-22T20:23:01+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:01+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:02+0200 WARN No passthru device is configured 2023-03-22T20:23:02+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:02+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:03+0200 WARN No passthru device is configured 2023-03-22T20:23:03+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:03+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:04+0200 WARN No passthru device is configured 2023-03-22T20:23:04+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:04+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:05+0200 WARN No passthru device is configured 2023-03-22T20:23:05+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:05+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:06+0200 WARN No passthru device is configured 2023-03-22T20:23:06+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:06+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:07+0200 WARN No passthru device is configured 2023-03-22T20:23:07+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:07+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:08+0200 WARN No passthru device is configured 2023-03-22T20:23:08+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:08+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:09+0200 WARN No passthru device is configured 2023-03-22T20:23:09+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:09+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:10+0200 WARN No passthru device is configured 2023-03-22T20:23:10+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:10+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:11+0200 WARN No passthru device is configured 2023-03-22T20:23:11+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:11+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:12+0200 WARN No passthru device is configured 2023-03-22T20:23:12+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:12+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:13+0200 WARN No passthru device is configured 2023-03-22T20:23:13+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:13+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:14+0200 WARN No passthru device is configured 2023-03-22T20:23:14+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:14+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:16+0200 WARN No passthru device is configured 2023-03-22T20:23:16+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:16+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:17+0200 WARN No passthru device is configured 2023-03-22T20:23:17+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:17+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:18+0200 WARN No passthru device is configured 2023-03-22T20:23:18+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:18+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:19+0200 WARN No passthru device is configured 2023-03-22T20:23:19+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:19+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:20+0200 WARN No passthru device is configured 2023-03-22T20:23:20+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:20+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:21+0200 WARN No passthru device is configured 2023-03-22T20:23:21+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:21+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:22+0200 WARN No passthru device is configured 2023-03-22T20:23:22+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:22+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:23+0200 WARN No passthru device is configured 2023-03-22T20:23:23+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:23+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:24+0200 WARN No passthru device is configured 2023-03-22T20:23:24+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:24+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:25+0200 WARN No passthru device is configured 2023-03-22T20:23:25+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:25+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:26+0200 WARN No passthru device is configured 2023-03-22T20:23:26+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:26+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:27+0200 WARN No passthru device is configured 2023-03-22T20:23:27+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:27+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:28+0200 WARN No passthru device is configured 2023-03-22T20:23:28+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:28+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:29+0200 WARN No passthru device is configured 2023-03-22T20:23:29+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:29+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:30+0200 WARN No passthru device is configured 2023-03-22T20:23:30+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:30+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:31+0200 WARN No passthru device is configured 2023-03-22T20:23:31+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:31+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:32+0200 WARN No passthru device is configured 2023-03-22T20:23:32+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:32+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:33+0200 WARN No passthru device is configured 2023-03-22T20:23:33+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:33+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:34+0200 WARN No passthru device is configured 2023-03-22T20:23:34+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:34+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:35+0200 WARN No passthru device is configured 2023-03-22T20:23:35+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:35+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:37+0200 WARN No passthru device is configured 2023-03-22T20:23:37+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:37+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:38+0200 WARN No passthru device is configured 2023-03-22T20:23:38+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:38+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:39+0200 WARN No passthru device is configured 2023-03-22T20:23:39+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:39+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:40+0200 WARN No passthru device is configured 2023-03-22T20:23:40+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:40+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:41+0200 WARN No passthru device is configured 2023-03-22T20:23:41+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:41+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:42+0200 WARN No passthru device is configured 2023-03-22T20:23:42+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:42+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:43+0200 WARN No passthru device is configured 2023-03-22T20:23:43+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:43+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:44+0200 WARN No passthru device is configured 2023-03-22T20:23:44+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:44+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:45+0200 WARN No passthru device is configured 2023-03-22T20:23:45+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:45+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:46+0200 WARN No passthru device is configured 2023-03-22T20:23:46+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:46+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:47+0200 WARN No passthru device is configured 2023-03-22T20:23:47+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:47+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:48+0200 WARN No passthru device is configured 2023-03-22T20:23:48+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:48+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:49+0200 WARN No passthru device is configured 2023-03-22T20:23:49+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:49+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:50+0200 WARN No passthru device is configured 2023-03-22T20:23:50+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:50+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:51+0200 WARN No passthru device is configured 2023-03-22T20:23:51+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:51+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:52+0200 WARN No passthru device is configured 2023-03-22T20:23:52+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:52+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:53+0200 WARN No passthru device is configured 2023-03-22T20:23:53+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:53+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:54+0200 WARN No passthru device is configured 2023-03-22T20:23:54+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:54+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:55+0200 WARN No passthru device is configured 2023-03-22T20:23:55+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:55+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:56+0200 WARN No passthru device is configured 2023-03-22T20:23:56+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:56+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:57+0200 WARN No passthru device is configured 2023-03-22T20:23:57+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:57+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:23:58+0200 WARN No passthru device is configured 2023-03-22T20:23:58+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:23:58+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:00+0200 WARN No passthru device is configured 2023-03-22T20:24:00+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:00+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:01+0200 WARN No passthru device is configured 2023-03-22T20:24:01+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:01+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:02+0200 WARN No passthru device is configured 2023-03-22T20:24:02+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:02+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:03+0200 WARN No passthru device is configured 2023-03-22T20:24:03+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:03+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:04+0200 WARN No passthru device is configured 2023-03-22T20:24:04+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:04+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:05+0200 WARN No passthru device is configured 2023-03-22T20:24:05+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:05+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:06+0200 WARN No passthru device is configured 2023-03-22T20:24:06+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:06+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:07+0200 WARN No passthru device is configured 2023-03-22T20:24:07+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:07+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:08+0200 WARN No passthru device is configured 2023-03-22T20:24:08+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:08+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:09+0200 WARN No passthru device is configured 2023-03-22T20:24:09+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:09+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:10+0200 WARN No passthru device is configured 2023-03-22T20:24:10+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:10+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:11+0200 WARN No passthru device is configured 2023-03-22T20:24:11+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:11+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:12+0200 WARN No passthru device is configured 2023-03-22T20:24:12+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:12+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:13+0200 WARN No passthru device is configured 2023-03-22T20:24:13+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:13+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:14+0200 WARN No passthru device is configured 2023-03-22T20:24:14+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:14+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:15+0200 WARN No passthru device is configured 2023-03-22T20:24:15+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:15+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:16+0200 WARN No passthru device is configured 2023-03-22T20:24:16+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:16+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:17+0200 WARN No passthru device is configured 2023-03-22T20:24:17+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:18+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:19+0200 WARN No passthru device is configured 2023-03-22T20:24:19+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:19+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:20+0200 WARN No passthru device is configured 2023-03-22T20:24:20+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:20+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:21+0200 WARN No passthru device is configured 2023-03-22T20:24:21+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:21+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:22+0200 WARN No passthru device is configured 2023-03-22T20:24:22+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:22+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:23+0200 WARN No passthru device is configured 2023-03-22T20:24:23+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:23+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:24+0200 WARN No passthru device is configured 2023-03-22T20:24:24+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:24+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:25+0200 WARN No passthru device is configured 2023-03-22T20:24:25+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:25+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:26+0200 WARN No passthru device is configured 2023-03-22T20:24:26+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:26+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:27+0200 WARN No passthru device is configured 2023-03-22T20:24:27+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:27+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:28+0200 WARN No passthru device is configured 2023-03-22T20:24:28+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:28+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:29+0200 WARN No passthru device is configured 2023-03-22T20:24:29+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:29+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:30+0200 WARN No passthru device is configured 2023-03-22T20:24:30+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:30+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:31+0200 WARN No passthru device is configured 2023-03-22T20:24:31+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:31+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:32+0200 WARN No passthru device is configured 2023-03-22T20:24:32+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:32+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:33+0200 WARN No passthru device is configured 2023-03-22T20:24:33+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:33+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:34+0200 WARN No passthru device is configured 2023-03-22T20:24:34+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:34+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:35+0200 WARN No passthru device is configured 2023-03-22T20:24:35+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:35+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:24:36+0200 WARN No passthru device is configured 2023-03-22T20:24:36+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:24:36+0200 ERROR No tap interface is available, cannot proceed 2023-03-22T20:32:55+0200 WARN No passthru device is configured 2023-03-22T20:32:55+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:33:49+0200 WARN No bhyve PPT device could be found 2023-03-22T20:33:49+0200 WARN No passthru device is configured 2023-03-22T20:33:49+0200 WARN No PPT driver is attached due to lack of device 2023-03-22T20:34:19+0200 WARN No bhyve PPT device could be found 2023-03-22T20:34:19+0200 WARN No passthru device is configured 2023-03-22T20:34:19+0200 WARN No PPT driver is attached due to lack of device 2023-03-23T09:21:54+0200 WARN Guest is not running, hence not stopped 2023-03-23T09:21:54+0200 WARN No linked tap inteface found for wifibox0 2023-03-23T09:22:25+0200 WARN The PPT device could not be destroyed 2023-03-23T09:22:32+0200 WARN The PPT device could not be destroyed 2023-03-23T09:22:39+0200 WARN The PPT device could not be destroyed 2023-03-23T09:22:47+0200 WARN The PPT device could not be destroyed 2023-03-23T09:22:54+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:01+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:09+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:16+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:24+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:31+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:38+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:45+0200 WARN The PPT device could not be destroyed 2023-03-23T09:23:53+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:00+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:07+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:14+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:22+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:29+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:36+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:44+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:51+0200 WARN The PPT device could not be destroyed 2023-03-23T09:24:58+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:05+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:12+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:19+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:27+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:34+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:41+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:48+0200 WARN The PPT device could not be destroyed 2023-03-23T09:25:55+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:03+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:10+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:17+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:24+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:31+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:38+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:45+0200 WARN The PPT device could not be destroyed 2023-03-23T09:26:53+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:00+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:07+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:15+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:22+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:29+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:36+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:43+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:51+0200 WARN The PPT device could not be destroyed 2023-03-23T09:27:58+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:05+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:12+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:19+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:27+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:34+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:41+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:48+0200 WARN The PPT device could not be destroyed 2023-03-23T09:28:55+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:02+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:09+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:17+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:24+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:31+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:38+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:45+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:52+0200 WARN The PPT device could not be destroyed 2023-03-23T09:29:59+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:07+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:14+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:21+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:28+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:35+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:42+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:49+0200 WARN The PPT device could not be destroyed 2023-03-23T09:30:56+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:04+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:11+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:18+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:25+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:32+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:39+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:46+0200 WARN The PPT device could not be destroyed 2023-03-23T09:31:53+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:01+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:08+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:15+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:22+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:30+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:37+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:44+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:51+0200 WARN The PPT device could not be destroyed 2023-03-23T09:32:58+0200 WARN The PPT device could not be destroyed 2023-03-23T09:33:05+0200 WARN The PPT device could not be destroyed 2023-03-23T09:33:13+0200 WARN The PPT device could not be destroyed 2023-03-23T09:33:20+0200 WARN The PPT device could not be destroyed 2023-03-23T09:33:27+0200 WARN The PPT device could not be destroyed 2023-03-23T09:43:40+0200 WARN The PPT device could not be destroyed 2023-03-23T09:43:47+0200 WARN The PPT device could not be destroyed 2023-03-23T09:43:54+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:01+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:09+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:16+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:24+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:31+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:39+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:46+0200 WARN The PPT device could not be destroyed 2023-03-23T09:44:53+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:01+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:08+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:15+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:22+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:30+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:37+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:44+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:51+0200 WARN The PPT device could not be destroyed 2023-03-23T09:45:58+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:05+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:13+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:20+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:27+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:34+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:41+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:48+0200 WARN The PPT device could not be destroyed 2023-03-23T09:46:56+0200 WARN The PPT device could not be destroyed 2023-03-23T10:11:08+0200 WARN The PPT device could not be destroyed 2023-03-23T10:32:27+0200 WARN The PPT device could not be destroyed 2023-03-23T10:41:45+0200 WARN The PPT device could not be destroyed 2023-03-23T10:41:52+0200 WARN The PPT device could not be destroyed 2023-03-23T10:41:59+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:06+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:14+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:21+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:28+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:36+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:43+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:51+0200 WARN The PPT device could not be destroyed 2023-03-23T10:42:58+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:05+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:12+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:20+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:27+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:34+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:41+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:49+0200 WARN The PPT device could not be destroyed 2023-03-23T10:43:56+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:03+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:10+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:17+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:24+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:32+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:39+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:46+0200 WARN The PPT device could not be destroyed 2023-03-23T10:44:53+0200 WARN The PPT device could not be destroyed 2023-03-23T10:45:01+0200 WARN The PPT device could not be destroyed 2023-03-23T16:38:56+0200 WARN The PPT device could not be destroyed 2023-03-23T16:39:04+0200 WARN Bridge interface already exists: wifibox0, skipping creation 2023-03-23T16:39:04+0200 WARN Linked tap interface already exists: tap0, skipping creation 2023-03-23T16:39:04+0200 WARN Guest is already run by PID 63719, left intact 2023-03-23T16:39:04+0200 WARN Unix Domain Sockets are already forwarded, skipping 2023-03-23T16:39:26+0200 WARN The PPT device could not be destroyed 2023-03-23T16:39:29+0200 WARN Guest is not running, hence not stopped 2023-03-23T16:39:29+0200 WARN No linked tap inteface found for wifibox0 2023-03-23T16:39:31+0200 WARN Guest is not running, hence not stopped 2023-03-23T16:39:31+0200 WARN No linked tap inteface found for wifibox0 2023-03-24T11:02:44+0200 WARN The PPT device could not be destroyed 2023-03-24T15:47:00+0200 WARN The PPT device could not be destroyed 2023-03-24T16:55:45+0200 WARN The PPT device could not be destroyed 2023-03-24T17:55:32+0200 WARN The PPT device could not be destroyed 2023-03-24T23:21:43+0200 WARN The PPT device could not be destroyed 2023-03-25T00:13:20+0200 WARN The PPT device could not be destroyed 2023-03-25T00:34:59+0200 WARN The PPT device could not be destroyed 2023-03-25T10:24:41+0200 WARN The PPT device could not be destroyed 2023-03-25T10:24:48+0200 WARN The PPT device could not be destroyed 2023-03-25T10:24:55+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:02+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:09+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:16+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:24+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:31+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:38+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:45+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:52+0200 WARN The PPT device could not be destroyed 2023-03-25T10:25:59+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:07+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:14+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:21+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:28+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:35+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:42+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:50+0200 WARN The PPT device could not be destroyed 2023-03-25T10:26:57+0200 WARN The PPT device could not be destroyed 2023-03-25T10:27:04+0200 WARN The PPT device could not be destroyed 2023-03-25T10:27:15+0200 WARN The PPT device could not be destroyed 2023-03-25T16:46:45+0200 WARN The PPT device could not be destroyed 2023-03-25T16:46:52+0200 WARN The PPT device could not be destroyed 2023-03-25T16:46:59+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:07+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:14+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:22+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:29+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:36+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:44+0200 WARN The PPT device could not be destroyed 2023-03-25T16:47:51+0200 WARN The PPT device could not be destroyed 2023-03-25T16:48:24+0200 WARN The PPT device could not be destroyed 2023-03-25T16:48:31+0200 WARN The PPT device could not be destroyed 2023-03-25T16:48:39+0200 WARN The PPT device could not be destroyed 2023-03-25T16:48:46+0200 WARN The PPT device could not be destroyed 2023-03-25T16:48:53+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:01+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:08+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:16+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:23+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:31+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:38+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:46+0200 WARN The PPT device could not be destroyed 2023-03-25T16:49:53+0200 WARN The PPT device could not be destroyed 2023-03-25T16:50:01+0200 WARN The PPT device could not be destroyed 2023-03-25T16:50:08+0200 WARN The PPT device could not be destroyed 2023-03-25T16:50:15+0200 WARN The PPT device could not be destroyed 2023-03-25T16:50:23+0200 WARN The PPT device could not be destroyed 2023-03-25T18:03:05+0200 INFO Begin: wifibox start 2023-03-25T18:03:05+0200 INFO Creating bridge interface: wifibox0 2023-03-25T18:03:05+0200 INFO Linking tap interface to wifibox0: tap0 2023-03-25T18:03:05+0200 INFO vmm.ko is expected at path: /boot/kernel/vmm.ko 2023-03-25T18:03:05+0200 INFO vmm.ko is found at path: /boot/kernel/vmm.ko 2023-03-25T18:03:05+0200 INFO Waiting for bhyve to start up 2023-03-25T18:03:05+0200 INFO VM manager launched 2023-03-25T18:03:05+0200 INFO Gathering necessary configuration files for launching the guest 2023-03-25T18:03:05+0200 INFO Pulling bhyve options from configuration file 2023-03-25T18:03:05+0200 INFO Guest console is not configured to use 2023-03-25T18:03:05+0200 INFO Passthru device is configured: 1/0/0 2023-03-25T18:03:05+0200 INFO PPT driver is configured for pci1:0:0 device 2023-03-25T18:03:05+0200 INFO tap interface is configured: tap0 2023-03-25T18:03:05+0200 INFO Launching guest wifibox from /usr/local/share/wifibox with grub-bhyve 2023-03-25T18:03:05+0200 INFO Application config is found at /usr/local/etc/wifibox/wpa_supplicant 2023-03-25T18:03:05+0200 INFO Application config will be mounted writeable 2023-03-25T18:03:05+0200 INFO Launching guest wifibox from /usr/local/share/wifibox with bhyve 2023-03-25T18:03:06+0200 INFO Guest wifibox has started up 2023-03-25T18:03:06+0200 INFO Guest is managed by PID 44183 2023-03-25T18:03:06+0200 INFO Bringing up Unix Domain Socket pass-through 2023-03-25T18:03:06+0200 INFO Found guest IP address: 10.0.0.1 2023-03-25T18:03:06+0200 INFO Configured sockets: [path=/var/run/wpa_supplicant/wlan0,user=root,group=0,mode=770,port=1200 path=/var/run/wpa_supplicant/p2p-dev-wlan0,user=root,group=0,mode=770,port=1201] 2023-03-25T18:03:06+0200 INFO Hooking up 10.0.0.1:1200 as /var/run/wpa_supplicant/wlan0 (root:0@770) 2023-03-25T18:03:06+0200 INFO Hooking up 10.0.0.1:1201 as /var/run/wpa_supplicant/p2p-dev-wlan0 (root:0@770) 2023-03-25T18:03:06+0200 INFO End: wifibox start 2023-03-25T18:07:39+0200 DEBUG Program started as /usr/local/sbin/wifibox, with arguments: start 2023-03-25T18:07:39+0200 INFO Begin: wifibox start 2023-03-25T18:07:39+0200 DEBUG start=GN 2023-03-25T18:07:39+0200 INFO Creating bridge interface: wifibox0 2023-03-25T18:07:39+0200 DEBUG [ifconfig] wifibox0 2023-03-25T18:07:39+0200 INFO Linking tap interface to wifibox0: tap0 2023-03-25T18:07:39+0200 INFO vmm.ko is expected at path: /boot/kernel/vmm.ko 2023-03-25T18:07:39+0200 INFO vmm.ko is found at path: /boot/kernel/vmm.ko 2023-03-25T18:07:39+0200 DEBUG assert loaded: kmod=vmm, kmod_file=/boot/kernel/vmm.ko 2023-03-25T18:07:39+0200 DEBUG assert hardware support present: iommu=1, amdvi=1 2023-03-25T18:07:39+0200 DEBUG Backends reported by bhyve: 2023-03-25T18:07:39+0200 DEBUG [bhyve] ahci 2023-03-25T18:07:39+0200 DEBUG [bhyve] ahci-hd 2023-03-25T18:07:39+0200 DEBUG [bhyve] ahci-cd 2023-03-25T18:07:39+0200 DEBUG [bhyve] e1000 2023-03-25T18:07:39+0200 DEBUG [bhyve] dummy 2023-03-25T18:07:39+0200 DEBUG [bhyve] hda 2023-03-25T18:07:39+0200 DEBUG [bhyve] fbuf 2023-03-25T18:07:39+0200 DEBUG [bhyve] amd_hostbridge 2023-03-25T18:07:39+0200 DEBUG [bhyve] hostbridge 2023-03-25T18:07:39+0200 DEBUG [bhyve] lpc 2023-03-25T18:07:39+0200 DEBUG [bhyve] nvme 2023-03-25T18:07:39+0200 DEBUG [bhyve] passthru 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-9p 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-blk 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-console 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-input 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-net 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-rnd 2023-03-25T18:07:39+0200 DEBUG [bhyve] virtio-scsi 2023-03-25T18:07:39+0200 DEBUG [bhyve] uart 2023-03-25T18:07:39+0200 DEBUG [bhyve] xhci 2023-03-25T18:07:39+0200 INFO Waiting for bhyve to start up 2023-03-25T18:07:39+0200 DEBUG Program started as /usr/local/sbin/wifibox, with arguments: _manage_vm 2023-03-25T18:07:39+0200 DEBUG assert daemonized: parent=daemon 2023-03-25T18:07:39+0200 INFO VM manager launched 2023-03-25T18:07:39+0200 INFO Gathering necessary configuration files for launching the guest 2023-03-25T18:07:39+0200 INFO Pulling bhyve options from configuration file 2023-03-25T18:07:39+0200 DEBUG cpus=1, memory=356M, passthru=1/0/0, console=no 2023-03-25T18:07:39+0200 INFO Guest console is not configured to use 2023-03-25T18:07:39+0200 INFO Passthru device is configured: 1/0/0 2023-03-25T18:07:39+0200 INFO PPT driver is configured for pci1:0:0 device 2023-03-25T18:07:39+0200 INFO tap interface is configured: tap0 2023-03-25T18:07:39+0200 INFO Launching guest wifibox from /usr/local/share/wifibox with grub-bhyve 2023-03-25T18:07:39+0200 INFO Application config is found at /usr/local/etc/wifibox/wpa_supplicant 2023-03-25T18:07:39+0200 INFO Application config will be mounted writeable 2023-03-25T18:07:39+0200 DEBUG Devices: virtio-blk,/usr/local/share/wifibox/disk.img virtio-9p,config=/usr/local/etc/wifibox/appliance,ro virtio-9p,var=/var/run/wifibox/appliance virtio-9p,app_config=/usr/local/etc/wifibox/wpa_supplicant 2023-03-25T18:07:39+0200 DEBUG Arguments: -S -M 356M -r host -d /usr/local/share/wifibox wifibox 2023-03-25T18:07:39+0200 INFO Launching guest wifibox from /usr/local/share/wifibox with bhyve 2023-03-25T18:07:39+0200 DEBUG Arguments: -c 1 -m 356M -AHP -u -S -s 0,hostbridge -s 31,lpc -s 4:0,virtio-blk,/usr/local/share/wifibox/disk.img -s 4:1,virtio-9p,config=/usr/local/etc/wifibox/appliance,ro -s 4:2,virtio-9p,var=/var/run/wifibox/appliance -s 4:3,virtio-9p,app_config=/usr/local/etc/wifibox/wpa_supplicant -s 5:0,e1000,tap0 -s 6:0,passthru,1/0/0 wifibox 2023-03-25T18:07:39+0200 DEBUG [bhyve] wrmsr to register 0xc0011029(0x3) on vcpu 0 2023-03-25T18:07:39+0200 DEBUG [bhyve] rdmsr to register 0xc00000e9 on vcpu 0 2023-03-25T18:07:40+0200 INFO Guest wifibox has started up 2023-03-25T18:07:40+0200 INFO Guest is managed by PID 58031 2023-03-25T18:07:40+0200 INFO Bringing up Unix Domain Socket pass-through 2023-03-25T18:07:40+0200 INFO Found guest IP address: 10.0.0.1 2023-03-25T18:07:40+0200 INFO Configured sockets: [path=/var/run/wpa_supplicant/wlan0,user=root,group=0,mode=770,port=1200 path=/var/run/wpa_supplicant/p2p-dev-wlan0,user=root,group=0,mode=770,port=1201] 2023-03-25T18:07:40+0200 INFO Hooking up 10.0.0.1:1200 as /var/run/wpa_supplicant/wlan0 (root:0@770) 2023-03-25T18:07:40+0200 INFO Hooking up 10.0.0.1:1201 as /var/run/wpa_supplicant/p2p-dev-wlan0 (root:0@770) 2023-03-25T18:07:40+0200 INFO End: wifibox start 2023-03-25T23:06:33+0200 WARN The PPT device could not be destroyed 2023-03-26T00:59:13+0200 WARN The PPT device could not be destroyed 2023-03-26T12:58:29+0300 WARN The PPT device could not be destroyed 2023-03-26T14:28:14+0300 WARN The PPT device could not be destroyed 2023-03-26T15:19:25+0300 WARN The PPT device could not be destroyed 2023-03-26T20:08:40+0300 WARN The PPT device could not be destroyed 2023-03-27T00:56:41+0300 WARN The PPT device could not be destroyed 2023-03-28T03:02:18+0300 WARN The PPT device could not be destroyed 2023-03-28T13:25:49+0300 WARN The PPT device could not be destroyed 2023-03-28T20:27:43+0300 WARN The PPT device could not be destroyed 2023-03-28T23:02:23+0300 WARN The PPT device could not be destroyed 2023-03-29T01:00:50+0300 WARN The PPT device could not be destroyed 2023-03-29T10:56:38+0300 WARN The PPT device could not be destroyed 2023-03-29T11:26:52+0300 WARN The PPT device could not be destroyed 2023-03-29T17:07:33+0300 WARN The PPT device could not be destroyed 2023-03-29T17:37:13+0300 WARN The PPT device could not be destroyed 2023-03-29T19:58:45+0300 WARN The PPT device could not be destroyed 2023-03-30T01:43:01+0300 WARN The PPT device could not be destroyed 2023-03-30T10:25:14+0300 WARN The PPT device could not be destroyed 2023-03-30T13:28:34+0300 WARN The PPT device could not be destroyed 2023-03-31T02:19:51+0300 WARN The PPT device could not be destroyed 2023-03-31T12:49:29+0300 WARN The PPT device could not be destroyed 2023-04-01T01:11:33+0300 WARN The PPT device could not be destroyed 2023-04-01T10:19:24+0300 WARN The PPT device could not be destroyed 2023-04-01T21:02:29+0300 WARN The PPT device could not be destroyed 2023-04-02T00:13:26+0300 WARN The PPT device could not be destroyed 2023-04-02T01:38:28+0300 WARN The PPT device could not be destroyed 2023-04-02T13:47:18+0300 WARN The PPT device could not be destroyed 2023-04-02T14:04:33+0300 WARN The PPT device could not be destroyed 2023-04-02T16:27:15+0300 WARN The PPT device could not be destroyed 2023-04-02T17:11:52+0300 WARN The PPT device could not be destroyed 2023-04-02T18:03:00+0300 WARN The PPT device could not be destroyed 2023-04-02T18:09:47+0300 WARN The PPT device could not be destroyed 2023-04-02T18:16:48+0300 WARN The PPT device could not be destroyed 2023-04-02T18:25:08+0300 WARN The PPT device could not be destroyed 2023-04-02T19:04:47+0300 WARN The PPT device could not be destroyed 2023-04-02T19:08:08+0300 WARN The PPT device could not be destroyed 2023-04-03T00:17:37+0300 WARN The PPT device could not be destroyed 2023-04-03T00:42:09+0300 WARN The PPT device could not be destroyed 2023-04-03T01:15:17+0300 WARN The PPT device could not be destroyed 2023-04-03T01:28:21+0300 WARN The PPT device could not be destroyed 2023-04-03T10:10:25+0300 WARN The PPT device could not be destroyed 2023-04-03T11:09:51+0300 WARN The PPT device could not be destroyed 2023-04-03T16:58:03+0300 WARN The PPT device could not be destroyed 2023-04-03T19:50:09+0300 WARN The PPT device could not be destroyed 2023-04-03T20:09:36+0300 WARN The PPT device could not be destroyed 2023-04-03T20:30:41+0300 WARN The PPT device could not be destroyed 2023-04-04T01:48:54+0300 WARN The PPT device could not be destroyed 2023-04-04T12:32:37+0300 WARN The PPT device could not be destroyed 2023-04-05T01:26:21+0300 WARN The PPT device could not be destroyed 2023-04-05T10:40:28+0300 WARN The PPT device could not be destroyed 2023-04-05T12:24:48+0300 WARN The PPT device could not be destroyed 2023-04-05T18:44:30+0300 WARN The PPT device could not be destroyed 2023-04-06T00:02:46+0300 WARN The PPT device could not be destroyed 2023-04-06T01:10:53+0300 WARN The PPT device could not be destroyed 2023-04-06T11:08:38+0300 WARN The PPT device could not be destroyed 2023-04-06T12:21:00+0300 WARN The PPT device could not be destroyed 2023-04-06T15:08:48+0300 WARN The PPT device could not be destroyed 2023-04-06T15:36:13+0300 WARN The PPT device could not be destroyed 2023-04-06T15:50:35+0300 WARN The PPT device could not be destroyed 2023-04-06T16:03:21+0300 WARN The PPT device could not be destroyed 2023-04-06T16:32:49+0300 WARN The PPT device could not be destroyed 2023-04-06T18:03:36+0300 WARN The PPT device could not be destroyed 2023-04-06T18:41:45+0300 WARN The PPT device could not be destroyed 2023-04-07T02:19:38+0300 WARN The PPT device could not be destroyed 2023-04-07T11:03:59+0300 WARN The PPT device could not be destroyed 2023-04-07T11:42:48+0300 WARN The PPT device could not be destroyed 2023-04-07T12:36:37+0300 WARN The PPT device could not be destroyed 2023-04-07T12:46:09+0300 WARN The PPT device could not be destroyed 2023-04-07T16:20:25+0300 WARN The PPT device could not be destroyed 2023-04-07T17:48:31+0300 WARN The PPT device could not be destroyed 2023-04-08T10:22:44+0300 WARN The PPT device could not be destroyed 2023-04-08T22:43:09+0300 WARN The PPT device could not be destroyed 2023-04-08T22:48:46+0300 WARN The PPT device could not be destroyed 2023-04-09T01:43:13+0300 WARN The PPT device could not be destroyed 2023-04-09T02:47:29+0300 WARN The PPT device could not be destroyed 2023-04-09T03:02:15+0300 WARN The PPT device could not be destroyed 2023-04-10T02:09:44+0300 WARN The PPT device could not be destroyed 2023-04-11T01:09:53+0300 WARN The PPT device could not be destroyed 2023-04-11T08:54:01+0300 WARN The PPT device could not be destroyed 2023-04-11T09:31:55+0300 WARN The PPT device could not be destroyed 2023-04-11T09:35:25+0300 WARN The PPT device could not be destroyed

pgj commented 1 year ago

What is the exact value you tried for cpus? In the attached logs, it still seems to be set to 1. Anyhow, I am inclined to think that the problem is with bhyve(8) itself but I will check myself.

pgj commented 1 year ago

Increasing the value of cpus seems to be ignored by the Alpine-based guest. That is what I get in dmesg on the guest when cpus is set to 4:

[    0.001504] system APIC only can use physical flat
[    0.001507] APIC: NR_CPUS/possible_cpus limit of 1 reached. Processor 1/0x1 ignored.
[    0.001508] APIC: NR_CPUS/possible_cpus limit of 1 reached. Processor 2/0x2 ignored.
[    0.001509] APIC: NR_CPUS/possible_cpus limit of 1 reached. Processor 3/0x3 ignored.
[    0.001512] ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])
[    0.001562] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-31

This is further supported by the nproc command after boot:

# nproc --all
1
pgj commented 1 year ago

Ah, yes -- this is how Linux is configured for the Alpine-based guest. That said, it does not make much sense to change the value of cpus to a higher number. And the high CPU utilization might be a result of that. However, this does not happen on my system.

Elimelech commented 1 year ago 
root@F3ja:/usr/home/luba # nproc --all
16

I don't have linux, but freeBSD. Or maybe the virtual machine does not work correctly if you increase the number of cpus, if ACPI does not work at all and for some reason hibernation, sleep mode in the laptop does not work?

I have this in the logs:

Apr 12 08:44:14 F3ja kernel: acpi_button0: <Power Button> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_syscontainer0: <System Container> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_wmi1: <ACPI-WMI mapping> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_wmi1: Embedded MOF found
Apr 12 08:44:14 F3ja kernel: ACPI: \_SB.WMID.WQAB: 1 arguments were passed to a non-method ACPI object (Buffer) (20201113/nsarguments-361)
Apr 12 08:44:14 F3ja kernel: acpi_hp0: <HP ACPI-WMI Mapping> on acpi_wmi1
Apr 12 08:44:14 F3ja kernel: acpi_hp0: HP event GUID detected, installing event handler
Apr 12 08:44:14 F3ja kernel: acpi_hp0: HP CMI GUID detected
Apr 12 08:44:14 F3ja kernel: battery0: <ACPI Control Method Battery> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_acad0: <AC Adapter> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_lid0: <Control Method Lid Switch> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_tz0: <Thermal Zone> on acpi0
Apr 12 08:44:14 F3ja kernel: acpi_tz0: _CRT value is absurd, ignored (255.1C)
Apr 12 08:44:14 F3ja kernel: cpu0: <ACPI CPU> on acpi0
pgj commented 1 year ago

I know that you have FreeBSD otherwise you did not create this ticket. But you should also understand that the essence of Wifibox is that it uses the bhyve hypervisor to run a Linux guest operating system in a virtual machine. Please read more about bhyve to wrap your mind around the idea in general.

I believe the virtual machine or the guest operating system works just fine. As cited above, that is how the Linux guest is put together: it is configured to work with only a single CPU. It will ignore all the other CPUs even if they are offered by bhyve. Therefore it makes no sense to increase their count.

Issues with the hibernation and sleep modes of the host (FreeBSD) system are completely independent from how Wifibox works. For example, I also have that working on my system but the actual chances depend on the given hardware. Please find other channels for help regarding issues about suspend and resume.

Elimelech commented 1 year ago

Thanks a lot for your work and help! Will study further....

pgj commented 1 year ago

You are welcome. That said, I now consider this ticket resolved: the value of cpus should not be increased because it has no effect and not required for the optimal performance. Random stats to support the case: on my system (Intel Wireless 8260) I could do a speed test with 250 Mbits/s download and 10 Mbits/s upload through 802.11ac, which peaked at 60% of CPU utilization. Even though there was a single virtual CPU allocated for the bhyve guest, the load was roughly evenly distributed between the 4 cores of the host.

As a side note, I would add that keeping the cpus parameter in bhyve.conf could still make sense as Wifibox itself is only responsible for the orchestration of the virtual machine and there may be guests where it is possible to use more virtual CPUs. The Wifibox/Alpine guest is not like that, but that is only one of the many "firmwares" to use.