From: Liang Chen <liang.chen@canonical.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [Bug 1546445] Re: support vhost user without specifying vhostforce
Date: Fri, 19 Feb 2016 12:16:31 -0000 [thread overview]
Message-ID: <20160219121631.24885.89879.malone@chaenomeles.canonical.com> (raw)
In-Reply-To: 20160217094237.24220.45325.malonedeb@chaenomeles.canonical.com
** Changed in: qemu
Status: New => In Progress
** Patch added: "debian patch for qemu 1:2.2+dfsg"
https://bugs.launchpad.net/qemu/+bug/1546445/+attachment/4575585/+files/1%3A2.2+dfsg-5expubuntu9.8-lp1546445.patch
** Tags added: patch
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1546445
Title:
support vhost user without specifying vhostforce
Status in QEMU:
In Progress
Bug description:
[Impact]
* vhost-user falls back to virtio-net which causes performance lose
without specifying the vhostforce option. But it should be the default
behavior for vhost-user, since guests using PMD doesn't support msi-x.
[Test Case]
create a vhost-user virtio backend without specifying the vhostforce option, i.e. -netdev type=vhost-user,id=mynet1,chardev=<char_dev_for_the_controll_channel>
start the VM
vhost-user is not enabled
[Regression Potential]
* none
vhost user nic doesn't support non msi guests(like pxe stage) by default.
Vhost user nic can't fall back to qemu like normal vhost net nic does. So we should
enable it for non msi guests.
The problem has been fix in qemu upstream -
http://git.qemu.org/?p=qemu.git;a=commitdiff;h=24f938a682d934b133863eb421aac33592f7a09e.
And the patch needs to be backported to 1:2.2+dfsg-5expubuntu9.8 .
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1546445/+subscriptions
next prev parent reply other threads:[~2016-02-19 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 9:42 [Qemu-devel] [Bug 1546445] [NEW] support vhost user without specifying vhostforce Liang Chen
2016-02-19 12:16 ` Liang Chen [this message]
2016-02-23 19:45 ` [Qemu-devel] [Bug 1546445] " Edward Hope-Morley
2016-02-23 19:47 ` Louis Bouchard
2016-02-23 20:30 ` Ubuntu Foundations Team Bug Bot
2016-02-23 20:33 ` Liang Chen
2016-02-23 20:34 ` Louis Bouchard
2016-02-23 20:37 ` Liang Chen
2016-02-24 0:05 ` Mathew Hodson
2016-02-26 4:47 ` Serge Hallyn
2016-03-15 9:50 ` Liang Chen
2016-03-15 9:56 ` Liang Chen
2016-03-18 16:26 ` Corey Bryant
2016-03-18 16:39 ` Corey Bryant
2016-03-18 17:05 ` Corey Bryant
2016-03-18 17:48 ` Corey Bryant
2016-03-19 9:08 ` James Page
2016-03-20 7:11 ` James Page
2016-03-21 10:13 ` [Qemu-devel] [Bug 1546445] Please test proposed package James Page
2016-03-23 8:07 ` [Qemu-devel] [Bug 1546445] Re: support vhost user without specifying vhostforce Liang Chen
2016-03-29 13:41 ` Ryan Beisner
2016-11-09 12:18 ` Louis Bouchard
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=20160219121631.24885.89879.malone@chaenomeles.canonical.com \
--to=liang.chen@canonical.com \
--cc=1546445@bugs.launchpad.net \
--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 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.