All of lore.kernel.org
 help / color / mirror / Atom feed
From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2405061 ] kvm-80: virtio networking broken
Date: Tue, 16 Dec 2008 01:25:23 +0000	[thread overview]
Message-ID: <E1LCOgd-0007b5-SO@cdv4jf1.ch3.sourceforge.com> (raw)

Bugs item #2405061, was opened at 2008-12-08 11:07
Message generated for change (Comment added) made by danv
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2405061&group_id=180599

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: libkvm
Group: None
>Status: Closed
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Daniel van Vugt (danv)
Assigned to: Nobody/Anonymous (nobody)
Summary: kvm-80: virtio networking broken

Initial Comment:
Using the Qumranet Paravirtualized Ethernet Adapter, my guest doesn't get any DHCP responses (or in fact any packets received at all) after upgrading to kvm-80. kvm-79 continues to work fine.


Host CPU: Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz
Host dist: Ubuntu 8.04 amd64
Guest: WinXP x86 32-bit

----------------------------------------------------------------------

>Comment By: Daniel van Vugt (danv)
Date: 2008-12-16 10:25

Message:
Sorry I didn't have time to test the patch, but CONFIRM kvm-81 is fixed.
Closed.

----------------------------------------------------------------------

Comment By: Mishehu Mashehu (mishehu)
Date: 2008-12-10 02:01

Message:
Sorry, forgot to mention that my trial on Athlon64 Slamd64 12.1 kernel
2.6.27.7 kvm-80+this patch running a winXP guest.

----------------------------------------------------------------------

Comment By: Mishehu Mashehu (mishehu)
Date: 2008-12-10 00:43

Message:
Confirmed working on Athlon64 Socket AM2 Slamd64 12.1 kvm-80 + patch.  Will
be testing it on an Intel machine soon.


----------------------------------------------------------------------

Comment By: Mark McLoughlin (markmc)
Date: 2008-12-09 01:53

Message:
Thanks, fixed is in git and will be in kvm-81

----------------------------------------------------------------------

Comment By: infernix (infernix)
Date: 2008-12-09 01:18

Message:
Patch seems to work for me. Briefly tested on Debian Sid, 2.6.27.8, kvm-80.

----------------------------------------------------------------------

Comment By: Mark McLoughlin (markmc)
Date: 2008-12-08 22:51

Message:
This is probably fixed in git by:

 
http://git.kernel.org/?p=linux/kernel/git/avi/kvm-userspace.git;a=commitdiff;h=67cd35299

danv: could you try the patch out and confirm it fixes it for you?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2405061&group_id=180599

             reply	other threads:[~2008-12-16  1:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-16  1:25 SourceForge.net [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-09 17:01 [ kvm-Bugs-2405061 ] kvm-80: virtio networking broken SourceForge.net
2008-12-09 15:43 SourceForge.net
2008-12-08 16:53 SourceForge.net
2008-12-08 16:18 SourceForge.net
2008-12-08 13:51 SourceForge.net
2008-12-08  2:07 SourceForge.net

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=E1LCOgd-0007b5-SO@cdv4jf1.ch3.sourceforge.com \
    --to=noreply@sourceforge.net \
    /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.