From: Jan Kiszka <jan.kiszka@siemens.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, "Hao\, Xudong" <xudong.hao@intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: -pcidevice broken - fix or remove it?
Date: Tue, 02 Nov 2010 15:31:31 +0100 [thread overview]
Message-ID: <4CD020C3.1030803@siemens.com> (raw)
In-Reply-To: <m3vd4f278j.fsf@blackfin.pond.sub.org>
Am 02.11.2010 14:19, Markus Armbruster wrote:
> 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.
>
Patch queued.
While at it, I wondered if we should kill "pci_add ... host" as well.
But it looks like libvirt uses it - and should stumble over this
breakage (it does not specify a device name). I can fix it by removing
the silly auto-naming, or can libvirt live without it?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-11-02 14:32 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
2010-11-02 14:31 ` Jan Kiszka [this message]
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=4CD020C3.1030803@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--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.