From: "Daniel P. Berrange" <berrange@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Markus Armbruster <armbru@redhat.com>, 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, 2 Nov 2010 14:35:20 +0000 [thread overview]
Message-ID: <20101102143520.GS23490@redhat.com> (raw)
In-Reply-To: <4CD020C3.1030803@siemens.com>
On Tue, Nov 02, 2010 at 03:31:31PM +0100, Jan Kiszka wrote:
> 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?
As of libvirt >= 0.8.1 & QEMU >= 0.12.x we use switched to using -device
for everything. Older libvirt versions had rather broken checking for
PCI device topology, so I think it is fine to require libvirt >= 0.8.1
for latest QEMU releases if users want PCI dev assignment. Thus -pcidevice
and pci_add can both be killed from our POV.
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2010-11-02 14:35 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
2010-11-02 14:35 ` Daniel P. Berrange [this message]
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=20101102143520.GS23490@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.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.