From: Mark <lists+xen@internecto.net>
To: xen-devel@lists.xen.org
Subject: bug report for network device i82599er: eepro100_write4: Assertion `!"feature is missing in this emulation: " "unknown longword write"' failed.
Date: Sat, 12 May 2012 04:28:31 +0200 [thread overview]
Message-ID: <20120512042831.6460b834@internecto.net> (raw)
When trying to start a FreeBSD 9.0 HVM guest I see the following line
in qemu-dm-freebsd.log:
qemu-dm: /src/xen-stable-hg/src/xen-4.1-testing.hg-build/tools/ioemu-dir/hw/eepro100.c:1320: eepro100_write4: Assertion `!"feature is missing in this emulation: " "unknown longword write"' failed.
The domain crashes.
I suspect this occurs because I am trying to build the domain with a
vif where model=i82559er. Changing the model to e1000 does build
the domain.
I would prefer to have the ability to use 10Gbps because my physical
nic is also a 10Gbps nic:
02:00.0 Ethernet controller: Intel Corporation 82599EB 10-Gigabit SFI/SFP+ Network Connection (rev 01)
For further contact please be aware I am not receiving xen-devel
emails, so please include me in CC's when more info is required.
Thank you,
Mark
reply other threads:[~2012-05-12 2:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120512042831.6460b834@internecto.net \
--to=lists+xen@internecto.net \
--cc=xen-devel@lists.xen.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 NNTP newsgroup(s).