From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Thomas Ieong <th.ieong@free.fr>
Cc: help-guix@gnu.org
Subject: Re: Qemu not creating virtual ports
Date: Wed, 25 Jan 2023 15:57:12 +0100 [thread overview]
Message-ID: <87v8kufyjs.fsf@nckx> (raw)
In-Reply-To: <87zga6dfan.fsf@free.fr>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
Hi Thomas,
Thomas Ieong 写道：
> I checked that all the kernel modules related to virtio are
> loaded.
>
> Apparently it's something specific to my configuration as I
> talked
> to another guixer and it was working perfectly for him with the
> latest
> guix and kernel.
It's not clear to me what refers to the guest and/or host. Is the
host a Guix System? Something else?
If it is a Guix System, could you provide your system.scm and the
output of ‘guix describe’?
If it's not, could you install Guix on the host (using
http://guix-install.sh) if you haven't yet, then try using its
qemu package rather than your distro's?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2023-01-25 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 11:28 Qemu not creating virtual ports Thomas Ieong
2023-01-25 14:57 ` Tobias Geerinckx-Rice [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=87v8kufyjs.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=th.ieong@free.fr \
/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).