tcctl not displaying failed upon starting vmd when interface does not exist

[Richard Bucker]

Fresh install of OpenBSD 6.8, completely patched.

here is vm.conf:

 internet gateway and backend server

switch "my_switch" {
    interface bridge0
}

vm "gw" {
    memory 1G
    disable
    disk "/home/rbucker/disk2.qcow2"
    local interface
    interface { switch "gw_switch" }
    interfaces 1
}

vm "vm1" {
    memory 1G
    disable
    disk /home/rbucker/disk1.qcow2
    local interface
    interfaces 1
    #interface vio0
}



here is my ifconfig... note that the switch interface bridge0 does not exist

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 32768
        index 4 priority 0 llprio 3
        groups: lo
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
        inet 127.0.0.1 netmask 0xff000000
iwm0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        lladdr XXXXXXXXXXXX
        index 1 priority 4 llprio 3
        groups: wlan
        media: IEEE802.11 autoselect
        status: no network
        ieee80211: nwid ""
em0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
        lladdr b8:ae:ed:eb:73:ac
        index 2 priority 0 llprio 3
        groups: egress
        media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause)
        status: active
        inet 192.168.86.116 netmask 0xffffff00 broadcast 192.168.86.255
enc0: flags=0<>
        index 3 priority 0 llprio 3
        groups: enc
        status: active
pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33136
        index 5 priority 0 llprio 3
        groups: pflog



configuration test:

$ vmd -dvn
configuration OK



start the service

$ sudo rcctl start vmd
vmd(ok)


show the status

$ sudo vmctl status
vmctl: connect: /var/run/vmd.sock: Connection refused


ps ax|grep vmd ... and nothing is returned... 'cause nothing is
running....  So I did some debug...


$ sudo vmd -vd
startup
priv: priv_dispatch_parent: bridge "bridge0" does not exist
vmm exiting, pid 5634
control exiting, pid 33017



I'm thinking that this should have FAILED when trying to start the service
... likely missing an error return value because a typo in the config
produces a FAIL.













*--Richard  *