> On 24 Sep 2020, at 13:52, Sebastien Marie wrote:
>
> On Thu, Sep 24, 2020 at 12:47:30PM +0200, Mischa wrote:
>>>
>>> One quirk of the archive: It just creates a directory every night, no
>>> matter if a snap was built or not, you can check with what(1) if you
>>> actually have a different
On Thu, Sep 24, 2020 at 12:47:30PM +0200, Mischa wrote:
> >
> > One quirk of the archive: It just creates a directory every night, no
> > matter if a snap was built or not, you can check with what(1) if you
> > actually have a different kernel to the one you already tested.
>
> for i in $(jot -w
I can confirm what Theo is seeing. On my workstation with a test VM
running the latest snapshot I get:
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...
Using drive 0, partition
On Thu, Sep 24, 2020 at 09:15:20AM +0200, Florian Obser 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
> On 24 Sep 2020, at 12:23, Florian Obser wrote:
>
> On Thu, Sep 24, 2020 at 12:13:31PM +0200, Mischa wrote:
>>
>>
>>> On 24 Sep 2020, at 09:15, Florian Obser wrote:
>>> 3a) does it also shutdown: bisect the hypervisor (tbh I expect the problem
>>> here).
>>
>> 6.8 bsd.rd shuts down
>>
On Thu, Sep 24, 2020 at 12:13:31PM +0200, Mischa wrote:
>
>
> > On 24 Sep 2020, at 09:15, Florian Obser wrote:
> > 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
> On 24 Sep 2020, at 09:15, Florian Obser 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
> On 24 Sep 2020, at 09:15, Florian Obser 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
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
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.
I don’t know exactly when it started but something in the late #60s.
Running sysupgrade from within the VM, it reboots and goes through the upgrade
as normal. Once
10 matches
Mail list logo