From: Tobias Geerinckx-Rice <me@tobias.gr>
To: help-guix@gnu.org
Subject: Re: Qemu image broken?
Date: Wed, 22 Jan 2020 18:18:24 +0100 [thread overview]
Message-ID: <87r1zrflzz.fsf@nckx> (raw)
In-Reply-To: <CAFkJGRduEPPDhDx-YrBrpfMj4FzZdEXAEU33r1k2UDSH0MaGRA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Josh,
Josh Marshall 写道：
> Starting up the Qemu image off the website immediately results
> in a kernel
> panic and can't run. This should be fixed quickly.
I agree that any bugs should be promptly fixed. However, I'm not
yet convinced there's anything wrong with the image. We'll need
more information to help you.
The Qemu image on <https://guix.gnu.org/download/> hasn't been
touched since May 2019 and still works for me today:
λ curl -LI
https://ftp.gnu.org/gnu/guix/guix-system-vm-image-1.0.1.x86_64-linux.xz
λ unxz guix-system-vm-image-1.0.1.x86_64-linux.xz
λ qemu-system-x86_64 \
-net user -net nic,model=virtio \
-enable-kvm -m 512 \
-device virtio-blk,drive=myhd \
-drive
if=none,file=$PWD/guix-system-vm-image-1.0.1.x86_64-linux.xz,id=myhd
# …and be greeted by a happy XFCE mouse.
How, exactly, are you trying to run it, and which error(s) do you
get?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-01-22 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 16:14 Qemu image is broken Josh Marshall
2020-01-22 17:18 ` Tobias Geerinckx-Rice [this message]
2020-01-22 17:22 ` Qemu image broken? Tobias Geerinckx-Rice
2020-01-22 17:41 ` Josh Marshall
2020-01-22 17:53 ` Tobias Geerinckx-Rice
2020-01-22 19:13 ` Leo Famulari
2020-02-07 20:43 ` Josh Marshall
2020-02-07 20:52 ` [EXTERNAL]Re: " Josh Marshall
2020-02-07 23:16 ` Leo Famulari
2020-02-08 16:44 ` Tobias Geerinckx-Rice
2020-02-08 18:56 ` Leo Famulari
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=87r1zrflzz.fsf@nckx \
--to=me@tobias.gr \
--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).