On Tue, Oct 11, 2022 at 07:59:27PM -, Christos Zoulas wrote:
> In article ,
> Paul Ripke wrote:
> >Not sure if it's worth logging or not, but I just had 'vi -r' segv.
> >System is amd64, NetBSD 9.3_STABLE (SLAVE) #15: Sat Sep 17 23:12:17 AEST 2022
> >
> >Core was generated by `vi'.
>
Date:Wed, 12 Oct 2022 22:57:00 +1100
From:Paul Ripke
Message-ID:
| "vi -r", etc, and it seemed to work fine. The recovery file that causes the
| crash was left behind after a kernel panic.
The recovery file will be corrupted. I have seen that kind of thing
On Wed, Oct 12, 2022 at 01:23:17PM +0530, Mayuresh wrote:
> > I tried creating a machine (machine init, machine start). It seems to
> > download fedora coresos 36 and start the machine but get stucks at the
> > "Waiting for VM" prompt. "machine ssh" fails to connect to it.
>
>
On Wed, Oct 12, 2022 at 01:17:08PM +0530, Mayuresh wrote:
> On NetBSD 9.2 amd64 I have installed podman from pkgsrc.
>
> I see the following message:
>
> You will need to build a kernel with options HZ=1000, or edit the
> created VM to append "noapic" to the Grub command line.
>
> I
On NetBSD 9.2 amd64 I have installed podman from pkgsrc.
I see the following message:
You will need to build a kernel with options HZ=1000, or edit the
created VM to append "noapic" to the Grub command line.
I tried creating a machine (machine init, machine start). It seems to
download
