Bug 678731

Summary: Update qemu-kvm -device pci-assign,? properties
Product: Red Hat Enterprise Linux 6 Reporter: juzhang <juzhang>
Component: qemu-kvmAssignee: Gerd Hoffmann <kraxel>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 6.1CC: chayang, chrisw, kraxel, laine, michen, mkenneth, nachandr, tburke, virt-maint
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-0.12.1.2-2.206.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 15:44:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 580953    

Description juzhang 2011-02-19 06:55:58 UTC
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:

Comment 3 Gerd Hoffmann 2011-09-20 07:55:51 UTC
Patch posted.

Comment 4 Gerd Hoffmann 2011-09-20 09:05:27 UTC
*** Bug 738430 has been marked as a duplicate of this bug. ***

Comment 6 Laine Stump 2011-09-21 16:17:08 UTC
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)

Comment 8 Chris Wright 2011-09-21 17:42:19 UTC
(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?

Comment 9 Nandini Chandra 2011-09-21 18:08:10 UTC
Hi Chris,

(In reply to comment #8)

> Is there libvirt bz to use this info?

BZ 738388 is the libvirt BZ.

Comment 13 juzhang 2011-09-28 02:06:29 UTC
Verified this issue with qemu-kvm-0.12.1.2-2.193.el6.

#/usr/libexec/qemu-kvm -device pci-assign,\?
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

Comment 15 Gerd Hoffmann 2011-10-10 15:02:55 UTC
[ just clear needinfo from comment #6, comment #8 answers it ]

Comment 17 Eduardo Habkost 2011-10-28 18:01:34 UTC
Moving to ON_QA because Errata Tool did not do it

Comment 19 errata-xmlrpc 2011-12-06 15:44:34 UTC
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