From: "Michael S. Tsirkin" <mst@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] vhost broken?
Date: Thu, 5 Jan 2012 17:00:47 +0200 [thread overview]
Message-ID: <20120105150047.GB2751@redhat.com> (raw)
In-Reply-To: <4F058686.2030805@redhat.com>
On Thu, Jan 05, 2012 at 01:16:22PM +0200, Avi Kivity wrote:
> On 01/05/2012 01:05 PM, Gerd Hoffmann wrote:
> > Hi,
> >
> > current master seems to corrupt guest memory, I get guest errors like
> > this one:
> >
> > swap_dup: Bad swap file entry 1999800080
> > BUG: Bad page map in process udevd pte:bec5f30054520100 pmd:1f6f4067
> > addr:00007fc464a02000 vm_flags:00100073 anon_vma:ffff88001f928ec0
> > mapping:(null) index:7fc464a02
> > Pid: 555, comm: udevd Not tainted 2.6.32-220.el6.x86_64 #1
> >
> > bisecting points to this commit:
> >
> > commit 04097f7c5957273c578f72b9bd603ba6b1d69e33
> > Author: Avi Kivity <avi@redhat.com>
> > Date: Sun Dec 18 14:06:05 2011 +0200
> >
> > vhost: convert to MemoryListener API
> >
>
> Very likely. Michael, can you help?
>
> I don't have a vhost setup, can you share your command line?
Just chmod /dev/vhost-net to allow access, then
add vhost=on to the tap device.
Example
-netdev
tap,id=foo,ifname=msttap0,script=/home/mst/ifup,downscript=no,vhost=on
-device virtio-net-pci,netdev=foo
> --
> error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-05 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 11:05 [Qemu-devel] vhost broken? Gerd Hoffmann
2012-01-05 11:16 ` Avi Kivity
2012-01-05 11:33 ` Gerd Hoffmann
2012-01-05 11:37 ` Daniel P. Berrange
2012-01-05 15:00 ` Michael S. Tsirkin [this message]
2012-01-20 22:13 ` Lutz Vieweg
2012-01-21 10:06 ` Michael Tokarev
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=20120105150047.GB2751@redhat.com \
--to=mst@redhat.com \
--cc=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).