vermaden on Nostr: With 'vm-bhyve' on #FreeBSD the #Bhyve VMs will not autostart on boot if 'run.lock' ...
With 'vm-bhyve' on #FreeBSD the #Bhyve VMs will not autostart on boot if 'run.lock' files are present.
I use simple workaround for that:
# cat /etc/rc.conf
# BHYVE
/usr/bin/find /vm/* -name run.lock -delete
vm_enable="YES"
vm_dir="zfs:zroot/vm"
vm_list="vm1 vm2"
Published at
2024-05-15 13:33:44Event JSON
{
"id": "f8793b0383425392b73014cbf336994ab079e9424fa62cd879f6300ec6c83817",
"pubkey": "c8fb65ebef145affc8ea06d5f6971fffb6236dfd3396551102133861e4244326",
"created_at": 1715780024,
"kind": 1,
"tags": [
[
"t",
"freebsd"
],
[
"t",
"bhyve"
],
[
"proxy",
"https://mastodon.bsd.cafe/users/vermaden/statuses/112445359708483241",
"activitypub"
]
],
"content": "With 'vm-bhyve' on #FreeBSD the #Bhyve VMs will not autostart on boot if 'run.lock' files are present.\n\nI use simple workaround for that:\n\n# cat /etc/rc.conf\n# BHYVE\n /usr/bin/find /vm/* -name run.lock -delete\n vm_enable=\"YES\"\n vm_dir=\"zfs:zroot/vm\"\n vm_list=\"vm1 vm2\"",
"sig": "3a3c3b8da04126abdf0cb6fa4372fa9ba642a68e70810b57935e0a0cd65df36092723fd8076f94d3048f24fd6adf12b105e8d3a4bfc818fbef4cc5555d38f848"
}
