On Thu, Oct 12, 2017 at 09:16:39AM +0200, Roar Waagsbø wrote: > Hi. > > I've enabled the AHCI in bios now. > > I started the vm now, and downloaded the newest -current and that worked. > > But when I do -c -b to boot I get into console and after a while it just > stops. > > I get into console, press U for upgrade and then it hangs here: > > Welcome to the OpenBSD/amd64 6.2 installation program. > (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? u > At any prompt except password prompts you can escape to a shell by > typing '!'. Default answers are shown in []'s and are selected by > pressing RETURN. You > > And the VM is shut down. >
No, the console is stuck. > I ran vmd with -dvvv now and when it crashes I get this error: > > vmd: vm 4 event thread exited unexpectedly > vmm_sighdlr: handling signal 20 > vmm_sighdlr: attempting to terminate vm 1 > terminate_vm: terminating vmid 4 > proc_compose_imsg: about to compose_event to proc 0 > vmm_sighdlr: calling vm_remove > vm_remove: removing vm id 1 from running config > vm_remove: calling vm_stop > vm_stop: stopping vm 1 > vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 1 > > Entirely expected because vmd was still running, and you ran it again. It cleaned up your VM that you ran manually. You could have saved yourself a lot of time had you just scanned the lists. The stuck console is a known issue. There is no need to run VMs with -b anymore, either. Why are you doing it this way? -ml > > > > > > > 2017-10-11 18:48 GMT+02:00 Mike Larkin <[email protected]>: > > > On Wed, Oct 11, 2017 at 10:27:04AM +0200, Roar Waagsbø wrote: > > > Hi. > > > > > > Architecture is: amd64 > > > > > > dmesg: > > > http://dpaste.com/0MEFBGT > > > > > > My scripts for starting my vms: > > > 1st vm: http://dpaste.com/0CN3JTD > > > 2nd vm: http://dpaste.com/3XXNCE7 > > > > > > Vm.conf: http://dpaste.com/2QZA4FG > > > > > > Hostname.bridge0: http://dpaste.com/07FJP0X > > > > > > I run openbsd as guest vms on both > > > > > > I have 2 vms. > > > > > > I started vmd with -dvvv now and it gave me this error a little while > > after > > > starting my vm: > > > vmd_dispatch_vmm: handling TERMINATE_EVENT for vm id 1 > > > > > > > > > > if you start the vm with the -c option for vmctl, what's displayed on the > > console > > as the vm terminates? > > > > I'm guessing you forgot to set tty com0 in boot.conf and it just reboots > > immediately. > > > > -ml > > > > > I hope this is enough info. > > > > > > And sorry for my terrible first post. > > > > > > Will try to get better at it > > > > > > 2017-10-10 21:11 GMT+02:00 Carlos Cardenas <[email protected]>: > > > > > > > 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" <[email protected]> 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 > > > > > >
