Date: Sat, 26 Oct 2024 19:58:00 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 280959] New FreeBSD EC2 Machines Don't Boot Message-ID: <bug-280959-27103-wdTd4QFtEB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-280959-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-280959-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280959 --- Comment #3 from Colin Percival <cperciva@FreeBSD.org> --- Yeah, the problem here is that bspatch takes a lot of memory when patching a large file -- in particular a 100 MB kernel.debug. Even if you get the system booting, you could run into problems if you freebsd-update later. I'm not sure what the best solution is here. Maybe I should tell EC2 instances not to update debug files in freebsd-update? -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-280959-27103-wdTd4QFtEB>