From: Josh Marshall <Josh.Marshall@jax.org>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>,
Leo Famulari <leo@famulari.name>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: [EXTERNAL]Re: Qemu image broken?
Date: Fri, 7 Feb 2020 20:52:43 +0000 [thread overview]
Message-ID: <BL0PR06MB46738EC826B412737A78FFB9E91C0@BL0PR06MB4673.namprd06.prod.outlook.com> (raw)
In-Reply-To: <CAFkJGRfFhkP5yrTdRFGRLHGS2=P7VRifcXu1oS-CVL_tPdaKrw@mail.gmail.com>
Omitting the model gets it to boot. However, Xorg fails and logind fails. I can't log into the system.
________________________________________
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Sent: Friday, February 7, 2020 3:43 PM
To: Leo Famulari
Cc: Tobias Geerinckx-Rice; help-guix; Josh Marshall
Subject: [EXTERNAL]Re: Qemu image broken?
Finally getting back to this. Instructions don't work either. The `-nic` param is unsupported, and the `virtio-net-pci` is an unsupported nic model.
CC'ing my work email where I'm seeing this. Host OS is CentOS 7.7.
On Wed, Jan 22, 2020, 14:13 Leo Famulari <leo@famulari.name<mailto:leo@famulari.name>> wrote:
On Wed, Jan 22, 2020 at 12:41:18PM -0500, Josh Marshall wrote:
> `qemu-system-x86_64 <image path>`. Just the naive default starting point.
At the very least you will need to allocate some more RAM, for example
with '-m 4096'; that will provide 4 GB RAM to the virtual machine. The
default of 128 megabytes is not enough.
But I agree with the other responders, you should copy the instructions
in our manual unless you need to do something specific.
I hope that helps!
---
The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.
next prev parent reply other threads:[~2020-02-07 20:52 UTC|newest]
Thread overview: 12+ 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 ` Qemu image broken? Tobias Geerinckx-Rice
2020-01-22 17:22 ` 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 ` Josh Marshall [this message]
2020-02-07 23:16 ` Leo Famulari
2020-02-08 16:44 ` Tobias Geerinckx-Rice
2020-02-08 18:56 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2020-02-13 16:50 [EXTERNAL]Re: " Josh Marshall
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=BL0PR06MB46738EC826B412737A78FFB9E91C0@BL0PR06MB4673.namprd06.prod.outlook.com \
--to=josh.marshall@jax.org \
--cc=help-guix@gnu.org \
--cc=joshua.r.marshall.1991@gmail.com \
--cc=leo@famulari.name \
/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).