<>
Not new. Been in production for years now.
https://github.com/firecracker-microvm/firecracker
p vixie
i've never been able to get tip or cu to accept a paste. this was not
the only reason but it was one reason why i wrote rtty many years ago.
/usr/ports/sysutils/rtty
hard to configure, sorry, it didn't have to scale.
pkg install vm-bhyve
--
P Vixie
in the old days i used to have to hard wire it. now it picks the same
value i used to hard code. ntpd encountered chaos with other values.
kern.timecounter.hardware: TSC-low
i don't know if this has become an urban legend since i last fought it.
re:
Sean McBride wrote on 2023-10-11 11:28:
Hi
Alejandro Imass wrote on 2024-02-01 07:18:
...
But I don't think anyone really wants Docker and there's the hypervisor
for that. The intent of the thread is to deliberate on native freebsd
orchestration and autoscaling.
I don't think anyone would mind re-writing Dockerfile to Bastillefile o
just add
> > virt_console0="Yes" to the configuration file).
> >
> > Based on the logs, these device settings are used by it:
> > bhyve devices:
> >-s 0,hostbridge \
> >-s 31,lpc \
> >-s 4:0,virtio-blk,/dev/zvol/zroot/vms/freebsd14-test/disk0 \
> >-s 5:0,virtio-net,tap0,mac=58:9c:fc:aa:aa:aa \
> >-s 6:0,virtio-console,0=/vms/freebsd14-test/vtcon.0
> >
> > I could connect to /vms/freebsd14-test/vtcon.0 using socat:
> > socat - UNIX-CONNECT:/vms/freebsd14-test/vtcon.0
> >
> > Inside the vm it's /dev/vtcon/0.
> >
> > -m
--
Paul Vixie
Miroslav Lachman wrote on 2021-12-01 08:52:
On 01/12/2021 17:17, John Doherty via freebsd-virtualization wrote:
...
I am sorry for hijacking this thread but your information is very
interesting. I was playing with VMs in VirtualBox and Bhyve and compared
performance with increasing vCPU c
