> 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.
Will try to find the one where it started.
>> 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?
Indeed.
> 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?
> 2) if yes, get a 6.7 bsd.rd (which I presume is known good) and retry
> 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
> here).
> 3b) does it reboot: bisect bsd.rd
>
> You can use https://ftp.hostserver.de/archive/
> <https://ftp.hostserver.de/archive/> for bisecting.
6.7 is fine, majority of the VMs are on 6.7-stable, issuing a reboot does an
actual reboot.
Will try with -current bsd.rd and see what happens.
Mischa
