Here is the boot log after a crash (says there are no core dumps found... any
way to figure out why it is not dumping the core?):
-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/[H[J-\|/-\
Hm, the runtime going backwards is a bit odd, maybe they fixed that in
-HEAD recently. Other than that, yeah, you'll need a crash dump or at
least some screenshot when it does reboot.
-a
___
freebsd-stable@freebsd.org mailing list
After setting crash dump settings correctly I'm still not seeing a dump in
/var/crash/ - will try to get screenshot my of the boot screen after the crash
and get back to you.
Scott
On Feb 7, 2016, at 12:08 AM, Adrian Chadd wrote:
Hm, the runtime going backwards is a
hiya,
how much RAM does the VM have?
Yes, you need to either run dumpon or reboot once you update /etc/rc.conf .
-a
On 5 February 2016 at 13:55, Scott Otis wrote:
> Been trying to get a FreeBSD VM server running on Azure on a "Standard DS"
> size VM (so I have
Adrian,
3.5 GB of RAM.
Here is the list from dmseg if that helps:
Copyright (c) 1992-2015 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of