From f2ee1f5796353e4cd98f7ce0a1d3cdee36a5a552 Mon Sep 17 00:00:00 2001 From: david Date: Mon, 19 Aug 2019 02:16:24 +0000 Subject: Added a comment: grub failure --- .../comment_4_5a2b2748c7e9eadc3c85ad6037ebc39a._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/running_commands_in_Libvirt_guests/comment_4_5a2b2748c7e9eadc3c85ad6037ebc39a._comment (limited to 'doc') diff --git a/doc/forum/running_commands_in_Libvirt_guests/comment_4_5a2b2748c7e9eadc3c85ad6037ebc39a._comment b/doc/forum/running_commands_in_Libvirt_guests/comment_4_5a2b2748c7e9eadc3c85ad6037ebc39a._comment new file mode 100644 index 00000000..67c11f0a --- /dev/null +++ b/doc/forum/running_commands_in_Libvirt_guests/comment_4_5a2b2748c7e9eadc3c85ad6037ebc39a._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="david" + avatar="http://cdn.libravatar.org/avatar/22c2d800db6a7699139df604a67cb221" + subject="grub failure" + date="2019-08-19T02:16:24Z" + content=""" +I narrowed it down to the call to Grub.mkConfig, which basically calls \"update-grub\". If I just copy the ConfFile.containsShellSetting from Grub.configured, then things work fine, presumably because of some later call to update-grub (when the image is finalized?). I'm just guessing, but maybe something later sets up /boot so that update-grub can succeed. I noticed the the call to mkConfig in Grub.installed is guarded against being in a contained, so maybe Grub.configured needs something similar. +"""]] -- cgit v1.2.3