From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Jintack Lim <jintack@cs.columbia.edu>,
QEMU Devel Mailing List <qemu-devel@nongnu.org>,
Jason Wang <jasowang@redhat.com>,
yvugenfi@redhat.com
Subject: Re: [Qemu-devel] Virtual IOMMU + Virtio-net devices in a Windows VM doesn't work
Date: Tue, 24 Jul 2018 14:57:08 +0300 [thread overview]
Message-ID: <20180724145603-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20180724055501.GA2479@xz-mi>
On Tue, Jul 24, 2018 at 01:55:01PM +0800, Peter Xu wrote:
> On Mon, Jul 23, 2018 at 04:13:18PM -0400, Jintack Lim wrote:
> > Hi,
> >
> > I'm running a Windows VM on top of KVM on x86, and one of virtio-net
> > device in the Windows VM doesn't seem to work. I provided virtual
> > IOMMU and two virtio-net devices to the VM: one bypassing the virtual
> > IOMMU and the other one behind the virtual IOMMU[1]. It turned out
> > that the virtio-net device behind virtual IOMMU didn't work while the
> > one bypassing the virtual IOMMU worked well. In a linux VM with the
> > same configuration, both of virtio-net device worked well.
> >
> > I found that there is a subtle difference between virtio-net devices
> > bypassing and behind virtual IOMMU in a Linux VM. The lscpu command in
> > the Linux VM shows different device names for them; the first line is
> > for the bypassing one, and the second line is for the one behind the
> > virtual IOMMU
> >
> > 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device
> > 01:00.0 Ethernet controller: Red Hat, Inc Device 1041 (rev 01)
> >
> > I wonder if this difference somehow caused the problem in the Windows
> > VM. I've installed the latest virtio drivers (0.1.149) from the fedora
> > project [2]
> >
> > Any thoughts?
> >
> > I'm using v4.15 Linux kernel as a host, and QEMU 2.11.0.
>
> Have you tried the latest QEMU?
>
> Also CC Jason and Michael.
I'm not sure windows virtio drivers support the virtual iommu option.
CC Yan to make sure.
> >
> > Thanks,
> > Jintack
> >
> > [1] https://wiki.qemu.org/Features/VT-d
> > [2] https://docs.fedoraproject.org/quick-docs/en-US/creating-windows-virtual-machines-using-virtio-drivers.html
> >
> >
>
> Regards,
>
> --
> Peter Xu
next prev parent reply other threads:[~2018-07-24 11:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 20:13 [Qemu-devel] Virtual IOMMU + Virtio-net devices in a Windows VM doesn't work Jintack Lim
2018-07-24 5:55 ` Peter Xu
2018-07-24 11:57 ` Michael S. Tsirkin [this message]
2018-07-26 2:53 ` Jintack Lim
2018-07-29 11:44 ` Yan Vugenfirer
2018-07-29 11:53 ` Jintack Lim
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=20180724145603-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=jintack@cs.columbia.edu \
--cc=peterx@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.