Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When issue commands,/usr/libexec/qemu-kvm -device pci-assign,\?",we get the following messages.
pci-assign.host=pci-hostaddr
pci-assign.iommu=uint32
pci-assign.bootindex=int32
pci-assign.configfd=string
However,actually,we can also identify device bus number and address.for example,we can boot guest,with.
#--qemu-kvm .. -device pci-assign,host=09:10.2,id=zhang1,iommu=1,bus=pci.0,addr=0x6.
so we had better list all pci-assign's properties
Version-Release number of selected component (if applicable):
1.Qemu version
qemu-kvm-0.12.1.2-2.144.el6.x86_64
How reproducible:
Steps to Reproduce:
1./usr/libexec/qemu-kvm -device pci-assign,\?
2.
3.
Actual results:
pci-assign.host=pci-hostaddr
pci-assign.iommu=uint32
pci-assign.bootindex=int32
pci-assign.configfd=string
Expected results:
pci-assign.host=pci-hostaddr
pci-assign.iommu=uint32
pci-assign.bootindex=int32
pci-assign.configfd=string
pci-assign.addr=...
Additional info:
1) Is this the patch?
http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00588.html
(It would be helpful if a link to the appropriate patch was pasted into the BZ, and the patch comment contained a link back to the BZ record).
2) It's not immediately obvious to a qemu-outsider like me - will this patch result in "rombar=..." being printed in the properties? (See Bug 738095)
(In reply to comment #6)
> 1) Is this the patch?
>
>
> http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-September/msg00588.html
Yes
> (It would be helpful if a link to the appropriate patch was pasted into the BZ,
> and the patch comment contained a link back to the BZ record).
>
> 2) It's not immediately obvious to a qemu-outsider like me - will this patch
> result in "rombar=..." being printed in the properties? (See Bug 738095)
Yes, here's example output:
pci-assign.host=pci-hostaddr
pci-assign.iommu=uint32
pci-assign.bootindex=int32
pci-assign.configfd=string
pci-assign.addr=pci-devfn
pci-assign.romfile=string
pci-assign.rombar=uint32
pci-assign.multifunction=on/off
Is there libvirt bz to use this info?
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHSA-2011-1531.html