Hi bugs@ A bit of a weird one.
This used to not be an issue, for some reason. I suspect it might have
something to do with either the file descriptor or mp changes to vmd.
Here's my vm.conf:
~ $ cat /etc/vm.conf
switch "uplink" {
interface veb0
}
vm "debian" {
disable
memory 4G
disk "/home/izder456/VMs/Debian.qcow2"
interface { switch "uplink" }
owner izder456
}
vm "openbsd" {
# disable
cpus 2
memory 4G
disk "/home/izder456/VMs/OpenBSD.qcow2"
interface { switch "uplink" }
owner izder456
}
vm "alpine" {
# disable
cpus 2
memory 1G
disk "/home/izder456/VMs/Alpine.qcow2"
interface { switch "uplink" }
owner izder456
}
vm "chimera" {
# disable
memory 1G
disk "/home/izder456/VMs/Chimera.qcow2"
interface { switch "uplink" }
owner izder456
}
vm "arch" {
# disable
memory 1G
disk "/home/izder456/VMs/Arch.qcow2"
interface { switch "uplink" }
owner izder456
}
This is my hostname.veb0 and hostname.vport0:
~ $ cat /etc/hostname.veb0
add vport0
up
~ $ cat /etc/hostname.vport0
inet 172.16.100.1 255.255.255.0
up
I do static networking via NAT for all my VMs.
I typically keep my debian 13 guest disabled until I need to test
something with it. Recently, unsure when it started, vmctl has
come up with this error when I attempt to start the VM:
~ $ vmctl start -c debian
vmctl: start vm command failed: No such file or directory
I hand-verified the specified file, the qcow2 disk image does indeed
exist, so it doesn't seem to be an issue with my configuration.
This is my vmctl status:
~ $ vmctl status
ID PID VCPUS MAXMEM CURMEM TTY OWNER STATE NAME
2 56695 2 4.0G 2.1G ttyp0 izder456 running openbsd
3 13982 2 1.0G 471M ttyp1 izder456 running alpine
4 18941 1 1.0G 1.0G ttyp2 izder456 running chimera
5 33188 1 1.0G 576M ttyp3 izder456 running arch
1 - 1 4.0G - - izder456 stopped debian
It doesn't seem to be an issue with the debian vm itself. I tried
adding an i386 7.9-stable OpenBSD guest later on, and I was met with
the same error.
Is this expected behavior? It seems weird to me that I cannot run more
than 4 guests at a time, when previously I could.
When I enable verbose logging, this is what I get:
~ $ doas vmctl log verbose
~ $ vmctl start -c debian
vmctl: start vm command failed: No such file or directory
~ $ tail -10 /var/log/messages
Oct 12 13:00:01 Tower-OpenBaSeD syslogd[82512]: restart
Oct 12 14:53:14 Tower-OpenBaSeD root: Xmessage said: 143
Oct 12 14:53:14 Tower-OpenBaSeD root: XMessage said: WAITING
Oct 12 14:59:18 Tower-OpenBaSeD vmd[38243]: config_setvm: can't open
/dev/tap4 Oct 12 14:59:18 Tower-OpenBaSeD vmd[38243]: failed to start
vm debian Oct 12 15:09:13 Tower-OpenBaSeD vmd[38243]: config_setvm:
can't open /dev/tap4 Oct 12 15:09:13 Tower-OpenBaSeD vmd[38243]: failed
to start vm debian Oct 12 15:09:25 Tower-OpenBaSeD vmd[60481]: denied
request 3 from uid 1000 Oct 12 15:09:32 Tower-OpenBaSeD vmd[38243]:
config_setvm: can't open /dev/tap4 Oct 12 15:09:32 Tower-OpenBaSeD
vmd[38243]: failed to start vm debian
This is weird as I only see 4 existing tap(4) devices in /dev:
~ $ ls /dev/tap*
/dev/tap0 /dev/tap1 /dev/tap2 /dev/tap3
Do I need to MAKEDEV more tap(4) devices to fix this? I'm too worried
I'll break something if I try
I also have this set in sysctl.conf:
~ $ cat /etc/sysctl.conf
hw.blockcpu=L
net.inet.ip.forwarding=1
kern.audio.record=1
kern.video.record=1
My dmesg(8) is attached.
This happens on the latest 8.0-current snapshot.
--
iz (she/her)
> I say mundane things
> so the uninteresting
> just might get noticed.
izder456 (dot) neocities (dot) org
dmesg
Description: Binary data
