From: ludo@gnu.org (Ludovic Courtès)
To: Catonano <catonano@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: system vm
Date: Thu, 17 May 2018 16:39:54 +0200 [thread overview]
Message-ID: <87po1uxs5h.fsf@gnu.org> (raw)
In-Reply-To: <CAJ98PDzvTMJD5PFx74x8yO-YG+C57iNUgmF8kPzqwbQAd17aRA@mail.gmail.com> (catonano@gmail.com's message of "Thu, 17 May 2018 11:23:05 +0200")
Hello,
Catonano <catonano@gmail.com> skribis:
> ~/GNU/guix$ ./pre-inst-env guix system vm
> ~/configs/vm-config-desktop.scm --image-size=10GB
> --share=$HOME/transit=/transit
>
> These are the last lines I can see in the terminal
>
> ...
> [ 1.084823] 9p: Installing v9fs 9p2000 file system support
> [ 1.086036] FS-Cache: Netfs '9p' registered for caching
> configuring QEMU networking...
> [ 1.102362] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
> loading '/gnu/store/rgpivnrpwr9mxadaxh2yq5g54ffnjkp9-linux-vm-loader'...
> [ 1.137673] random: fast init done
> environment variable `PATH' set to
> `/gnu/store/qbqzhwbl90kpmvz1r31rwl940n1cs33s'
> creating partition table with 2 partitions (20.0 MiB, 40.0 MiB)...
> [ 1.568159] tsc: Refined TSC clocksource calibration: 2494.260 MHz
> [ 1.569060] clocksource: tsc: mask: 0xffffffffffffffff max_cycles:
> 0x23f40b6s
> [ 2.080097] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
>
>
> and it remains like this for several minutes
This is a bug caused by a recent Linux-libre upgrade:
https://bugs.gnu.org/31268
Ludo’.
next prev parent reply other threads:[~2018-05-17 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 9:23 system vm Catonano
2018-05-17 12:46 ` Tobias Geerinckx-Rice
2018-05-17 13:20 ` Catonano
2018-05-17 13:34 ` Tobias Geerinckx-Rice
2018-05-17 13:36 ` Catonano
2018-05-17 14:39 ` Ludovic Courtès [this message]
2018-05-17 17:38 ` Catonano
2018-05-17 15:10 ` Tobias Geerinckx-Rice
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=87po1uxs5h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=catonano@gmail.com \
--cc=help-guix@gnu.org \
/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.
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).