Hi Mike,
I got curious again and tried starting a second vmd process when there is already a running vmd process. The new process causes the original process to stop responding. As expected, this makes a mess of the disk image files already loaded by the first vmd process. I also tried starting the second vmd process using a distinct vm.conf which used none of the disk image files from the original vmd process. This still causes the VMs running under the first vmd process to stop responding, even after the second vmd process is killed. The disk image files from the original process were also flagged for fsck at reboot of the VMs. Perhaps another sanity check for the to-do list... don't start vmd if it is already running? Yours truly, Breen ________________________________ From: Mike Larkin <mlar...@azathoth.net> Sent: February 3, 2018 4:49 PM To: openbsd2012 Cc: 'misc@openbsd.org' Subject: Re: "vmctl stop" causing disk image corruption with OpenBSD 6.2-stable VM ... > May I suggest a vmd sanity check to avoid a VM disk image being loaded by > more than one VM simultaneously? Providing a patch is outside my skill set, > unfortunately. > > > Yours truly, > > > Breen > Not a bad idea, I'll toss it on the to-do list. thanks.. -ml
