From: "SourceForge.net" <noreply@sourceforge.net>
To: noreply@sourceforge.net
Subject: [ kvm-Bugs-2405061 ] kvm-80: virtio networking broken
Date: Mon, 08 Dec 2008 02:07:07 +0000 [thread overview]
Message-ID: <E1L9VWd-0004gu-Sy@d45xhf1.ch3.sourceforge.com> (raw)
Bugs item #2405061, was opened at 2008-12-08 11:07
Message generated for change (Tracker Item Submitted) made by Item Submitter
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: Open
Resolution: None
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
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2405061&group_id=180599
next reply other threads:[~2008-12-08 2:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 2:07 SourceForge.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-08 13:51 [ kvm-Bugs-2405061 ] kvm-80: virtio networking broken SourceForge.net
2008-12-08 16:18 SourceForge.net
2008-12-08 16:53 SourceForge.net
2008-12-09 15:43 SourceForge.net
2008-12-09 17:01 SourceForge.net
2008-12-16 1:25 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=E1L9VWd-0004gu-Sy@d45xhf1.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.