From: "Michael S. Tsirkin" <mst@redhat.com>
To: Dhaval Giani <dhaval.lists@thegianis.in>
Cc: kvm@vger.kernel.org
Subject: Re: vhost, something changed between 2.6.35 and 2.6.36 ?
Date: Sun, 12 Sep 2010 16:40:57 +0200 [thread overview]
Message-ID: <20100912144057.GB25138@redhat.com> (raw)
In-Reply-To: <AANLkTimV=KOzWmmcDytNydWiTvRiotQg1ZBawX6UggNa@mail.gmail.com>
On Sun, Sep 12, 2010 at 04:39:29PM +0200, Dhaval Giani wrote:
> On Sun, Sep 12, 2010 at 2:05 PM, Michael S. Tsirkin <mst@redhat.com> wrote:
> > On Fri, Sep 10, 2010 at 03:37:36PM +0200, Dhaval Giani wrote:
> >> Hi,
> >>
> >> I have been trying to get vhost+macvtap to work for me. I run it as
> >>
> >> /root/qemu-kvm-vhost-net/bin/qemu-system-x86_64 -hda $IMAGE -serial
> >> stdio -monitor telnet::4444,server,nowait -vnc :4: -m 3G -net
> >> nic,model=virtio,macaddr=$MACADDR,netdev=macvtap0 -netdev
> >> tap,id=macvtap0,vhost=on,fd=3 3<> /dev/tap5
> >>
> >> in 2.6.35, which worked just fine. On the other hand, with 2.6.36, i
> >> don't have working networking. I am using the same image and same
> >> macaddress. The qemu is the version from
> >> git://git.kernel.org/pub/scm/linux/kernel/git/mst/qemu-kvm.git vhost .
> >
> > BTW, by now, all these patches are merged so upstream qemu-kvm should work
> > just fine for you as well.
> >
> >> Any suggestions will be welcome!
> >>
> >> Thanks,
> >> Dhaval
> >
> > You are running this as non-root user, correct?
>
> nope as root.
>
> > This could be the permission issue that got fixed
> > by 87d6a412bd1ed82c14cabd4b408003b23bbd2880.
> > Could you please check the latest master from Linus,
> > and let me and the list know? Thanks!
> >
>
> this is with git of friday evening CEST.
>
> > Another thing to try if this does *not* help:
> >
> > enable CONFIG_DYNAMIC_DEBUG in kernel,
> > rebuild the kernel,
> > mount debugfs:
> >
> > mount -t debugfs none /sys/kernel/debug
> >
> > and then enable debug for vhost_net as described in
> > Documentation/dynamic-debug-howto.txt:
> >
>
> I will give this a run on monday morning when i am at the lab again.
>
> > echo 'module vhost_net +p' > /sys/kernel/debug/dynamic_debug/control
> >
> > Then start qemu, and after running a test, run dmesg and see if there
> > are any messages from vhost_net. If yes please send them to
> > me and to the list.
> >
> > Thanks!
> >
>
>
> thanks!
> Dhaval
Another thing to try check is generic net core issues.
For this, try running tcpdump on both tap in host
and on virtio net device in guest. Then
send packets to host from guest and back, and check whether
they appears on virtio and on tap.
Thanks!
--
MST
next prev parent reply other threads:[~2010-09-12 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 13:37 vhost, something changed between 2.6.35 and 2.6.36 ? Dhaval Giani
2010-09-12 12:05 ` Michael S. Tsirkin
2010-09-12 14:39 ` Dhaval Giani
2010-09-12 14:40 ` Michael S. Tsirkin [this message]
2010-09-13 14:25 ` Dhaval Giani
2010-09-13 14:42 ` 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=20100912144057.GB25138@redhat.com \
--to=mst@redhat.com \
--cc=dhaval.lists@thegianis.in \
--cc=kvm@vger.kernel.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