From: Alex Williamson <alex.williamson@redhat.com>
To: "Sébastien BRICE" <seb@so-sweet.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] eepro100 and qemu0.14: unknown word write
Date: Mon, 21 Mar 2011 15:48:17 -0600 [thread overview]
Message-ID: <AANLkTimc0whB+5MnnOA2kM7=FOk-PkVB4gGkgx0VgsCT@mail.gmail.com> (raw)
In-Reply-To: <AANLkTin1pX=80WYHSx-MGMU9w8KSjt_UiG-bg0c5Vp-d@mail.gmail.com>
2011/3/21 Sébastien BRICE <seb@so-sweet.org>:
> Hi everyone
>
> I have been using qemu-kvm with success the last two years and its really
> amazing.
> I am new to this mailing list and i am requesting your assistance because i
> struggle to have my virtual card working with an 'exotic' virtual System
>
> seb@debian:~/qemu-kvm-0.14.0$ kvm -net nic,model=i82557b /media/prologue.img
>
>
> Whatever i try the guest system never initializes the Intel 100 Pro NIC Card
> as it is supposed to do
>
> And thats almost working with eep100.c source and -net nic,model=i82557b
> option
> But each time the qemu hangs with:
>
> eepro100: feature is missing in this emulation: unknown word write
...
> default:
> logout("addr=%s val=0x%04x\n", regname(addr), val);
> missing("unknown word write");
> }
> }
Can you set DEBUG_EEPRO100 in the source file, rebuild and let us know
what extra debug output you get? Just change the #if 0 around the
define near the top of the file to #if 1.
Alex
prev parent reply other threads:[~2011-03-21 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 19:56 [Qemu-devel] eepro100 and qemu0.14: unknown word write Sébastien BRICE
2011-03-21 21:48 ` Alex Williamson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimc0whB+5MnnOA2kM7=FOk-PkVB4gGkgx0VgsCT@mail.gmail.com' \
--to=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seb@so-sweet.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).