On 10/10/17 11:57, Roar Waagsbø wrote:
> Hi.
> 
> Sorry.
> 
> Its my first report.
> 
> Im not even sure its a bug or if its me doing something wrong.
> 
> The logs arent saying much either, besides the one line I posted.
> 
> Roar
> 
> On Oct 10, 2017 5:21 PM, "Mike Larkin" <mlar...@azathoth.net> wrote:
> 
>> On Tue, Oct 10, 2017 at 02:39:05PM +0200, Roar Waagsbř wrote:
>>> Hi.
>>>
>>> I starting using openbsd a while back and I was told on #openbsd@freenode
>>> that vmm was the way to go, and not use qemu.
>>>
>>> I want to use openbsd on my host machine.
>>>
>>> I setup two vms and it worked fine.
>>>
>>> After about a week I noticed that one of my vms was shutdown.
>>>
>>> I started it back up again and didnt give it much thought.
>>>
>>> After a few days my other vm was shut down.
>>>
>>> Then after a few days again both my vms was shutdown.
>>>
>>> Today I upgraded the host to a new -current snapshot (10/10/2017)
>>>
>>> And when I start my vm now, it says that it starts successfully, then
>> after
>>> a few seconds it is shutdown again.
>>>
>>> I started vmd with -d (tried -dv but it said that -v wasnt an options,
>> even
>>> though man vmd say so)
>>>
>>> And the only thing /var/log/daemon says was:
>>>
>>> vmd2: vm2 even trhead exited unexpectedly.
>>>
>>> Am I missing something?
>>>
>>> Or am I doing anything wrong?
>>>
>>> Regards Roar
>>
>> Your bug report is horrible.
>>
>> man sendbug
>>
>> -ml
>>

Roar,

Let's start with this:
* You said you are running -current (2017-10-10), which architecture (amd64 or 
i386)? A dmesg would be good.
* What are your VM params (i.e. how did you start them)? Do you have a vm.conf 
file you can share?
* What guest VMs are you running?
* How many vmd's are you running? (asking because of the "vmd2: ...." line) 
There should be only one.

If you are going to run vmd in the foreground, make sure no other vmd instances 
are running.

I don't understand your comment about '-v' since not only is it present in the 
usage of vmd but also
in the man page (man vmd).

los@rollo:% doas vmd -h
vmd: unknown option -- h
usage: vmd [-dnv] [-D macro=value] [-f file]

Either way, run vmd in the foreground with '-dvvv' as in:
doas vmd -dvvv

Once you're able to share all of that info then we can start the process of 
troubleshooting.

+--+
Carlos

Reply via email to