All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm <kvm@vger.kernel.org>, "Hao\, Xudong" <xudong.hao@intel.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Subject: Re: -pcidevice broken - fix or remove it?
Date: Tue, 02 Nov 2010 14:19:24 +0100	[thread overview]
Message-ID: <m3vd4f278j.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <4CCD8CA3.8020807@web.de> (Jan Kiszka's message of "Sun, 31 Oct 2010 16:34:59 +0100")

Jan Kiszka <jan.kiszka@web.de> writes:

> Hi,
>
> looks like the documented way to configure device assignment at qemu-kvm
> level is broken in 0.13 and git head:
>
>   # qemu-system-x86_64 -pcidevice host=0:1a.0
>   qemu-system-x86_64: Parameter 'id' expects an identifier
>   Identifiers consist of letters, digits, '-', '.', '_', starting with a letter.
>   pcidevice argument parse error; please check the help text for usage
>
> "-device pci-assign" works, but only if specify "iommu=0" (otherwise: No
> IOMMU found.  Unable to assign device "(null)").
>
> Fix that legacy qemu-kvm switch or remove it at this chance? No one
> seems to have complained yet.
>
> Jan

Broken since June.  Xudong Hao (cc'ed) reported it then[1], and
Hidetoshi Seto (also cc'ed) attempted to get it patched [2,3].

Removing -pcidevice would be fine with me.  For what it's worth, it's
not in upstream qemu.


[1] http://lists.nongnu.org/archive/html/qemu-devel/2010-06/msg02858.html
[2] http://lists.nongnu.org/archive/html/qemu-devel/2010-06/msg03073.html
[3] http://lists.nongnu.org/archive/html/qemu-devel/2010-06/msg02858.html

  reply	other threads:[~2010-11-02 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-31 15:34 -pcidevice broken - fix or remove it? Jan Kiszka
2010-11-02 13:19 ` Markus Armbruster [this message]
2010-11-02 14:31   ` Jan Kiszka
2010-11-02 14:35     ` Daniel P. Berrange

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=m3vd4f278j.fsf@blackfin.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=xudong.hao@intel.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 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.