From: Wei Liu <wei.liu2@citrix.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: Alon Levy <alevy@redhat.com>,
xen-devel <xen-devel@lists.xensource.com>,
Wei Liu <wei.liu2@citrix.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
spice-devel@lists.freedesktop.org
Subject: Re: [Qemu-devel] [Spice-devel] Vdagent not working on xen linux hvm DomUs
Date: Thu, 12 Dec 2013 15:23:01 +0000 [thread overview]
Message-ID: <20131212152301.GC21900@zion.uk.xensource.com> (raw)
In-Reply-To: <52A9B5BF.2040605@m2r.biz>
On Thu, Dec 12, 2013 at 02:10:23PM +0100, Fabio Fantoni wrote:
[...]
> I did some other tests, I narrowed down the commit range to the one between:
>
> commit c9fea5d701f8fd33f0843728ec264d95cee3ed37 Mon, 22 Jul 2013
> 15:14:18 (Merge remote-tracking branch 'bonzini/iommu-for-anthony')
> where there is virtio net regression with xen
>
> and
>
> commit 962b03fcf509db25c847aa67c4eff574c240dcfe Thu, 4 Jul 2013
> 15:42:43 +0000 (xen: Mark fixed platform I/O as unaligned)
> where virtio net is working
>
> I also tested:
> commit 2562becfc126ed7678c662ee23b7c1fe135d8966 Mon, 15 Jul 2013
> 19:02:41 +0000
> and
> commit dcb117bfda5af6f6ceb7231778d36d8bce4aee93 Thu, 4 Jul 2013
> 15:42:46 +0000
> but qemu crashes on xl create for another error and I haven't found
> which is the commit to apply with git cherry-pick so that I can
> check if the virtio net regression is present.
>
> Can someone help me please?
>
> I added also qemu-devel to cc.
>
I did a quick test with Xen's QEMU, currently at
commit 1c514a7734b7f98625a0d18d5e8ee7581f26e50c
Merge: 79c097d 35bdc13
Author: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Date: Tue Jun 25 11:34:24 2013 +0000
Merge remote branch 'perard/cpu-hotplug-port-v2' into xen-staging-master-7
from git://xenbits.xen.org/qemu-upstream-unstable.git
My guest is Squeeze with stock kernel 2.6.32.
vif=['model=virtio-net-pci,bridge=xenbr0']
No pci=nomsi in guest kernel command line.
Everything worked fine. And /proc/interrupts shows that it's indeed
using MSI for virtio PCI.
I'm kind of confused. (And in the long run of this thread I probably
didn't remember everything.)
Wei.
> Thanks for any reply.
next prev parent reply other threads:[~2013-12-12 15:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20131206131703.GC30613@zion.uk.xensource.com>
[not found] ` <52A1D676.70308@m2r.biz>
[not found] ` <20131206144030.GD30613@zion.uk.xensource.com>
[not found] ` <52A1E3FA.6090809@m2r.biz>
[not found] ` <20131206145546.GF30613@zion.uk.xensource.com>
[not found] ` <20131206153937.GB4419@zion.uk.xensource.com>
[not found] ` <52A7274A.90906@m2r.biz>
[not found] ` <52A86BA5.3040100@m2r.biz>
[not found] ` <20131211153841.GA17528@zion.uk.xensource.com>
[not found] ` <52A88EB9.8050708@m2r.biz>
[not found] ` <20131211165557.GA11063@zion.uk.xensource.com>
2013-12-12 13:10 ` [Qemu-devel] [Spice-devel] Vdagent not working on xen linux hvm DomUs Fabio Fantoni
2013-12-12 15:23 ` Wei Liu [this message]
2013-12-12 16:05 ` Fabio Fantoni
2013-12-13 9:51 ` Fabio Fantoni
2013-12-13 16:22 ` Wei Liu
2013-12-17 16:01 ` Fabio Fantoni
2013-12-17 16:18 ` Wei Liu
2014-03-10 12:32 ` Michael S. Tsirkin
2014-03-10 12:36 ` Wei Liu
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=20131212152301.GC21900@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=alevy@redhat.com \
--cc=fabio.fantoni@m2r.biz \
--cc=qemu-devel@nongnu.org \
--cc=spice-devel@lists.freedesktop.org \
--cc=xen-devel@lists.xensource.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 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).