From: Thomas Huth <1917161@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1917161] Re: Parameter 'type' expects a netdev backend type
Date: Mon, 01 Mar 2021 06:29:16 -0000 [thread overview]
Message-ID: <161458015701.24619.13829281628104078291.malone@gac.canonical.com> (raw)
In-Reply-To: 161444687583.24678.13238506356231835061.malonedeb@wampee.canonical.com
What output do you get when you run:
qemu-system-i386 -netdev help
It's likely that your binary has been compiled without "user" networking
(aka. "slirp") support. If so, please use a binary that has "slirp"
enabled instead.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1917161
Title:
Parameter 'type' expects a netdev backend type
Status in QEMU:
Incomplete
Bug description:
When using QEMU on an M1 Mac with Mac OS 11.1, I see this error
message when trying to enable networking for a guest:
Parameter 'type' expects a netdev backend type
Example command:
qemu-system-i386 -m 700 -hda <Windows XP HD file> -netdev user,id=n0 -device rtl8139,netdev=n0
What should happen is networking should work when issuing the above
command. What actually happens is QEMU exits immediately.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1917161/+subscriptions
next prev parent reply other threads:[~2021-03-01 6:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 17:27 [Bug 1917161] [NEW] Parameter 'type' expects a netdev backend type John Arbuckle
2021-03-01 6:29 ` Thomas Huth [this message]
2021-03-01 13:00 ` [Bug 1917161] " John Arbuckle
2021-03-02 6:37 ` Thomas Huth
2021-03-02 13:13 ` [Bug 1917161] " John Arbuckle
2021-03-15 12:47 ` [Bug 1917161] " John Arbuckle
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=161458015701.24619.13829281628104078291.malone@gac.canonical.com \
--to=1917161@bugs.launchpad.net \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.