Hi George, did you solved the issue? I remember that I faces similar thing when I installed headless ubuntu as a guest … My issue was related to the fact that I used ‚boot cdrom‘ directive inside my configuration (seems that there is a bit inconsistency between the man page and the real configuration).
This is is a relevant piece of my config: vm "ubuntu" { memory 2G cdrom /data/vms/_iso/mini-serial.iso disk /data/vms/ubuntu.raw interface tap { switch "uplink" } disable } I had bad experience with usage of qcow2 disk format for Linux based guests — especially when you’re trying to do dozens of I/O operations — several disk containers crashed before I migrated them to raw format. if you have more than 4 vms, don’t forget to create another /dev/tap<X> device, otherwise you could expect the unexpectable behaviour :) M> > >> Hi guys, >> >> I apologize if this maybe out of topic even though it is truly related >> to VMM than Debian. >> >> I am trying to setup a VMM Debian based guest but I'm not able to get it >> to work. I found some description on the web about which settings to >> edit in grub.cfg to enable the serial console and created a VM with 10.3 >> in qcow2 disk format in KVM. Now I am trying to start the same on >> OpenBSD 6.7 but keep getting the connected message and then just >> "Rebooting " after I hit some keyboard keys seems like baud rate issue >> but not sure. >> >> After messing with it for a while now I am getting a new error: >> >> vmctl: could not open disk image(s) >> >> even thought the disk is there and readable to the user I have setup in >> vm.conf in fact I have another VM with the same configuration and disk >> with the same permissions and in the same location that works (it is >> OpenBSD based). >> >> I would greatly appreciate it if someone has gone this path and can >> share some config info with me. >> >> Cheers and thanks in advance, >> >> George > >