From: ludo@gnu.org (Ludovic Courtès)
To: dian_cecht@zoho.com
Cc: 24943-done@debbugs.gnu.org
Subject: bug#24943: Error when starting a vm-image in qemu
Date: Sat, 19 Nov 2016 18:48:44 +0100 [thread overview]
Message-ID: <87oa1b2web.fsf@gnu.org> (raw)
In-Reply-To: <20161118220908.GA10079@khaalida> (dian cecht's message of "Fri, 18 Nov 2016 14:09:08 -0800")
dian_cecht@zoho.com skribis:
> I thought I had included that info, but yes that does work. Part of the reason
> for filing the bugreport was so that this case could be handled more elegantly
> instead of bugging out and dropping a user in the REPL. Unless one is a dev, the
> REPL might as well be a kernel panic, only without the (potentially) useful
> timeout.
>
> I'd personally prefer it if the image generated by vm-image could either
>
> A) Spit out an error that there isn't a networking device found and shutdown
> (not a fan, but if there is a reason vm-image /has/ to have a working network
> connection, this would likely be better. Including a chance to hit a key to drop
> a dev/advanced user into the REPL would be nice as well) or
> B) Spit out an error and finish the booting process, with guix complaining about
> no network connection any time it's needing to download something (easily the
> better option).
Yes, that makes sense.
On closer inspection, that feature (setting up QEMU guest networking
directly from the initrd) is something we need in only 1 situation,
which is ‘expression->derivation-in-linux-vm’, so commit
6129dd8b5989f77b2976c68ecdf1f7dbfa63ec46 removed that feature for images
produced by ‘guix system vm’ and ‘guix system vm-image’.
So now you should no longer have this problem when networking is
missing.
Thank you,
Ludo’.
prev parent reply other threads:[~2016-11-19 17:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 5:01 bug#24943: Error when starting a vm-image in qemu dian_cecht
2016-11-15 10:08 ` Ludovic Courtès
2016-11-18 22:09 ` dian_cecht
2016-11-19 17:48 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oa1b2web.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=24943-done@debbugs.gnu.org \
--cc=dian_cecht@zoho.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).