All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: yvugenfi@redhat.com, Jason Wang <jasowang@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] Headsup: windows virtio networking does not work on current git
Date: Sun, 03 Feb 2013 07:08:28 +1100	[thread overview]
Message-ID: <1359835708.1968.3.camel@localhost> (raw)
In-Reply-To: <510D09C2.6050905@redhat.com>

On Sat, 2013-02-02 at 20:42 +0800, Jason Wang wrote:
> On 02/02/2013 05:13 AM, Anthony Liguori wrote:
> > Michael Tokarev <mjt@tls.msk.ru> writes:
> >
> >> 02.02.2013 00:36, Anthony Liguori wrote:
> >>> Michael Tokarev <mjt@tls.msk.ru> writes:
> >>>
> >>>> 02.02.2013 00:18, Michael Tokarev wrote:
> >>>>> Just a heads-up for now, no real diagnostics or anything like that.
> >>>>>
> >>>>> Current git master (a9c87c586ba9ee290792a98dc126b2861b7f8b03), when booted
> >>>>> a windows guest, results in no virtio-net inside.  Neither winXP nor Win7,
> >>>>> neither older nor latest (22 Jan 2013) virtio-net drivers works.
> >>>>>
> >>>>> Windows displays a yellow exclamation mark near the virtio-net device and
> >>>>> says it can't start the device (Code 10).
> >>>>>
> >>>>> Linux guests work fine, quick test anyway.
> >>>>>
> >>>>> Cc'ing Jason since his virtio-net changes was last.  But I repeat: no
> >>>>> diagnostics as of yet, no bisection.
> >>>> Bisection was easy, since win works fine right before the multiqueue
> >>>> virtio-net series.  This is the first bad commit:
> >>> Adding Vadim and Michael.
> >>>
> >>> If you use -M pc-1.3 or explicitly disable multiqueue, does the driver work?
> >> Neither one of these nor both makes any visible difference.
> >> Neither does -M pc-1.1 (just in case).
> > Hrm, then it's very likely not a driver problem.  Thanks.
> >
> > Regards,
> >
> > Anthony Liguori
> 
> Have a look at this issue. It was caused by multiqueue patch who adds a
> new field to virtio_net_cfg. Not sure multiqueue is the root cause since
> I also find even w/o multiqueue, adding any new field to virtio_net_cfg
> will break windows guest. Haven't had a clue on this, will continue
> investigate.

cc'ing Yan, our NDIS guy.
Thank you,
Vadim.
> >
> >>> Regards,
> >>>
> >>> Anthony Liguori
> >>>
> >>>> commit fed699f9ca6ae8a0fb62803334cf46fa64d1eb91
> >>>> Author: Jason Wang <jasowang@redhat.com>
> >>>> Date:   Wed Jan 30 19:12:39 2013 +0800
> >>>>
> >>>>       virtio-net: multiqueue support
> >>>>
> >>>>       This patch implements both userspace and vhost support for multiple queue
> >>>>       virtio-net (VIRTIO_NET_F_MQ). This is done by introducing an array of
> >>>>       VirtIONetQueue to VirtIONet.
> >>>>
> >>>>       Signed-off-by: Jason Wang <jasowang@redhat.com>
> >>>>       Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
> >>>>
> >>>> After this commit, win guest (winXP and win7) shows yellow
> >>>> exclamation sign and is unable to start the device with
> >>>> code 10.
> >>>>
> >>>> FWIW.  I'm not sure it is a good idea to make a release with
> >>>> such a breakage, even rc0.
> >>>>
> >>>> Thanks,
> >>>>
> >>>> /mjt
> >
> 

  reply	other threads:[~2013-02-02 20:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01 20:18 [Qemu-devel] Headsup: windows virtio networking does not work on current git Michael Tokarev
2013-02-01 20:30 ` Michael Tokarev
2013-02-01 20:36   ` Anthony Liguori
2013-02-01 20:42     ` Michael Tokarev
2013-02-01 21:13       ` Anthony Liguori
2013-02-02 12:42         ` Jason Wang
2013-02-02 20:08           ` Vadim Rozenfeld [this message]
2013-02-02 23:07             ` Anthony Liguori
2013-02-03 13:23               ` Yan Vugenfirer
2013-02-03 16:09                 ` Michael Tokarev
2013-02-03 21:09                   ` Anthony Liguori
     [not found] <1359981484.1968.29.camel@localhost>
     [not found] ` <87fw1ckupa.fsf@codemonkey.ws>
     [not found]   ` <1360063865.1968.85.camel@localhost>
     [not found]     ` <5110F0E2.1030705@msgid.tls.msk.ru>
     [not found]       ` <20130205115816.GD6420@redhat.com>
     [not found]         ` <1360144040.1968.119.camel@localhost>
     [not found]           ` <877gmlj5pz.fsf@rustcorp.com.au>
     [not found]             ` <1360229050.1968.149.camel@localhost>
     [not found]               ` <20130207101813.GA3837@redhat.com>
     [not found]                 ` <1360234419.1968.162.camel@localhost>
2013-02-07 11:33                   ` Michael S. Tsirkin
2013-02-07 11:46                     ` Vadim Rozenfeld
2013-02-07 13:02                       ` Yan Vugenfirer
2013-02-07 13:10                         ` Michael S. Tsirkin

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=1359835708.1968.3.camel@localhost \
    --to=vrozenfe@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=jasowang@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yvugenfi@redhat.com \
    /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.