"Kirill A. Korinsky" <kir...@korins.ky> writes:
> [[PGP Signed Part:Undecided]] >> On 2. Jan 2024, at 18:41, Dave Voutila <d...@sisu.io> wrote: >> "Kirill A. Korinsky" <kir...@korins.ky> writes: > >>> vmctl -v start... doesn't help a bit >> >> How much physicaly memory does the host machine have? We currently don't >> allow oversubscribing memory with vmm/vmd. If the host only has 16GB >> that could be the cause. > > hw.physmem=137257779200 > hw.usermem=133537726464 > > and machine is used only for run VMs. > >> If that's not the case, can you run vmd in debug mode and get the log >> output? > > Sure, I run /usr/sbin/vmd -vvvvvvv -d and the error is: > > vmd: config_setvm: vm 3 restarted after 9.757221 seconds, limit 0/3 > vmd: config_setvm: can't open tap tap Ah, that. > vmd: failed to start vm podman > vmd: vm_stop: vmd config_setvm stopping vm 3 > > This machine runs 4 more VM and this one (huge) should be 5th. Try this: # cd /dev && sh MAKEDEV tap4 By default I believe on amd64 we create tap[0-3]. You might need to define additional special files to represent 4+ taps. -dv