public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Alistair John Strachan
	<alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Vista/rtl8139 broken?
Date: Sun, 19 Aug 2007 00:47:04 +0100	[thread overview]
Message-ID: <20070818234704.GA26152@redhat.com> (raw)
In-Reply-To: <200708190031.14264.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>

On Sun, Aug 19, 2007 at 12:31:14AM +0100, Alistair John Strachan wrote:
> Hi,
> 
> I've been using ne2k with BSD/Linux/WindowsXP just fine with 
> KVM-35/2.6.23-rc2, but when I try to run Vista, which doesn't support the 
> ne2k any more, I tried switching to the rtl8139 emulation.
> 
> I observed that the rtl8139 emulation works fine in WindowsXP, so it's not 
> broken. But it does not seem to work in Vista (x86). The host is AMD64/SVM. 
> The way that it doesn't work is that no packets are sent/received over the 
> interface, so the device does not route.
> 
> The only difference between XP and Vista's KVM startup is that for Vista I 
> enable ACPI (necessary to install).
> 
> WindowsXP -->
> kvm -no-reboot -localtime -no-acpi -m 256 -hda $IMAGE \
>     -net nic,model=rtl8139 -net tap,script=/etc/kvm/kvm-ifup $*
> 
> Vista -->
> kvm -no-reboot -localtime -m 512 -hda $IMAGE \
>     -net nic,model=rtl8139 -net tap,script=/etc/kvm/kvm-ifup $*
> 
> The problem seems to be similar to a QEMU endian bug from some time ago, but I 
> don't think that's the problem here. It looks like it's some sort of 
> incompatibility between Vista and the rtl8139 emulation.

The rtl8139 driver was fixed in upstream QEMU a week or two back - it was
calculating checksums incorrectly which Vista didn't like.  The patch needs
to be applied to KVM too...

Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

      parent reply	other threads:[~2007-08-18 23:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18 23:31 Vista/rtl8139 broken? Alistair John Strachan
     [not found] ` <59abf66e0708181637k11dc0261hf632372641cbe3f2@mail.gmail.com>
     [not found]   ` <59abf66e0708181637k11dc0261hf632372641cbe3f2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-18 23:38     ` Jorge Lucángeli Obes
     [not found] ` <200708190031.14264.alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org>
2007-08-18 23:47   ` Daniel P. Berrange [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=20070818234704.GA26152@redhat.com \
    --to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=alistair-T7eSMZptz7IqdlJmJB21zg@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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