Bug 1076518

Summary:	sPAPR VLAN interfaces are accounted as PCI devices
Product:	[Retired] oVirt	Reporter:	Vitor de Lima <vitor.lima>
Component:	ovirt-engine-core	Assignee:	Vitor de Lima <vdelima>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.4	CC:	gklein, gustavo.pedrosa, iheim, leonardo.bianconi, michal.skrivanek, rbalakri, vdelima, vitor.lima, yeylon
Target Milestone:	---
Target Release:	3.5.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	ppc
Fixed In Version:	ovirt-3.5.1_rc1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-21 16:02:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vitor de Lima 2014-03-14 13:34:07 UTC

Description of problem:
The total sum of PCI devices present in a VM takes into account the number of sPAPR VLAN network interfaces, but this kind of device is not PCI.

Version-Release number of selected component (if applicable):
3.4rc2

How reproducible:
Always

Steps to Reproduce:
1. Create a VM in a Cluster with ppc64 hosts
2. Add multiple sPAPR VLAN interfaces until the maximum number of PCI devices is reached

Actual results:
The total number of sPAPR VLAN devices that can be inserted is much smaller than the what can be used in QEMU.

Expected results:
The user should be able to add a large amount of these interfaces into a VM.

Additional info:

Comment 1 Sandro Bonazzola 2014-05-08 13:55:09 UTC

This is an automated message.

oVirt 3.4.1 has been released.
This issue has been retargeted to 3.5.0 since it has not been marked as high priority or severity issue, please retarget if needed.

Comment 2 Sandro Bonazzola 2014-10-17 12:14:12 UTC

Moving pending bugs not fixed in 3.5.0 to 3.5.1.

Comment 3 Sandro Bonazzola 2015-01-15 14:14:38 UTC

This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA

Comment 4 Sandro Bonazzola 2015-01-21 16:02:11 UTC

oVirt 3.5.1 has been released. If problems still persist, please make note of it in this bug report.