> On 24 Sep 2020, at 09:15, Florian Obser <[email protected]> wrote:
>
> Hi Mischa,
>
> On Thu, Sep 24, 2020 at 08:52:55AM +0200, Mischa wrote:
>> Hi All,
>>
>> With the last couple of -current updates I noticed a VM doesn’t come back
>> after running sysupgrade, which it used to do.
>
> it's very unlikely that this is a sysupgrade problem.
> More likely something in the kernel changed (vm or hypervisor).
>
>> I don’t know exactly when it started but something in the late #60s.
>
> This number doesn't mean anything. Please provide build dates.
>
>>
>> Running sysupgrade from within the VM, it reboots and goes through the
>> upgrade as normal. Once it’s done with the upgrade it shuts down.
>> Tail-end of the process from the latest sysupgrade.
>>
>> Set name(s)? (or 'abort' or 'done') [done] done
>> Directory does not contain SHA256.sig. Continue without verification? [no]
>> yes
>> Installing bsd 100% |**************************| 20383 KB 00:01
>>
>> Installing bsd.rd 100% |**************************| 10141 KB 00:00
>>
>> Installing base68.tgz 100% |**************************| 289 MB 01:42
>>
>> Installing comp68.tgz 100% |**************************| 74305 KB 00:52
>>
>> Installing man68.tgz 100% |**************************| 7484 KB 00:10
>>
>> Installing game68.tgz 100% |**************************| 2739 KB 00:01
>>
>> Installing xbase68.tgz 100% |**************************| 28866 KB 00:17
>>
>> Installing xshare68.tgz 100% |**************************| 4499 KB 00:15
>>
>> Installing xfont68.tgz 100% |**************************| 39342 KB 00:23
>>
>> Installing xserv68.tgz 100% |**************************| 18333 KB 00:07
>>
>> Location of sets? (disk http nfs or 'done') [done] done
>> Making all device nodes... done.
>> Relinking to create unique kernel... done.
>>
>> CONGRATULATIONS! Your OpenBSD upgrade has been successfully completed!
>>
>> syncing disks... done
>> vmmci0: powerdown
>
> ^^^^^^^^^
> Why does it think it should power down?
>
> I never ran vmm, so this is all a wild guess, but here is how I would
> approach this:
>
> 1) manually boot into bsd.rd, hit 's' to get to a shell prompt and
> type reboot, does it shutdown?
>> OpenBSD/amd64 BOOT 3.52
>>
boot> bsd.rd
booting hd0a:bsd.rd: 3818189+1573888+3878136+0+757760
[324353+128+468792+313530]=0xaa0780
entry point at 0xffffffff81001000
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2020 OpenBSD. All rights reserved. https://www.OpenBSD.org
OpenBSD 6.8-beta (RAMDISK_CD) #75: Wed Sep 23 15:43:49 MDT 2020
[email protected]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
[snip]
Welcome to the OpenBSD/amd64 6.8 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
# reboot
syncing disks... done
vmmci0: powerdown
rebooting…
[EOT]
> 2) if yes, get a 6.7 bsd.rd (which I presume is known good) and retry
>> OpenBSD/amd64 BOOT 3.47
boot> bsd.rd
booting hd0a:bsd.rd: 3826379+1557504+3881976+0+598016
[301104+128+465696+311208]=0xa71778
entry point at 0xffffffff81001000
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California. All rights reserved.
Copyright (c) 1995-2020 OpenBSD. All rights reserved. https://www.OpenBSD.org
OpenBSD 6.7 (RAMDISK_CD) #177: Thu May 7 11:19:02 MDT 2020
[email protected]:/usr/src/sys/arch/amd64/compile/RAMDISK_CD
[snip]
Welcome to the OpenBSD/amd64 6.7 installation program.
(I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s
# reboot
syncing disks... done
vmmci0: powerdown
rebooting...
Using drive 0, partition 3.
Loading......
probing: pc0 com0 mem[638K 1022M a20=on]
disk: hd0+
>> OpenBSD/amd64 BOOT 3.47
boot>
> 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
> here).
6.8 bsd.rd shuts down
6.7 bsd.rd reboots
Both VMs are running on the same host which is on 6.7.
# sysctl kern.version
kern.version=OpenBSD 6.7 (GENERIC.MP) #1: Sat May 16 16:33:02 MDT 2020
[email protected]:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> 3b) does it reboot: bisect bsd.rd
What do you mean?
Mischa
