From: "Gábor Boskovits" <boskovits@gmail.com>
To: swedebugia@riseup.net
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Qemu image asking for password
Date: Fri, 2 Nov 2018 09:28:05 +0100 [thread overview]
Message-ID: <CAE4v=ph=cGX4Z4kozxG0HGZprXwLq2W_48uS6oi9ToaXUge9vg@mail.gmail.com> (raw)
In-Reply-To: <8bceb901-4368-dced-b7a4-47c237f95063@riseup.net>
Hello,
swedebugia <swedebugia@riseup.net> ezt írta (időpont: 2018. nov. 2., P, 8:54):
>
> Hi
>
> I recently tried firing up https://alpha.gnu.org/gnu/guix/guixsd-vm-image-0.15.0.x86_64-linux.xz with qemu.
>
> It booted up alright and took me to a login prompt.
>
> I tried gnu/gnu guix/guix but it did not work.
>
> I lookend for instructions here:
>
> https://www.gnu.org/software/guix/manual/html_node/Running-GuixSD-in-a-VM.html
>
> But they were not really what I needed as they did not answer my to questions:
>
> how to log in?
as far as I remember it comes with root as username and an empty password.
> can I use the image as a basis for contributing to guix? That is:
>
> is it readonly?
No, it is not, unless you make it so.
> if yes how do I connect a .dmg or similar virtual harddisk (example qemu commands or link to something helpful)?
I would recommend using a qcow2 image, you can create one using
qemu-img, and then specify it on the qemu
command line just like you specify the vm image (one option is to use
the deprecated hdb, hdc ... options or
if you already specify it using the new style, then just add the hd to
a new location)
> ho much space is needed on this .dmg to download the guix-source and compile?
I don't know. But I don't think you need too much. But you most
probably have to resize
the downloaded vm image, or do some magic regarding /tmp and /gnu/store.
>
> Cheers
>
> Swedebugia
Best regards,
g_bor
prev parent reply other threads:[~2018-11-02 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 7:59 Qemu image asking for password swedebugia
2018-11-02 8:28 ` Gábor Boskovits [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='CAE4v=ph=cGX4Z4kozxG0HGZprXwLq2W_48uS6oi9ToaXUge9vg@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=help-guix@gnu.org \
--cc=swedebugia@riseup.net \
/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).