qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "pbonzini@redhat.com" <pbonzini@redhat.com>,
	"Gaohaifeng (A)" <gaohaifeng.gao@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"Lilijun (Jerry)" <jerry.lilijun@huawei.com>
Subject: Re: [Qemu-devel] [Question] about vhost user Interface
Date: Thu, 26 Feb 2015 13:55:54 +0200	[thread overview]
Message-ID: <CADDJ2=PC8Az25mn_yTr_f43tUKEc6HiagAy06Yn4NJskzmdw8A@mail.gmail.com> (raw)
In-Reply-To: <20150226093625.GA24766@redhat.com>

On Thu, Feb 26, 2015 at 11:36 AM, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Thu, Feb 26, 2015 at 09:30:40AM +0000, Gaohaifeng (A) wrote:
> > Hi
> >
> >   I want to use pxe to install a guest os whose nic type is vhost user. However
> > pxe rom doesn’t support msi-x interrupt, so qemu won’t start vhost net.
> >
> > Call relationship:
> >
> > virtio_net_vhost_status-> vhost_net_query-> vhost_dev_query->
> > virtio_pci_query_guest_notifiers -> msix_enabled
> >
> >
> >
> > In my test, I remove the msix check for vhost user interface and successfully
> > install the guest os by pxe.
> >
> > Is it OK to do like this and will it cause other problems?
> >
> >
> >
> > Thanks.
> >
> > Haifeng Gao
> >
>
> I think we should fix it.
> As a quick hack, you should be able to just use vhostforce.


But isn't that what vhostforce is for, runnign vhost with non
MSI-enabled guests?

regards,
Nikolay Nikolaev

>
>
> --
> MST
>

  reply	other threads:[~2015-02-26 11:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-26  9:30 [Qemu-devel] [Question] about vhost user Interface Gaohaifeng (A)
2015-02-26  9:36 ` Michael S. Tsirkin
2015-02-26 11:55   ` Nikolay Nikolaev [this message]
2015-02-26 12:01     ` Michael S. Tsirkin
2015-02-27  8:47       ` gaohaifeng

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='CADDJ2=PC8Az25mn_yTr_f43tUKEc6HiagAy06Yn4NJskzmdw8A@mail.gmail.com' \
    --to=n.nikolaev@virtualopensystems.com \
    --cc=gaohaifeng.gao@huawei.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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).